I'm having some problems with my network. Here's the backgrund: We originally had a single 192.168.2.X subnet and they used a Linux server (Red Hat EL 4 x64) as their router for the Internet. The router had a NIC eth0 for the WAN/Internet and eth1 for the LAN (192.168.2.1). I was having issues with my backups on that server in that the backup server would lose its connection to the router for a few seconds and then it'd come back. To remedy this (hopefully) I added a separate network strictly for backups. All of our servers have a second NIC so I created a second network and added all of the servers to it, including the router. The subnet is 192.168.1.X. I used the same subnet mask of 255.255.255.0 and left the gateway entry blank. All of the servers can communicate with each other just fine, except the Linux router. The problem is that communication with the Linux router isn't working properly. I cannot ping the router from the other servers, but I CAN ping the other servers from the router; however I receive a message in every ping reply that says "wrong data byte #XX should be 0xXZ but was 0xXY". What's even more strange is that I can ping the router's SAN NIC (192.168.1.1) from my workstation which is on the main subnet just fine, as well as the other servers on the SAN. I've done some searching on the net and most people say that the common cause of something like this is a firewall. The router is running iptables for its firewall and for NAT. I've added entries to permit all internal traffic and checked the log (it displays a message in syslog when it rejects a packet) but it's not rejecting the traffic. None of the other servers are running a firewall. Here's the routing table from one of the Windows servers: IPv4 Route Table =========================================================================== Interface List 0x1 ........................... MS TCP Loopback interface 0x10003 ...00 13 72 53 09 02 ...... Intel(R) PRO/1000 MT Network Connection #2 0x10004 ...00 13 72 53 09 01 ...... Intel(R) PRO/1000 MT Network Connection =========================================================================== =========================================================================== Active Routes: Network Destination Netmask Gateway Interface Metric 0.0.0.0 0.0.0.0 192.168.2.1 192.168.2.11 10 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1 192.168.1.0 255.255.255.0 192.168.1.11 192.168.1.11 10 192.168.1.11 255.255.255.255 127.0.0.1 127.0.0.1 10 192.168.1.255 255.255.255.255 192.168.1.11 192.168.1.11 10 192.168.2.0 255.255.255.0 192.168.2.11 192.168.2.11 10 192.168.2.11 255.255.255.255 127.0.0.1 127.0.0.1 10 192.168.2.255 255.255.255.255 192.168.2.11 192.168.2.11 10 224.0.0.0 240.0.0.0 192.168.1.11 192.168.1.11 10 224.0.0.0 240.0.0.0 192.168.2.11 192.168.2.11 10 255.255.255.255 255.255.255.255 192.168.1.11 192.168.1.11 1 255.255.255.255 255.255.255.255 192.168.2.11 192.168.2.11 1 Default Gateway: 192.168.2.1 =========================================================================== Persistent Routes: None And here's the routing table from the router: Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 66.241.66.224 * 255.255.255.240 U 0 0 0 eth0 192.168.2.0 * 255.255.255.0 U 0 0 0 eth1 192.168.1.0 * 255.255.255.0 U 0 0 0 eth2 169.254.0.0 * 255.255.0.0 U 0 0 0 eth2 default 66.241.66.225 0.0.0.0 UG 0 0 0 eth0 If anyone has any ideas or suggestions, I'd greatly appreciate some help. If desired I can post the iptables script. I'm pretty much at a loss at this point. All I can think of is that maybe there's something wrong with the NIC... but that doesn't really make sense since I can ping it just fine from this workstation. Thanks in advance, Jacob. - To unsubscribe from this list: send the line "unsubscribe linux-net" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
