Public bug reported:
Binary package hint: avahi-autoipd
I have set up a wired network with a hub, one Feisty PC and one Edgy PC.
Edgy has a connection to an external network which uses DHCP, but on the
private wired network it has a static address in the Link local address
range (169.254.2.102). When I boot Feisty it doesn't find a DHCP server,
so it falls back to avahi-autoip (169.254.6.101). I test the connection
and both can ping each other successfully, I can also resolve mDNS/avahi
services.
Now, I have enabled IP forwarding and NAT on Edgy because I want Feisty
to be able to access the external network. Previously it was enough to
add a route to the external network via Edgy. So I do this on Feisty and
it doesn't work, I can't ping any PCs on the external network from
Feisty.
Using tcpdump on Edgy I can see that Feisty is using the 0.0.0.0 IP address. If
I specify Feisty's IP address in ping then I get replies,
i.e. ping -I 169.254.6.101 192.168.0.1 is successful.
So avahi-autoip allows access to the local netowork, but won't access
external networks. Is this the intended behaviour? It means that I will
have to use a static address instead.
Thanks
** Affects: avahi (Ubuntu)
Importance: Undecided
Status: Unconfirmed
--
avahi-autoipd in roaming mode set ip address to 0.0.0.0
https://bugs.launchpad.net/bugs/102865
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
