From owner-freebsd-current@freebsd.org  Fri Aug 11 05:48:52 2017
Return-Path: <owner-freebsd-current@freebsd.org>
Delivered-To: freebsd-current@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 2A991DC375A
 for <freebsd-current@mailman.ysv.freebsd.org>;
 Fri, 11 Aug 2017 05:48:52 +0000 (UTC)
 (envelope-from jkim@FreeBSD.org)
Received: from freefall.freebsd.org (freefall.freebsd.org
 [IPv6:2610:1c1:1:6074::16:84])
 by mx1.freebsd.org (Postfix) with ESMTP id 3E00123F7;
 Fri, 11 Aug 2017 05:48:49 +0000 (UTC)
 (envelope-from jkim@FreeBSD.org)
Subject: Re: r322076 breaks vtnet connectivity
To: Ian FREISLICH <ian.freislich@capeaugusta.com>,
 FreeBSD Current <freebsd-current@freebsd.org>
References: <cb77cdde-7cff-b656-a2f1-2139b0d9c5ec@capeaugusta.com>
From: Jung-uk Kim <jkim@FreeBSD.org>
Message-ID: <c11342b2-71c6-12e8-36d1-ead3dee694ae@FreeBSD.org>
Date: Fri, 11 Aug 2017 01:48:35 -0400
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101
 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <cb77cdde-7cff-b656-a2f1-2139b0d9c5ec@capeaugusta.com>
Content-Type: multipart/signed; micalg=pgp-sha256;
 protocol="application/pgp-signature";
 boundary="m5wuLCD9Q0X6WH9PRLEKHhv6qjN2PDRcl"
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Aug 2017 05:48:52 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--m5wuLCD9Q0X6WH9PRLEKHhv6qjN2PDRcl
Content-Type: multipart/mixed; boundary="NhHmoGf95HTmxjhXaERvuIcdmbO4GPJbO";
 protected-headers="v1"
From: Jung-uk Kim <jkim@FreeBSD.org>
To: Ian FREISLICH <ian.freislich@capeaugusta.com>,
 FreeBSD Current <freebsd-current@freebsd.org>
Message-ID: <c11342b2-71c6-12e8-36d1-ead3dee694ae@FreeBSD.org>
Subject: Re: r322076 breaks vtnet connectivity
References: <cb77cdde-7cff-b656-a2f1-2139b0d9c5ec@capeaugusta.com>
In-Reply-To: <cb77cdde-7cff-b656-a2f1-2139b0d9c5ec@capeaugusta.com>

--NhHmoGf95HTmxjhXaERvuIcdmbO4GPJbO
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable

On 08/10/2017 21:27, Ian FREISLICH wrote:
> I have a host on Digital Ocean (qemu) and the change in r322076 breaks
> my vtnet0 interface.  The interface still comes up but does not pass
> traffic any more.  It's not obvious to my why the changes from r322075
> to r322076 affect the vtnet interface.

Can you please try r322323 or later?  Basically, r322076 was incomplete
and r322323 corrected the stupid mistake.

Jung-uk Kim


--NhHmoGf95HTmxjhXaERvuIcdmbO4GPJbO--

--m5wuLCD9Q0X6WH9PRLEKHhv6qjN2PDRcl
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEEl1bqgKaRyqfWXu/CfJ+WJvzb8UYFAlmNRT4ACgkQfJ+WJvzb
8UanmQf/WIRM3qNTkxSK9k2L5r8ilBgrY9MPPeF/OUEEHGBQ/kZpM/kHvy7MKdRz
TKQVnGFpvg4ZcQOyXILbm+WJR7esfZ7Gy1ieDJ15U9phxApd4FhRMYvIleWR12MO
HWPzbIqGsbkAfNv6RclRKxfiIXybhSVfvZTLmNGp/6/t/Fr+pH0eejE8MZ45D83n
aa2UHE6q8JhvCOO5uLGZsFb1USTQZDgR0p2OTkqqkIZBV5jxeWlRJgtnxr9AVDC4
zccRzeNsbGHOTgRZHpVQWsK+i3qhoEDIAj4B5IEBYSHc5V+k8e3GeweJahohnGbe
tHu8np0AimYL4I0uwOBnSIy6PXhuKA==
=w7Vs
-----END PGP SIGNATURE-----

--m5wuLCD9Q0X6WH9PRLEKHhv6qjN2PDRcl--