OpenVPN CSO what happened to custom_options

[gulaschcowboy]

Hi everybody,

in the old "Servers" menu, we use the "Advanced" section a lot:

Code: [Select]

learn-address "/usr/local/sbin/openvpn.learn-address-nsupdate.sh";
push "dhcp-option DOMAIN lan.domain.com";
push "dhcp-option DOMAIN-SEARCH lan.domain.com";
push "dhcp-option DOMAIN-ROUTE lan.domain.com";
push "dhcp-option DOMAIN-ROUTE .";
push "dhcp-option DOMAIN ~.";Especially the custom "learn-adress" script and "dhcp-option DOMAIN ~." are essential for us. Is this old "Servers" going to stay, or how we can achieve those custom options with the new logic behind "Instances [new]"?

[mgiammarco]

Hi All,
I'm Mario and this is my first post on this forum. Pleased to meet You.

I.ve upgraded OPNSense to version 23.7.6 and tried to reconfigure static ip assignment to my OpenVPN clients but this does not work.

My OpenVPN server creates the following subnet 192.168.20.0/24. I want a certain user to login and get always IP 192.168.20.8, so I configured in CSO "IPv4 Tunnel network" to "192.168.20.8/32". It does not work. 

It seems that CSO are completely ignored when client with specific username is logging in. Confirmed also by trying to check the option "Connection blocking"; use can still login normally.

It seems that common name and username never match. I also checked "Force CSO Login Matching" but does not work.

HI,
I have the same name (Mario!) and the same problem.
I am on OPNSense 23.7.12 bought from Azure (so it seems OPNSense earns a commission) and, after an update from previous version I have lost custom options in cso. Now I put topology, but ipv4 ip tunnel network is ignored so I cannot set ip for clients.
I have several openvpn servers active, can it be the problem?

[adam@entropy.cc]

Hi all,
If anyone is still watching this thread we have a similar issue as we used the "plugin" option here to integrate Duo Security.

Hoping this could get added in as an option in lieu of an actual custom field.

We had something in the attached png.