Skip to content
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

Allow configuration of target device name for bridge interfaces #1627

Open
JeffWDH opened this issue May 9, 2024 · 0 comments
Open

Allow configuration of target device name for bridge interfaces #1627

JeffWDH opened this issue May 9, 2024 · 0 comments

Comments

@JeffWDH
Copy link

JeffWDH commented May 9, 2024

Libvirt supports overriding the name of tap devices used for bridge interfaces. I propose adding this functionality to Cockpit-machines as telling the difference between dozens of vnetX interfaces is not a great experience.

Example config:

<interface type='bridge'>
  <mac address='52:54:00:ae:f7:f2'/>
  <source bridge='LAN'/>
  <target dev='VM_TestVM'/>
  <model type='virtio'/>
  <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/>
</interface>

Resulting device:

42: VM_TestVM: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master LAN state UNKNOWN group default qlen 1000
    link/ether fe:54:00:ae:f7:f2 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::fc54:ff:feae:f7f2/64 scope link
       valid_lft forever preferred_lft forever

Restrictions:

  • Device names seem to be limited to 15 characters
  • Name should not start with either 'vnet', 'vif', 'macvtap', or 'macvlan'

Libvirt documentation: https://libvirt.org/formatdomain.html#overriding-the-target-element

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant