Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
is this the way to show the output? does ip6tables make any difference coz working machines have both iptables and ip6tables enabled in services while this prolematic one has just iptables. plz note hardware/software details if needed Gateway/Server(multipurpose server,(storage server,nfs,samba)
HP Proliant DL380, Generation 5, Enhanced
2xDual Core Intel Xeon, 3.0 Ghz each, L2 Cache=4MB/dual core processor, FSB=1333 MHz
4GB DDR2, 667 Mhz, HP brand
Running RHEL 4.4 and VMWare Server 1.0.3 Master Node
Clients(all wtih same config)
Intel Core 2 Duo 6600, 2.4 Ghz, L2 Cach=4MB, FSB=1066 MHz
Water cooled Gigbyte motherboard, PXE boot capable, built in RAID Controller
4GB DDR2, 800 Mhz
Running RHEL 4.4 and VMWare Server 1.0.3 Client Nodes(the problematic one doesn't have VMWare Server 1.0.3)
Last edited by farooqnasim; 08-12-2009 at 03:29 AM.
OK, so the arp reply from the gateway just never gets back inside the original machine. Odd. What does the switching setup look like here? It's possible that if you have slightly cranky switches they might refuse to play ball with their FDB tables or something, certainly getting odd now. I'd be intested to know if the arp reply is seen on the wire, but as the reply is unicast you couldn't just sniff it from a third box, so let's leave that for now.
What I would also query is the .2.11 IP. Why is that appearing on the same network interface? Could well be something of interest there.
Finally, let's try bypassing arp and see if it pings once you have a static arp entry in your machine... run "arp -s 192.168.1.254 00:1a:4b:b0:54:68" and try pinging once more. With tcpdumps again if it doesn't work.
192.168.2.11 could be virtual computer's node IP on the same interface.i have found a document regarding current network which i am attaching as an image. it might elaborate 192.168.2.11 more. i tried "arp -s" and after that when i ping 254, it didn't give me any answer for aournd 20 minutes and i had to press ctl+c to quit. i configured eth0 instead of eth1 but again i can't ping to 254 and still can ping to 2 and others
Hmm, with VMware in the equation as well it seems, that's getting pretty messy, and without the base network infrastructure being consistent and reliable, I wouldn't really want to speculate what else is going on there.
Try filling the ARP cache (/etc/ethers) with MAC IP pairs on 192.168.1.5(problematic machine) then 'arp -f /etc/ethers' to see if that works?
Lines have one MAC and IP per line, values are space separated and look like:
Personally from what I can see, your layer 2 networking is most likely to be the issue, you clearly have issues with subnets getting mixed up that .2.11 IP intruding in .1.0/24 so as I can't have any real confidence in the switching, the only advice I can give from here is to fix your switching.