After a week or so of testing things with my new ISP we came to the discovery that OPNsense wasn't responding to the ISP's Neighbour Solicitation messages which caused instability in DHCPv6 PD messages.
An example of this is
Frame 7295: Packet, 86 bytes on wire (688 bits), 86 bytes captured (688 bits)
Ethernet II, Src: JuniperNetwo_11:48:3b (fc:33:42:11:48:3b), Dst: SBluetech_1e:16:40 (60:be:b4:1e:16:40)
Internet Protocol Version 6, Src: 2a02:8010::188, Dst: fe80::62be:b4ff:fe1e:1640
Internet Control Message Protocol v6
Type: Neighbor Solicitation (135)
Code: 0
Checksum: 0xf04c [correct]
[Checksum Status: Good]
Reserved: 00000000
Target Address: fe80::62be:b4ff:fe1e:1640
ICMPv6 Option (Source link-layer address : fc:33:42:11:48:3b)
Type: Source link-layer address (1)
Length: 1 (8 bytes)
Link-layer address: JuniperNetwo_11:48:3b (fc:33:42:11:48:3b)
It required me to set the following before responses would be sent out 'sysctl net.inet6.icmp6.nd6_onlink_ns_rfc4861=1'. My research is giving conflicting info as to why this is needed when there was no problem with my previous ISP.
Does anyone have any ideas?
An example of this is
Frame 7295: Packet, 86 bytes on wire (688 bits), 86 bytes captured (688 bits)
Ethernet II, Src: JuniperNetwo_11:48:3b (fc:33:42:11:48:3b), Dst: SBluetech_1e:16:40 (60:be:b4:1e:16:40)
Internet Protocol Version 6, Src: 2a02:8010::188, Dst: fe80::62be:b4ff:fe1e:1640
Internet Control Message Protocol v6
Type: Neighbor Solicitation (135)
Code: 0
Checksum: 0xf04c [correct]
[Checksum Status: Good]
Reserved: 00000000
Target Address: fe80::62be:b4ff:fe1e:1640
ICMPv6 Option (Source link-layer address : fc:33:42:11:48:3b)
Type: Source link-layer address (1)
Length: 1 (8 bytes)
Link-layer address: JuniperNetwo_11:48:3b (fc:33:42:11:48:3b)
It required me to set the following before responses would be sent out 'sysctl net.inet6.icmp6.nd6_onlink_ns_rfc4861=1'. My research is giving conflicting info as to why this is needed when there was no problem with my previous ISP.
Does anyone have any ideas?
"