From owner-freebsd-emulation@freebsd.org  Sun Jun  5 00:50:31 2016
Return-Path: <owner-freebsd-emulation@freebsd.org>
Delivered-To: freebsd-emulation@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 10021B4EC88;
 Sun,  5 Jun 2016 00:50:31 +0000 (UTC)
 (envelope-from truckman@FreeBSD.org)
Received: from gw.catspoiler.org (unknown [IPv6:2602:304:b010:ef20::f2])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "gw.catspoiler.org", Issuer "gw.catspoiler.org" (not verified))
 by mx1.freebsd.org (Postfix) with ESMTPS id D2CC319C7;
 Sun,  5 Jun 2016 00:50:30 +0000 (UTC)
 (envelope-from truckman@FreeBSD.org)
Received: from FreeBSD.org (mousie.catspoiler.org [192.168.101.2])
 by gw.catspoiler.org (8.15.2/8.15.2) with ESMTP id u550oLRd049134;
 Sat, 4 Jun 2016 17:50:25 -0700 (PDT)
 (envelope-from truckman@FreeBSD.org)
Message-Id: <201606050050.u550oLRd049134@gw.catspoiler.org>
Date: Sat, 4 Jun 2016 17:50:21 -0700 (PDT)
From: Don Lewis <truckman@FreeBSD.org>
Subject: Re: VirtualBox network connectivity broken on recent -CURRENT
To: asomers@freebsd.org
cc: freebsd-current@freebsd.org, freebsd-emulation@freebsd.org
In-Reply-To: <CAOtMX2hX3sLuubASTuq2bbyNn3wrM=j6p4nfr0gebLpn3_mcdw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
X-BeenThere: freebsd-emulation@freebsd.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Development of Emulators of other operating systems
 <freebsd-emulation.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-emulation>, 
 <mailto:freebsd-emulation-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-emulation/>
List-Post: <mailto:freebsd-emulation@freebsd.org>
List-Help: <mailto:freebsd-emulation-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-emulation>, 
 <mailto:freebsd-emulation-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 05 Jun 2016 00:50:31 -0000

On  4 Jun, Alan Somers wrote:
> 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

Doesn't look like it.  The questionable commit there seems to be
r293159.  I didn't see breakage until after r299139.