VirtualBox Bridged Adapter Not Working Slackware 15.0
Linux - Virtualization and CloudThis forum is for the discussion of all topics relating to Linux Virtualization and Linux Cloud platforms. Xen, KVM, OpenVZ, VirtualBox, VMware, Linux-VServer and all other Linux Virtualization platforms are welcome. OpenStack, CloudStack, ownCloud, Cloud Foundry, Eucalyptus, Nimbus, OpenNebula and all other Linux Cloud platforms are welcome. Note that questions relating solely to non-Linux OS's should be asked in the General forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
VirtualBox Bridged Adapter Not Working Slackware 15.0
Hello guys,
I successfully built and installed VirtualBox 6.1 from slackbuilds and everything is working as they supposed to be. The only issue I encountered is bridged adapter is not working I am getting ;
Code:
Failed to open/create the internal network 'HostInterfaceNetworking-wlan0' (VERR_SUPDRV_COMPONENT_NOT_FOUND).
Failed to attach the network LUN (VERR_SUPDRV_COMPONENT_NOT_FOUND).
I think error is related to a kernel module but I don't know which one. Can anyone point me into the right direction ?
I've used VB for years and not encountered such an error, so all I can do is ask another question.
Do you have a VM installed, and can that VM access the internet?
I have another thought. In the VirtualBox settings dialog for each VM, at Settings-->Network-->Adapter 1-->Advanced-->Adapter Type, there are usually several adapter types that can be selected. Have you tried cycling through the various "Adapter Types" to see whether one of the works?
In my experience, VB's default choice is usually correct, but occasionally I've found that I've had to try the others to find the one that works.
I've used VB for years and not encountered such an error, so all I can do is ask another question.
Do you have a VM installed, and can that VM access the internet?
I have another thought. In the VirtualBox settings dialog for each VM, at Settings-->Network-->Adapter 1-->Advanced-->Adapter Type, there are usually several adapter types that can be selected. Have you tried cycling through the various "Adapter Types" to see whether one of the works?
In my experience, VB's default choice is usually correct, but occasionally I've found that I've had to try the others to find the one that works.
Thats correct I have also been using VBox from the earliest days of before Oracle ownership and with the default settings built and installed there should not be any issue regarding switching between network interfaces. I built 7.0 from source on a different device running Debian and bridged adapter is performing perfectly. There is a section I suppose in slackbuild file from slackbuilds that corresponds to a different kernel module which can provide bridged networking functionality. This would be my diagnostic so far
Maybe if you start VB from the command line and replicate your commands, you might get more helpful error messages, but I will freely admit I'm grasping as straws here!
Maybe if you start VB from the command line and replicate your commands, you might get more helpful error messages, but I will freely admit I'm grasping as straws here!
Probably the guy who prepared the build script disabled kernel modules required to bridged networking for security reasons. We'll see if someone else might provide more useful info on this particular issue
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.