Re: [Hampshire] Bridging networks on Ubuntu 7.10

Top Page

Reply to this message
Author: John Hunt
Date:  
To: Hampshire LUG Discussion List
Subject: Re: [Hampshire] Bridging networks on Ubuntu 7.10
I thought it might help if I cleared out my network configuration and
started fresh based off the guide in the VirtualBox user manual.

Appended to the bottom of this email I've added as much info as I think
anyone can take.

Basically, I made sure everything was 'normal', no weird bridges or tap
networks set up before I started. I've logged the status of pretty much
everything before and after following the pdf guide from the virtualbox
site.

I chose to use the tun/tap method of setting it all up rather than
VBoxAddIf method (an alternate step 4.)

To summarise, the VM (nitrogen) had full access to the host (feeg), and
feeg had full access to nitrogen. However, nitrogen had no connectivity
outside of feeg whatsoever.

---

* Current network setup:
The laptop (feeg) has ipw2200 and a standard 10/100 ethernet card and is
running a clean install of xubuntu 7.10. The wireless card is up, the
ethernet is down. 192.168.1.1 is my wireless router and we'll use that
for pinging.

I have a second machine argon which we can use for pinging the VM from
which is also on the same wireless network.

The virtual machine is debian etch under the latest(ish?) stable release
of virtualbox (v1.56) This is a fresh net-install with nothing but the
base system installed. The VM is called nitrogen.

* What I'm trying to do:
Get the virtual machine on the wireless network using bridged networking
rather than NAT so I can run servers on it. Nothing complex, I just want
to give it an IP that can be accessed from the rest of the network.

* Before starting, feeg's network config was like this (and had fully
working network/internet connectivity):
john@feeg:~$ ifconfig
eth1      Link encap:Ethernet  HWaddr 00:12:F0:B6:67:38  
          inet addr:192.168.1.3  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::212:f0ff:feb6:6738/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:49 errors:0 dropped:0 overruns:0 frame:0
          TX packets:36 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:1568 (1.5 KB)  TX bytes:4433 (4.3 KB)
          Interrupt:11 Base address:0x2000 Memory:d0200000-d0200fff 


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:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)


Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use
Iface
192.168.1.0     *               255.255.255.0   U     0      0        0
eth1
link-local      *               255.255.0.0     U     1000   0        0
eth1
ifconfig
default         192.168.1.1     0.0.0.0         UG    100    0        0
eth1


* After following the guide and restarting networking (and logging
out/in), the network configuration looked like this, and these are the
facts:
- 192.168.1.1 (wireless router) is pingable from feeg
- feeg is pingable from argon
- nitrogen is pingable from feeg
- feeg (192.168.1.3) is pingable from nitrogen(the VM)
- router/argon are not pingable from nitrogen

nitrogen is set up as follows:
static config:
IP: 192.168.1.20
subnet: 255.255.255.0
gateway: 192.168.1.1

br0       Link encap:Ethernet  HWaddr 00:12:F0:B6:67:38  
          inet addr:192.168.1.3  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::212:f0ff:feb6:6738/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:17 errors:0 dropped:0 overruns:0 frame:0
          TX packets:32 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:2070 (2.0 KB)  TX bytes:4837 (4.7 KB)


eth1      Link encap:Ethernet  HWaddr 00:12:F0:B6:67:38  
          inet6 addr: fe80::212:f0ff:feb6:6738/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:100 errors:0 dropped:2 overruns:0 frame:0
          TX packets:40 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:17979 (17.5 KB)  TX bytes:24255 (23.6 KB)
          Interrupt:11 Base address:0x2000 Memory:d0200000-d0200fff 


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:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)


tap0      Link encap:Ethernet  HWaddr 00:FF:96:97:AC:7E  
          inet6 addr: fe80::2ff:96ff:fe97:ac7e/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:33 overruns:0 carrier:0
          collisions:0 txqueuelen:500 
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)


Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use
Iface
192.168.1.0     *               255.255.255.0   U     0      0        0
br0
link-local      *               255.255.0.0     U     1000   0        0
br0
default         192.168.1.1     0.0.0.0         UG    100    0        0
br0



Phewph!

Thanks for your help guys, I *know* we'll crack this one somehow!

John.

--
John Hunt - johnrhunt@???
http://john-hunt.com/