IPv6 constant dhcp request and solicits

[Jeffrey]

I've been trying to get IPv6 working with Verizon FiOS and I actually received a /56 prefix along with a link local address on my wan interface.  I'm successfully able to apply an IPv6 address to my LAN interfaces (utilizing 3 vlans on the lan interface) by tracking the WAN interface and specifying an IPv6 prefix ID, however the connectivity only works for a few seconds and then stops working.  If I do a simple tcpdump on my wan interface "tcpdump -igb4 ipv6" I see the following:

11:11:52.450942 IP6 2600:4040:af10::1 > ff02::1:ff6d:f468: ICMP6, neighbor solicitation, who has fe80::20e:b6ff:fe6d:f468, length 32
11:11:52.846407 IP6 fe80::20e:b6ff:fe6d:f468 > ff02::1:ff1c:a00c: ICMP6, neighbor solicitation, who has fe80::8aa2:5eff:fe1c:a00c, length 32
11:11:52.852941 IP6 fe80::20e:b6ff:feb0:6dc2.546 > ff02::1:2.547: dhcp6 request
11:11:53.002705 IP6 fe80::20e:b6ff:feb0:6dc2.546 > ff02::1:2.547: dhcp6 solicit
11:11:53.846201 IP6 fe80::20e:b6ff:fe6d:f468 > ff02::1:ff1c:a00c: ICMP6, neighbor solicitation, who has fe80::8aa2:5eff:fe1c:a00c, length 32
11:11:54.012969 IP6 fe80::20e:b6ff:feb0:6dc2.546 > ff02::1:2.547: dhcp6 request
11:11:54.362938 IP6 fe80::20e:b6ff:feb0:6dc2.546 > ff02::1:2.547: dhcp6 solicit
11:11:54.846199 IP6 fe80::20e:b6ff:fe6d:f468 > ff02::1:ff1c:a00c: ICMP6, neighbor solicitation, who has fe80::8aa2:5eff:fe1c:a00c, length 32
11:11:55.372914 IP6 fe80::20e:b6ff:feb0:6dc2.546 > ff02::1:2.547: dhcp6 request
11:11:55.456058 IP6 2600:4040:af10::1 > ff02::1:ff6d:f468: ICMP6, neighbor solicitation, who has fe80::20e:b6ff:fe6d:f468, length 32

This repeats continuously in rapid succession and never stops.

I have configured IPv6 for a friend utilizing the same hardware and was successful with the configuration and I noted that that setup does not generate the continuous stream of requests and solicits. 

I attempted to back everything out and have gone so far as to disable every IPv6 setting on the firewall that I could find and the firewall continues to send the same IPv6 request and solicit packets.  I have tried reinstalling the software and then reimporting my configuration and the solicits and requests start all over again.  My next attempt will be to simply recreate the configuration from scratch and not import my configuration.

One thing to note, I originally was using IPv6 over hurricane electric via GIT tunnel, could this be causing me grief?  I've deleted all the remnants of this configuration from the GUI.

Where is this coming from?  Why can I not stop it?

Jeff

[wbk]

Seeing your account has been registered for a while, I expect your installation is an upgrade of previous versions to 23.x.

My IPv6 got totally upset between 22.x and 23.x. After weeks of trial and error in restoring connectivity, I took the plunge and started over with a clean install of 23.1 and got basic IPv6 working in an instant. If I were in your situation now, I would boot a live install and configure IPv6 to exclude any traces of migrations from previous versions; then make a plan depending of the outcome of that test.

[Jeffrey]

a little drastic but it did solve the problem, at least I was able to restore individual portions of the configuration without causing a problem, restoring the complete configuration will trigger the problem.

I found I was able to trigger the issue once when creating vlan's on my inside interface.

I really wish I know what was triggering the failure.

Next issue, the ISP (Verizon FiOS) doesn't issue a IPv6 address to the WAN interface, it instead relies on a link-local address, just a /56 prefix, is there a way to automatically assign a /64 to the WAN interface? I would like all my systems behind the opnsense device to query unbound for dns and let unbound do the query to the outside, I'm assuming it wants to use the WAN interface's address.