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

xen-devel

[Top] [All Lists]

Re: [Xen-devel] veth0 problems and network-route

To: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] veth0 problems and network-route
From: wei huang <huanwei@xxxxxxxxxxxxxxxxxx>
Date: 2005年7月29日 15:27:22 -0400 (EDT)
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: 2005年7月29日 19:26:04 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <08c357e4edbc29e4c82de754a72b3ef2@xxxxxxxxxxxx>
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
Hi,
Many thanks to your reply. But there has to be something else different
with xen-2.0. I didn't compile the loopback as you suggested. Now
it's close to work until the DomU boots.
The strange thing is that domU and dom0 both can talk to the whole world
but they can NOT talk to each other. They can even ping each other but
cannot ssh. (I use the same disk image as I use for xen-2.0 so I don't
think there is some forwarding policy problem, etc. And actually I turned
off all the firewall, security things)
Here is the route table of dom0 after domU boots:
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
9.2.72.0 0.0.0.0 255.255.255.128 U 0 0 0 xen-br0
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 xen-br0
0.0.0.0 9.2.72.1 0.0.0.0 UG 0 0 0 xen-br0
And ifconfig of dom0:
eth0 Link encap:Ethernet HWaddr 00:0D:60:9A:15:60
 inet addr:9.2.72.112 Bcast:9.2.72.127 Mask:255.255.255.128
lo Link encap:Local Loopback
 inet addr:127.0.0.1 Mask:255.0.0.0
vif1.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
xen-br0 Link encap:Ethernet HWaddr 00:0D:60:9A:15:60
 inet addr:9.2.72.112 Bcast:9.2.72.127 Mask:255.255.255.128
ifconfig of domU:
eth0 Link encap:Ethernet HWaddr AA:00:00:00:00:1ame:0
 inet addr:9.2.72.101 Bcast:9.2.72.127 Mask:255.255.255.128
lo Link encap:Local Loopback
 inet addr:127.0.0.1 Mask:255.0.X packets:18 errors:0 dropped:0
It's almost working but it seems that something is preventing those two OS
on the same machine talking to each other.
Do you have any ideas? Thank you very much!
Regards,
Wei Huang
> On 29 Jul 2005, at 18:49, wei huang wrote:
>
> > Do you have any back port patch to the version vnet which doesn't use
> > veth0? It might help in my case. PS: I need to run program with some
> > new
> > features in unstable, so I have to stick to the unstable versoin.
>
> I think you can remove loopback.o from
> linux/drivers/xen/netback/Makefile, and that will give you old-style
> behaviour.
>
> -- Keir
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel 
>
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>
Previous by Date: [Xen-devel] why in the ustable developement tree are scsi and ethernet device driver build in , Ralph Blach
Next by Date: Re: [Xen-devel] veth0 problems and network-route , wei huang
Previous by Thread: Re: [Xen-devel] veth0 problems and network-route , Keir Fraser
Next by Thread: Re: [Xen-devel] veth0 problems and network-route , wei huang
Indexes: [Date] [Thread] [Top] [All Lists]

Copyright ©, Citrix Systems Inc. All rights reserved. Legal and Privacy
Citrix This site is hosted by Citrix

AltStyle によって変換されたページ (->オリジナル) /