> >
> > Also try running wireshark or another traffic capture routine and
see
> > what that picks up. It could be getting corrupt packets or no
packets at
> > all.
> >
> > There could maybe be something wrong with broadcast packets... try
> > adding an arp entry manually in Dom0 for DomU and then try pinging
it.
> >
>
> After adding static arp, wireshark on domU shows it sends ICMP echo
> packets but doesn't receive anything (not even corrupted packets).
> tcpdump on dom0 shows something interesting though.
>
> 05:58:02.333904 IP (tos 0x0, ttl 128, id 41, offset 0, flags [none],
> proto: ICMP (1), length: 60) 192.168.129.99 > 192.168.129.89: ICMP
> echo request, id 512, seq 1280, length 40
> 05:58:02.334044 IP (tos 0x0, ttl 255, id 64313, offset 0, flags [DF],
> proto: ICMP (1), length: 60) 192.168.129.89 > 192.168.129.99: ICMP
> echo reply, id 512, seq 1280, length 40
>
> the ICMP reply (which domU never got) has [DF] flag. Is this normal?
> Is this MTU-related issue?
>
I thought windows only asserted DF when you used the '-f' flag, but with
a length of 60 bytes it won't be an MTU issue.
It could be that the interrupts are never getting called... which
version of GPLPV are you running? Could you try the very latest version
- 0.9.12-pre15-dont-use.exe? That one is definitely not suitable for
production use but it does contain a few changes in the network.
Also, if it is an interrupt issue, there should be a total of <256 that
will be sent before the queue fills up and no more can be sent. Can you
send 256 ping packets from Windows to Dom0 and then see if Dom0 receives
more after that?
James
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
Home