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

Re: [Xen-users] Strange Networking Issue

To answer your question about eth0 vs. eth1, on the dom0 eth1 has the public IP but the below dump from ip addr list was on the domU showing that the .242 IP was added to the domU in the same way as the .240 IP however  .240 reaches the domU and .242 does not.

Yes, pingable means from the outside world.  Otherwise I will specify for clarity.

No firewalls.

Other services are also unreachable.

tcpdump was a great tip, thanks.  I'll add that to my tool belt.  The dom0 is receiving the ping request for .242 but that IP is added to the domU.  The domU is receiving the ping request for .240 however.

You made the following statement which I don't understand: "Another thing is that your gateway/Dom0 ip is looking exactly like a transfer network, 75.126.153.176/29 for routing purpose. You should get some information from your provider how exactly the routing setup is."

What exactly are the implications of them setting up the dom0 IP in that way and why does it matter?

I do appreciate all of your help.  Thanks much!

Jon

Martin Hierling wrote:
Hi,
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

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?


pingable means from outside, right. So are there any firewalls between outside and xen?
have you tested any other service, like http? try that.
does your xen box get/answer the ping? tcpdump -i eth0 icmp. Do you see any echo/echo-replys generated from your box?
According to your first mail, eth1 is the if with the public interface!  Why are the addresses configured on eth0?

Another thing is that your gateway/Dom0 ip is looking exactly like a transfer network, 75.126.153.176/29 for routing purpose. You should get some information from your provider how exactly the routing setup is.

I dont believe it is xen, i have a similar setup.

Martin

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