We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
--network_(device|config)
While working on LACP bonding support, I realize that VLAN configuration on cmdline allows some non-sensical configurations like:
--network_device=all --network_config=dhcp:vlan=10
Also "just specifying a VLAN on a given interface" requires today to repeat the dhcp default with no good reason:
dhcp
--network_device=eth0 --network_config=dhcp:vlan=10
I think we should move the VLAN specification to the --network_device option, like
--network_device
--network_device=eth[:vlan=VLAN]|mac[:vlan=VLAN]|all
The "just specifying a VLAN on a given interface" usecase will then become:
--network_device=eth0:vlan=10
The text was updated successfully, but these errors were encountered:
No branches or pull requests
While working on LACP bonding support, I realize that VLAN configuration on cmdline allows some non-sensical configurations like:
Also "just specifying a VLAN on a given interface" requires today to repeat the
dhcp
default with no good reason:I think we should move the VLAN specification to the
--network_device
option, likeThe "just specifying a VLAN on a given interface" usecase will then become:
The text was updated successfully, but these errors were encountered: