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

Jonathon,

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.

does DomU send an answer? Does the echo-reply package leaves Dom0 network interface. in bridged mode dump the traffic on your bridge interface, you should see all traffic there.


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."

Sorry, wrong netmask, it should be /30. This is a small network (only 2 hosts) between 2 routers. So the setup should be as followed:

INET  --> x.x.173.177/30  --> x.x.173.178/30 ---------> x.x.174.240/29
                ^provider Router     ^ your Router (Dom0)    ^ your DomU

So this small network is only used to transfer data between 2 routers.
provider router has a router for x.x.174.240/29 pointing to your Dom0 (173.178)

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