[SOLVED] Can ping onboard NIC but not PCI

Mitch Gaylord · 11-02-2009, 10:17 PM

The solution was in the setup of the gateways of server three. I had each of the subnets reply on
192.168.1.2 eth1. This doesn't work for the subnets that are comming off the NIC. The solution was to have the table read:

Server3:

Code:

# route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
192.168.5.0     *               255.255.255.0   U     0      0        0 eth5
192.168.4.0     192.168.5.2     255.255.255.0   UG    0      0        0 eth1
192.168.3.0     *               255.255.255.0   U     0      0        0 eth3
192.168.2.0     192.168.3.2     255.255.255.0   UG    0      0        0 eth1
192.168.1.0     *               255.255.255.0   U     0      0        0 eth1
192.168.0.0     192.168.1.2     255.255.255.0   UG    0      0        0 eth1
WAN             *               255.255.248.0   U     0      0        0 eth0
default         ISP_PROVIDED    0.0.0.0         UG    100    0        0 eth0

Quote:

I have a set up of three identical servers. They all have a dual gigabit onboard network adapter (eth0, eth1) and an Intel PRO 1000VT Quad Port 1GbE NIC (eth2, eth3, eth4, eth5). I have them connected to each other as follows:

Code:

Server1            Server2            Server3
eth0 ------------- eth0
eth2 ------------- eth2
eth4 ------------- eth4
                   eth1 ------------- eth1
                   eth3 ------------- eth3
                   eth5 ------------- eth5

I then configured the IPs as follows:

Code:

Server1            Server2            Server3
192.168.0.1 ------ 192.168.0.2
192.168.2.1 ------ 192.168.2.2
192.168.4.1 ------ 192.168.4.2
                   192.168.1.2 ------ 192.168.1.3
                   192.168.3.2 ------ 192.168.3.3
                   192.168.5.2 ------ 192.168.5.3

I set up routing on Server1 (eth1 is set to a utility server for remote connection):

Code:

# route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
192.168.4.0     *               255.255.255.0   U     0      0        0 eth4
192.168.2.0     *               255.255.255.0   U     0      0        0 eth2
192.168.0.0     *               255.255.255.0   U     0      0        0 eth0
192.168.254.0   *               255.255.255.0   U     0      0        0 eth1
default         192.168.0.2     0.0.0.0         UG    100    0        0 eth0

Server2:

Code:

# route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
192.168.5.0     *               255.255.255.0   U     0      0        0 eth5
192.168.4.0     *               255.255.255.0   U     0      0        0 eth4
192.168.3.0     *               255.255.255.0   U     0      0        0 eth3
192.168.2.0     *               255.255.255.0   U     0      0        0 eth2
192.168.1.0     *               255.255.255.0   U     0      0        0 eth1
192.168.0.0     *               255.255.255.0   U     0      0        0 eth0

Server3:

Code:

# route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
192.168.5.0     *               255.255.255.0   U     0      0        0 eth5
192.168.4.0     192.168.1.2     255.255.255.0   UG    0      0        0 eth1
192.168.3.0     *               255.255.255.0   U     0      0        0 eth3
192.168.2.0     192.168.1.2     255.255.255.0   UG    0      0        0 eth1
192.168.1.0     *               255.255.255.0   U     0      0        0 eth1
192.168.0.0     192.168.1.2     255.255.255.0   UG    0      0        0 eth1
WAN             *               255.255.248.0   U     0      0        0 eth0
default         ISP_PROVIDED    0.0.0.0         UG    100    0        0 eth0

I have forwarding on

Code:

echo 1 > /proc/sys/net/ipv4/ip_forward

Now my problem is, from Server1 i can ping 192.168.1.3, but not 192.168.3.3 or 192.168.5.3. Similarly, from Server3 i can ping 192.168.0.1, but not 192.168.2.1 or 192.168.4.1. Finally, from Server2 i can ping all of them.

Any ideas?

tredegar · 11-03-2009, 03:57 PM

Well, if you have solved your problem, please make time time to post your solution, that way, others can learn from your efforts.

Welcome to LQ!

[Off-topic: Now off the zero-replies list]