mondoarchive NFS does not work with zeroconf installed

[andree]

zeroconf (www.zeroconf.org) apparently adds an IP address from the 169.254.0.0/16 range to an interface. So, with zeroconf installed I get the following outout from 'ip addr':

1: lo: <LOOPBACK,UP,10000> mtu 16436 qdisc noqueue

link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo inet6 ::1/128 scope host

valid_lft forever preferred_lft forever

2: eth0: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc pfifo_fast qlen 1000

link/ether 00:11:d8:50:e0:80 brd ff:ff:ff:ff:ff:ff inet 169.254.134.104/16 brd 169.254.255.255 scope link eth0 inet 192.168.1.213/24 brd 192.168.1.255 scope global eth0 inet6 fe80::211:d8ff:fe50:e080/64 scope link

valid_lft forever preferred_lft forever

3: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop qlen 1000

link/ieee1394 00:e0:18:00:00:ce:cf:54 brd ff:ff:ff:ff:ff:ff:ff:ff

4: sit0: <NOARP> mtu 1480 qdisc noop

link/sit 0.0.0.0 brd 0.0.0.0

The interesting one here is 2: The 192.168.1.213 address is what is configured as a static address. 169.254.134.104 is what zeroconf adds.

Networking in general works fine with this. However, mondoarchive uses ifconfig to obtain the IP address for the NFS config. 'ifconfig' gives:

eth0 Link encap:Ethernet HWaddr 00:11:D8:50:E0:80

inet addr:169.254.134.104 Bcast:169.254.255.255 Mask:255.255.0.0 inet6 addr: fe80::211:d8ff:fe50:e080/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:13785 errors:0 dropped:0 overruns:0 frame:0 TX packets:10514 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:17528791 (16.7 MiB) TX bytes:977510 (954.5 KiB) Interrupt:177

lo Link encap:Local Loopback

inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:358 errors:0 dropped:0 overruns:0 frame:0 TX packets:358 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:20284 (19.8 KiB) TX bytes:20284 (19.8 KiB)

which means it only gives the IP address configured by zeroconf. And that address is what is using during restore and of course doesn't work.

I am not 100% sure what to do here but don't think it is super urgent. I mainly wanted it documented somewhere - maybe we should also put it in the wiki?

One interesting comment I saw is that apparently ifconfig is getting superseded by the ip command. Maybe we need at some stage replace ifconfig with ip.

Cheers, Andree