Hi Chrisz, 4 bytes for the vlan header .. have you tried increasing the parent intetface mtu by 4bytes
So for vlan of 1500 mtu set parent interface mtu to 1504 bytes If you are doing q in q vlan nesting Then the parent interface should be 1500bytes +4× number of levels of nesting eg 1 vlan nested inside another vlan (2 levels ov vlans 1500+(4×2) for parent physical interface The first ( outer vlan should be 1500+4 bytes mtu) Innerclan can be 1500 mtu Hope this helps On Tuesday, 21 April 2020, Christopher Zimmermann <chr...@openbsd.org> wrote: > On Sun, Jul 07, 2019 at 01:26:55PM -0700, Chris Cappuccio wrote: > >> Christopher Zimmermann [chr...@openbsd.org] wrote: >> >>> This works: >>> >>> doas ifconfig vlan67 mtu 1496 >>> >>> this doesn't: >>> >>> doas ifconfig vlan67 mtu 1497 >>> >>> >>> Should we therefore disable VLAN_MTU on this chipset? >>> >>> - ifp->if_capabilities = IFCAP_VLAN_MTU; >>> - >>> >> >> >> Yes absolutely. If IFCAP_VLAN_MTU actually worked for some chip versions, >> more work is needed to distinguish the working chipsets. >> > > Hi, > > I'm looking for reponts of aue(4) chipsets actually supporting VLAN_MTU. > Mine does not. It identifies as: > > aue0 at uhub9 port 5 configuration 1 interface 0 "ADMtek USB To LAN > Converter" rev 2.00/1.01 addr 5 > aue0: address 00:05:1b:b2:96:02 > ukphy0 at aue0 phy 1: Generic IEEE 802.3u media interface, rev. 1: OUI > 0x000749, model 0x0001 > > In case there are none, I would like to drop above mentioned > IFCAP_VLAN_MTU flag for the aue(4) driver and look for OKs. > > > Christopher > > > -- > http://gmerlin.de > OpenPGP: http://gmerlin.de/christopher.pub > CB07 DA40 B0B6 571D 35E2 0DEF 87E2 92A7 13E5 DEE1 > > -- Kindest regards, Tom Smyth.
