> On 23 May 2020, at 7:54 am, Christopher Zimmermann wrote:
>
> On Tue, Apr 21, 2020 at 04:12:16PM -0700, Chris Cappuccio wrote:
>> Tom Smyth [tom.sm...@wirelessconnect.eu] wrote:
>>> Hi Chrisz,
>>>
>>> 4 bytes for the vlan header .. have you tried increasing the parent
>>> intetface mtu by
On Tue, Apr 21, 2020 at 04:12:16PM -0700, Chris Cappuccio wrote:
Tom Smyth [tom.sm...@wirelessconnect.eu] wrote:
Hi Chrisz,
4 bytes for the vlan header .. have you tried increasing the parent
intetface mtu by 4bytes
IFCAP_VLAN_MTU is a direct bypass for this. "hardmtu" on the parent
Ok thanks for the info i always find mtu confusing as i thought generally
it was referring to ip mtu. while layer2 headers vlans and layer 2.5
headers such as mpls labels cw etc...would be outside the ip mtu...
Thanks again
On Wednesday, 22 April 2020, Chris Cappuccio wrote:
> Tom Smyth
Tom Smyth [tom.sm...@wirelessconnect.eu] wrote:
> Hi Chrisz,
>
> 4 bytes for the vlan header .. have you tried increasing the parent
> intetface mtu by 4bytes
>
IFCAP_VLAN_MTU is a direct bypass for this. "hardmtu" on the parent interface
is perhaps more interesting as it will limit everything
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
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 =
