Networking Conflict Between Virtual Box Network Bridge & OpenSSH Server, Debian Etch
Hello;
I am running an AMD64 3300+ on an Epox motherboard with 1 Gig of Ram. the OS is 32 bit Debian Etch, upgraded to Kernel 2.6.23-1-i486. I am running two programs that are conflicting. One, Innotek VirtualBox. I have a number of virtual machines including Windows and Linux OS's. I use them for experimentation, studying, and the occasional Windows App. (Haven't gotten to WINE) they require internet and network support. Both to get online as well as to share my Data Drives on the Host OS. I refuse to let windows have direct control over any of my data hard drives, it likes to foul up drives. anyway, None of the virtual machines run at the same time, and I accomplished networking via a Network Bridge to the Host eth0. the following is from my /etc/network/interfaces file. the virtual Ethernet drive vbox0 is pointed to the network bridge (br0) via a configuration in virtual box itself. Quote:
Thank you for your time; Tim Quote:
|
I'm playing around in the dark a little here, but try this, obviously keeping a backup of your interfaces file!
Change bolded parts: Quote:
Code:
# The primary network interface |
No Dice
alright, No Dice...
I made the changes you suggested, Pulling IP address 192.168.2.116 for br0 (I am using numbers 115 and 116 because there are other systems on our network that pull dynamic IP's, but not 15 of them. since IP's are usually assigned by the router sequentially, I am pulling static IP's above the pool) anyway, I configured, did a /etc/init.d/network restart. br0 pulled the IP as shown by ifconfig, but same as usual, SSH worked (had the br0 commented out before) and the Virtual machines refused to pull an IP. I rebooted, the virtual machines network lit up like a Christmas tree, but SSH would no longer respond. Interestingly though, the br0 pulled IP 116, but the VM's where pulling dynamic address 104, and 107. I set it to static 116, rebooted everything and they wouldn't communicate anymore. I reset it to dynamic and it lit up again. almost like it was having an IP conflict with itself, or it's own interface / bridge at least. I tested the settings on both VM's running MS XP Professional, and Vista Ultimate. Unfortunately My SUSE 10 VM is refusing to boot and giving me some really annoying error that I don't have the patience for at the moment. but I'm sure it would behave the same. |
Hmm, at this stage it's beyond my knowledge level I'm afraid.
On the other hand, some other people have done this kinda thing before, take a look at this: http://samiux.wordpress.com/2007/07/...on-virtualbox/ and more complex: http://en.opensuse.org/Virtualbox_Network_Bridging and from VirtualBox: http://forums.virtualbox.org/viewtopic.php?t=1787 |
I have been using VirtualBox 2.0.4 OSE with a Win98 virtual machine. To get the Win98 virtual machine to network with the host Linux system I needed to use host networking in VirtualBox, but this did not allow for internet access from the virtual machine. I then added a proxy server (tinyproxy) to my host system and configured my virtual machine to use the proxy server. Now I have both networking and internet access for the virtual machine.
|
All times are GMT -5. The time now is 08:31 PM. |