On 11/27/06, Torsten Lehmann <tlehmann@xxxxxxxxxxxxx> wrote:
l1:~# tcpdump -vv -n -i eth0 host NFSserver and udp
17:15:04.814142 IP (tos 0x0, ttl 64, id 65529, offset 0, flags [+],
length: 1500) 193.123.123.86.2879998019 > 193.123.123.85.2049: 1472 write
[|nfs]
17:15:04.814203 IP (tos 0x0, ttl 64, id 65529, offset 1480, flags [none],
length: 720) 193.123.123.86 > 193.123.123.85: udp
17:15:05.266099 IP (tos 0x0, ttl 64, id 65530, offset 0, flags [+],
length: 1500) 193.123.123.86.2896775235 > 193.123.123.85.2049: 1472 write
[|nfs]
17:15:05.266176 IP (tos 0x0, ttl 64, id 65530, offset 1480, flags [none],
length: 720) 193.123.123.86 > 193.123.123.85: udp
17:15:05.714048 IP (tos 0x0, ttl 64, id 65531, offset 0, flags [+],
length: 1500) 193.123.123.86.2913552451 > 193.123.123.85.2049: 1472 write
[|nfs]
17:15:05.714122 IP (tos 0x0, ttl 64, id 65531, offset 1480, flags [none],
length: 720) 193.123.123.86 > 193.123.123.85: udp
This is telling you that domU's eth0 interface is not getting any
response from NFS server. The problem might reside on domU's network
configuration or dom0 network (don't think it's on NFS server
networking, althoug you could check to find out more info).
## - dump on xen0
l0:~# tcpdump -vv -n -i eth0 host NFSserver and udp
## ... nothing...
- xen0:eth0 seen to be blind...
If you're using Xen bridged networking you should try to run tcpdump
on the bridge interface in dom0.
Any solutions?
Might be related to bridged networking when applying iptables rules to
a bridged interface (eth0, in your case). If you aren't using bridged
networking I have no idea of what could be happening... In any case
your workaround is interesting. Are your sure that this solves the
problem or does it go away after waiting for some time? Does your
netfilter script play with the interfaces? Could you post its content?
regards Torsten
Launoc
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|