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

Re: [Xen-users] Strange Networking Issue



On Fri, Mar 09, 2007 at 07:08:28PM -0500, Jonathon Jones wrote:
> In the domU....
</snip> 
> 2: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000
>    link/ether 00:16:3e:3d:20:f0 brd ff:ff:ff:ff:ff:ff
>    inet 75.126.154.240/22 brd 75.126.155.255 scope global eth0
>    inet 75.126.154.241/22 brd 75.126.155.255 scope global secondary eth0:0
>    inet 75.126.154.242/22 brd 75.126.155.255 scope global secondary eth0:1
>    inet 75.126.154.243/22 brd 75.126.155.255 scope global secondary eth0:2
>    inet6 fe80::216:3eff:fe3d:20f0/64 scope link
>       valid_lft forever preferred_lft forever
</snip> 
> You can see that all IP's are added in the same way yet only .240 is 
> pingable.  I can add the IP manually to dom0 and get it to ping so I'm 
> thinking there is some bug in this latest version of xen.  Does anybody 
> else have any other conclusion?
> 
> Jon

Hi Jon, 

your first post says that additional IPs on eth0 in Dom1 are /32 not /22 - 
which is it? 

Also, can you fill in the details on the following:

1. "ip addr show" on Dom0
2. "brctl show" on Dom0
3. "route -n" on Dom0
4. The vif configurations for Dom1 and Dom2 (from their config files)
5. The settings for (network-script ...) and (vif-script ...) in your
   xend configuration file.
6. The version of xen you are running.

Depending on what you come back with, I might have more questions. 

Also, do you have any idea if you would prefer a bridged or a routed
setup?

jez


_______________________________________________
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®.