Comment 23 for bug 584048

Quoting Andrew Klettke (<email address hidden>):
> General instability exists with this bug as well. For example, SSHing to
> the VM:
>
> $ ssh root@192.168.8.166
> root@192.168.8.166's password:
> Linux deb64 2.6.26-2-amd64 #1 SMP Sun Jun 20 20:16:30 UTC 2010 x86_64
>
> The programs included with the Debian GNU/Linux system are free software;
> the exact distribution terms for each program are described in the
> individual files in /usr/share/doc/*/copyright.
>
> Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
> permitted by applicable law.
> Last login: Thu Jul 22 15:57:28 2010 from 192.168.8.1
> deb64:~#
>
> ///////////////////////////////////////////////////////////////////////////////////////
> After waiting a few minutes, and pressing "Enter"...
> ////////////////////////////////////////////////////////////////////////////////////
>
> deb64:~# Write failed: Broken pipe
>
> ///////////////////////////////////////////////////////////////////////////////////////
> Then, trying to re-SSH into the server...
> ////////////////////////////////////////////////////////////////////////////////////

So now is this going through the firewall?

> $ ssh root@192.168.8.166
> root@192.168.8.166's password:
> Read from socket failed: Connection reset by peer
> $ ssh root@192.168.8.166
> ssh: connect to host 192.168.8.166 port 22: Connection refused
>
>
> This is when the ARP entry changes on the firewall I'm SSHing from, and the
> bridge connectivity freezes, and I have to restart the VM.

What kind of firewall? Do other hosts inside the firewall have the
right ARP entry for the guest? What about the host itself?

Note that this sounds like a different problem from what others are
reporting. Others are saying that their bridge hangs when new devices
are added or removed.