Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 26 Oct 2014 15:50:32 -0700
From:      Benjamin Perrault <ben.perrault@gmail.com>
To:        Allan Jude <allanjude@freebsd.org>
Cc:        freebsd-virtualization@freebsd.org
Subject:   Re: No bhyve guests can reach the network after update.
Message-ID:  <53C7A7C9-A563-4975-9974-99630FA057A1@gmail.com>
In-Reply-To: <544D78EF.4010205@freebsd.org>
References:  <D6EF4C50-51FC-41F8-AD86-126DEE2C3BEB@gmail.com> <544D78EF.4010205@freebsd.org>

next in thread | previous in thread | raw e-mail | index | archive | help
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 <allanjude@freebsd.org> 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




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?53C7A7C9-A563-4975-9974-99630FA057A1>