Hello,
is it possible to bring back the OpenVPN Connection grouping by IP-Pool?
This was a good feature!
Now all connections are shown up in one table.
I’m on CU 198.
Greetz
Hello,
is it possible to bring back the OpenVPN Connection grouping by IP-Pool?
This was a good feature!
Now all connections are shown up in one table.
I’m on CU 198.
Greetz
+1
Exactly!
Please devs! It’s Christmas! Let the magic happen ![]()
Greetz
Having multiple tables with essentially the same type of information ended up with a lot of duplicated code which periodically would end up out of sync.
So we will not go back to having the previous duplicated code.
However, I am working on a patch which will add in to the new table the pool info (dynamic or static) for the Road Warrior connections.
More sorting options is always a nice way to help end user keep focus.
I will see what can be done regarding sorting the types and pools but that will have to wait until I can get some time int the New Year.
What about a small workaround by adding some js to the site to let the user manually sort the HTML table?
A competent software developer did not enjoyed that much use of js into webapplications, mostly because move the “thinking engine” outside of the server/interface and into the browser. In pure display this could be anyway acceptable, however if the table would be, in a future, used as a starting point to deliver configurations or worse… commands to the system, rely in js-managed data could be used as attack surface.
So… while understanding the reasoning behind this hint, I’d probably avoid use of js.
![]()
Maybe a small change in line (ovpnmain.cgi file) will be enough?
foreach my $key (sort { ncmp ($confighash{$a}[1],$confighash{$b}[1]) } keys %confighash) {

to
foreach my $key (sort { ncmp ($confighash{$a}[3],$confighash{$b}[3]) || ncmp($confighash{$a}[1], $confighash{$b}[1]) } keys %confighash) {
Best regards