Sponsored Content
Full Discussion: routing problem/question
Special Forums IP Networking routing problem/question Post 302577357 by hopfensp on Monday 28th of November 2011 11:29:01 PM
Old 11-29-2011
routing problem/question

Internet Gateway
192.168.0.201

Server 1
192.168.0.101
192.168.1.101
192.168.2.101
gateway: 192.168.0.201
VIP: 192.168.1.100
VIP: 192.168.2.100

Server 2
192.168.0.102
192.168.1.102
192.168.2.102
gateway: 192.168.0.201

Client 1
192.168.2.201
gateway: 192.168.2.100

From Client 1, I can ping 192.168.2.102 (Server 2), this would make sense all three computers are on the same network. However, from client 1, I cannot ping or ssh to 192.168.1.102 (server 2). Why? I don't know. Using wireshark, I can see the ICMP echo request go through server 1 and pass to server 2. This path makes sense. I see the echo request being recieved on the 192.168.2.102 NIC on Server 2. But no response is sent out on either NIC on Server 2. Why?

I have made no routing table modification on either server. I have IP forwarding set in sysctl.conf on both servers. I have iptables turned off. The only way I can ping from client 1 to 192.168.1.102 (server 2) is enabling masquerading in iptables on both servers on all interfaces. The question is: why can't client 1 ping to 192.168.1.102 with no modifications to any routing table and with the iptables service stopped?
 

10 More Discussions You Might Find Interesting

1. IP Networking

Routing problem

Hi I know this problem is more likely some windows problem but it has also something to do with unix. We have a windows nt environment wich uses AIX (unix) machines as file servers (samba). In our windows network environment we nicely see al the unix file servers via the 10 MB network. Last... (2 Replies)
Discussion started by: Mark Detrez
2 Replies

2. IP Networking

routing problem

following Problem. I configured my SuSE Linux 8.0 as a router. I4l, named, ip_forward, iptables (NAT/MASQUERADING) are running or are aktivatet. I just can get a internet connection about the proxy server squid, but if i want to use other protocols i need functional routing. (I had this... (1 Reply)
Discussion started by: razor
1 Replies

3. IP Networking

Routing Problem

I have a question concerning networking. Could any forum members explain to me why I might be getting "no route to host" messages when I try to connect through ftp and http protocols? I have went to my etc/hosts file and everything seems to be configured properly. I can connect within my... (1 Reply)
Discussion started by: cstovall
1 Replies

4. IP Networking

HPUX Routing Question

We have an HPUX machine that is having a routing problem. Any traffic sent on the local network (same switch) works fine. However, when we try to send traffic to any other ip the machine NAT's the ip to that of the gatway and nothing goes any further. For example if I try to ping 10.1.1.1 from... (3 Replies)
Discussion started by: robanic
3 Replies

5. IP Networking

routing problem in solaris

hi, below is the situation: my server is in 128.10.200.xxx network. i have a solaris computer running in a subnet. this computer got 2 nic card. 1 is 172.18.198.xxx , another 1 is 10.100.xxx.11 there is a machine stick with this computer, ip is 10.100.xxx.12 so, 10.100.xxx.11 and... (3 Replies)
Discussion started by: kyhah
3 Replies

6. Solaris

Routing problem of Solaris

Hi, I got problem of Sun Solaris 8 routing. IP of SunA is 10.16.64.164, and have routing table: 10.16.64.0 10.16.64.164 U 1 19236 bge1 10.6.0.0 10.6.0.3 U 1 16534 bge0 224.0.0.0 10.6.0.3 U 1 ... (4 Replies)
Discussion started by: milo
4 Replies

7. Red Hat

routing table question

I have below routing table in linux kernel 2.6.9 # netstat -rn Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 10.155.24.0 0.0.0.0 255.255.252.0 U 0 0 0 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U ... (5 Replies)
Discussion started by: chuikingman
5 Replies

8. Red Hat

routing problem...im missing something

hi, having an issue on a class C network with trying to get a redhat diskless setup going. I am using oracle enterprise 5, which is RHEL 5.3 i believe. here is the scenario: sun sparc m4k that i am planning on making the red hat boxes boot off after i get the network issue fixed. ... (3 Replies)
Discussion started by: caddyjoe77
3 Replies

9. AIX

Aix Routing Problem

I need the following solution , please help me... Current situation ip: 192.168.0.12 persistent and 192.168.254.12 service ip gateway: 192.168.0.254 subnet: 255.255.255.0 i have added a new ip on a new nic ip: 10.10.255.40 gateway: 10.10.255.62 subnet: 255.255.255.224 ... (1 Reply)
Discussion started by: rajibimran
1 Replies

10. Solaris

Routing problem

Hi, I have two physical interfaces on a servers. We have connected them to differerent subnets. 1) First interface: 10.158.49.87 to newtwork 10.158.49.0, its gateway is 10.158.49.1 (It is added as default gateway) It is existing set up. It works well 2) Second interface: ... (1 Reply)
Discussion started by: sri243
1 Replies
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
All times are GMT -4. The time now is 08:44 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy