Yes, both bugs are related. ntp assumes 0::ip-v4-address, ff:ff::ip-v4-address and ip-v4-address the same (they are not, but this is what ntpd thinks of). Since ip-v4-address is already opened, opening 0::ip-v4-address and ff:ff::ipv4-address will fail, because ntpd just strips off the higher bits and uses ip-v4-address instead.
-- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/697592 Title: unable to create socket on eth0 (210) for ::ffff:192.168.1.4#123 -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
