Fixed in a later release of ntpd
** Changed in: ntp (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/697592
Title:
unable to create socket on eth0 (2
Aaarr: has to read :::ip-v4-address and ::ip-v4-address, not
ff:ff::ip-v4-address and 0::ip-v4-address!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/697592
Title:
unable to create socket o
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
I have been able to confirm this bug using the information supplied by
the Thomas in the last update.
Although ntp generates error messages every 5 minutes, it does respond
to queries on the ipv6 address.
This may be related to bug 700492 (although the error message is
slightly different they bot
Networking setup is quite simple: the machine in question does only have
one network interface:
auto eth0
iface eth0 inet static
address 192.168.1.4
netmask 255.255.255.0
gateway 192.168.1.1
iface eth0 inet6 static
address :::192.168.1.4
netmask 96
gateway :::192.168.1.1
ntp
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
This looks like a potential bug/configuration problem with the IP setup
of your Ubuntu installation; :::192.168.1.4 is a ipv4 address that
has been mapped to the ipv6 address space.
Please could your provide m
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/697592
Title:
unable to create socket on eth0 (210) for :::192.168.1.4#123
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://list
