On zaterdag 17 september 2011 14:37:51 Moshe Kamensky wrote: > * Freek de Kruijf <[email protected]> [17/09/11 06:54]: > > On zaterdag 17 september 2011 02:23:09 Moshe Kamensky wrote: > > > Hi There, > > > > > > I have a network problem with a bridged connection. My setup is: > > > > > > A router running a dhcp server.
Address is 192.168.1.254 > > > A host "carrot" running Mac osx, connected to the router through a > > > wireless card. Address is 192.168.1.66 > > > A guest "dibbler" running Linux. The network connection is set to > > > "bridged". Address is 192.168.1.65 > > > Another machine "gaspode" on the home network running Linux, connected > > > to the router by a cable. Address is 192.168.1.69 > > Do these system get all their network information through DHCP? > > Yes, the DHCP server is on the router, and assigns a fixed ip to each. > > > Anyway check with "/sbin/route -n" on a Linux machine and the equivalent > > on your MAC, the routing information they use. > They are rather similar. On the guest: > > Kernel IP routing table > Destination Gateway Genmask Flags Metric Ref Use > Iface 0.0.0.0 192.168.1.254 0.0.0.0 UG 2 0 > 0 eth1 127.0.0.0 127.0.0.1 255.0.0.0 UG 0 0 > 0 lo 192.168.1.0 0.0.0.0 255.255.255.0 U 2 0 > 0 eth1 This looks OK. > On the host, "netstat -r" gives: > > Destination Gateway Flags Refs Use Netif > Expire > default home UGSc 50 0 > en1 > default link#4 UCSI 0 0 > en0 > 127 localhost UCS 0 0 > lo0 > localhost localhost UH 6 3653 > lo0 > 169.254 link#4 UCS 0 0 > en0 > 192.168.1 link#5 UCS 3 0 > en1 > 192.168.1 link#4 UCSI 0 0 > en0 > dibbler 8:0:27:3a:49:3a UHLWI 1 860 > en1 454 Apparently the above is the MAC address of dibbler > carrot localhost UHS 0 > 13 lo0 > gaspode 58:b0:35:ee:a5:5f UHLWI 4 > 1896 en1 1198 The above is the MAC address of gaspode > 192.168.1.200 localhost UHS > 0 0 lo0 The above is strange, you did not give your host two addresses? > home 0:25:3c:c0:f3:49 UHLWI 69 > 742 en1 1189 The above is the MAC address of your router > 192.168.2 192.168.2.1 Uc > 1 0 en0 You need to find an explanation of the above line. It should not be there, although it does not seem to be a problem. > en1 is the wireless I use to connect to the router. I don't know what is > en0. dibbler is the guest, carrot is the host, gaspode is the other > machine, home is the router. I don't know what are the other things. Can you use something like -n in the above commando, so the names are replaced by numbers. > > > Things are fine connecting between the guest and the host. Also no > > > problems between the host and the other machine. However, when I try to > > > ping from the other machine, gaspode, to the guest, I get: > > > > > > PING dibbler.gateway.2wire.net (192.168.1.65) 56(84) bytes of data. > > > > > > >From carrot (192.168.1.66): icmp_seq=1 Redirect Host(New nexthop: > > > >dibbler (192.168.1.65)) > > > > > > 64 bytes from dibbler (192.168.1.65): icmp_req=1 ttl=64 time=33.0 ms > > > 64 bytes from dibbler (192.168.1.65): icmp_req=1 ttl=63 time=33.1 ms > > > (DUP!) The different ttl's are strange, I expect only ttl=64, because the communication is directly from 69 to 65 and there should not be a router in between which counts the ttl down by 1. > > > > > > Likewise, when I ping from dibbler to gaspode, I get > > > > > > PING gaspode (192.168.1.69) 56(84) bytes of data. > > > 64 bytes from gaspode (192.168.1.69): icmp_req=1 ttl=64 time=11.8 ms > > > 64 bytes from carrot (192.168.1.66): icmp_req=1 ttl=63 time=12.0 ms > > > (DUP!) Here the same problem with the ttl, but also one ping returned by gaspode and the other by carrot, which is wrong. This looks like carrot is intervening, maybe a bug in VirtualBox. > > > Also, I cannot ping the router from the guest at all. Or a routing problem in carrot. Can you show the ping command in the guest. Did you use the IP address in the command? The processing of this command in the guest and the host should not be different from the ping to gaspode. I am not sure Wireshark, which captures network packets, is available in your Mac. If it is, you can capture the traffic on the wireless interface in your host. Try to disable most of network traffic on your host, or apply proper filtering. Do these ping tests again and analyse the captured traffic. In each captured packet you can see the source and destination MAC address, so it becomes more clear where the duplicate packet is coming from. -- fr.gr. Freek de Kruijf ------------------------------------------------------------------------------ BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA http://p.sf.net/sfu/rim-devcon-copy2 _______________________________________________ VBox-users-community mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/vbox-users-community
