Bug #9548
closed
Do not use VLANMTU flag to decide if interface supports to run VLAN
100%
Description
Today there is a function called is_jumbo_capable() that detects if VLANMTU flag is supported by interface and this function is used to build the list of available parent interfaces to configure VLANs.
VLANMTU means interface can do 1500 MTU even using VLAN. Not having it is not a blocker to setup VLAN on the interface. Fix the code removing this check, but make sure only physical interfaces are being listed.
Updated by Renato Botelho over 5 years ago
- Status changed from New to Feedback
- % Done changed from 0 to 100
Applied in changeset 08fe7601ef535aa354255658215475223a23ddee.
Updated by Chris Linstruth almost 5 years ago
Evaluated this but could not figure out how to test it in the negative sense. Tried to make existing NICs drop the VLAN_MTU option with -vlanmtu but no luck. Interfaces that should be available for VLANs still populate, however.
ETA: I am seeing ipsec VTI and OpenVPN interfaces available for VLAN assignment. That should probably not be the case.
Updated by Jim Pingle almost 5 years ago
The only way to really try it is to track down a bit of hardware that didn't allow VLANs before, but does now.
But that's a pretty rare case, so it may be that so long as a variety of interfaces that worked before still work now, it may be good enough.
Updated by Anonymous about 4 years ago
- Status changed from Feedback to Resolved
No activity for ten months