Setting interface options is impossible with stacked (lagg, vlan) interfaces via the GUI
|Reported by:||gcooper||Owned by:|
When setting up interfaces via the GUI, if for example one wants to configure jumbo frames with vlans and lagg interfaces, they cannot do it today because the GUI requires each interface to an address associated with it.
In reality doing something like setting the MTU must be done all the way up the interface stack. This includes setting the MTU at the physical interface(s), the lagg interface, and finally at the vlan interface. Same thing with setting other interface options like the media type, etc.
In reality when DHCP is not specified (because DHCP has a tricky way of overriding MTU, media type, etc because it autonegotiates these properties):
- MTUs should be an optional property in the base interface 'class'. It should be inherited all the way up the stack. If it's changed on one level, it should be trickled up the stack. This is a more complicated to do right (thus more error prone and a PITA to support); I highly discourage doing this because it's error prone and would decrease portability of the code.
- Options should be configurable all the way up the stack, regardless of whether or not the interface has an address associated with it (again, if DHCP is not specified). This would be trivial to implement and test.
If possible it would be nice to backport this to 8.0.3 as we've had customers run into this issue, so please please.. don't rototill things if at all possible and try being as portable as possible!
Change History (3)
comment:1 Changed 19 months ago by gcooper
- Summary changed from Setting jumbo frames and interface media type is impossible with stacked (lagg, vlan) interfaces is impossible via the GUI to Setting interface options is impossible with stacked (lagg, vlan) interfaces via the GUI