Date: Sat, 4 Jun 2016 13:50:46 -0600 From: Alan Somers <asomers@freebsd.org> To: Don Lewis <truckman@freebsd.org> Cc: FreeBSD CURRENT <freebsd-current@freebsd.org>, freebsd-emulation@freebsd.org Subject: Re: VirtualBox network connectivity broken on recent -CURRENT Message-ID: <CAOtMX2hX3sLuubASTuq2bbyNn3wrM=j6p4nfr0gebLpn3_mcdw@mail.gmail.com> In-Reply-To: <201606040043.u540hOVq045060@gw.catspoiler.org> References: <201606040011.u540BODD045000@gw.catspoiler.org> <201606040043.u540hOVq045060@gw.catspoiler.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Jun 3, 2016 at 6:43 PM, Don Lewis <truckman@freebsd.org> wrote: > On 3 Jun, Don Lewis wrote: >> It looks like something changed in -CURRENT to break network >> connectivity to VirtualBox guests. This was last known to work with >> r299139 (May 6th) and is definitely broken with r301229. The VirtualBox >> port revisions are: >> virtualbox-ose-4.3.38_1 >> virtualbox-ose-kmod-4.3.38 >> It looks like there was one change to the VirtualBox on May 9th, but it >> looks unlikely to be the cause of the problem. >> >> The network settings are: >> Attached to: Bridged Adapter >> Name: re0 >> Adapter Type: Paravirtualized Network (virtio-net) >> Promiscuous Mode: Deny >> MAC Address: [snip] >> Ifconfig says that the interface is up, but I am unable to ping either >> the host or anything else on the LAN from the guest. It looks like the >> problem is with outbound traffic. If I attempt to ping the guest, the >> source IP address and MAC address show up in the guest's arp table, but >> ping reports: >> ping: sendto: Host is down >> That makes me think that the arp responses from the guest are not >> getting transmitted. None of the machines involved are running >> firewalls. If I ping from the guest, I don't see any arp requests on >> the wire and the arp command shows the table entry as incomplete. >> >> The problem shows up with both FreeBSD -CURRENT and Debian guests. > > I see the same behaviour if I set: > Attached to: NAT > or > Adapter Type: 82540EM > Might be related to this routing bug: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207831
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAOtMX2hX3sLuubASTuq2bbyNn3wrM=j6p4nfr0gebLpn3_mcdw>