[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] no network traffic between domUs


  • To: "Justin R Findlay" <justin@xxxxxxxxxxx>
  • From: "Gabriel Gunderson" <ggundy@xxxxxxxxx>
  • Date: Fri, 4 Aug 2006 11:17:34 -0600
  • Cc: xen-users@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Fri, 04 Aug 2006 10:18:19 -0700
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=mGTZ14dZ2+8TQMgg4zERLTllQlNGqaVNsVA/vFOLq2LbWirnl8uSYPDkg+V9a3W9U3zwxGRdHrWsERMmNZ6oU3sSAl8SeVKTDLmQg4pknP50LSiBPwCRLtDvIHrY89BmeWgvyZBpy6zYMbGx/Zhr67idS0zWR7pizx5e/xuRRIQ=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

On 8/3/06, Justin R Findlay <justin@xxxxxxxxxxx> wrote:
UPDATE: Just before sending this email I noticed that traffic between
the two domUs starts flowing as expected only after I ping the client
from the server, however I'm still mystified as to what is really going
on.

I'm working with Justin on this and wanted to add a few details.  As he said, if you try to ping the client DomU from the gateway/firewall/router server DomU, then (after 5 or 6 seconds) the traffic will start flowing.  Only *after* doing this can the client DomU then ping the gateway (or beyond).  I'm 99.9% sure that the networking is setup correctly and *should* be working.

I believe it's a Xen or NIC kernel module problem.  We are testing a setup like it and it *seems* to work well for us on different hardware.  This box is a Dell PowerEdge with Broadcom chips (e1000).  Ever heard of this type of behavior?  Any ideas?

Thanks,
Gabe

P.S.  Additional info:

It's running Ubuntu 6.06 LTS Server (updated) with the official Xen 3.0.2 kernel.

# lspci | grep Ether
Intel Corporation 82544EI Gigabit Ethernet Controller (Copper) (rev 02)
Intel Corporation 82544EI Gigabit Ethernet Controller (Copper) (rev 02)

P.P.S.  D'oh!  I just noticed all of these dropped packets shown below (vif0.0, vif12.0, vif12.1, vif12.2, vif13.0).   Now I have to figure out what that means.

peth0     Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
          UP BROADCAST RUNNING NOARP MULTICAST  MTU:1500  Metric:1
          RX packets:89084 errors:0 dropped:0 overruns:0 frame:0
          TX packets:110727 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:24713772 (23.5 MiB)  TX bytes:18362931 (17.5 MiB)
          Base address:0xdce0 Memory:feb60000-feb80000

vif0.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:79852 errors:0 dropped:0 overruns:0 frame:0
          TX packets:60698 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:13187315 (12.5 MiB)  TX bytes:10060245 (9.5 MiB)

vif12.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:3856 errors:0 dropped:0 overruns:0 frame:0
          TX packets:5290 errors:0 dropped:224 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:471277 (460.2 KiB)  TX bytes:1723434 (1.6 MiB)

vif12.1   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:1030 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1817 errors:0 dropped:223 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:1230197 (1.1 MiB)  TX bytes:132427 (129.3 KiB)

vif12.2   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:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:1484 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

vif13.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:4850 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2441 errors:0 dropped:97 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:842701 (822.9 KiB)  TX bytes:1314526 (1.2 MiB)

xenbr0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
          inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:4470 errors:0 dropped:0 overruns:0 frame:0
          TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:202946 (198.1 KiB)  TX bytes:468 (468.0 b)

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

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.