virtual box networking

fakie_flip · 10-21-2007, 02:46 AM

How can I configure this? I want to use it instead of NAT.

http://img296.imageshack.us/img296/8...ettingsch6.png

acid_kewpie · 10-21-2007, 03:14 AM

what's that picture got to do with anything... doesn't seem to relate to virtual box in any way... i guess you probably want a bridged network, so 5 seconds on google gives me this... http://www.virtualbox.org/wiki/Automatic_Bridge_Ubuntu which should help.

fakie_flip · 10-21-2007, 11:16 AM

I want to be able to ssh or ping from my host os to the guest os. Bridge shouldn't be required for that, so why am I not able to ping or ssh when using NAT?

acid_kewpie · 10-21-2007, 11:32 AM

if this is between the host and the guest, then NAT isn't even going to be involved. they both have an ip on a seperate private network. do they have suitable addresses on both operating systems?

fakie_flip · 10-21-2007, 11:47 AM

This is what I mean.

http://img48.imageshack.us/img48/916...orking2xe5.png

http://img48.imageshack.us/img48/722/networkingkr4.png

acid_kewpie · 10-21-2007, 11:54 AM

i'd really reather you actually explained things that provide screenshots with little context... anyway. so on the ubuntu host box there should be another network adapter which is also on 10.0.2.0/24. then the machiens will be able to hit each other on a private network inside your single bit of tin. the NAT side then comes into play when and internal machine wants to get out pastr the host system, so the host system then NAT's the IP packets to it's own external ip address.

fakie_flip · 10-21-2007, 11:57 AM

Should I change the subnet mask on the guest to be the same as the host?

fakie_flip · 10-21-2007, 12:01 PM

Quote:

Originally Posted by acid_kewpie

so on the ubuntu host box there should be another network adapter which is also on 10.0.2.0/24.

No, there's not. Here's what I have on the Ubuntu host.

Code:

$ sudo ifconfig 
eth0      Link encap:Ethernet  HWaddr 00:14:2A:BD:89:A2  
          inet addr:192.168.1.102  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::214:2aff:febd:89a2/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:4664862 errors:10 dropped:0 overruns:0 frame:10
          TX packets:4677190 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:3348243647 (3.1 GB)  TX bytes:561228538 (535.2 MB)
          Interrupt:20 Base address:0xa000 

eth1      Link encap:Ethernet  HWaddr 00:C0:26:7D:4C:DF  
          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:17 Base address:0x6000 

ham0      Link encap:Ethernet  HWaddr 00:FF:1B:16:81:EB  
          inet addr:5.181.26.158  Bcast:5.255.255.255  Mask:255.0.0.0
          UP BROADCAST RUNNING MULTICAST  MTU:1200  Metric:1
          RX packets:23628 errors:0 dropped:0 overruns:0 frame:0
          TX packets:44716 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:500 
          RX bytes:1654437 (1.5 MB)  TX bytes:54219615 (51.7 MB)

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:52492 errors:0 dropped:0 overruns:0 frame:0
          TX packets:52492 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:2738673 (2.6 MB)  TX bytes:2738673 (2.6 MB)

vmnet8    Link encap:Ethernet  HWaddr 00:50:56:C0:00:08  
          inet addr:192.168.106.1  Bcast:192.168.106.255  Mask:255.255.255.0
          inet6 addr: fe80::250:56ff:fec0:8/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:85 errors:0 dropped:0 overruns:0 frame:0
          TX packets:78 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

fakie_flip · 10-21-2007, 12:16 PM

Does that mean I must used bridge networking?

acid_kewpie · 10-21-2007, 12:42 PM

where did the 10.0.2.0/24 network come from in the first place? you have vmnet8, which is the NAT virtual NIC on the host in 192.168.160.0/24, so your guests should also be in that network.

fakie_flip · 10-21-2007, 01:52 PM

vmnet8 is a virtual nic created by vmware server. In other words, you are saying that I could network VMware Server and Virtualbox together. Screw Virtualbox. I'm removing it and using VMware Server instead.