Re: [Xen-devel] DOM0 diskless => NAT doesn't work ?!

[Ian Pratt <Ian.Pratt@xxxxxxxxxxxx>]

> On Thu, 2004-04-08 at 10:27, Ian Pratt wrote:
> 
> > 169.254/16 addresses are VMM-local: they're never allowed out on
> > the LAN.
> > 
> > For your purposes of accessing an external NFS server use some
> > other subnet e.g. 192.168/16.
> 
> I don't think it is a routing problem, and (despite my long post :-), I
> must have not been clear enough.
> 
> If I boot DOM0 diskfull , and then boot DOM1 diskful or diskless, I can
> ping DOM1 from DOM0 (ping 169.254.1.1 works), but if I boot DOM0
> diskless, and DOM1 either diskless or diskfull, the ping command fails. 

I don't think NAT'ing NFS traffic is going to work -- to my
knowledge Linux iptables hasn't got state-full masquerading for
NFS. It's a bit tricky with all the portmapper and sunrpc
interaction.

Any reason why you can't just give both dom0 and dom1 LAN-visible
IP addresses?

However, it is odd that you can't ping dom1 even if it is booted
diskfull.

It might be worth trying to back this change out, but I can't see
why it would cause problems:

http://xen.bkbits.net:8080/xeno-1.2.bk/diffs/xen/net/dev.c@xxxx?nav=index.html|src/.|src/xen|src/xen/net|hist/xen/net/dev.c


Ian


-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel