Re: [Xen-users] Trouble with Nat Xen setup

[Ian Campbell <ian.campbell@xxxxxxxxxx>]

On Mon, 2015-02-23 at 10:45 -0800, JMW MVM wrote:

>         inet 169.254.15.51  netmask 255.255.0.0  broadcast 169.254.255.255

> I don't know why it would be getting that ip.

169.254.x.x is the link-local IPv4 space
http://en.wikipedia.org/wiki/Link-local_address

"The Internet"(tm) seems to think that these get assigned if an
interface is configured for DHCP but unable to talk to a DHCP server or
similar situations. It might also indicate you have avahi or some other
zeroconf thing enabled in the domU.

I'm not a gentoo user but you say you used config_eth0="192.168.0.42" in
your conf.d/net, while
https://forums.gentoo.org/viewtopic-t-747458-start-0.html gives an
example with more fields and more ()s involved. I don't know if those
differences are relevant.

You could try doing it by hand to confirm it is working with:
    ifconfig eth0 192.168.0.42 netmask 255.255.255.0 up
and once that is working worry about how to translate that into a gentoo
config.

> The ip of DomU looks different on the host side, which you can see
> here from the output of running ifconfig: http://dpaste.com/3FQ2HWG.
> That output looks the same even if I specify the ip address on the
> DomU side. I assume this is normal behavior.

tools/hotplug/Linux/vif-nat contains:
routing_ip()
{
  echo $(echo $1 | awk -F. '{print $1"."$2"."$3"."$4 + 127}')
}

which AIUI is supposed to calculate the dom0 IP given the domU IP by
adding 127 to the final quad. 42+127 == 169 as you have seen. So I think
this is normal.

Ian.



_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users