On 2/5/07, Daniel S. Reichenbach <daniel.s.reichenbach@xxxxxxx> wrote:
I can ping the guests IPs from the outside, and when I console into the guest
using xm console I can see it's ifconfig showing the correct IP.
But here comes trouble: neither do packages for the assigned IP reach the guest,
The last sentence is in direct conflict to the first one. if you can
ping it, packages reach the guest..
nor can I reach any IP from within the guest.
So the guest is pingable from the outside, but can't ping to the
outside and get replies back?
I couldn't find any solution to this issue, searched several hours on Wiki and
google. Could anyone give me some hints what I am doing wrong?
Hi, knowing that some things are hard to explain in just three words,
I still have a bit of a hard time understanding this long post.
At first glance, I see all the aliases you give for eth2:X and don't
understand, what this is good for. I see you try to assign your
different network segments, but I don't understand why and what for.
Another important question: do you want to use bridged, nat or routed
networking? For what kind of virtual setup are you heading here - can
you give us a big picture of the whole network?
I also don't understand why you don't have an eth0 or eth1. Can you
explain your hardware setup?
Still, some things you might try:
1)If you use bridging, it's possi ble that the default bridge setup
does assume that vif0.0 is the dom0 interface, and tries to add this
ti the bridge. If you only have eth2, and therefore vif2.0 (hmm,
right?!), that might not work.
Look at brctl show if all interfaces are connected to bridges correctly.
2) look with tcpdump to check on which interface your packets get lost
3) when you hook your different subnet into one pohysical bridge
(which is strrange and I donät see the reason what this should bring),
the you have to make sure that packet get routed somewhere, or the
interfaces in the different subnets can't connect each other.
Xen-users mailing list