--- David Murphy <[EMAIL PROTECTED]> wrote:
> Hi folks. I have the following setup:
>
> - Broadband router (CompUSA-branded cheapy) running DHCP
> - PC running OpenSUSE 10.2
> - VirtualBox 1.3.8 VM with Windows 2000 Pro
>
> I'm trying to set up the VM's network via bridging, a la section 5.3.3.2
> of
> the user manual. I run the following commands as root:
>
> # tunctl -t tap1 -u <my username>
> # brctl addbr br0
> (At this point I kill dhcpcd to avoid problems DHCPing the bridge)
> # ifconfig eth0 0.0.0.0 promisc
> # brctl addif br0 eth0
> # dhclient br0
> # brctl addif br0 tap1
> # ifconfig tap1 up
>
> At this point my host is talking to the router again just fine.
> 'ifconfig'
> and 'brctl show br0' show what I would expect. I then went into the Win2k
> VM's settings and changed the Network Adapter 0 setup to "Host
> Interface",
> Interface Name "tap1", Setup and Terminate Applications blank.
>
> When I boot up the guest, though, it's not getting configured. The
> network
> interface exists and is set to DHCP, but after trying for a bit, it fails
> out and comes up with one of those autoconfiguration (169.x.x.x)
> addresses.
>
> Is this a DHCP issue? Is the guest unable to see the router at this
> point?
>
> For what it's worth, I'm pretty sure this isn't a permission issue on the
> host. I chowned /dev/net/tun to :vboxusers, of which my user is a member.
> And I ran "chmod g+rw" on it too. As a final check, I also rebooted,
> logged
> in as root, and ran through the whole process again. Same result.
Ok, I ran tcpdump on tap1 and eth0 while running an "ipconfig /renew" on
the guest. I should preface this by saying I'm very amateur at packet
analyzing.
Looks like it's not a VirtualBox problem. tap1 shows:
08:57:29.896419 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP,
Request from 08:00:27:xx:xx:xx (oui Unknown), length: 300
08:57:32.896155 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP,
Request from 08:00:27:xx:xx:xx (oui Unknown), length: 300
08:57:40.903887 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP,
Request from 08:00:27:xx:xx:xx (oui Unknown), length: 300
08:57:56.903685 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP,
Request from 08:00:27:xx:xx:xx (oui Unknown), length: 300
So the DHCP requests are getting to the host interface. eth0 shows the
following (after removing some NTP traffic). 192.168.2.10 is my host
machine, 192.168.2.1 is my router/DHCP server.
08:57:30.043666 arp who-has 192.168.2.10 tell 192.168.2.1
08:57:30.043707 arp reply 192.168.2.10 is-at 00:20:ed:xx:xx:xx (oui
Unknown)
08:57:55.051446 IP 192.168.2.10.iad3 > 192.168.2.1.domain: 52618+ AAAA?
scs.msg.yahoo.com. (35)
08:57:55.099360 IP 192.168.2.1.domain > 192.168.2.10.iad3: 52618 1/1/0
CNAME[|domain]
08:57:55.099460 IP 192.168.2.10.iad3 > 192.168.2.1.domain: 31736+ A?
scs.msg.yahoo.com. (35)
08:57:55.113080 IP 192.168.2.1.domain > 192.168.2.10.iad3: 31736 9/7/7
CNAME[|domain]
08:58:00.051047 arp who-has 192.168.2.1 tell 192.168.2.10
08:58:00.051408 arp reply 192.168.2.1 is-at 00:0e:2e:xx:xx:xx (oui Unknown)
So there's a couple of arp requests, first from the router for the host,
then the other way around. And the stuff in the middle looks like random
crap from something else I ran. So in my totally inexpert estimation, it
looks like the bridge isn't passing on the DHCP requests from the guest? A
"brctl show br0" gives:
bridge name bridge id STP enabled interfaces
br0 8000.0020ed4674b3 no eth0
tap1
If I tcpdump the br0 interface as well, it just gives basically the merging
of the two interfaces, which I imagine is what to expect.
Any ideas? Should I find some bridging experts? Anyone know where to look
for some?
-David Murphy
____________________________________________________________________________________
It's here! Your new message!
Get new email alerts with the free Yahoo! Toolbar.
http://tools.search.yahoo.com/toolbar/features/mail/
_______________________________________________
vbox-users mailing list
[email protected]
http://vbox.innotek.de/mailman/listinfo/vbox-users
