dpinger (IPv6) dies after upstream IP renewal

[Space]

Hi,

I am running OPNsense behind a FritzBox (which get's new IPv4 and IPv6 addresses each night) and with 19.1.8 the dpinger always dies during IP renewal. The IPv6 address on WAN get's renewed via DHCPv6 and LAN follows WAN IPv6 address. In the log (gateways.log) I only see the following lines:

Code Select Expand

May 29 03:58:57 OPNvirt dpinger: WAN_DHCP6 2a03:f580:2:0:85:22:54:90: Alarm latency 1948us stddev 150us loss 22%
May 29 03:58:57 OPNvirt dpinger: GATEWAY ALARM: WAN_DHCP6 (Addr: 2a03:f580:2:0:85:22:54:90 Alarm: 1 RTT: 1948ms RTTd: 150ms Loss: 22%)

In system.log I only find the DHCP Reply before and after the renewal and OpenVPN complaining:

Code Select Expand

May 29 03:44:49 OPNvirt dhcp6c[46992]: Sending Renew
May 29 03:44:49 OPNvirt dhcp6c[46992]: unknown or unexpected DHCP6 option opt_86, len 16
May 29 03:44:49 OPNvirt dhcp6c[46992]: Received REPLY for RENEW
May 29 03:58:59 OPNvirt opnsense: /usr/local/etc/rc.openvpn: OpenVPN: One or more OpenVPN tunnel endpoints may have changed its IP. Reloading endpoints that may use WAN_DHCP6.
May 29 03:58:59 OPNvirt opnsense: /usr/local/etc/rc.openvpn: OpenVPN: Resync server1 SpaceNet OpenVPN Server
May 29 04:14:49 OPNvirt dhcp6c[46992]: Sending Renew
May 29 04:14:49 OPNvirt dhcp6c[46992]: Received REPLY for RENEW
May 29 04:14:49 OPNvirt dhcp6c[46992]: status code: no binding

If I start the IPv6 dpinger it works fine until the next morning ...

Code Select Expand

May 29 14:36:23 OPNvirt opnsense: /status_services.php: Removing static route for monitor 2a03:f580:2:0:85:22:54:90 via fe80::eadf:70ff:fe59:bd49%igb1
May 29 14:36:23 OPNvirt opnsense: /status_services.php: Adding static route for monitor 2a03:f580:2:0:85:22:54:90 via fe80::eadf:70ff:fe59:bd49%igb1

Any idea how to troubleshoot?

Thanks and best regards,

    Space

[Space]

Just to be clear: this issue was present since a longer time ... so it did not start with 19.1.8 ...

Best regards,

    Space

[sbuckmann]

I have the same problem, and it also started with 19.1.8 (never seen before),