In order to use bridged adapter of virtualbox 4.2.6 , how to config kernel ?
I upload my kernel config.
Now I can not use bridged adapter function of virtualbox.
I think the matter is about kernel config.
http://dpaste.de/1EOJz/
Thanks_________________i5-2450M, gnome, amd64
R,Mathematica,Emacs

Last edited by waterloo2005 on Wed Jan 30, 2013 1:26 pm; edited 1 time in total

i didn't to read thru your whole kernel-config but you need at least CONFIG_BRIDGE and CONFIG_TUN.
also i think it's necessary to install net-misc/bridge-utils.
GOOD LUCK!_________________DUMM KLICKT GUT.

Some wiki says we do not need CONFIG_BRIDGE and CONFIG_TUN for vbox>=2.1.
My now version is 4.2.6.
I also try enable CONFIG_BRIDGE and CONFIG_TUN and install bridge-utils . But I still can not use bridged adapter .

In ubuntu12.04, I can use bridged adapter in network config .

I think if there are other kernel settings I ignore .
But I see the official manual , with no finding about other kernel config.

The problem is that Virtualbox has a hard-coded path to /sbin/ifconfig but that program is no longer available there. As a workaround, you could symlink /bin/ifconfig back to /sbin/ifconfig. Alternately, file a bug and request that it be fixed properly. Please note that placing a symlink is only a workaround, not a real fix to the problem, and you should only do that if you will remember to remove the symlink when the problem is fixed.

If you do not understand how to do the workaround or if you have any doubts, please just file a bug and be patient. It is considered poor practice to manually modify things in /sbin, which is why I label this as a workaround and not a fix.

The problem is that Virtualbox has a hard-coded path to /sbin/ifconfig but that program is no longer available there. As a workaround, you could symlink /bin/ifconfig back to /sbin/ifconfig. Alternately, file a bug and request that it be fixed properly. Please note that placing a symlink is only a workaround, not a real fix to the problem, and you should only do that if you will remember to remove the symlink when the problem is fixed.

If you do not understand how to do the workaround or if you have any doubts, please just file a bug and be patient. It is considered poor practice to manually modify things in /sbin, which is why I label this as a workaround and not a fix.

I run sudo ln -s /bin/ifconfig /sbin/ifconfig , but the problem still exists.
Do I need CONFIG_BRIDGE and CONFIG_TUN and bridge-utils ?
Thanks_________________i5-2450M, gnome, amd64
R,Mathematica,Emacs

The problem is that Virtualbox has a hard-coded path to /sbin/ifconfig but that program is no longer available there. As a workaround, you could symlink /bin/ifconfig back to /sbin/ifconfig. Alternately, file a bug and request that it be fixed properly. Please note that placing a symlink is only a workaround, not a real fix to the problem, and you should only do that if you will remember to remove the symlink when the problem is fixed.

If you do not understand how to do the workaround or if you have any doubts, please just file a bug and be patient. It is considered poor practice to manually modify things in /sbin, which is why I label this as a workaround and not a fix.

I run sudo ln -s /bin/ifconfig /sbin/ifconfig , but the problem still exists.
Do I need CONFIG_BRIDGE and CONFIG_TUN and bridge-utils ?
Thanks

I do not have those. Are you sure that the vboxdrv, vboxnetadp, and vboxnetflt modules are loaded?

The problem is that Virtualbox has a hard-coded path to /sbin/ifconfig but that program is no longer available there. As a workaround, you could symlink /bin/ifconfig back to /sbin/ifconfig. Alternately, file a bug and request that it be fixed properly. Please note that placing a symlink is only a workaround, not a real fix to the problem, and you should only do that if you will remember to remove the symlink when the problem is fixed.

If you do not understand how to do the workaround or if you have any doubts, please just file a bug and be patient. It is considered poor practice to manually modify things in /sbin, which is why I label this as a workaround and not a fix.

I run sudo ln -s /bin/ifconfig /sbin/ifconfig , but the problem still exists.
Do I need CONFIG_BRIDGE and CONFIG_TUN and bridge-utils ?
Thanks

I do not have those. Are you sure that the vboxdrv, vboxnetadp, and vboxnetflt modules are loaded?

I have loaded the 3 modules and run sudo ln -s /bin/ifconfig /sbin/ifconfig, the problem still exists.

As far as I know, CONFIG_BRIDGE isn't needed, although I have it enabled in my kernel
CONFIG_TUN definitely isn't needed, and nor are bridge-utils.

Will

So strange.
I also cancel CONFIG_BRIDGE and CONFIG_TUN support, and do not install bridge-utils.
Why bridged adapter can not work in my machine ?
Thanks_________________i5-2450M, gnome, amd64
R,Mathematica,Emacs

Be aware that you don't need TUN/TAP for VirtualBox. I'm not sure that you even
need the kernel CONFIG_BRIDGE, and you certainly don't need bridge-utils,
although you used to a few years ago. VirtualBox does it all itself, these days.

If I cancel CONFIG_TUN in kernel config, I find no /dev/net/tun.
Thanks

As you can see, you dont have permissions to access the tun device. thats why you need the usermode-utilities. This provides the tunctl tool for changeing permissions while creating the necessary devices. Check this wiki entry for the netconfig:

I also try use kernel config of ubuntu12.04, that makes bridged adapter network config in vbox work.
But I do not how to find that critical item in kernel config._________________i5-2450M, gnome, amd64
R,Mathematica,Emacs