Re: Machine cannot respond to NAT
- From: linuxnewbie1234 <linuxnewbie1234@xxxxxxxxxxx>
- Date: Thu, 26 Jul 2007 17:40:03 +0200
Joern Bredereck wrote:
linuxnewbie1234 <linuxnewbie1234@xxxxxxxxxxx> wrote:
sounds like an poisoned arp cache to me.
I have just realized/remembered that machine 47 has a software bridge in it between a virtual network (qemu virtual machine) and eth0. This is a complicated setup and it might have been screwed because of some kind of bug in linux networking.
Have you ever seen a bug in Linux 2.6 networking (maybe on simpler setups than this) so that the network would hang up until ifdown-ifup, or is it really totally reliable?
I would exclude a malicious arp poisoning in our environment. Also this does not explain why after the reboot the poisoning stopped (remember that the poisoning is to be actively maintained or will expire from the cache)
Thanks
.
- References:
- Machine cannot respond to NAT
- From: linuxnewbie1234
- Re: Machine cannot respond to NAT
- From: Joern Bredereck
- Machine cannot respond to NAT
- Prev by Date: Threaded Server Load Capacity
- Next by Date: ssh question
- Previous by thread: Re: Machine cannot respond to NAT
- Next by thread: Help on Ciprico NAS
- Index(es):