-
Notifications
You must be signed in to change notification settings - Fork 61
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
Extend shared/vnic.ksh to support creating vrrp vnics #375
Comments
I just realized this probably won’t work because mac-addr zone properly can’t contain ‘vrrp’ perhaps the more painful mac parsing is the way to go, that also means we don’t have to teach zadm and anders about this? |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Would still like to see this somehow properly supported, I have not come up with a better idea though :( |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Still interested in this, once I figure out a good way to do this. Feedback welcome |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Bump |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Unstale |
Currently it's not possible to have a brand automatically create vrrp vnics:
I had a look at shared/vnic.ksh and it seems like it should be possible to add this without too much trouble but I am not sure this is the best approach, I'd like some feedback before further fleshing this out.
I was thinking something along the lines of:
Full function below for easier reading:
This is just a rough untested idea on how I would like to implement it, there is no vrid and vridfamily parsing added higher up to the awk script yet.
Does this approach look good? If so flash this out more (update the awk parsing and such) and give it a spin.
An alternative idea I had was just to be able to feed it a vrrp mac e.g.
0:0:5e:0:1:62
for inet and0:0:5e:0:2:62
for inet6 and then parse those to extract the vrid and vrid family from them, this is doable because the VRRP mac follow the same format:0:0:5e:0:
prefix,1
for IPv4 (inet) or2
for IPv6 (inet6),XX
is the vrid in hex, so it's certainly possible to parse the required info from this, but I feel this would make for a lot of complex parsing in ksh which I prefer to avoid, simply creating a vnic with one of those mac addresses is not sufficient to make vrrpadm create-router happy, I tried.Edit: some more context, https://blackdot.be/2021/12/using-vrrp-inside-a-lipkg-zone-on-omnios/ manually creating the vnic first and just passing it in works as a workaround but I would prefer not to manually have to create any vnics.
The text was updated successfully, but these errors were encountered: