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] Bridged networking weirdness

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Bridged networking weirdness
From: JP Viljoen <viljoenjp@xxxxxxxxxxxxxxx>
Date: Thu, 7 Aug 2008 15:45:03 +0200
Delivery-date: Thu, 07 Aug 2008 06:46:41 -0700
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/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Organization: Workforce
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: KMail/1.9.9
Hi

I've got a (gentoo) box set up for xen, 2.6.21-xen kernel as per portage about 
2 weeks ago. Already got all my guests set up and almost good to go, except 
for very erratic networking issues. Networking on the domU's does not always 
work. I have set up two physical adapters, and bridged both (by use of the 
modified network-bridge script from the archives) adapters for use with the 
domU's. The domU's all have unique MAC addresses for each adapter assigned to 
it, manually specified in the config file. The problem I'm having is that 
most of the time I seem unable to have any TCP/IP traffic pass through/out 
over the Xen interfaces, even though it has worked once or twice. I have also 
ruled out wonky network cards as the source of the problem, as I can utilize 
any of them extensively without an issue from the dom0.

Terminal output:

mnemosyne ~ # xm console jhb-svr2

jhb-svr2:~# ifconfig -a
eth0      Link encap:Ethernet  HWaddr 00:16:3E:01:01:01
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

eth1      Link encap:Ethernet  HWaddr 00:16:3E:01:01:04
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

jhb-svr2:~# dhclient eth0
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/eth0/00:16:3e:01:01:01
Sending on   LPF/eth0/00:16:3e:01:01:01
Sending on   Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 10
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 10
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 11
^C

jhb-svr2:~# ifconfig eth0 10.0.2.43 netmask 255.255.252.0 up
jhb-svr2:~# ping 10.0.0.2
PING 10.0.0.2 (10.0.0.2) 56(84) bytes of data.

--- 10.0.0.2 ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 2000ms

jhb-svr2:~# ifconfig eth0
eth0      Link encap:Ethernet  HWaddr 00:16:3E:01:01:01
          inet addr:10.0.2.43  Bcast:10.0.3.255  Mask:255.255.252.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:13 errors:0 dropped:0 overruns:0 frame:0
          TX packets:62 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:406 (406.0 b)  TX bytes:8491 (8.2 KiB)


And then on the dom0:

mnemosyne ~ # ifconfig vif1.0
vif1.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:62 errors:0 dropped:0 overruns:0 frame:0
          TX packets:13 errors:0 dropped:2 overruns:0 carrier:0
          collisions:0 txqueuelen:32
          RX bytes:7623 (7.4 Kb)  TX bytes:588 (588.0 b)

mnemosyne ~ # ifconfig peth0
peth0     Link encap:Ethernet  HWaddr 00:1D:7D:4E:E7:06
          inet6 addr: fe80::21d:7dff:fe4e:e706/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:8205 errors:0 dropped:1289861534 overruns:0 frame:0
          TX packets:17 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:719577 (702.7 Kb)  TX bytes:1128 (1.1 Kb)
          Interrupt:17 Base address:0x4000


Further information regarding the network cards:

eth0: Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI 
Express Gigabit Ethernet controller (rev 02)
eth1: Ethernet controller: Realtek Semiconductor Co., Ltd. 
RTL-8139/8139C/8139C+ (rev 10)
eth2: Ethernet controller: Realtek Semiconductor Co., Ltd. 
RTL-8139/8139C/8139C+ (rev 10)

eth0 and eth2 are used for the bridging.

Any help would be appreciated.

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

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