WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

[Xen-users] Xen 3 and VLAN

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Xen 3 and VLAN
From: Timo Virtaneva <timo@xxxxxxxxxxxx>
Date: Sat, 21 Jan 2006 17:04:30 +0200 (EET)
Delivery-date: Mon, 23 Jan 2006 13:34:12 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Hi

I have a realy weird problem with XEN and VLAN's and I hope that someone would 
be able to help me tp
o get the VLAN's working properly. I have seen one mail in the achives with 
same problem, but unfortunately without solution.

The XEN-U machines network is not working for tcp and udp without manual 
TCPDUMP to the VLAN interface. The icmp is working ok all the time even for big 
packages.

Why the network is working ONLY when the tcpdump is on ?

The facts:

1. After the XEN-U machine is started I try to establish ssh session without 
success. Here is the tcp dump of vif1.0 taken from XEN-0:

[root@v4 ~]# tcpdump -i vif1.0
tcpdump: WARNING: vif1.0: no IPv4 address assigned
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on vif1.0, link-type EN10MB (Ethernet), capture size 96 bytes
12:20:45.606658 00:50:73:76:12:b8 > 01:00:0c:cc:cc:cd snap ui/C len=39
12:20:47.609263 00:50:73:76:12:b8 > 01:00:0c:cc:cc:cd snap ui/C len=39
12:20:49.337568 IP 10.10.13.197.56098 > 10.10.13.34.ssh: S 
3921153772:3921153772(0) win 5840 <mss 1460,sackOK,timestamp 2977540 
0,nop,wscale 2>
12:20:49.338615 IP 10.10.13.34.ssh > 10.10.13.197.56098: S 
3271221253:3271221253(0) ack 3921153773 win 5792 <mss 1460,sackOK,timestamp 
34939 2977540,nop,wscale 2>
12:20:49.339655 IP 10.10.13.197.56098 > 10.10.13.34.ssh: . ack 1 win 1460 
<nop,nop,timestamp 2977540 34939>
12:20:49.352471 IP 10.10.13.34.ssh > 10.10.13.197.56098: P 1:21(20) ack 1 win 
1448 <nop,nop,timestamp 34939 2977540>
12:20:49.545342 IP 10.10.13.34.ssh > 10.10.13.197.56098: P 1:21(20) ack 1 win 
1448 <nop,nop,timestamp 34960 2977540>
12:20:49.612571 00:50:73:76:12:b8 > 01:00:0c:cc:cc:cd snap ui/C len=39
12:20:49.965309 IP 10.10.13.34.ssh > 10.10.13.197.56098: P 1:21(20) ack 1 win 
1448 <nop,nop,timestamp 35002 2977540>

It seems that the acknowledge packet is not going back.

2. If I try again but I will take the same dump from eth1.13 interface, the 
connection will be established.

[root@v4 ~]# tcpdump -i eth1.13
tcpdump: WARNING: eth1.13: no IPv4 address assigned
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth1.13, link-type EN10MB (Ethernet), capture size 96 bytes
12:25:40.001068 00:50:73:76:12:b8 > 01:00:0c:cc:cc:cd snap ui/C len=39
12:25:40.794480 IP 10.10.13.197.38227 > 10.10.13.34.ssh: S 
4233926646:4233926646(0) win 5840 <mss 1460,sackOK,timestamp 3050404 
0,nop,wscale 2>
12:25:40.795464 IP 10.10.13.34.ssh > 10.10.13.197.38227: S 
3570848065:3570848065(0) ack 4233926647 win 5792 <mss 1460,sackOK,timestamp 
64087 3050404,nop,wscale 2>
12:25:40.797572 IP 10.10.13.197.38227 > 10.10.13.34.ssh: . ack 1 win 1460 
<nop,nop,timestamp 3050405 64087>
12:25:40.810343 IP 10.10.13.34.ssh > 10.10.13.197.38227: P 1:21(20) ack 1 win 
1448 <nop,nop,timestamp 64087 3050405>
12:25:40.811438 IP 10.10.13.197.38227 > 10.10.13.34.ssh: . ack 21 win 1460 
<nop,nop,timestamp 3050409 64087>
12:25:40.971168 IP 10.10.13.197.38227 > 10.10.13.34.ssh: P 1:21(20) ack 21 win 
1460 <nop,nop,timestamp 3050449 64087>
12:25:40.971342 IP 10.10.13.34.ssh > 10.10.13.197.38227: . ack 21 win 1448 
<nop,nop,timestamp 64104 3050449>
12:25:40.973130 IP 10.10.13.197.38227 > 10.10.13.34.ssh: P 21:733(712) ack 21 
win 1460 <nop,nop,timestamp 3050449 64104>

The system is Fedora 4 and network card is Intel 1000 pci card and driver e100. 

-- Timo

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-users] Xen 3 and VLAN, Timo Virtaneva <=