You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The new MAC functionality is reasonably implemented - the GUI with the [+] certainly is nice, however after adding a MAC to an interface, the user next needs to go back in to the Interface's editing screen, and select the (only) MAC to be primary.
While I can appreciate the importance of handling multiple MACs on an interface, unlike an IP address, a single (or first) MAC on an interface ought to be considered the primary by default - as that's likely true more than 99% of the time. Netbox appears to have considered any pre-existing MAC to become the primary during the upgrade - so my rationale isn't without some agreement here!
I did some searching, didn't find any discussion about this; not sure if it's a bug, or I am contemplating a feature request... just seems a bit outside of POLA. (S'pose there could be a preference to enable this behaviour, should there be no 'primary' per se.)
NB: I think chassis-wide MACs (or primary MAC) should be equally considered (eg: PTMP WAPs or Sun servers) as they're more likely than multiple MACs per interface...
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
The new MAC functionality is reasonably implemented - the GUI with the [+] certainly is nice, however after adding a MAC to an interface, the user next needs to go back in to the Interface's editing screen, and select the (only) MAC to be primary.
While I can appreciate the importance of handling multiple MACs on an interface, unlike an IP address, a single (or first) MAC on an interface ought to be considered the primary by default - as that's likely true more than 99% of the time. Netbox appears to have considered any pre-existing MAC to become the primary during the upgrade - so my rationale isn't without some agreement here!
I did some searching, didn't find any discussion about this; not sure if it's a bug, or I am contemplating a feature request... just seems a bit outside of POLA. (S'pose there could be a preference to enable this behaviour, should there be no 'primary' per se.)
NB: I think chassis-wide MACs (or primary MAC) should be equally considered (eg: PTMP WAPs or Sun servers) as they're more likely than multiple MACs per interface...
Beta Was this translation helpful? Give feedback.
All reactions