Date: Sun, 11 Dec 2016 15:27:06 +0000 From: Tom Beard <tom.beard@public-internet.co.uk> To: freebsd-net@freebsd.org Subject: Re: bce vlan stripping limitations Message-ID: <E6036F9F-97CB-4518-B738-9AE087521167@public-internet.co.uk> In-Reply-To: <1C233AAF-E7F3-4FE9-8936-A36F827F4137@public-internet.co.uk> References: <1C233AAF-E7F3-4FE9-8936-A36F827F4137@public-internet.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
Keen observers will have noticed that I pasted the output from the wrong =
vlan1. The correct output is below.
vlan1: flags=3D8942<BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric =
0 mtu 1500
ether 84:2b:2b:0b:b3:72
nd6 options=3D29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
media: Ethernet autoselect (1000baseT <full-duplex>)
status: active
vlan: 304 vlanpcp: 0 parent interface: bce0
groups: vlan=20
> On 11 Dec 2016, at 14:44, Tom Beard via freebsd-net =
<freebsd-net@freebsd.org> wrote:
>=20
> Hi all
>=20
> I=E2=80=99m having issues with vlan handling on a bce interface on =
11.0-RELEASE. =46rom what I=E2=80=99ve read, the bce driver supports =
hardware vlan stripping and is indeed doing this. My intent was to =
create a vlan interface bound to the bce interface and bridge this to a =
tap interface to use with a bhyve VM (as below). =20
>=20
> Outbound traffic from the VM is correctly bridged from tap1 to vlan1 =
then tagged with vlan 304 and passed out on bce0
>=20
> Inbound traffic tagged with vlan 304 on bce0 never makes it to vlan0.
>=20
> =46rom what I can tell this is caused by vlan stripping on the bce0 =
interface and it looks like I can=E2=80=99t disable it leaving me with =
little option but to buy a new network card.
>=20
> Can anyone validate that I=E2=80=99m correct here and this is a known =
limitation or am I barking up completely the wrong tree?
>=20
> Thanks
> Tom
>=20
> bce0: <QLogic NetXtreme II BCM5716 1000Base-T (C0)> mem =
0xda000000-0xdbffffff irq 36 at device 0.0 on pci1
>=20
> bce0: flags=3D8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> =
metric 0 mtu 1500
> options=3D80028<VLAN_MTU,JUMBO_MTU,LINKSTATE>
> ether 84:2b:2b:0b:b3:72
> nd6 options=3D29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
> media: Ethernet autoselect (1000baseT <full-duplex>)
> status: active
>=20
> bridge1: flags=3D8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 =
mtu 1500
> ether 02:eb:af:cf:7c:01
> nd6 options=3D1<PERFORMNUD>
> groups: bridge=20
> id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15
> maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200
> root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0
> member: tap1 flags=3D143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
> ifmaxaddr 0 port 11 priority 128 path cost 2000000
> member: vlan1 flags=3D143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
> ifmaxaddr 0 port 9 priority 128 path cost 55
>=20
> vlan1: flags=3D8102<BROADCAST,PROMISC,MULTICAST> metric 0 mtu 1500
> ether 00:00:00:00:00:00
> nd6 options=3D29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
> vlan: 0 vlanpcp: 0 parent interface: <none>
> groups: vlan=20
>=20
> tap1: flags=3D8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> =
metric 0 mtu 1500
> options=3D80000<LINKSTATE>
> ether 00:bd:3a:17:4c:02
> nd6 options=3D29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
> media: Ethernet autoselect
> status: active
> groups: tap=20
> Opened by PID 12880
>=20
> _______________________________________________
> freebsd-net@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-net
> To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E6036F9F-97CB-4518-B738-9AE087521167>