May 8 15:41:46 dhcp6c[53628]: exitingMay 8 15:41:45 dhcp6c[53628]: no responses were receivedMay 8 15:41:27 dhcp6c[53628]: transmit failed: Device not configuredMay 8 15:41:27 dhcp6c[53628]: Sending ReleaseMay 8 15:41:18 dhcp6c[53628]: transmit failed: Device not configuredMay 8 15:41:18 dhcp6c[53628]: Sending ReleaseMay 8 15:41:14 dhcp6c[53628]: transmit failed: Device not configuredMay 8 15:41:14 dhcp6c[53628]: Sending ReleaseMay 8 15:41:12 dhcp6c[53628]: transmit failed: Device not configuredMay 8 15:41:12 dhcp6c[53628]: Sending ReleaseMay 8 15:41:10 dhcp6c[53628]: remove an address 2a02:678:10:b01:XXX:XXXX:XXXX:XXXX/64 on em0May 8 15:41:10 dhcp6c[53628]: remove an address 2a02:678:10:b02:XXX:XXXX:fXXXX:XXXX/64 on em3May 8 15:41:10 dhcp6c[53628]: transmit failed: Can't assign requested addressMay 8 15:41:10 dhcp6c[53628]: Sending ReleaseMay 8 15:41:10 dhcp6c[53628]: Start address releaseMay 8 15:41:04 dhcp6c[53628]: status code for NA-0: no addressesMay 8 15:41:04 dhcp6c[53628]: dhcp6c Received REQUESTMay 8 15:41:04 dhcp6c[53628]: Sending RequestMay 8 15:41:03 dhcp6c[53628]: Sending SolicitMay 8 15:41:03 dhcp6c[53628]: status code for NA-0: no addressesMay 8 15:41:03 dhcp6c[53628]: dhcp6c Received REQUESTMay 8 15:41:03 dhcp6c[53628]: Sending RequestMay 8 15:41:02 dhcp6c[53628]: Sending SolicitMay 8 15:41:01 dhcp6c[53628]: status code for NA-0: no addressesMay 8 15:41:01 dhcp6c[53628]: dhcp6c Received REQUESTMay 8 15:41:01 dhcp6c[53628]: Sending RequestMay 8 15:41:00 dhcp6c[53628]: Sending SolicitMay 8 15:41:00 dhcp6c[53628]: status code for NA-0: no addressesMay 8 15:41:00 dhcp6c[53628]: dhcp6c Received REQUESTMay 8 15:41:00 dhcp6c[53628]: Sending RequestMay 8 15:40:59 dhcp6c[53628]: Sending SolicitMay 8 15:40:58 dhcp6c[53628]: status code for NA-0: no addressesMay 8 15:40:58 dhcp6c[53628]: dhcp6c Received REQUESTMay 8 15:40:58 dhcp6c[53628]: Sending RequestMay 8 15:40:57 dhcp6c[53628]: Sending SolicitMay 8 15:40:57 dhcp6c[53628]: status code for NA-0: no addressesMay 8 15:40:57 dhcp6c[53628]: dhcp6c Received REQUESTMay 8 15:40:57 dhcp6c[53628]: Sending RequestMay 8 15:40:56 dhcp6c[53628]: Sending SolicitMay 8 15:40:55 dhcp6c[53628]: status code for NA-0: no addressesMay 8 15:40:55 dhcp6c[53628]: dhcp6c Received REQUESTMay 8 15:40:55 dhcp6c[53628]: Sending RequestMay 8 15:40:54 dhcp6c[53628]: Sending SolicitMay 8 15:40:54 dhcp6c[53628]: status code for NA-0: no addressesMay 8 15:40:54 dhcp6c[53628]: dhcp6c Received REQUESTMay 8 15:40:54 dhcp6c[53628]: Sending RequestMay 8 15:40:53 dhcp6c[53628]: Sending SolicitMay 8 15:40:53 dhcp6c[53628]: status code for NA-0: no addressesMay 8 15:40:53 dhcp6c[53628]: dhcp6c Received REQUESTMay 8 15:40:53 dhcp6c[53628]: Sending Request
It sounds funny but I've seen this too. First boot is perfect, afterwards reconfigure takes a up to a minute or it fails. Next reboot is perfect again.
What I've also seen is that although LAN is tracking, reloading LAN doesn't have any effect other than removing the IPv6, so you always want to reload WAN or better yet use the console option 11 to fully cycle the interface configuration.
The log says that it seems to be still asking for an address, did you enable the request prefix only option? Perhaps the logs are from before?
Quote from: franco on May 08, 2017, 06:42:59 amIt sounds funny but I've seen this too. First boot is perfect, afterwards reconfigure takes a up to a minute or it fails. Next reboot is perfect again.Taking up to a minute is likely due to having to wait for the next Router Advertisement when "Directly Send Solicit" is disabled. But when it completely fails, even with config that previously worked perfectly, it is some kind of bug.Quote from: franco on May 08, 2017, 06:42:59 amWhat I've also seen is that although LAN is tracking, reloading LAN doesn't have any effect other than removing the IPv6, so you always want to reload WAN or better yet use the console option 11 to fully cycle the interface configuration.All that is required to fix that is to send the HUP signal to the dhcp6c process of the "Parent Interface" when reconfiguring a Track Interface interface. This will cause it to reconfigure.