Messages

As AdSchellevis mentioned:

Code Select Expand

opnsense-patch 2c2eca7
will do the trick

Feature request opened.

To keep things together here is the issue https://github.com/opnsense/core/issues/3290.

I would realy love to see this feature on the roadmap!

(Viscosity has this feature too.)

On the FW directly yes:

Code Select Expand

--- 2606:4700:4700::1111 ping6 statistics ---
3 packets transmitted, 3 packets received, 0.0% packet loss
round-trip min/avg/max/std-dev = 2.514/2.566/2.616/0.042 ms

To check that from a device I have to test it from inside my LAN. I dont have VPN with IPv6 support yet.

Yes, I did, IPv4 is default in browser, ipv6 enabled on the device, IPv6 connectivity not supported, DNS4 + IP6 and DNS6 + IP6 unreachable, but DNS6 + IP4 is reachable.

I have the same occurance.

Although I can't acces ipv6.google.com from a device, but I can ping it from WAN/LAN/DMZ interface, but this is another issue (on my side I think).

We found the thing that causes this issue. For a temp solution until it gets included in 19.1.2 use this patch:

Code Select Expand

# opnsense-patch 90c0c395

The patch worked for me and I know now why the connection dropped every time.

I had "Firewall: Settings: Advanced: Dynamic state reset" active (Reset all states when a dynamic IP address changes.This option flushes the entire state table on IPv4 address changes in dynamic setups to e.g. allow VoIP servers to re-register.)
But the IP didn't change, so this trigger shouldn't have been triggered.

Code Select Expand

# opnsense-patch c83bb8d

I opened an issue on github:
https://github.com/opnsense/core/issues/3197

According to github, the last changes where 5 month ago.
I think it has something to do with the switch to HardenedBSD, but I am absolutly not a unix guy...

I can trigger the connection drop by manually executing /usr/local/etc/rc.newwanip

That is exactly what I also have monitored.

Ok, I need to update my case... It is not just the VPN connection that drops, the whole WAN connection gets disconnected every 20 minutes (I watch TV over the internet and every 20 minutes the stream hangs, i have to rewind to build up the new stream).

It has to be something with DHCP and the rc.newwanip script that runs every 20 minutes...

How can I help to debug this issue?

Is your Hostname and Port on the Client Export page correct?
It seams, that you left the internal ip in there, and port 443 is that correct for your setup?

This client setting didn't change anything.
The interface on the serverside gets its state changed every 20 minute.

The script that is running before (and while) the state changes is

Code Select Expand

opnsense: /usr/local/etc/rc.newwanip

I just upgraded from 18.7.10_4 to 19.1 and 19.1.1.
This is the only config change...

Could this be something with the change to HardenedBSD? I stayd connected with the 18.7.x version over hours