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] HELP: xenbr on vlan if --> tcp checksum error

To: <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-users] HELP: xenbr on vlan if --> tcp checksum error
From: "Lockenvitz, Jan \(EXT\)" <Jan.Lockenvitz.extern@xxxxxxxxxxxxxx>
Date: Wed, 14 Dec 2005 18:13:25 +0100
Delivery-date: Wed, 14 Dec 2005 17:15:39 +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
Thread-index: AcYA0bF0vdusfHsOTvKt+62gHEkvBg==
Thread-topic: HELP: xenbr on vlan if --> tcp checksum error
Hi

I'm testing around with xen 3.0 snapshot from last week. And i'm now having a 
problem with a xenbr which is based on a vlan if (dot1q).

this is all in dom0

os: debian testing
network: tg3

I can start the bridge based on my normal physical eth0 which is working 
without any problems.
My clan without bridge is also working.
I can start the bridge based on a vlan if with help of the following command:

  # network-bridge start netdev=vlan100 bridge=xenbr0

The bridge is started (as i think) correctly. My interfaces and bridge looks 
like this:

  # ifconfig

eth0      Protokoll:Ethernet  Hardware Adresse 00:0D:60:14:85:D4
          UP BROADCAST RUNNING PROMISC MULTICAST  MTU:1500  Metric:1
          RX packets:27198 errors:0 dropped:0 overruns:0 frame:0
          TX packets:17073 errors:0 dropped:0 overruns:0 carrier:0
          Kollisionen:0 Sendewarteschlangenl%G�%@ge:1000
          RX bytes:4262353 (4.0 MiB)  TX bytes:11003381 (10.4 MiB)
          Interrupt:24

lo        Protokoll:Lokale Schleife
          inet Adresse:127.0.0.1  Maske:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:27033 errors:0 dropped:0 overruns:0 frame:0
          TX packets:27033 errors:0 dropped:0 overruns:0 carrier:0
          Kollisionen:0 Sendewarteschlangenl%G�%@ge:0
          RX bytes:11642656 (11.1 MiB)  TX bytes:11642656 (11.1 MiB)

pvlan100  Protokoll:Ethernet  Hardware Adresse FE:FF:FF:FF:FF:FF
          UP BROADCAST RUNNING NOARP MULTICAST  MTU:1500  Metric:1
          RX packets:24613 errors:0 dropped:0 overruns:0 frame:0
          TX packets:17073 errors:0 dropped:0 overruns:0 carrier:0
          Kollisionen:0 Sendewarteschlangenl%G�%@ge:0
          RX bytes:3419341 (3.2 MiB)  TX bytes:10865571 (10.3 MiB)

vif0.0    Protokoll:Ethernet  Hardware Adresse FE:FF:FF:FF:FF:FF
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:9 errors:0 dropped:0 overruns:0 carrier:0
          Kollisionen:0 Sendewarteschlangenl%G�%@ge:0
          RX bytes:0 (0.0 b)  TX bytes:1600 (1.5 KiB)

vlan100   Protokoll:Ethernet  Hardware Adresse 00:0D:60:14:85:D4
          inet Adresse:10.8.15.129  Bcast:10.8.15.255  Maske:255.255.255.128
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:9 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          Kollisionen:0 Sendewarteschlangenl%G�%@ge:0
          RX bytes:1600 (1.5 KiB)  TX bytes:0 (0.0 b)

vlan105   Protokoll:Ethernet  Hardware Adresse 00:0D:60:14:85:D4
          inet Adresse:10.8.16.161  Bcast:10.8.15.191  Maske:255.255.255.224
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1327 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          Kollisionen:0 Sendewarteschlangenl%G�%@ge:0
          RX bytes:66350 (64.7 KiB)  TX bytes:0 (0.0 b)

xenbr0    Protokoll:Ethernet  Hardware Adresse FE:FF:FF:FF:FF:FF
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:9 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          Kollisionen:0 Sendewarteschlangenl%G�%@ge:0
          RX bytes:1474 (1.4 KiB)  TX bytes:0 (0.0 b)

  # brctl show

bridge name     bridge id               STP enabled     interfaces
xenbr0          8000.feffffffffff       no              pvlan100
                                                        vif0.0

a ping to an other machine is fine

But i can't ssh to any other machine. I started tracing on another machine and 
ethereal shows an incorrect TCP checksum. And the TCP checksum is this case 
seems to depend on the packet size.
I also traced in dom0 on the following IF: vlan100, pvlan100 and eth0 (where 
the vlan is bound to)
On vlan100 i can see the same packets as on the destination machine, but on 
pvlan100 and eth0 the TCP checksum is correct.

Is this problem known? 

Can someone help to solve this? I can post some traces if necessary

Thanx in advance,
Jan

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

<Prev in Thread] Current Thread [Next in Thread>