On Sat, Mar 10, 2007 at 06:33:28PM -0500, Jonathon Jones wrote:
> Well, I did as you suggested and changed the netmask for x.x.153.178 to
> 255.255.252.0 and rebooted the machine just to give a clean slate. I'm
> still in the same situation though. Xen just isn't forwarding the
> packets to the domU for some reason. I can watch the ping requests come
> in but since the IP is not bound to dom0, it doesn't respond to the
> request and the domU isn't responding to it, nor is it receiving the
> request according to tcpdump.
>
> I just don't understand why xen isn't forwarding the traffic for some
> IP's but it is for others. The only commonality to the IP's that do
> work are that they are the primary IP bound to eth0 in the domU. It
> seems to me that if that IP works then any other IP's should work,
> especially if added tot he interface with the same network mask and
> everything so that ip addr show lists them the same way....
>
> *confused and frustrated*
>
You kidding! we're only just getting started here. Actually, I think
things are looking quite good. My next suggestion is as follows:
Xen does not appear to like multiple addresses configured on the same
card, so lets configure one interface for each address. I should of seen this
earlier, but there's a lot of smoke around. Change the Dom1 config
file to read:
vif=[ '', '', '' ]
I'm not sure if this will work as is, but it should create three
interfaces for Dom1 and add them all to the default bridge. Sorry, it's
not convienient for me to test this with my present setup. We might
need to add mac="..." and/or bridge="..." statements - but hopefully it
should work as is.
Then in Dom1 configure each interface (eth0, eth1, eth2) with their own
address.
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
Home