-
Notifications
You must be signed in to change notification settings - Fork 62
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Some bonded interface fixes #104
base: master
Are you sure you want to change the base?
Conversation
HWADDR is used to match interfaces, e.g. when selecting bond members
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Well, TIL about MACADDR vs HWADDR. I see the logic in using MACADDR for a bond, since there is no real device to select by HWADDR. However it is a bit inconsistent now. Would it make more sense to support both macaddr and hwaddr for RH systems? is there some equivalent we can use for Ubuntu?
@@ -15,6 +15,9 @@ netmask {{ item.netmask }} | |||
{% if item.gateway is defined %} | |||
gateway {{ item.gateway }} | |||
{% endif %} | |||
{% if item.dnsnameservers is defined %} | |||
dns-nameservers {{ item.dnsnameservers }} | |||
{% endif %} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you add the same for bridge_Debian.j2?
@@ -25,6 +28,9 @@ hwaddress {{ item.hwaddr }} | |||
{% if item.pre_up is defined %} | |||
pre-up {{ item.pre_up }} | |||
{% endif %} | |||
{% if item.dnssearch is defined %} | |||
dns-search {{ item.dnssearch }} | |||
{% endif %} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ditto
{% endif %} | ||
{% if item.dnssearch is defined %} | ||
DOMAIN={{ item.dnssearch }} | ||
{% endif %} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you add the same for templates/bridge_RedHat.j2?
It wouldn't make sense to support HWADDR for bonds and bridges, but it probably makes sense to support both for ethernet interfaces. I'll send some changes. 👍🏻 |
onboot
optional for bonded interfaces, as it is for the others.MACADDR
on Red Hat systems to set the address. [1][1] Note that I have only changed this in the bond template, because it's necessary for my use case. Changing it in the other templates would cause surprising compatibility problems if anyone is already using
hwaddr
to choose the interface by MAC address.