bhyve vm-bhyve and VLAN

I had installed Alpine Linux in VirtualBox two months ago. It worked perfectly and always had good network connectivity.

Today I realized I forgot my Alpine Linux password so I couldn't login anymore. I therefore wanted to reinstall Alpine in VirtualBox, but I am not getting network connectivity. I've tried all possible settings, I can't get connectivity. When I select Bridged it simply always crashes directly during startup, although in my memory this was my old setting.

I think the problem may not be limited to bhyve but also applies to VirtualBox. Or can you get network connectivity in the standard version of Alpine Linux currently?
The problems I'm describing does not happen in Virtualbox. I believe this is because the problem is actually in the bridge interface, and Virtualbox does not use the bridge.
 
The problems I'm describing does not happen in Virtualbox. I believe this is because the problem is actually in the bridge interface, and Virtualbox does not use the bridge.
I didn't have vboxnet_enable="YES" in rc.conf
This was the issue..

VirtualBox works well again for me:

Screenshot_2022-10-23_11-17-38.png
 
I had installed Alpine Linux in VirtualBox two months ago. It worked perfectly and always had good network connectivity.

Today I realized I forgot my Alpine Linux password so I couldn't login anymore. I therefore wanted to reinstall Alpine in VirtualBox, but I am not getting network connectivity. I've tried all possible settings, I can't get connectivity. When I select Bridged it simply always crashes directly during startup, although in my memory this was my old setting.

I think the problem may not be limited to bhyve but also applies to VirtualBox. Or can you get network connectivity in the standard version of Alpine Linux currently?
Are you getting network connectivity on NAT?
If yes, are you using WiFi?
If yes, then there's your problem.
Most WiFi cards (if running encrypted) cannot obtain multiple IP addresses on the same card unless you do some weird things with WDS. You gotta' either use an ethernet card or run NAT. This is NOT an OS limitation, this is a hardware limitation.
 
It is completely solved by changing the setting in rc.conf. I configured it as bridged. I don't use wi-fi.

I haven't used VirtualBox for several months, maybe that's why I removed the line from the etc.conf file. Today I wanted to use VirtualBox again and I'm running into this problem because vboxnet_enable is not enabled because of my previous action. I don't really know what happened, but it's solved :)
 
Back
Top