From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephan Seitz Subject: Jeremy's GIT-tree and network problems Date: Mon, 29 Mar 2010 17:40:23 +0200 Message-ID: <20100329T1647.GA.2c139.stse@fsing.rootsland.net> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1989903939==" Return-path: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org --===============1989903939== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="4Ckj6UjgE2iN1+kY" Content-Disposition: inline --4Ckj6UjgE2iN1+kY Content-Type: text/plain; charset=utf-8; format=flowed Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi! I have bridging problems with the Dom0 kernels from Jeremy=E2=80=99s tree. = =20 I wrote a mail to xen-user (MSG-ID=20 <20091220T1944.GA.ab998.stse@fsing.rootsland.net>, 20 Dec 2009), but=20 without solutions. So I try xen-devel this time. My hardware setup: A PC with two NICs (Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI=20 Express Gigabit Ethernet controller) is used as working environment=20 (Dom0) and as firewall/proxy/DSL-router (DomU). The two NICs are bridged between Dom0 and DomU. Bridge eth0 containing peth0 and vif1.0 has an IP address in Dom0 and=20 DomU. The DomU IP address is the gateway address in Dom0. Bridge xenbr1 containing eth1 and vif1.1 has no IP address in Dom0 and=20 DomU and is only used to connect the DSL modem to DomU. The IP address is= =20 given to the PPP interface in DomU. Linux distribution is Debian/Testing (64bit) with XEN version 3.4.2 in=20 December and 3.4.3rc3 now. The kernels are always self-compiled. My working setup: Dom0 with kernel 2.6.29.5 with xen-patches-2.6.29-6.tar.bz2 and DomU with= =20 standard kernel 2.6.32.x (and the 2.6.29.5 xen kernel before). The=20 hypervisor was 3.4.2 and is now 3.4.3rc3. Here everything works as expected. DomU acts as firewall and is using=20 correct masquerading for all internet traffic. My non-working setup: Dom0 with the PV-Ops kernel from Jeremy=E2=80=99s tree (I tried the follwoi= ng=20 kernels: 2.6.31.5-00500-g34013be, 2.6.31.6-00696-g41a0695 (tested in=20 December) and now from xen/stable the versions 2.6.32.10-02792-gf112549=20 and 2.6.32.10-02798-gd945b01). DomU kernel and hypervisor are the same as= =20 in the working setup. What is working? IP connection between Dom0 and DomU is working and between DomU and the=20 internet. Traffic from Dom0 to the internet is working if DomU is used as= =20 a proxy (e.g. HTTP traffice with a squid in DomU). What is not working? Direct IP connection between Dom0 and the internet (tested with ping and=20 =E2=80=9Etelnet =E2=80=9D. If I trace in DomU I see the packets leaving the ppp0 interface=20 (correctly masqueraded), but I see no answering packets. If I trace in Dom0 using the bridge interfaces between the DSL modem and=20 DomU (xenbr1, eth1, vif1.1, see hardware setup above), I don=E2=80=99t see = the=20 packets anymore. I only see packets from traffic generated directly by=20 DomU. The DomU configuration between the working and non-working setup is not=20 changed, only the Dom0 kernel is changed. So if anyone has an idea, what this could be and how to fix it, I will be= =20 glad. Further information: The NIC and the bridge driver are the same in all kernels from 2.6.29.5=20 until 2.6.32.10: osgiliath:~# ethtool -i eth1 driver: r8169 version: 2.3LK-NAPI firmware-version: bus-info: 0000:03:00.0 osgiliath:~# ethtool -i xenbr1 driver: bridge version: 2.3 firmware-version: N/A bus-info: N/A The only difference in the output of =E2=80=9Eethtool eth1=E2=80=9D are add= itional=20 information about =E2=80=9Elink partner advertised modes=E2=80=9D in the 2.= 6.3x kernels. =E2=80=9Eethtool -k eth1=E2=80=9D shows the error message =E2=80=9ECannot g= et device flags:=20 Operation not supported=E2=80=9D in the working setup for the working Dom0= =20 kernel. All other output is identical in all kernel versions: osgiliath:~# ethtool -k eth1 Offload parameters for eth1: rx-checksumming: on tx-checksumming: off scatter-gather: off tcp-segmentation-offload: off udp-fragmentation-offload: off generic-segmentation-offload: off generic-receive-offload: off large-receive-offload: off Switching rx-checksumming off does not help. dmesg and the log files don=E2=80=99t show error messages in the non-workin= g=20 setup.=20 Shade and sweet water! Stephan --=20 | Stephan Seitz E-Mail: stse@fsing.rootsland.net | | PGP Public Keys: http://fsing.rootsland.net/~stse/pgp.html | --4Ckj6UjgE2iN1+kY Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAkuwyecACgkQXse+NwPOAZ7m+ACgsl/8Bhcv3L9VffhuIHtJ3U5q sUEAn2YKw0zKnTQkg6w43xLjrU50u8iU =Z51E -----END PGP SIGNATURE----- --4Ckj6UjgE2iN1+kY-- --===============1989903939== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel --===============1989903939==--