From owner-freebsd-virtualization@FreeBSD.ORG Sun Oct 26 22:50:40 2014 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C15C3515; Sun, 26 Oct 2014 22:50:40 +0000 (UTC) Received: from mail-pa0-x232.google.com (mail-pa0-x232.google.com [IPv6:2607:f8b0:400e:c03::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 91B0F85; Sun, 26 Oct 2014 22:50:40 +0000 (UTC) Received: by mail-pa0-f50.google.com with SMTP id eu11so4231634pac.37 for ; Sun, 26 Oct 2014 15:50:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=6//3dlJFXpcev2iwZfacIPpka8BiOyaUl6tnlSw3hYI=; b=N5ScZAOPLgVpyEiWCIh9f26vCx+R1OT9bj70zMW/ZOpjEHRVRp+koPgGcBZ3kiaUJZ lCg4naHT/4Y+HaL7d5EAcScgrhFeZ1grsG52PfzOlC3XH76fvHCLfxIpnnYhz/hYWVMA m6T6aw2WtSvDmxG5Pm2xHytCgf9lqSwyyalVijYLwgOi1KRk2kCKa5Er0AvFgnIR9cnc QyIcWUrMwQmu+D24wg704sqxC/IBGbdA1H5/iRW1LJr7vAMTQuyTGC0xd0TeC31zJvTE Aw3Q7b3/ou1Yct/IUXcduDPTOp4sBBSFcM+vPzUWOrS8KKecZHgJTfdea2mc28ZE3frX n5qw== X-Received: by 10.66.140.8 with SMTP id rc8mr20368014pab.83.1414363840142; Sun, 26 Oct 2014 15:50:40 -0700 (PDT) Received: from neil.creepingfur.org (tessier.creepingfur.is. [70.36.196.188]) by mx.google.com with ESMTPSA id jq5sm9120374pbc.32.2014.10.26.15.50.38 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 26 Oct 2014 15:50:39 -0700 (PDT) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 8.0 \(1990.1\)) Subject: Re: No bhyve guests can reach the network after update. From: Benjamin Perrault In-Reply-To: <544D78EF.4010205@freebsd.org> Date: Sun, 26 Oct 2014 15:50:32 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: <53C7A7C9-A563-4975-9974-99630FA057A1@gmail.com> References: <544D78EF.4010205@freebsd.org> To: Allan Jude X-Mailer: Apple Mail (2.1990.1) Cc: freebsd-virtualization@freebsd.org X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Oct 2014 22:50:40 -0000 Thank you! I feel like an idiot now.. it seems I did indeed = somehow/accidently mergemastered out my usual sysctl.conf for the stock = one. I should have checked that first.=20 Setting sysctl net.link.tap.up_on_open=3D1 seems to have done it.=20 sorry for the noise.. cheers, -bp > On Oct 26, 2014, at 3:42 PM, Allan Jude wrote: >=20 > On 2014-10-26 18:36, Benjamin Perrault wrote: >> Hi all, >>=20 >> So I just update one of my systems to 10-STABLE r273710 ( GENERIC = kernel config ) and now all the bhyve guests are unable to connect to = the network ( be it linux, freebsd, or openbsd ). They guests see their = network interfaces fine - but they are unable to connect to anything. = Additionally on the host, the tap interfaces appear to be connecting = just fine.=20 >>=20 >> Everything appears fine on the host and it=E2=80=99s reporting no = errors. The networking is working/performing as normal. >>=20 >> There has been no configuration changes. Here is the relevant = networks stuff ( that=E2=80=99s been working reliably since 10-RELEASE, = and is running fine on 10.1-RC2 and -current just fine. ). >>=20 >> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D >> ifconfig_em0=3D"up -txcsum=E2=80=9D >> ifconfig_igb0=3D"up -txcsum=E2=80=9D >> defaultrouter=3D=E2=80=9C10.0.x.x" >> cloned_interfaces=3D"lagg0 bridge0 tap0 tap1 tap2 tap3 tap4 tap5 tap6 = tap7 tap8 tap9=E2=80=9D >>=20 >> ifconfig_lagg0=3D"laggproto lacp laggport em0 laggport igb0 = 10.0.x.x/24=E2=80=9D >>=20 >> ifconfig_bridge0=3D"addm lagg0 addm tap0 addm tap1 addm tap2 addm = tap3 addm tap4 addm tap5 addm tap6 addm tap7 addm tap8 addm tap9=E2=80=9D >> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >>=20 >> Any one have any ideas or suggestions? I always get spooked/bothered = when something that was working fine just sort of breaks.. >>=20 >> cheers and thanks, >> -bp >>=20 >>=20 >> _______________________________________________ >> freebsd-virtualization@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization >> To unsubscribe, send any mail to = "freebsd-virtualization-unsubscribe@freebsd.org" >>=20 >=20 > try: ifconfig bridge0 up >=20 > and make sure your tap interfaces are up as well (sysctl > net.link.tap.up_on_open=3D1 is useful) >=20 > --=20 > Allan Jude >=20