As soon as I create an VLAN-interface on a port and assign an address to it I can no longer manage the router via Winbox. I can ping the address on the infercace though.
Sometimes I can’t even login to Winbox. When I can login, most tabs are empty (like the interfaces tab, vlans tab, firewall tab, …) and the router disconnects within minutes. I’m going to mail a supout.rif to support but I was wondering whether someone else has come accross this?
edit: when I connect via serial cable, all the config looks ok.
For the VLAN interface you can only set an L2MTU of 1502 bytes (could nog get it to set 1504 or more). The MTU on the VLAN interface has to lowered (from 1500) to 1498 bytes in order for this to work.
1502 bytes - 4 bytes for VLAN header = 1498 bytes.
This looks like an issue to me. The physical interface, ether1, has an L2MTU of 1506 bytes. And a MTU of 1500 bytes.
Contrasting this to a 450G the VLAN interface has a L2MTU of 1516 bytes and an MTU of 1500 bytes.
The physical interface, has a L2MTU of 1520 bytes and a MTU of 1500 bytes.
So it seems a VLAN interface follows this rule: L2MTU of VLAN interface = L2MTU of pshysical interface - 4 bytes for VLAN header.
You can set Cisco’s and Junipers’s to ignore the DF flag and they will happily fragment away. I’ll take a wireshark capture on a windows PC connected to the WAN port. But thanks for fixing this so quickly!
If it is good, it must be said too!
Should I take this as an indication that a “little birdie” told you that we can expect the L2MTU on this product to eventually go beyond even 1580? Is support for 9K frames on the horizon, perchance?