Comments on: VirtualBox Wireless Bridging http://www.savvyadmin.com/virtualbox-wireless-bridging/ For savvy admins everywhere... Wed, 07 Jan 2009 02:24:45 +0000 http://wordpress.org/?v=2.6.3 By: panos http://www.savvyadmin.com/virtualbox-wireless-bridging/#comment-305 panos Tue, 23 Dec 2008 11:55:52 +0000 http://www.savvyadmin.com/?p=101#comment-305 I just installed vb 2.1, and at first glance it seems that wireless bridging works finally out of the box. At least this is the case for my Ubuntu host - Debian guest setup. Along with the tap device my wireless eth1 device appeared on the list. As I said, it works! I just installed vb 2.1, and at first glance it seems that wireless bridging works finally out of the box. At least this is the case for my Ubuntu host - Debian guest setup. Along with the tap device my wireless eth1 device appeared on the list. As I said, it works!

]]> By: gmendoza http://www.savvyadmin.com/virtualbox-wireless-bridging/#comment-259 gmendoza Sun, 09 Nov 2008 17:06:06 +0000 http://www.savvyadmin.com/?p=101#comment-259 @panos Awesome. Thanks for commenting. Since you are bringing up your machine from RAM, routing and proxy ARP may be turned off on resume. Check the variables like so: sudo sysctl net.ipv4.ip_forward sudo sysctl net.ipv4.conf.wlan0.proxy_arp sudo sysctl net.ipv4.conf.tapX.proxy_arp If they show up with a value of zero, then the feature was disabled on resume. You can enable them manually just as describe in the script: sudo sysctl net.ipv4.ip_forward=1 sudo sysctl net.ipv4.conf.wlan0.proxy_arp=1 sudo sysctl net.ipv4.conf.tapX.proxy_arp=1 You can also modify /etc/sysctl.conf with these values so that your settings are resilient after reboots, etc. The downside is that you may not want this at all times. Another option would be to create a resume script that is executed after a suspend or hibernate, but you may not want that all the time either. I would probably just automate the process with another very easy to remember fix it script... or add an additional function to the example I gave in the script. @panos

Awesome. Thanks for commenting. Since you are bringing up your machine from RAM, routing and proxy ARP may be turned off on resume. Check the variables like so:

sudo sysctl net.ipv4.ip_forward
sudo sysctl net.ipv4.conf.wlan0.proxy_arp
sudo sysctl net.ipv4.conf.tapX.proxy_arp

If they show up with a value of zero, then the feature was disabled on resume. You can enable them manually just as describe in the script:

sudo sysctl net.ipv4.ip_forward=1
sudo sysctl net.ipv4.conf.wlan0.proxy_arp=1
sudo sysctl net.ipv4.conf.tapX.proxy_arp=1

You can also modify /etc/sysctl.conf with these values so that your settings are resilient after reboots, etc. The downside is that you may not want this at all times. Another option would be to create a resume script that is executed after a suspend or hibernate, but you may not want that all the time either.

I would probably just automate the process with another very easy to remember fix it script… or add an additional function to the example I gave in the script.

]]> By: panos http://www.savvyadmin.com/virtualbox-wireless-bridging/#comment-258 panos Sun, 09 Nov 2008 12:10:43 +0000 http://www.savvyadmin.com/?p=101#comment-258 Works flawlessly on a Debian Etch guest (ubuntu hardy host)! Congratulations. However, there is a minor issue: after a suspend to ram the routing does not work. I can ping my host but not my router. Of course, it's not important at all, I'm just curious what could be the reason (I use the knetworkmanager). Works flawlessly on a Debian Etch guest (ubuntu hardy host)! Congratulations. However, there is a minor issue: after a suspend to ram the routing does not work. I can ping my host but not my router. Of course, it’s not important at all, I’m just curious what could be the reason (I use the knetworkmanager).

]]> By: panos http://www.savvyadmin.com/virtualbox-wireless-bridging/#comment-202 panos Fri, 22 Aug 2008 14:14:04 +0000 http://www.savvyadmin.com/?p=101#comment-202 Great. But my FreeBSD guest (ubuntu hardy host) can only ping my internal network. I cannot even ping my router... Great. But my FreeBSD guest (ubuntu hardy host) can only ping my internal network. I cannot even ping my router…

]]> By: debian user http://www.savvyadmin.com/virtualbox-wireless-bridging/#comment-192 debian user Thu, 21 Aug 2008 13:02:44 +0000 http://www.savvyadmin.com/?p=101#comment-192 In case the Virtualbox GUEST debian does not bring up eth0 and displayes error: SIOCSIFADDR: No such device eth0: ERROR while getting interface flags: No such device The solution is in the Virtualbox site: http://www.virtualbox.org/ticket/660 Namely, at GUEST Debian: rm /etc/udev/rules.d/z25_persistent-net.rules reboot In case the Virtualbox GUEST debian does not bring up eth0 and displayes error:

SIOCSIFADDR: No such device
eth0: ERROR while getting interface flags: No such device

The solution is in the Virtualbox site:
http://www.virtualbox.org/ticket/660

Namely, at GUEST Debian:

rm /etc/udev/rules.d/z25_persistent-net.rules
reboot

]]> By: Nick http://www.savvyadmin.com/virtualbox-wireless-bridging/#comment-153 Nick Tue, 29 Jul 2008 21:57:04 +0000 http://www.savvyadmin.com/?p=101#comment-153 Excellent. I thought it should be able to be done via proxy arp - so a great starting point. It works well with a static IP, butI use my laptop on more than one network:( No pressure, but it I tried to figure out how to do the dhcprelay thing but cannot! I think it is because of the return route back to the VM, but you cannot add this until you have the actual address... Excellent. I thought it should be able to be done via proxy arp - so a great starting point. It works well with a static IP, butI use my laptop on more than one network:(

No pressure, but it I tried to figure out how to do the dhcprelay thing but cannot! I think it is because of the return route back to the VM, but you cannot add this until you have the actual address…

]]>