On Mon, Sep 19, 2011 at 5:21 AM, Freek de Kruijf <[email protected]>wrote:
> On maandag 19 september 2011 03:00:08 Moshe Kamensky wrote: > > * Freek de Kruijf <[email protected]> [18/09/11 07:48]: > > > > The new output is: > > > > Internet: > > Destination Gateway Flags Refs Use Netif > > Expire > > default 192.168.1.254 UGSc 144 0 en1 > > 127 127.0.0.1 UCS 0 0 lo0 > > 127.0.0.1 127.0.0.1 UH 4 218 lo0 > > 169.254 link#5 UCS 0 0 en1 > > 192.168.1 link#5 UCS 4 0 en1 > > 192.168.1.65 8:0:27:3a:49:3a UHLWI 0 18 en1 > > 944 > > 192.168.1.66 127.0.0.1 UHS 0 0 lo0 > 192.168.1.69 58:b0:35:ee:a5:5f UHLWI 4 1910 en1 > > 957 > > 192.168.1.254 0:25:3c:c0:f3:49 UHLWI 162 175 en1 > > 1200 > > 192.168.1.255 ff:ff:ff:ff:ff:ff UHLWbI 0 12 en1 > > > > There is also an Internet6 part that I omitted. > > > > > 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. > > > > Now that I tried it again, the ping from the guest to the router did > > work. I don't know if this is something I changed, or I was just > > confused the first time. > > So that's explained > > > > 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. > > > > I installed wireshark on the host. As I said, I don't know anything > > about network, so this is a bit hard to read. When I ping from dibbler > > to gaspode, what I see is a repetitive pattern of 4 items, the first a > > ping request from dibbler to gaspode, then a ping reply from gaspode to > > dibbler, another (duplicate) reply from carrot to dibbler, and finally a > > redirect from carrot to gaspode that wireshark marks as an ICMP error. > > The only thing that seems out of place is that in the first ping > > request, in the 'Ethernet II' level, the mac address that appears as the > > source is the address of carrot (the host), rather than dibbler. The > > only place where the mac address of the guest appears is in the > > duplicate reply from carrot to dibbler. The IP addresses do appear to be > > correct. > > You seem to get around with this. > This really looks like a bug in the bridge software. The wireless interface > needs to have promiscuous mode set, because it needs to get packets to the > MAC > address of the host and to the MAC address of the guest and pass that last > packet unaltered to the guest. From what you write this does not seem to > happen properly. > > So file a bug report and include the Wireshark trace file in that report. > > > Thank you for your help! > > Moshe > > You're welcome. > > -- > Hi! Since we're talking about network issues here, i'll do a little hijacking in this thread. i have a related issue with host-only-adapter setup, but in linux. I've been doing some experiments with DHCP+WPAD and i'm using virtualbox to do it. I have a Ubuntu 11.04 host (reploid) with vbox 4.0.12 connected via a host-only interface with a Windows XP guest (void). There is a DHCP server (the ISC version, not the embedded in virtualbox) running in reploid delivering IP on the vboxnet0 interface. Things are going OK, until i tried to capture the packets in the vboxnet0 interface of reploid using Wireshark. I could only see the packets coming FROM THE GUEST TO THE HOST. The packets going FROM THE HOST TO THE GUEST wasn't visible by the capture. On the other side, when i tried to capture on the network interface of void, i could see all packets coming IN and OUT of the interface. Why can't i see the packets coming out of the host interface in the capture? Is there a way to work around this? Should i report a bug or this is intended to work in this way? Should I give more details? The same behavior occurs in 4.1.2.
------------------------------------------------------------------------------ BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA Learn about the latest advances in developing for the BlackBerry® mobile platform with sessions, labs & more. See new tools and technologies. Register for BlackBerry® DevCon today! http://p.sf.net/sfu/rim-devcon-copy1
_______________________________________________ VBox-users-community mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/vbox-users-community
