I'm running VB under Jeos (ubuntu) 8.04 and have VB 2.1.0 installed.
I'm trying to get bridging working so that I can use a public ip space ip in VB. The VB manual tells me that with VB 2.1.0 that all i need to do i s select 'Host Interface' and simply select one of my active net devices, currently 'eth0', for bridging.
However, when i boot into linux in VB, all i get is the 'lo' device. Attempts to bring up eth0 fail via 'sudo ifup eth0' w/ error message "No such device".
Thoughts?
Thanks!
JJ
VB 2.1.0 Linux - Host Interface Bridging not working
Re: VB 2.1.0 Linux - Host Interface Bridging not working
Same in my case, where host is Ubuntu 8.10 and guest is WinXP. I selected "eth0" as host interface, but under windows there's no networking...
let me know...
...if you figure it out. I'm still searching for the fix.
Re: let me know...
well anyway I can tell you that I tried port forwarding as well, didn't worked either.jeremiahj wrote:...if you figure it out. I'm still searching for the fix.
I downgraded to 2.0.6 as it seems to be known bug in 2.1.0, later I compiled the latest SVN version but none of this worked properly ...
-
sej7278
- Volunteer
- Posts: 1003
- Joined: 5. Sep 2008, 14:40
- Primary OS: Debian other
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Solaris, Linux, Windows, OS/2, MacOSX, FreeBSD
- Contact:
ah come on, it was pretty funny!migajek wrote:not funnysej7278 wrote:time to switch to a real distro?
Actually, VB is listening on the proper port for sure, checked it.
what do you mean proper port - there's no port to listen on, do you mean interface?
your eth0 isn't a wireless card is it, as that probably won't work, if its wired is the cable connected (to a switch/hub/router/whatever)?
which model card did you select - the intel 1000's i have no problem with, only ever use pcnet for old windows pre-xp.
-
Sasquatch
- Volunteer
- Posts: 17798
- Joined: 17. Mar 2008, 13:41
- Primary OS: Debian other
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Windows XP, Windows 7, Linux
- Location: /dev/random
Do you have a valid config for eth0 in your VM? Do you even have an ethernet device in the VM? Do an ifconfig -a to see them, or lshw -C network. An lspci will also reveal any network devices.
Read the Forum Posting Guide before opening a topic.
VirtualBox FAQ: Check this before asking questions.
Online User Manual: A must read if you want to know what we're talking about.
Howto: Install Linux Guest Additions
Howto: Use Shared Folders on Linux Guest
See the Tutorials and FAQ section at the top of the Forum for more guides.
Try searching the forums first with Google and add the site filter for this forum.
E.g. install guest additions site:forums.virtualbox.org
Retired from this Forum since OSSO introduction.
VirtualBox FAQ: Check this before asking questions.
Online User Manual: A must read if you want to know what we're talking about.
Howto: Install Linux Guest Additions
Howto: Use Shared Folders on Linux Guest
See the Tutorials and FAQ section at the top of the Forum for more guides.
Try searching the forums first with Google and add the site filter for this forum.
E.g. install guest additions site:forums.virtualbox.org
Retired from this Forum since OSSO introduction.
1. nope, downgrading didn't workedSasquatch wrote:Do you have a valid config for eth0 in your VM? Do you even have an ethernet device in the VM? Do an ifconfig -a to see them, or lshw -C network. An lspci will also reveal any network devices.
2. I checked the port on which VirtualBox was supposed to listen and forward to it's Guest
3. eth0 is wired connection
4. the guest is winxp so there's nothing to configure I guess?
Thank you very muchsej7278 wrote:did you try a different ethernet card - e1000 instead of pcnet3?
It did resolved the problem - I selected the pro/1000, downloaded the drivers installed and now the port forwarding works.
However, I run into some strange problem (which fortunately is very easy to resolve)
If I ran the listening app under guest from the shared directory (yes, I did downloaded the windows program under linux, and copied it into the shared directory, than ran from guest os which is windows xp!) it simply doesn't work. It does not handle the port forwarding. However, if I copy the same app to my guest OS drive (virtualized drive) and run - it works fine... that is quite strange, but proven in my case (I did tried with many apps listening for TCP)
On last week I had many version vbox on my Ubuntu 8.10 to repair networking: 2.0.4-ose, 2.1 standalone from script, 2.1 from deb.migajek wrote:Thank you very muchsej7278 wrote:did you try a different ethernet card - e1000 instead of pcnet3?
It did resolved the problem - I selected the pro/1000, downloaded the drivers installed and now the port forwarding works.
However, I run into some strange problem (which fortunately is very easy to resolve)
At beggining and remove virtualbox-ose-2.0.4 and install 2.1 standalone windows networking works (with intel pro selected in settings) but i cant reproduce this working sittuation. What I can monitor problem ?
Now I tested on home router and vbox networking in xp works. I must ask network administrator why there are problem at work router (one time xp in vbox get ip but onlny one time per 30 ! ) Have you some suggession ?skajotde wrote: At beggining and remove virtualbox-ose-2.0.4 and install 2.1 standalone windows networking works (with intel pro selected in settings) but i cant reproduce this working sittuation. What I can monitor problem ?