The CSC seems to work when assigning a specific tunnel IP to the client. But it seems not to work for setting (all) the routes, and for limiting the access: The wish would be to set only one IP for the client to be routed etc I solved it for now by adding fw-rules on the OpenVPN-interface on the server side: allow traffic from tunnel-IP x.y to server-VM a.b.c reject traffic from tunnel-subnet to rest of server-LAN Seems to work right now, suggestions welcome ;-)

@JKnott Yes your are right I am on vacation and it is not possible to change the local network. Changing my local network I will do it (but when I will be back at home) So I was trying to find a temporary bypass :-)

@viragomann Thanks for help yes I set : DNS Default Domain "check valid" Provide a default domain name to clients DNS Default Domain "with" mydomain.net

@VioletDragon How did you configure the WAN IPs? I cannot think of any reason, why a OpenVPN server should not work on localhost with port 1194 forwarded from the WAN IP. Still waiting on the logs to see, what's the server complaining.

I either throw the subnet or IP, just depends on how you want to do it and as long as the firewall can route them. On mine, Under IPv4 Local network(s): 10.250.2.0/24,10.10.10.8/32,192.168.100.0/24,192.168.101.0/24,10.10.10.7/32,10.10.15.90/32,10.250.10.0/24

Just a follow-up, since there's been no reply. I've concluded that it's related to or at least severely exacerbated by this issue in 24.11 with the dashboard impacting the system load: https://redmine.pfsense.org/issues/15969 It's kind of like the observer effect--it seems most prone to happening when I'm investigating it happening, or more particularly, when I've accidentally left a tab running the dashboard open. Earlier this week I logged in to get some info on a DHCP lease, forgot to log out and went on my merry way, came back a couple hours later to find that most of the OpenVPN connections had gone down again, plus there were a bunch of entries in system.log relating to php-fpm and connections being refused for loading the dashboard widgets. I restarted php-fpm and the gui from the console menu, and the VPN connections all came back online within a short period of time. I'll be glad when 25.03 comes out so this problem is fixed!

@viragomann Thanks!!! It works!

@phil80 It works, syntax is wrong. You have to specify time that token is valid for: auth-gen-token 86400; auth-gen-token 0; --->>Set to 0 never expires For me it works on both Android clients and on windows also. We use duo push mfa and when we change networks, we see in log that session token is used for reauth... Also, if reneg-sec on server is 36000 and this option is not set on client it will still renegotiate after 3600 seconds because this is hard coded to 3600 if not set. And SMALLER number is used, so if server has 3600000 seconds set, and client has nothing specified, 3600 applies. My settings: reneg-sec 7200; push "reneg-sec 7200"; auth-gen-token 86400; status /var/log/openvpn-status.log; Works like charm for 400 openvpn clients.

This is a config. client setenv SERVER_POLL_TIMEOUT 4 nobind remote IP 1194 tcp dev tun dev-type tun ns-cert-type server reneg-sec 604800 sndbuf 100000 rcvbuf 100000 auth-retry nointeract verb 3 cipher AES-256-GCM ncp-ciphers AES-256-GCM:AES-256-CBC:AES-128-GCM auth SHA256 ca /config/openvpn/keys/ca.crt cert /config/openvpn/keys/phone1.crt key /config/openvpn/keys/phone1.key

@Lagan said in OpenVPN Client Specific Overrides ot updated until server restarted: I would like the new override to take effect when I restart the client. Hummm. It's possible that a save on the "Client Specific Overrides" page doesn't restart the OpenVPN server - I doesn't seem to do that. Maybe it isn't needed, as the server has a setting : client-config-dir /var/etc/openvpn/server1/csc/ that tells the server to look into that folder for client special settings, the "Client Specific Overrides". Anyway, I did restart the server, then connected the client and it got the '.30' IP.

I believe that is not affected. I can only see tls crypt (without V2) being enabled in my config.

Yes, I tried that too. I tried to ping the client's tunnel IP - unsuccessfully.

@viragomann That worked. You are awesome! Thank you so much.