Results 1 to 7 of 7
Hi everyone!
I decided to write in this section because my guest OS on VirtualBox is Fedora, and I need to configuring the internal network in order to communicate with ...
- 04-29-2011 #1Just Joined!
- Join Date
- Apr 2011
- Posts
- 38
Virtual Box internal network
Hi everyone!
I decided to write in this section because my guest OS on VirtualBox is Fedora, and I need to configuring the internal network in order to communicate with another guest running Mandriva (actually I don't succeed in configuring the network on Mandriva too). I configured VirtualBox (host OS is Ubuntu) from the graphical interface as follows:
Linux Fedora (VM) -> Settings -> Network -> Board 2 (the first is used with NAT) ->
Connected to: Internal Network
Name: intnet
To use DHCP I also used the command
$ VBoxManage dhcpserver add ...
but I accept also a suggestion for static configuration.
When I run Fedora now I can see two network interfaces (eth0 e eth1): the first connect Fedora to Ubuntu, the second should be my internal network (right?! I'm not sure about this). DHCP server doesn't seem to work, and I don't know how I can configure the network in a static way...
Any suggestions? Thank you!
Greetings from Italy.
- 04-30-2011 #2Linux Guru
- Join Date
- Apr 2009
- Location
- I can be found either 40 miles west of Chicago, or in a galaxy far, far away.
- Posts
- 8,974
I always configure my VM's with a bridged network adapter, instead of the internal network option. That way, the VM is visible on my LAN and I can access it from any other local system, including other VM's.
Sometimes, real fast is almost as good as real time.
Just remember, Semper Gumbi - always be flexible!
- 05-01-2011 #3Just Joined!
- Join Date
- Apr 2011
- Posts
- 38
Thank you! This way everything goes ok... even if I'm still interested in understanding how internal network works!
Bye
- 05-01-2011 #4Linux Guru
- Join Date
- Apr 2009
- Location
- I can be found either 40 miles west of Chicago, or in a galaxy far, far away.
- Posts
- 8,974
The internal network allows your virtual machines to be totally isolated from your other LAN, with the host system acting as a router/gateway. If you want to access other LAN resources from a VM inside the internal network, then you will have to adjust the host's routing table, and possibly that of the VM as well.
Sometimes, real fast is almost as good as real time.
Just remember, Semper Gumbi - always be flexible!
- 05-01-2011 #5Just Joined!
- Join Date
- Apr 2011
- Posts
- 38
How can I set the host's routing table? And that of the VM?
This way the problem is moving to Ubuntu, right?
- 05-02-2011 #6Just Joined!
- Join Date
- Sep 2010
- Location
- Dhaka, Bangladesh
- Posts
- 29
I also prefer bridged mode, this way I don't have difficulties adding the VM to the LAN and it takes second to setup.
Before moving on to Host machines routing table, first make sure you can ping one another successfully i.e. VM and host.
Static routes can be added using the following command
adds a route to the local network 192.168.10.x via "eth0".route add -net 192.168.10.0 netmask 255.255.255.0 dev eth0
Please add the routes on the network as per your requirements.
These routes may be temporary. To make them permanent, try adding them to a file named 'routes' in /etc/network/route. (I'm not sure about Ubuntu)
- 05-03-2011 #7Just Joined!
- Join Date
- Apr 2011
- Posts
- 38
Really thank you!


Reply With Quote