Hey All, I'm in the process of reorganizing my bhyve setup on my development laptop. I'd like to have rename the tap devices to match the name of the VM so that it's easier to keep track of. Otherwise, I have to keep a spreadsheet of (tap3 -> win10-vm, tap4 -> fbsd-vm).
It appears bhyve doesn't attach renamed tap devices. Here's the steps I used: ifconfig bridge0 create ifconfig tap0 create name fbsd-01 ifconfig bridge0 addm em0 addm fbsd-01 up sh /usr/share/examples/bhyve/vmrun.sh -t fbsd-01 [normal vmrun.sh arguments here] (In this example, em0 is the physical network device connected to the LAN. I want to share em0 with the host and the guest via the bridge.) The net.link.tap.up_on_open sysctl node is set to 1. Normally, when bhyve starts up (with tap0 instead of fbsd-01), it opens the tap device and UPs it. I'm not seeing that same behavior with a renamed tap interface: $ ifconfig ld-03_01 ld-03_01: flags=8903<UP,BROADCAST,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=80000<LINKSTATE> ether 00:bd:df:e9:f6:04 groups: tap media: Ethernet autoselect status: no carrier nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL> So, it seems to me that bhyve doesn't like it when tap devices are renamed. Can anyone shed some light on this? Thanks, -- Shawn Webb Cofounder and Security Engineer HardenedBSD Tor-ified Signal: +1 443-546-8752 GPG Key ID: 0x6A84658F52456EEE GPG Key Fingerprint: 2ABA B6BD EF6A F486 BE89 3D9E 6A84 658F 5245 6EEE
Description: PGP signature