Bridging VirtualBox 1.6.2 on Ubuntu 8.04.1

I had written a message about bridging VirtualBox in my blog. However, it is out-dated. I will show you how to do it on Ubuntu 8.04.1 with VirtualBox 1.6.2.

The steps I mentioned here is assumed that the host system is behind a router and the ip addresses are distributed by DHCP from the router.

Step 1 :

Install the required package for the bridged network on the host.

sudo apt-get install uml-utilities bridge-utils

Issue the following command to stop the network interface.

sudo invoke-rc.d networking stop

Edit the /etc/network/interfaces by the below command.

sudo nano /etc/network/interfaces

The content of the file should be like this. That is, append the line of ‘auto br0′ and the rest to the end of /etc/network/interfaces. The codes are for bridging eth0 and you can change it as required.

auto lo
iface lo inet loopback

auto eth0
iface eth0 inet manual

auto br0
iface br0 inet dhcp
bridge_ports eth0
bridge_fd 9
bridge_hello 2
bridge_maxage 12
bridge_stp off

Restart the network interface.

sudo /etc/init.d/networking restart

Step 2 :

Still on the host. Issue the following commands.

sudo VBoxAddIF vbox0 `whoami` br0
VBoxManage modifyvm "My VM" -hostifdev1 vbox0
sudo chmod 0666 /dev/net/tun

* where “My VM” is the name of your guest. The network interface should be Host Interface.

Make sure, at the GUI VirtualBox panel, select “Network”, Select “Host Interface” at “Attached to” and fill in the blank to “vbox0” at “Interface Name”.

Updated on 2009-FEB-22 :
This HOWTO is out-dated when VirtualBox 2.1.0 is out! The current version is 2.1.4 as at today. The current version of VirtualBox handles the network interfaces bridging automatically.

Advertisements

35 Responses

  1. […] wrote an updated method to bridge VirtualBox 1.6.2 on Ubuntu 8.04.1 at here. Possibly related posts: (automatically generated)Virtualbox 1.6.0 with Ubuntu 8.04 […]

  2. Note that you need to “apt-get install bridge-utils” and “chgrp vboxusers /dev/net/tun” this to work…

    In fact I didn’t manage to get this to work at all – the bridge couldn’t acquire an IP address via DHCP, eventually timing out with “No DHCPOFFERS received”. Setting a static IP didn’t seem to work either.

    Setting up the bridge manually with brctl as described in the following link did work, to the extent that I could connect to the guest machine if I set it to a static IP, but then there seemed to be no connectivity from the guest to anywhere on the network except the host. (See http://applocator.googlepages.com/virtualbox).

    Perhaps my problems are in part from using a wifi card – apparently these don’t work so well with ethernet bridging (see
    https://help.ubuntu.com/community/VirtualBox#Wireless%20Networking).

  3. wulee,

    Thank you. I really forgot to include the package “bridge-utils” in my tutorial.

    In general speaking, wireless card does not support bridging.

    I enhanced the official user manual for the purpose. Please refer to the official user manual for details.

  4. Can you put instructions for fixed IP addresses both in the host and the guest? Thanks, your site is very usefull!

  5. the bridging actually works for the vm, ip is assined and it is reachable from the network. but my eth0 on the host doesn’t work anymore. networkmanager doesn’t show the wired network entry any more, and i couldn’t get it to get an ip via dhcp on the commandline either. any ideas on that? my wireless still works (and networkmanager switches fine to it as soon as i restart the network after the changes), but that is not an option for longterm…

  6. kendon23,

    It is normal. The eth0 is no longer used on the host for connecting to the internet or router. The br0 on the host is used for that purpose instead.

    Here is my list of ifconfig :

    br0 Link encap:Ethernet HWaddr 00:00:00:00:00:00
    inet addr:192.168.0.69 Bcast:192.168.0.255 Mask:255.255.255.0
    inet6 addr: 0000::000:0000:0000:0000/64 Scope:Link
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:3371 errors:0 dropped:0 overruns:0 frame:0
    TX packets:3372 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:2227715 (2.1 MB) TX bytes:654443 (639.1 KB)

    eth0 Link encap:Ethernet HWaddr 00:00:00:00:00:00
    inet6 addr: 0000::000:0000:0000:0000/64 Scope:Link
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:3371 errors:0 dropped:0 overruns:0 frame:0
    TX packets:3374 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:2275626 (2.1 MB) TX bytes:655731 (640.3 KB)
    Interrupt:218 Base address:0x6000

    eth1 Link encap:Ethernet HWaddr 00:00:00:00:00:00
    UP BROADCAST MULTICAST MTU:1500 Metric:1
    RX packets:0 errors:0 dropped:0 overruns:0 frame:0
    TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
    Interrupt:217 Base address:0x6000

    lo Link encap:Local Loopback
    inet addr:127.0.0.1 Mask:255.0.0.0
    inet6 addr: ::1/128 Scope:Host
    UP LOOPBACK RUNNING MTU:16436 Metric:1
    RX packets:2834 errors:0 dropped:0 overruns:0 frame:0
    TX packets:2834 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:141700 (138.3 KB) TX bytes:141700 (138.3 KB)

    vbox0 Link encap:Ethernet HWaddr 00:00:00:00:00:00
    inet6 addr: 0000::000:0000:0000:0000/64 Scope:Link
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:0 errors:0 dropped:0 overruns:0 frame:0
    TX packets:0 errors:0 dropped:22 overruns:0 carrier:0
    collisions:0 txqueuelen:500
    RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

  7. thx for the quick answer, i reverted to my backup, but i will try this soon. do you know if there is a way to make network-manager to handle the br0 interface?

  8. kendon23,

    The network-manger on Ubuntu 8.04 can handle br0 automatically.

  9. Hello,

    I have the following lines in /etc/network/interfaces:
    auto eth0
    iface eth0 inet manual

    auto br0
    iface br0 inet dhcp
    bridge_ports eth0

    # The loopback network interface
    auto lo
    iface lo inet loopback

    I have to VM Box’s using vbox0 and vbox1. They are both getting IP’s from the DHCP Server in my network and they are able to access the net very cool. These 2 boxes are working as server. They are both a Web Server (http).

    The problem is: I am not able to access any of these Boxes from the Machine that is running them (the physical machine).

    How can I solve this problem? Do you have any idea?

    Thank you in advance.

  10. Just another note, I am now unable to access any device on my local network 10.0.0.0/8 :(

  11. rul3z,

    I cannot simulate your problem.

    My 2 virtual machines can be accessed via the host machine with no problem.

    Did you follow all the procedure as above captioned.

    Samiux

  12. Hi Samiux,

    Yes sir I did the same procedures exactly. As I told you I can reach the net from all 3 Boxes (Host, 2VM) but I can not reach any of them.
    For example: I can not access the 10.0.0.1 GW
    nor 10.0.0.2 Guest Box1 or 10.0.0.3 Guest Box2.

    Do you have any clues?

    And I appreciate very much your reply.

  13. BTW: is there any iptables rules needed?

  14. rul3z,

    My environment is that :
    All VMs can be reached by the host. The router and other physical machines also can be reached by the host. No firewall at the intranet.

    My ifconfig is here :
    br0 Link encap:Ethernet HWaddr 00:00:00:00:00:00
    inet addr:192.168.0.69 Bcast:192.168.0.255 Mask:255.255.255.0
    inet6 addr: 0000::000:0000:0000:0000/64 Scope:Link
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:316182 errors:0 dropped:0 overruns:0 frame:0
    TX packets:256414 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:349636818 (333.4 MB) TX bytes:29759833 (28.3 MB)

    eth0 Link encap:Ethernet HWaddr 00:00:00:00:00:00
    inet6 addr: 0000::000:0000:0000:0000/64 Scope:Link
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:322033 errors:0 dropped:0 overruns:0 frame:0
    TX packets:260340 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:362735032 (345.9 MB) TX bytes:30079702 (28.6 MB)
    Interrupt:218 Base address:0x6000

    eth1 Link encap:Ethernet HWaddr 00:00:00:00:00:00
    UP BROADCAST MULTICAST MTU:1500 Metric:1
    RX packets:0 errors:0 dropped:0 overruns:0 frame:0
    TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
    Interrupt:217 Base address:0xa000

    lo Link encap:Local Loopback
    inet addr:127.0.0.1 Mask:255.0.0.0
    inet6 addr: ::1/128 Scope:Host
    UP LOOPBACK RUNNING MTU:16436 Metric:1
    RX packets:2026 errors:0 dropped:0 overruns:0 frame:0
    TX packets:2026 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:101585 (99.2 KB) TX bytes:101585 (99.2 KB)

    vbox0 Link encap:Ethernet HWaddr 00:00:00:00:00:00
    inet6 addr: 0000::000:0000:0000:0000/64 Scope:Link
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:80 errors:0 dropped:0 overruns:0 frame:0
    TX packets:493 errors:0 dropped:1882 overruns:0 carrier:0
    collisions:0 txqueuelen:500
    RX bytes:66041 (64.4 KB) TX bytes:122135 (119.2 KB)

    vbox1 Link encap:Ethernet HWaddr 00:00:00:00:00:00
    inet6 addr: 0000::000:0000:0000:0000/64 Scope:Link
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:3993 errors:0 dropped:0 overruns:0 frame:0
    TX packets:6619 errors:0 dropped:1088 overruns:0 carrier:0
    collisions:0 txqueuelen:500
    RX bytes:303134 (296.0 KB) TX bytes:8904107 (8.4 MB)

    By the way, would you mind posting your ifconfig here?

    Samiux

  15. Samiux,

    I have managed to solve the problem. It was that the VirtualBox was not taking the new changes, so I had to restart the network service like this:

    sudo /etc/init.d/virtualbox-ose restart

    This is done after:
    sudo /etc/init.d/networking restart

    Samiux, I really appreciate your help thanx mate. And BTW if you still need my ifconfig output I can post it here for you, I don’t mind at all.

    Thank you again, and I shall be one of your BLOG readers, keep it going.

    Best regards,

  16. rul3z,

    Thank you very much.

    If you don’t mind, you can post your ifconfig here for reference.

    Samiux

  17. No problem at all, I only removed the MAC Address (Sorry for that):

    $ ifconfig
    br0 Link encap:Ethernet HWaddr MAC Address
    inet addr:10.0.0.100 Bcast:255.255.255.255 Mask:255.0.0.0
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:1136 errors:0 dropped:0 overruns:0 frame:0
    TX packets:1164 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:370810 (362.1 KB) TX bytes:143423 (140.0 KB)

    eth0 Link encap:Ethernet HWaddr MAC Address
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:5687583 errors:0 dropped:0 overruns:0 frame:0
    TX packets:4290289 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:2230935187 (2.0 GB) TX bytes:2033273418 (1.8 GB)
    Interrupt:21 Base address:0x2000

    lo Link encap:Local Loopback
    inet addr:127.0.0.1 Mask:255.0.0.0
    UP LOOPBACK RUNNING MTU:16436 Metric:1
    RX packets:200620 errors:0 dropped:0 overruns:0 frame:0
    TX packets:200620 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:183177263 (174.6 MB) TX bytes:183177263 (174.6 MB)

    vbox0 Link encap:Ethernet HWaddr MAC Address
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:0 errors:0 dropped:0 overruns:0 frame:0
    TX packets:0 errors:0 dropped:130 overruns:0 carrier:0
    collisions:0 txqueuelen:500
    RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

    vbox1 Link encap:Ethernet HWaddr MAC Address
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:108 errors:0 dropped:0 overruns:0 frame:0
    TX packets:79 errors:0 dropped:3 overruns:0 carrier:0
    collisions:0 txqueuelen:500
    RX bytes:26388 (25.7 KB) TX bytes:10628 (10.3 KB)

  18. is there any solution while using a wireless device?

  19. mycirilo,

    As far as I know, wifi interface cannot be bridged so far. Hope some experts are working on this.

    Samiux

  20. Hi,
    I have a happy Ubuntu 8.04 installation and a happy VirtualBox installation (all things go well according to my will :) ) now, I want to try VirtualBox networking, but I’m too scared if my Ubuntu installation will break. Is your script above can be reversed? (I mean if someday I want to delete VirtualBox and all of your settings above, and use eth0 again instead of br0)?
    Thank you,

    Faizal

  21. corinth2489,

    You can reverse the setting of /etc/network/interfaces to the original one and the Ubuntu will run without br0.

    Make sure you backup the file /etc/network/interfaces before doing so.

    Samiux

  22. you rock man!
    your tutorial is even easier than all others I found there on the net.

    now I have a happy Ubuntu – VirtualBox networking :)

    thank you,
    Faizal

  23. corinth2489,

    Thank you very much. :-)

    Samiux

  24. Hi Samiux,

    Thanks for your great tutorial, I managed to bridging the wired networks with my xp clients.And it works flawlessly! Cool.
    And then I tried to connect my intel 3945ABG wireless card to one AP at the office while the cable is still connected.
    I can see the AP and on my gnome network manager is being able to connect the AP and managed to get the IP automatically.
    Both, wired hub and the AP is broadcasting lsit of IP from the same DHCP server so any cleints wired/wirless is supposed to have the same subnet.
    And heres my ifconfig

    khairun@xxxxx:~$ ifconfig
    br0 Link encap:Ethernet HWaddr 00:18:f3:dd:64:08
    inet addr:192.168.0.11 Bcast:192.168.0.255 Mask:255.255.255.0
    inet6 addr: fe80::218:f3ff:fedd:6408/64 Scope:Link
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:135200 errors:0 dropped:0 overruns:0 frame:0
    TX packets:76956 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:15620975 (14.8 MB) TX bytes:53284388 (50.8 MB)

    eth0 Link encap:Ethernet HWaddr 00:18:f3:dd:64:08
    inet6 addr: fe80::218:f3ff:fedd:6408/64 Scope:Link
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:168845 errors:0 dropped:0 overruns:0 frame:0
    TX packets:94659 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:37930880 (36.1 MB) TX bytes:12494548 (11.9 MB)
    Interrupt:16 Base address:0xac00

    eth1 Link encap:Ethernet HWaddr 00:19:d2:8b:66:ae
    inet addr:192.168.0.70 Bcast:192.168.0.255 Mask:255.255.255.0
    inet6 addr: fe80::219:d2ff:fe8b:66ae/64 Scope:Link
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:34032 errors:0 dropped:0 overruns:0 frame:0
    TX packets:211 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:3161268 (3.0 MB) TX bytes:36267 (35.4 KB)

    lo Link encap:Local Loopback
    inet addr:127.0.0.1 Mask:255.0.0.0
    inet6 addr: ::1/128 Scope:Host
    UP LOOPBACK RUNNING MTU:16436 Metric:1
    RX packets:2691 errors:0 dropped:0 overruns:0 frame:0
    TX packets:2691 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:189035 (184.6 KB) TX bytes:189035 (184.6 KB)

    vbox0 Link encap:Ethernet HWaddr 00:ff:a3:9a:fb:a6
    inet6 addr: fe80::2ff:a3ff:fe9a:fba6/64 Scope:Link
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:96404 errors:0 dropped:0 overruns:0 frame:0
    TX packets:177646 errors:0 dropped:2678 overruns:0 carrier:0
    collisions:0 txqueuelen:500
    RX bytes:11280114 (10.7 MB) TX bytes:78418250 (74.7 MB)

    wmaster0 Link encap:UNSPEC HWaddr 00-19-D2-8B-66-AE-00-00-00-00-00-00-00-00-00-00
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:0 errors:0 dropped:0 overruns:0 frame:0
    TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

    But then by the time I unpluged the wired card I lost the whole connection to the server and also internet, it’s mean that the wirless didnt work at all.
    And here’s my detail info on ifconfig again while the cable unpluged..
    khairun@xxxxxx:~$ ifconfig
    br0 Link encap:Ethernet HWaddr 00:18:f3:dd:64:08
    inet addr:192.168.0.11 Bcast:192.168.0.255 Mask:255.255.255.0
    inet6 addr: fe80::218:f3ff:fedd:6408/64 Scope:Link
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:154269 errors:0 dropped:0 overruns:0 frame:0
    TX packets:81605 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:17317684 (16.5 MB) TX bytes:53900855 (51.4 MB)

    eth0 Link encap:Ethernet HWaddr 00:18:f3:dd:64:08
    inet6 addr: fe80::218:f3ff:fedd:6408/64 Scope:Link
    UP BROADCAST MULTICAST MTU:1500 Metric:1
    RX packets:263171 errors:0 dropped:0 overruns:0 frame:0
    TX packets:173878 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:134906421 (128.6 MB) TX bytes:22051930 (21.0 MB)
    Interrupt:16 Base address:0xac00

    eth1 Link encap:Ethernet HWaddr 00:19:d2:8b:66:ae
    inet addr:192.168.0.70 Bcast:192.168.0.255 Mask:255.255.255.0
    inet6 addr: fe80::219:d2ff:fe8b:66ae/64 Scope:Link
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:48857 errors:0 dropped:0 overruns:0 frame:0
    TX packets:301 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:4540989 (4.3 MB) TX bytes:66560 (65.0 KB)

    lo Link encap:Local Loopback
    inet addr:127.0.0.1 Mask:255.0.0.0
    inet6 addr: ::1/128 Scope:Host
    UP LOOPBACK RUNNING MTU:16436 Metric:1
    RX packets:2697 errors:0 dropped:0 overruns:0 frame:0
    TX packets:2697 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:189359 (184.9 KB) TX bytes:189359 (184.9 KB)

    vbox0 Link encap:Ethernet HWaddr 00:ff:a3:9a:fb:a6
    inet6 addr: fe80::2ff:a3ff:fe9a:fba6/64 Scope:Link
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:171008 errors:0 dropped:0 overruns:0 frame:0
    TX packets:267193 errors:0 dropped:2678 overruns:0 carrier:0
    collisions:0 txqueuelen:500
    RX bytes:20216273 (19.2 MB) TX bytes:174717626 (166.6 MB)

    wmaster0 Link encap:UNSPEC HWaddr 00-19-D2-8B-66-AE-00-00-00-00-00-00-00-00-00-00
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:0 errors:0 dropped:0 overruns:0 frame:0
    TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

    Any light to solve this problem is really appreciates.

    Thanks bro…

  25. qirun,

    As far as I know, wireless does not support bridging.

    Samiux

  26. Yes I heard that also, but the things that after I applied the bridging on the br0 seems that my wireless networking it doesn’t work properly. Perhaps it would be different case but I hope you know something about it.
    FYI I just found that the Eth1 is the wireless network. But by the time I unplugged the cable the internet is not working even though I check on the ifconfig that my wireless is having the IP from the DHCP server.
    If you could lead me to similar issue on the net it would be helpful also.

  27. Here the syslog monitor of by the time I connected to the AP:
    Dec 18 17:45:15 ketomedia kernel: [ 1116.965766] eth1: RX authentication from 00:1e:e5:47:92:be (alg=1 transaction=4 status=15)
    Dec 18 17:45:15 ketomedia kernel: [ 1116.965770] eth1: AP denied authentication (auth_alg=1 code=15)
    Dec 18 17:45:16 ketomedia kernel: [ 1117.963217] eth1: authenticate with AP 00:1e:e5:47:92:be
    Dec 18 17:45:16 ketomedia kernel: [ 1117.963249] eth1: privacy configuration mismatch and mixed-cell disabled – disassociate
    Dec 18 17:45:16 ketomedia kernel: [ 1117.965627] eth1: RX authentication from 00:1e:e5:47:92:be (alg=1 transaction=2 status=0)
    Dec 18 17:45:16 ketomedia kernel: [ 1117.965634] eth1: replying to auth challenge
    Dec 18 17:45:16 ketomedia kernel: [ 1117.968083] eth1: RX authentication from 00:1e:e5:47:92:be (alg=1 transaction=2 status=0)
    Dec 18 17:45:16 ketomedia kernel: [ 1117.968090] eth1: unexpected authentication frame (alg=1 transaction=2)
    Dec 18 17:45:16 ketomedia kernel: [ 1117.969417] eth1: RX deauthentication from 00:1e:e5:47:92:be (reason=6)
    Dec 18 17:45:16 ketomedia kernel: [ 1117.970324] eth1: RX authentication from 00:1e:e5:47:92:be (alg=1 transaction=4 status=15)
    Dec 18 17:45:16 ketomedia kernel: [ 1117.970329] eth1: AP denied authentication (auth_alg=1 code=15)
    Dec 18 17:45:17 ketomedia kernel: [ 1118.966799] eth1: authenticate with AP 00:1e:e5:47:92:be
    Dec 18 17:45:17 ketomedia kernel: [ 1118.966834] eth1: privacy configuration mismatch and mixed-cell disabled – disassociate
    Dec 18 17:45:17 ketomedia kernel: [ 1118.968708] eth1: RX deauthentication from 00:1e:e5:47:92:be (reason=6)
    Dec 18 17:45:18 ketomedia kernel: [ 1119.966389] eth1: authenticate with AP 00:1e:e5:47:92:be
    Dec 18 17:45:18 ketomedia kernel: [ 1119.966416] eth1: privacy configuration mismatch and mixed-cell disabled – disassociate
    Dec 18 17:45:18 ketomedia kernel: [ 1120.166313] eth1: authenticate with AP 00:1e:e5:47:92:be
    Dec 18 17:45:18 ketomedia kernel: [ 1120.166343] eth1: privacy configuration mismatch and mixed-cell disabled – disassociate
    Dec 18 17:45:19 ketomedia kernel: [ 1120.366263] eth1: authenticate with AP 00:1e:e5:47:92:be
    Dec 18 17:45:19 ketomedia kernel: [ 1120.366291] eth1: privacy configuration mismatch and mixed-cell disabled – disassociate
    Dec 18 17:45:19 ketomedia kernel: [ 1120.566139] eth1: authentication with AP 00:1e:e5:47:92:be timed out
    Dec 18 17:45:19 ketomedia kernel: [ 1120.566146] eth1: privacy configuration mismatch and mixed-cell disabled – disassociate
    Dec 18 17:45:19 ketomedia kernel: [ 1120.567248] eth1: RX deauthentication from 00:1e:e5:47:92:be (reason=6)
    Dec 18 17:45:20 ketomedia kernel: [ 1122.182565] eth1: privacy configuration mismatch and mixed-cell disabled – disassociate
    Dec 18 17:45:20 ketomedia kernel: [ 1122.184220] eth1: Initial auth_alg=1
    Dec 18 17:45:20 ketomedia kernel: [ 1122.184226] eth1: authenticate with AP 00:1e:e5:47:92:be
    Dec 18 17:45:20 ketomedia kernel: [ 1122.184242] eth1: RX deauthentication from 00:1e:e5:47:92:be (reason=6)
    Dec 18 17:45:20 ketomedia kernel: [ 1122.185073] eth1: Initial auth_alg=1
    Dec 18 17:45:20 ketomedia kernel: [ 1122.185077] eth1: authenticate with AP 00:1e:e5:47:92:be
    Dec 18 17:45:20 ketomedia kernel: [ 1122.188403] eth1: RX authentication from 00:1e:e5:47:92:be (alg=1 transaction=2 status=0)
    Dec 18 17:45:20 ketomedia kernel: [ 1122.188407] eth1: replying to auth challenge
    Dec 18 17:45:20 ketomedia kernel: [ 1122.190149] eth1: RX authentication from 00:1e:e5:47:92:be (alg=1 transaction=4 status=0)
    Dec 18 17:45:20 ketomedia kernel: [ 1122.190154] eth1: authenticated
    Dec 18 17:45:20 ketomedia kernel: [ 1122.190157] eth1: associate with AP 00:1e:e5:47:92:be
    Dec 18 17:45:20 ketomedia NetworkManager: Supplicant state changed: 1
    Dec 18 17:45:20 ketomedia NetworkManager: Activation (eth1/wireless) Stage 2 of 5 (Device Configure) successful. Connected to access point ‘CPI-LINKNET’.
    Dec 18 17:45:20 ketomedia NetworkManager: Activation (eth1) Stage 3 of 5 (IP Configure Start) scheduled.
    Dec 18 17:45:20 ketomedia NetworkManager: Activation (eth1) Stage 3 of 5 (IP Configure Start) started…
    Dec 18 17:45:20 ketomedia kernel: [ 1122.191831] eth1: RX AssocResp from 00:1e:e5:47:92:be (capab=0x411 status=0 aid=1)
    Dec 18 17:45:20 ketomedia kernel: [ 1122.191837] eth1: associated
    Dec 18 17:45:20 ketomedia kernel: [ 1122.191878] eth1: WMM queue=2 aci=0 acm=0 aifs=3 cWmin=15 cWmax=1023 burst=0
    Dec 18 17:45:20 ketomedia kernel: [ 1122.191882] eth1: WMM queue=3 aci=1 acm=0 aifs=7 cWmin=15 cWmax=1023 burst=0
    Dec 18 17:45:20 ketomedia kernel: [ 1122.191885] eth1: WMM queue=1 aci=2 acm=0 aifs=2 cWmin=7 cWmax=15 burst=30
    Dec 18 17:45:20 ketomedia kernel: [ 1122.191888] eth1: WMM queue=0 aci=3 acm=0 aifs=2 cWmin=3 cWmax=7 burst=15
    Dec 18 17:45:20 ketomedia kernel: [ 1122.193249] ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
    Dec 18 17:45:20 ketomedia kernel: [ 1122.196842] eth1: association frame received from 00:1e:e5:47:92:be, but not in associate state – ignored
    Dec 18 17:45:20 ketomedia kernel: [ 1122.197750] eth1: association frame received from 00:1e:e5:47:92:be, but not in associate state – ignored
    Dec 18 17:45:22 ketomedia avahi-daemon[5541]: Registering new address record for fe80::219:d2ff:fe8b:66ae on eth1.*.
    Dec 18 17:45:22 ketomedia NetworkManager: Activation (eth1) Beginning DHCP transaction.
    Dec 18 17:45:22 ketomedia dhclient: There is already a pid file /var/run/dhclient.eth1.pid with pid 134519072
    Dec 18 17:45:22 ketomedia dhclient: wmaster0: unknown hardware address type 801
    Dec 18 17:45:22 ketomedia NetworkManager: Activation (eth1) Stage 3 of 5 (IP Configure Start) complete.
    Dec 18 17:45:22 ketomedia NetworkManager: DHCP daemon state is now 12 (successfully started) for interface eth1
    Dec 18 17:45:23 ketomedia NetworkManager: DHCP daemon state is now 1 (starting) for interface eth1
    Dec 18 17:45:23 ketomedia dhclient: wmaster0: unknown hardware address type 801
    Dec 18 17:45:25 ketomedia NetworkManager: Old device ‘eth1’ activating, won’t change.
    Dec 18 17:45:27 ketomedia dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 3
    Dec 18 17:45:27 ketomedia dhclient: DHCPOFFER of 192.168.0.70 from 192.168.0.1
    Dec 18 17:45:27 ketomedia dhclient: DHCPREQUEST of 192.168.0.70 on eth1 to 255.255.255.255 port 67
    Dec 18 17:45:27 ketomedia dhclient: DHCPACK of 192.168.0.70 from 192.168.0.1
    Dec 18 17:45:27 ketomedia avahi-daemon[5541]: Joining mDNS multicast group on interface eth1.IPv4 with address 192.168.0.70.
    Dec 18 17:45:27 ketomedia avahi-daemon[5541]: New relevant interface eth1.IPv4 for mDNS.
    Dec 18 17:45:27 ketomedia avahi-daemon[5541]: Registering new address record for 192.168.0.70 on eth1.IPv4.
    Dec 18 17:45:27 ketomedia NetworkManager: DHCP daemon state is now 2 (bound) for interface eth1
    Dec 18 17:45:27 ketomedia NetworkManager: Activation (eth1) Stage 4 of 5 (IP Configure Get) scheduled…
    Dec 18 17:45:27 ketomedia NetworkManager: Activation (eth1) Stage 4 of 5 (IP Configure Get) started…
    Dec 18 17:45:27 ketomedia dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth1 for sub-path eth1.dbus.get.host_name
    Dec 18 17:45:27 ketomedia dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth1 for sub-path eth1.dbus.get.nis_domain
    Dec 18 17:45:27 ketomedia dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth1 for sub-path eth1.dbus.get.nis_servers
    Dec 18 17:45:27 ketomedia NetworkManager: Retrieved the following IP4 configuration from the DHCP daemon:
    Dec 18 17:45:27 ketomedia NetworkManager: address 192.168.0.70
    Dec 18 17:45:27 ketomedia NetworkManager: netmask 255.255.255.0
    Dec 18 17:45:27 ketomedia NetworkManager: broadcast 192.168.0.255
    Dec 18 17:45:27 ketomedia NetworkManager: gateway 192.168.0.2
    Dec 18 17:45:27 ketomedia NetworkManager: nameserver 192.168.0.1
    Dec 18 17:45:27 ketomedia NetworkManager: nameserver 192.168.0.2
    Dec 18 17:45:27 ketomedia NetworkManager: domain name ‘JGDML350.JGD2’
    Dec 18 17:45:27 ketomedia dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth1 for sub-path eth1.dbus.get.interface_mtu
    Dec 18 17:45:27 ketomedia NetworkManager: Activation (eth1) Stage 5 of 5 (IP Configure Commit) scheduled…
    Dec 18 17:45:27 ketomedia NetworkManager: Activation (eth1) Stage 4 of 5 (IP Configure Get) complete.
    Dec 18 17:45:27 ketomedia NetworkManager: Activation (eth1) Stage 5 of 5 (IP Configure Commit) started…
    Dec 18 17:45:27 ketomedia dhclient: bound to 192.168.0.70 — renewal in 231835 seconds.
    Dec 18 17:45:27 ketomedia avahi-daemon[5541]: Withdrawing address record for 192.168.0.70 on eth1.
    Dec 18 17:45:27 ketomedia avahi-daemon[5541]: Leaving mDNS multicast group on interface eth1.IPv4 with address 192.168.0.70.
    Dec 18 17:45:27 ketomedia avahi-daemon[5541]: Interface eth1.IPv4 no longer relevant for mDNS.
    Dec 18 17:45:27 ketomedia avahi-daemon[5541]: Withdrawing address record for fe80::219:d2ff:fe8b:66ae on eth1.
    Dec 18 17:45:27 ketomedia avahi-daemon[5541]: Joining mDNS multicast group on interface eth1.IPv4 with address 192.168.0.70.
    Dec 18 17:45:27 ketomedia avahi-daemon[5541]: New relevant interface eth1.IPv4 for mDNS.
    Dec 18 17:45:27 ketomedia avahi-daemon[5541]: Registering new address record for 192.168.0.70 on eth1.IPv4.
    Dec 18 17:45:28 ketomedia NetworkManager: Clearing nscd hosts cache.
    Dec 18 17:45:28 ketomedia NetworkManager: nm_spawn_process(): nm_spawn_process(‘/usr/sbin/nscd -i hosts’): could not spawn process. (Failed to execute child process “/usr/sbin/nscd” (No such file or directory))
    Dec 18 17:45:28 ketomedia NetworkManager: Activation (eth1) successful, device activated.
    Dec 18 17:45:28 ketomedia NetworkManager: [1229593528.263505] nm_dbus_signal_filter(): NetworkManagerInfo triggered update of wireless network ‘CPI-LINKNET’
    Dec 18 17:45:28 ketomedia NetworkManager: Activation (eth1) Finish handler scheduled.
    Dec 18 17:45:28 ketomedia NetworkManager: Activation (eth1) Stage 5 of 5 (IP Configure Commit) complete.
    Dec 18 17:45:29 ketomedia avahi-daemon[5541]: Registering new address record for fe80::219:d2ff:fe8b:66ae on eth1.*.
    Dec 18 17:45:30 ketomedia ntpdate[18344]: adjust time server 91.189.94.4 offset 0.016464 sec
    Dec 18 17:45:38 ketomedia kernel: [ 1139.922427] eth1: no IPv6 routers present

    I hope that I’m not flooding your comments section, If you want you can just delete if you think you have enough information even though you dont have any answer for me.

    Cheers

  28. qirun,

    I would like to know that what chipset of your wireless card or the brand name of the wireless card is? Furthermore, does br0 of your wireless card be bridged or not?

    Thanks for your information.

    Samiux

  29. Hi Samiux, the wireless card is the intel 3945ABG, I’m not planning to try the bridging for the wireless card for the moment as still I couldnt have an access to the network and the interent while I’m on the Access Point.
    As you can see below I managed to get automatic IP from my DHCP server but when I tried to pinging the network or the internet it it looks like got forwarded to the br0.

    Dec 18 17:45:27 ketomedia NetworkManager: Retrieved the following IP4 configuration from the DHCP daemon:
    Dec 18 17:45:27 ketomedia NetworkManager: address 192.168.0.70
    Dec 18 17:45:27 ketomedia NetworkManager: netmask 255.255.255.0
    Dec 18 17:45:27 ketomedia NetworkManager: broadcast 192.168.0.255
    Dec 18 17:45:27 ketomedia NetworkManager: gateway 192.168.0.2
    Dec 18 17:45:27 ketomedia NetworkManager: nameserver 192.168.0.1
    Dec 18 17:45:27 ketomedia NetworkManager: nameserver 192.168.0.2
    Dec 18 17:45:27 ketomedia NetworkManager: domain name ‘JGDML350.JGD2′

  30. Hi Samiux, dont bother to find the solution as the problem was resolved by the time I update the distribution.

    Cheers…

  31. Samiux, I’m using this under Ubuntu 8.10 without much of a problem. very happy that networking is finally working under virtual box.

    however, I have a problem. occasionally, my network just drops. I’m not certain why. I can ping 172.24.2.1 (I am 172.24.2.9) and that’s about it. pinging google, or even pinging farther along my network (ie 172.24.0.18) results in nothing. I have to rerun all of the comands and restart my virtualXP to get everything working. any clue why this might be happening?

    -Trab

  32. wordpress1232,

    I have no idea. I think you have to double check the cable that connect to the host and make sure that host computer is rebooted after configured the bridging on the host.

    Samiux

  33. the cable is fine, it doesn’t even say cable disconnected, and the host can still ping it’s gateway (and DNS/DHCP server). I never restarted after setting this up…generally I don’t restart ubuntu unless I’m adding hardware, but that could do something. I’ll try that next time it comes up.

Leave a Reply

Please log in using one of these methods to post your comment:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: