[solved] I seem to have found and fixed the problem and so have some
confirmation I was on the right track in my previous post. Specifically
in file common.c line 3328 I changed:
if (ioctl(s, ioctl_cmd, &req)) {
debug_printf(LOG_NOTICE, FNAME, "failed to %s an address on %s: %s",
I made some headway in figuring this out. One thing I did not
understand was T1 and T2 time and so was looking at the logs at the
vltime hour mark. The proper place to be looking for the first error
was at the T1 mark when the renew operation takes place. At this point
the following happens in t
I noticed going through the avahi docs that this is used by Apple
apparently. Also Cox says there is a compatibility issue with the Apple
Airport Extreme and IPv6 failing after a day with the resolution being
restart the device. My issue is the IPv6 update for the subnet fails
after 24 hours or s
Got distracted for a bit, but finally got some testing done. It looks
like I was only partially right in that the display formatter was wrong,
so now I am seeing the correct time displayed. There is still something
going wrong with the dhcpv6 subnet update. Will have to spend more time
to proper
I have found evidence that the wide-dhcpv6 version in Ubuntu 14.04 at least was
written on a 32-bit architecture and never properly redesigned for a 64-bit
compilation. The evidence for this found in the source code goes as follows:
1. Consistent use of the printf formatter %ul for 32-bit int fi
If it helps, I have been documenting my setup in a templated format
here: http://ubuntuforums.org/showthread.php?t=2279612
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1559741
Title:
wide-dhcpv6 cl
No. As I am understanding the linked documentation, if you are setting
up a wide-dhcpv6 server, this can be specified. However seeing I am not
an ISP, but instead a customer, I am relegated to being a client and
specifying these parameters do not seem to be an option for the client.
Especially wi
see http://manpages.ubuntu.com/manpages/lucid/man5/dhcp6c.conf.5.html
Have you tried to specify the vltime in your config file?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1559741
Title:
wide-dhc