Help with IPv6

[Taomyn]

A real one

[franco]

This is confusing. I need a break. :/

[Taomyn]

Welcome to my world :-)

[djGrrr]

Taomyn, can you try setting it to request ipv6 prefix only, and disable directly send solicit?

This should allow Router Advertisements to give you the IP, while letting dhcp6c to request the prefixes.

Make sure to reboot after making these changes to verify if they work.

[Taomyn]

WAN ended up with just an FE80, the LANs with no IPv6. I rebooted the firewall as well. The log shows:

Code: [Select]

May 8 15:41:46 dhcp6c[53628]: exiting
May 8 15:41:45 dhcp6c[53628]: no responses were received
May 8 15:41:27 dhcp6c[53628]: transmit failed: Device not configured
May 8 15:41:27 dhcp6c[53628]: Sending Release
May 8 15:41:18 dhcp6c[53628]: transmit failed: Device not configured
May 8 15:41:18 dhcp6c[53628]: Sending Release
May 8 15:41:14 dhcp6c[53628]: transmit failed: Device not configured
May 8 15:41:14 dhcp6c[53628]: Sending Release
May 8 15:41:12 dhcp6c[53628]: transmit failed: Device not configured
May 8 15:41:12 dhcp6c[53628]: Sending Release
May 8 15:41:10 dhcp6c[53628]: remove an address 2a02:678:10:b01:XXX:XXXX:XXXX:XXXX/64 on em0
May 8 15:41:10 dhcp6c[53628]: remove an address 2a02:678:10:b02:XXX:XXXX:fXXXX:XXXX/64 on em3
May 8 15:41:10 dhcp6c[53628]: transmit failed: Can't assign requested address
May 8 15:41:10 dhcp6c[53628]: Sending Release
May 8 15:41:10 dhcp6c[53628]: Start address release
May 8 15:41:04 dhcp6c[53628]: status code for NA-0: no addresses
May 8 15:41:04 dhcp6c[53628]: dhcp6c Received REQUEST
May 8 15:41:04 dhcp6c[53628]: Sending Request
May 8 15:41:03 dhcp6c[53628]: Sending Solicit
May 8 15:41:03 dhcp6c[53628]: status code for NA-0: no addresses
May 8 15:41:03 dhcp6c[53628]: dhcp6c Received REQUEST
May 8 15:41:03 dhcp6c[53628]: Sending Request
May 8 15:41:02 dhcp6c[53628]: Sending Solicit
May 8 15:41:01 dhcp6c[53628]: status code for NA-0: no addresses
May 8 15:41:01 dhcp6c[53628]: dhcp6c Received REQUEST
May 8 15:41:01 dhcp6c[53628]: Sending Request
May 8 15:41:00 dhcp6c[53628]: Sending Solicit
May 8 15:41:00 dhcp6c[53628]: status code for NA-0: no addresses
May 8 15:41:00 dhcp6c[53628]: dhcp6c Received REQUEST
May 8 15:41:00 dhcp6c[53628]: Sending Request
May 8 15:40:59 dhcp6c[53628]: Sending Solicit
May 8 15:40:58 dhcp6c[53628]: status code for NA-0: no addresses
May 8 15:40:58 dhcp6c[53628]: dhcp6c Received REQUEST
May 8 15:40:58 dhcp6c[53628]: Sending Request
May 8 15:40:57 dhcp6c[53628]: Sending Solicit
May 8 15:40:57 dhcp6c[53628]: status code for NA-0: no addresses
May 8 15:40:57 dhcp6c[53628]: dhcp6c Received REQUEST
May 8 15:40:57 dhcp6c[53628]: Sending Request
May 8 15:40:56 dhcp6c[53628]: Sending Solicit
May 8 15:40:55 dhcp6c[53628]: status code for NA-0: no addresses
May 8 15:40:55 dhcp6c[53628]: dhcp6c Received REQUEST
May 8 15:40:55 dhcp6c[53628]: Sending Request
May 8 15:40:54 dhcp6c[53628]: Sending Solicit
May 8 15:40:54 dhcp6c[53628]: status code for NA-0: no addresses
May 8 15:40:54 dhcp6c[53628]: dhcp6c Received REQUEST
May 8 15:40:54 dhcp6c[53628]: Sending Request
May 8 15:40:53 dhcp6c[53628]: Sending Solicit
May 8 15:40:53 dhcp6c[53628]: status code for NA-0: no addresses
May 8 15:40:53 dhcp6c[53628]: dhcp6c Received REQUEST
May 8 15:40:53 dhcp6c[53628]: Sending Request


[djGrrr]

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?

[djGrrr]

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.

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.

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.

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.

[Taomyn]

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?

[djGrrr]

What happens if you set the WAN IPv6 config to SLAAC? do you get an ip address then?

[Taomyn]

Nope, I even rebooted and waited 10 minutes - no IPv6 addresses anywhere

[djGrrr]

Then honestly, the only thing i can suggest is that your ISP has a misconfiguration somewhere, there is no reason why you shouldn't be able to request both a an address and a prefix at the same time.

Does routing work when you only have a prefix delegation?

[Taomyn]

Yes, routing is working as far as I can tell - I have performed some IPv6 testing internally and it appears to work.


I'll try to contact my ISP again, but they've been next to useless so far. They told me to connect my old FritzBox router and that that would work - which is all they officially support. Just getting them to enable IPv6 took me two months, and then they never told me until after I found out for myself.

[franco]

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.

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.

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.

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.

master should be a lot better now. Reloading works reliably although the delay is there sometimes. Releasing WAN lease removes LAN track IPv6. Renewing WAN lease brings back LAN tracking. Reloading LAN brings back tracked IPv6.

I also think I found that HUP bug:

https://github.com/opnsense/core/commit/d0a94a5b

To be honest, there was not a lot of work done on this code area in a few years.


Cheers,
Franco