I have NCR MP-RAS unix. I have been trying for several months to get our network working since we had never used it before. I have setup all routes that I can think of. I know it has something to do with the routing table, because out of sheer luck I was able to get it working, and than like a good ol computer it decided to restart and I lost my changes. Unfortunately I do not know what I changed/added to make it work. Any help would be greatly appreciated. Below is all the information I think you need. Tanks in advance.
Last edited by Scott; 01-04-2013 at 02:34 PM..
Reason: Code tags
We are unable to bring one of our linux boxes into the network once it was restarted. But once we stop and start the network service. We are able to ping the gateway and get into network. After a minute or two we get the following reponse for the ping command
64 bytes from 124.168.215.40:... (6 Replies)
Hello this is my first post at this forum.
Apologize for my lack of network understanding
but Im posting to learn.
I have a problem reaching default gateway 10.18.110.1
If I use my laptop I can ping 10.18.110.1 but with our red hat multihomed server the gateway does not respond to ping.
cat... (11 Replies)
I was install new solaris10 on m4000 model after that i "ping -s" to default gateway but it's take longtime (2 Min) to reply and if i use "ping" only it's reply to fase(2 sec). any body who can tell me about my problem and how to fix it please. i'm try to fix several days. (2 Replies)
Hello,
I am new to Unix :D and have been trying to configure an AIX server running 5.3. I used smitty or smit to configure interface 0 on the server. I am able to ping the IP I set, however I am still unable to ping the gateway. I configured the IP by navigating to Communications Applications... (6 Replies)
I know the subject line is very similar to: destination host unreachable
but the problem with my machine appears to be somewhat different from that thread. apologies if I missed something from there.
We recently moved a machine physically and from one subnet to another . I used... (1 Reply)
I just reinstalled a fresh install of 5300 07 on an old 44p model 170, after installing I set an IP Address on en2 and I tried to the ping default gateway, no response. I tried a
startsrc -g tcpip
... and then I can ping the default gateway. I broke the ping and tried again to ping. I cannot... (1 Reply)
Hi,
Here is the issue: There are 2 identical systems in the same subnet here. They can ping and ssh each other. One can ping the default gateway and one can not with error '... icmp_seq Destination Host Unreachable'. I can't find any difference between the two systems in terms of network... (4 Replies)
Hi,
I installed AIX 7.1 on a blade though (hmc with vio). I can ping the IP address, but not the gateway. Is there anything that I should configure?
Is there anything that I have to check with vio setting or Am I missing any configuration?
Please let me know further.
Thank you (5 Replies)
I have setup a Linux machine on my server but for some reason Im unable to reach my default gateway. This is causing me to not communicate with the outside world (unable to connect to CentOS repos)
# ifconfig
enp0s3: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet... (3 Replies)
Dear friends
I use RedHat 6.5, which sets the gateway in the configuration file / etc / sysconfig / network as GATEWAY = 192.168.1.26, and the gateway in the configuration file / etc / sysconfig / network-scripts / ifcfg-eth11 as GATEWAY = 192.168.1.256. The two gateways are different.... (6 Replies)
Discussion started by: tanpeng
6 Replies
LEARN ABOUT FREEBSD
if_gre
GRE(4) BSD Kernel Interfaces Manual GRE(4)NAME
gre -- encapsulating network device
SYNOPSIS
To compile the driver into the kernel, place the following line in the kernel configuration file:
device gre
Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5):
if_gre_load="YES"
DESCRIPTION
The gre network interface pseudo device encapsulates datagrams into IP. These encapsulated datagrams are routed to a destination host, where
they are decapsulated and further routed to their final destination. The ``tunnel'' appears to the inner datagrams as one hop.
gre interfaces are dynamically created and destroyed with the ifconfig(8) create and destroy subcommands.
This driver corresponds to RFC 2784. Encapsulated datagrams are prepended an outer datagram and a GRE header. The GRE header specifies the
type of the encapsulated datagram and thus allows for tunneling other protocols than IP. GRE mode is also the default tunnel mode on Cisco
routers. gre also supports Cisco WCCP protocol, both version 1 and version 2.
The gre interfaces support a number of additional parameters to the ifconfig(8):
grekey Set the GRE key used for outgoing packets. A value of 0 disables the key option.
enable_csum Enables checksum calculation for outgoing packets.
enable_seq Enables use of sequence number field in the GRE header for outgoing packets.
EXAMPLES
192.168.1.* --- Router A -------tunnel-------- Router B --- 192.168.2.*
/
/
+------ the Internet ------+
Assuming router A has the (external) IP address A and the internal address 192.168.1.1, while router B has external address B and internal
address 192.168.2.1, the following commands will configure the tunnel:
On router A:
ifconfig greN create
ifconfig greN inet 192.168.1.1 192.168.2.1
ifconfig greN inet tunnel A B
route add -net 192.168.2 -netmask 255.255.255.0 192.168.2.1
On router B:
ifconfig greN create
ifconfig greN inet 192.168.2.1 192.168.1.1
ifconfig greN inet tunnel B A
route add -net 192.168.1 -netmask 255.255.255.0 192.168.1.1
NOTES
The MTU of gre interfaces is set to 1476 by default, to match the value used by Cisco routers. This may not be an optimal value, depending
on the link between the two tunnel endpoints. It can be adjusted via ifconfig(8).
For correct operation, the gre device needs a route to the decapsulating host that does not run over the tunnel, as this would be a loop.
The kernel must be set to forward datagrams by setting the net.inet.ip.forwarding sysctl(8) variable to non-zero.
SEE ALSO gif(4), inet(4), ip(4), me(4), netintro(4), protocols(5), ifconfig(8), sysctl(8)
A description of GRE encapsulation can be found in RFC 2784 and RFC 2890.
AUTHORS
Andrey V. Elsukov <ae@FreeBSD.org>
Heiko W.Rupp <hwr@pilhuhn.de>
BUGS
The current implementation uses the key only for outgoing packets. Incoming packets with a different key or without a key will be treated as
if they would belong to this interface.
The sequence number field also used only for outgoing packets.
BSD November 7, 2014 BSD