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
CAN we have a feature like keepalived that we can make Mac VLAN optional? Or could someone else implement it for FRR?
With MAC VLAN mandatory, we need tons of config, even the official doc of FRR can not cover all of it,
eg: when creating a MAC VLAN interface used for OpenWRT, the addrgenmode can not be set,which makes it unusable against OpenWRT default config
I suggest making it optional, similar to how Keepalived operates. Currently, in FRR, the MAC VLAN is a requirement. I'm not advocating for the removal of the RFC-compliant mode; instead, let's provide the flexibility for users to choose whether they want to use the RFC-compliant mode or not.
OpenWRT is not the only platform , and it won't be the last. The documentation will continue to grow a list of notes, just as we have done with ESXI, Ingress, and the addrgenmode of IPv6, among other things.
These complexities make it more challenging and impose numerous limitations on deploying VRRP with FRR, thereby significantly restricting its potential applications.
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
-
CAN we have a feature like keepalived that we can make Mac VLAN optional?
Or could someone else implement it for FRR?
With MAC VLAN mandatory, we need tons of config, even the official doc of FRR can not cover all of it,
eg: when creating a MAC VLAN interface used for OpenWRT, the
addrgenmode
can not be set,which makes it unusable against OpenWRT default configI suggest making it optional, similar to how Keepalived operates. Currently, in FRR, the MAC VLAN is a requirement. I'm not advocating for the removal of the RFC-compliant mode; instead, let's provide the flexibility for users to choose whether they want to use the RFC-compliant mode or not.
OpenWRT is not the only platform , and it won't be the last. The documentation will continue to grow a list of notes, just as we have done with ESXI, Ingress, and the
addrgenmode
of IPv6, among other things.These complexities make it more challenging and impose numerous limitations on deploying VRRP with FRR, thereby significantly restricting its potential applications.
related: #5386 (comment)
Beta Was this translation helpful? Give feedback.
All reactions