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/
Home Products Support Community News


[Xen-devel] veth0 problems and network-route

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] veth0 problems and network-route
From: wei huang <huanwei@xxxxxxxxxxxxxxxxxx>
Date: Thu, 28 Jul 2005 18:31:38 -0400 (EDT)
Delivery-date: Thu, 28 Jul 2005 22:30:07 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx

After working on something else for a while, it is the time that I have to
solve the network problem wrt dom0 and domU.

I posted some emails about this problem before but it got overwhelmed. So
I re-post it here:
I am using AS4 linux with broadcom tg3 gigabit ethernet.

1) I am using the newest code in xen-unstable. Everything works smoothly
until I call 'xend start'. After that the network traffic just dies. I've
looked at the ifconfig before and after xend start, every seems normal:
veth0 gets the ip and mac address from eth0. And eth0's Mac is set to
fe:ff:ff:ff:ff:ff. xen-br0 is created and vif0.0 and veth0 is attached to
it. Actually I should say that it is exactly the same sympton as bug 62 in
your bugzilla. Is that problem solved? Am I miss something?

2) I stuck it there for some while. Then I find there is another path in
the network script:
        transfer_addrs ${netdev} ${bridge}
        transfer_routes ${netdev} ${bridge}
I believe this is the old way to setup network in xen-2.0 (are they?).
Anyway, I try to go through that path and things seem going fine. I can
start domU and domU even gets its ip address from dhcp. Both domU and dom0
can connect outside. But domU and dom0 just cannot talk to each other!
They can ping each other but ssh and socket doesn't work...
Following is ifconfig of domU (to save space, I only copy the address
eth0      Link encap:Ethernet  HWaddr AA:00:00:00:00:11
          inet addr:  Bcast:  Mask:
lo        Link encap:Local Loopback
          inet addr:1 overr27.0.0.1  Mask:
And the dom0:
eth0      Link encap:Ethernet  HWaddr 00:0D:60:9A:15:60
          inet addr:  Bcast:  Mask:
lo        Link encap:Local Loopback
          inet addr:  Mask:
vif1.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
xen-br0   Link encap:Ethernet  HWaddr 00:0D:60:9A:15:60
          inet addr:  Bcast:  Mask:
And the output of 'netstat -nr' in dom0:
Kernel IP routing table
Destination     Gateway         Genmask         Flags   MSS Window  irtt  Iface U         0 0          0 xen-br0     U         0 0          0 eth0         UG        0 0          0 xen-br0

Do you have any idea what is happening? And if you need more information
please suggest me.

Thank you very much!

Wei Huang

774 Dreese Lab, 2015 Neil Ave,
Dept. of Computer Science and Engineering
Ohio State University
OH 43210
Tel: (614)292-8501

Xen-devel mailing list