I can now reproduce the behavior on demand. I'll try to explain my setup:
A: Router. B: KVM guest on a Maverick Host. C: Other Host. A, B and C are all in the same subnet. I boot B and ssh from outside to B. While in B I ping C. C initially doesn't respond and the arp cache shows C as failed. After a while C suddenly starts responding and the arp cache reflects C as reachable. Deleting the entry from the arp cache and it starts over with the random delay before responding. Now, dumping arp traffic on the host bridge and on the vnet0 if also on the host side while running the scenario above shows who-has requests coming through nicely. But the is-at replies for C only appears on the host bridge for some time. It doesn't make it to vnet0. After anything from 10 to 60 seconds a couple of the is-at replies makes it through and the pings start getting sent and replied. Here's the odd part. IF there's no other traffic from B (ie. ssh output) while B is sending who-has requests for C, the ssh connection severely lags. Getting a CTRL-C through takes quite some time. Usually the lag lasts until B finally gets the is-at reply or gives up trying. But if there's a lot of output from pings and a top running in another connection, the lag is nearly unnoticable. -- Bridged Guests losing network connectivity https://bugs.launchpad.net/bugs/633392 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
