Actually, the intention of my message was to say that these tricks are NOT necessary under VirtualBox 2.1.x and in fact, are counter-productive. The most I would consider doing is adding bridge support utilities.
I was also suggesting that the feature completeness of various network device drivers under Linux may be at the core of the problem for users who are unsuccessful at getting host networking to work properly. Now with that said, a good test might be to go back to 2.0.x while deploying the tricks as I described them. If they work with 2.0.x, then it might be an interesting indicator. Jeremiah Jester さんは書きました: > Daniel, > > Sorry, I called you Larry in my last message. > > I tried the steps via the command line and it created the following > 'ifconfig' output. > > r...@ubuntu:~# ifconfig > br0 Link encap:Ethernet HWaddr 00:08:74:a3:b1:6d > inet addr:10.139.68.42 Bcast:10.139.68.255 Mask:255.255.255.0 > inet6 addr: fe80::208:74ff:fea3:b16d/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:173 errors:0 dropped:0 overruns:0 frame:0 > TX packets:55 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:21869 (21.3 KB) TX bytes:11149 (10.8 KB) > > eth0 Link encap:Ethernet HWaddr 00:08:74:a3:b1:6d > inet6 addr: fe80::208:74ff:fea3:b16d/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:1382 errors:0 dropped:0 overruns:0 frame:0 > TX packets:765 errors:1 dropped:0 overruns:0 carrier:1 > collisions:137 txqueuelen:100 > RX bytes:870571 (850.1 KB) TX bytes:135109 (131.9 KB) > Base address:0xecc0 Memory:ff8e0000-ff900000 > > 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:3024 errors:0 dropped:0 overruns:0 frame:0 > TX packets:3024 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:151200 (147.6 KB) TX bytes:151200 (147.6 KB) > > tap0 Link encap:Ethernet HWaddr 00:ff:2e:b5:d1:6b > inet6 addr: fe80::2ff:2eff:feb5:d16b/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:6 overruns:0 carrier:0 > collisions:0 txqueuelen:500 > RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) > > > Look right? > > Might /etc/network/interfaces file looks like this: > > auto lo > iface lo inet loopback > > auto eth0 > iface eth0 inet dhcp > > #auto br0 > #iface br0 inet dhcp > #bridge_ports eth0 > > > Networking in the Guest OS (jeos/ubuntu as well) still doesn't recognize any > devices other than 'lo'. I've tried NAT and Host Interface - no dice. Am also > unable to bring up eth0 - complains that "no device exists". > > Thoughts? > > Thanks, > JJ > > > > > -----Original Message----- > From: [email protected] on behalf of Daniel Hauck > Sent: Tue 1/6/2009 2:10 PM > To: VirtualBox end user list > Subject: Re: [vbox-users] VB 2.1.0 Linux - Host Interface Bridging notworking > > The tricks I refer to are the ones including the the added scripting in > rc.local that contains: > > brctl addbr br0 > ifconfig eth0 0.0.0.0 > brctl addif br eth0 > dhclient br0 > VBoxInterface=`VBoxTunctl -b -u username` > ifconfig $VBoxInterface up > brctl addif br0 $VBoxInterface > > Also, ensuring that bridging utilities are installed on your machine was > another important trick... I never removed them and perhaps they still > have a role and are needed for things to work? > > Jeremiah Jester ????????: >> Larry, >> >> Thanks for the reply. >> >> What 'tricks' did you try? I and I'm sure others would be interested. >> >> Thanks, >> JJ >> >> >> -----Original Message----- >> From: [email protected] on behalf of Daniel Hauck >> Sent: Tue 1/6/2009 1:31 PM >> To: VirtualBox end user list >> Subject: Re: [vbox-users] VB 2.1.0 Linux - Host Interface Bridging notworking >> >> The only trouble I had with it was not realizing that everything "just >> worked." I had to do some tricks with the 2.0.x series to allow for >> bridged networking to work and I blindly assumed the same thing with >> 2.1.x. It didn't work and then I pulled all the tricks out and >> magically, bridged networking worked. >> >> But I will offer this: I have noticed that under Linux, different >> network devices offer up different levels of functionality. Some will >> facilitate modes that others do not yet support. Some of this has >> everything to do with the firmware associated with the hardware. >> >> If you are using a machine that will allow you to use different means or >> methods to add different networking hardware, I would suggest trying >> additional bits to see if those work better for you. >> >> Larry Riedel ????????: >>>> Just curios,, Is anybody else having this problem. >>>> I've ran into one other person on the forums.... not >>>> getting much help from VB support folks. >>> I only read vbox-users; it seems like some people are >>> having problems with bridged mode networking in 2.1.0, >>> and no solutions or workarounds have been posted. I >>> am waiting for the next 2.1.x release because I get the >>> impression 2.1.0 has significant problems. >>> >>> >>> Larry >>> >>> _______________________________________________ >>> vbox-users mailing list >>> [email protected] >>> http://vbox.innotek.de/mailman/listinfo/vbox-users >>> >> >> _______________________________________________ >> vbox-users mailing list >> [email protected] >> http://vbox.innotek.de/mailman/listinfo/vbox-users >> >> >> >> >> >> Disclaimer: The information contained in this transmission, including any >> attachments, may contain confidential information of Panasonic Avionics >> Corporation. This transmission is intended only for the use of the >> addressee(s) listed above. Unauthorized review, dissemination or other use >> of the information contained in this transmission is strictly prohibited. >> If you have received this transmission in error or have reason to believe >> you are not authorized to receive it, please notify the sender by return >> email and promptly delete the transmission. >> >> >> >> _______________________________________________ >> vbox-users mailing list >> [email protected] >> http://vbox.innotek.de/mailman/listinfo/vbox-users >> > > > _______________________________________________ > vbox-users mailing list > [email protected] > http://vbox.innotek.de/mailman/listinfo/vbox-users > > > > _______________________________________________ > vbox-users mailing list > [email protected] > http://vbox.innotek.de/mailman/listinfo/vbox-users > _______________________________________________ vbox-users mailing list [email protected] http://vbox.innotek.de/mailman/listinfo/vbox-users
