Re: [Xen-users] xl nat and wrong IPs

[Matthias <matthias.kannenberg@xxxxxxxxxxxxxx>]

Hi,

I finally got the chance to do the testing..

You were right, the issue was due to routing_ip or better why the
calculated ($ip + 127) is used later here:

do_or_die ip addr add "$router_ip" dev "${dev}"
do_or_die ip route add "$vif_ip" dev "${dev}" src "$router_ip"

I don't really see any point in creating a dedicated router-IP and
using it this way and i dont' see why this worked for me when using xm
earlier, but I might did some hacking before to fix this in my xm
installation, i can't really remember..

At the end of the day, I did the following to fix the behavior for my
installation: (it's only exchanging router_ip to vif_ip)

diff vif-nat vif-nat_backup
174,177c174,175
<         #do_or_die ip addr add "$router_ip" dev "${dev}"
<       do_or_die ip addr add "$vif_ip" dev "${dev}"
<         #do_or_die ip route add "$vif_ip" dev "${dev}" src "$router_ip"
<       do_or_die ip route add "$vif_ip" dev "${dev}" src "$vif_ip"
---
>         do_or_die ip addr add "$router_ip" dev "${dev}"
>         do_or_die ip route add "$vif_ip" dev "${dev}" src "$router_ip"

This way i get correctly named interfaces with the right IPs to use in
iptables and policy based routing tables..



2013/1/28 Ian Campbell <Ian.Campbell@xxxxxxxxxx>:
> On Mon, 2013-01-28 at 01:28 +0000, Matthias wrote:
>> Hi,
>>
>> I'm currently switching from toolstacks from xm to xl. Because I have
>> a rather complex network setup with my domUs, I use xen's nat
>> capabilities. But what works fine with xm behaves slightly strange in
>> xl:
>>
>> I use something like the following to establish a domU interface
>> within my vif part:
>>
>> 'type=vif, mac=00:16:3E:06:DA:B2, ip=192.168.2.1, vifname=fw11,
>> model=e1000, script=vif-nat'
>>
>> Now xm would create an interface called 'fw11' with ip 192.168.2.1 and
>> netmask 255.255.255.0. I don't really care about the rest (iptables,
>> routes) because I overwrite this from other places anyway..
>>
>> But xl creates an interface 'fw11' with ip 192.168.2.128 and netmask
>> 255.255.255.255 which is defenetly not what I was expecting.
>
> Absolutely!
>
> At one point xl had a bug with handling spaces in the vif specification,
> which might cause ip= to not take affect. I thought it was fixed, but
> perhaps not?
>
> Do you see an "ip" node under the vif backend device in xenstore?
>
> Can you try dropping the spaces in your configuration file?
>
>> Can somebody explain why xl behaves the way it does and how can I
>> change this? I could only find vif-nat setting routes but nothing
>> about netmasks and IPs so I guess i'm missing something here..
>
> I expect that the .2.128 comes from routing_ip() in the vif-nat script.
> However this hasn't changed recently and should behave the same under xl
> as it did under xm so obviously something is up.
>
> If it's not the problem above then you might need to add some additional
> logging to the vif-nat script to figure out why it isn't accepting your
> ip setting.
>
> Ian.
>

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