# OpenVPN GUI - Bring Back IP-Pool Grouping

**URL:** <https://community.ipfire.org/t/openvpn-gui-bring-back-ip-pool-grouping/15310>\
**Category:** OpenVPN\
**Created:** [1 December 2025 13:26 UTC](https://community.ipfire.org/t/openvpn-gui-bring-back-ip-pool-grouping/15310 "2025-12-01T13:26:17Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![odongarma](https://community.ipfire.org/user_avatar/community.ipfire.org/odongarma/32/9635_2.png) [@odongarma](https://community.ipfire.org/u/odongarma)\
**Post date:** [1 December 2025 13:26 UTC](https://community.ipfire.org/t/openvpn-gui-bring-back-ip-pool-grouping/15310/1 "2025-12-01T13:26:17Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![kuni](https://community.ipfire.org/user_avatar/community.ipfire.org/kuni/32/15490_2.png) [@kuni](https://community.ipfire.org/u/kuni)\
**Post date:** [4 December 2025 11:34 UTC](https://community.ipfire.org/t/openvpn-gui-bring-back-ip-pool-grouping/15310/2 "2025-12-04T11:34:17Z")

</div>

+1

> [@Visual seperation of adress pools](https://community.ipfire.org/t/visual-seperation-of-adress-pools/15254/1):
>
> Hi, i’m not sure which core-update, but i think since 2 core-udpates back, the visual seperation between dynamic/static adress pools und net2net-connections in openvpn overview is gone and all connection are visually all in one block. It would be nice, if this can be revertet. I don’t know why this was done, but if you want to organize OpenVPN connections, this new overview doesn’t help.

---

<div class="post-metadata">

**Author:** ![odongarma](https://community.ipfire.org/user_avatar/community.ipfire.org/odongarma/32/9635_2.png) [@odongarma](https://community.ipfire.org/u/odongarma)\
**Post date:** [4 December 2025 12:03 UTC](https://community.ipfire.org/t/openvpn-gui-bring-back-ip-pool-grouping/15310/3 "2025-12-04T12:03:29Z")

</div>

Exactly!

Please devs! It’s Christmas! Let the magic happen 🥰

Greetz

---

<div class="post-metadata">

**Author:** ![bonnietwin](https://community.ipfire.org/user_avatar/community.ipfire.org/bonnietwin/32/12350_2.png) [@bonnietwin](https://community.ipfire.org/u/bonnietwin)\
**Post date:** [13 December 2025 13:39 UTC](https://community.ipfire.org/t/openvpn-gui-bring-back-ip-pool-grouping/15310/4 "2025-12-13T13:39:41Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![tphz](https://community.ipfire.org/user_avatar/community.ipfire.org/tphz/32/16551_2.png) [@tphz](https://community.ipfire.org/u/tphz)\
**Post date:** [13 December 2025 14:13 UTC](https://community.ipfire.org/t/openvpn-gui-bring-back-ip-pool-grouping/15310/5 "2025-12-13T14:13:02Z")

</div>

> [@bonnietwin](#):
>
> 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.

🤔  
If there is a problem with two tables, can you group/sort by “Type”?

 ![obraz](https://community.ipfire.org/uploads/default/original/2X/4/468ef245a74bf25a78ad9a2c5e05d1e72d53bfb2.png)

---

<div class="post-metadata">

**Author:** ![pike\_it](https://community.ipfire.org/user_avatar/community.ipfire.org/pike_it/32/16425_2.png) [@pike\_it](https://community.ipfire.org/u/pike_it)\
**Post date:** [13 December 2025 14:31 UTC](https://community.ipfire.org/t/openvpn-gui-bring-back-ip-pool-grouping/15310/6 "2025-12-13T14:31:36Z")

</div>

More sorting options is always a nice way to help end user keep focus.

---

<div class="post-metadata">

**Author:** ![bonnietwin](https://community.ipfire.org/user_avatar/community.ipfire.org/bonnietwin/32/12350_2.png) [@bonnietwin](https://community.ipfire.org/u/bonnietwin)\
**Post date:** [15 December 2025 11:54 UTC](https://community.ipfire.org/t/openvpn-gui-bring-back-ip-pool-grouping/15310/7 "2025-12-15T11:54:11Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![odongarma](https://community.ipfire.org/user_avatar/community.ipfire.org/odongarma/32/9635_2.png) [@odongarma](https://community.ipfire.org/u/odongarma)\
**Post date:** [15 December 2025 18:23 UTC](https://community.ipfire.org/t/openvpn-gui-bring-back-ip-pool-grouping/15310/8 "2025-12-15T18:23:35Z")

</div>

What about a small workaround by adding some js to the site to let the user manually sort the HTML table?

---

<div class="post-metadata">

**Author:** ![pike\_it](https://community.ipfire.org/user_avatar/community.ipfire.org/pike_it/32/16425_2.png) [@pike\_it](https://community.ipfire.org/u/pike_it)\
**Post date:** [15 December 2025 22:35 UTC](https://community.ipfire.org/t/openvpn-gui-bring-back-ip-pool-grouping/15310/9 "2025-12-15T22:35:56Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![tphz](https://community.ipfire.org/user_avatar/community.ipfire.org/tphz/32/16551_2.png) [@tphz](https://community.ipfire.org/u/tphz)\
**Post date:** [11 March 2026 17:55 UTC](https://community.ipfire.org/t/openvpn-gui-bring-back-ip-pool-grouping/15310/10 "2026-03-11T17:55:35Z")

</div>

🤔  
Maybe a small change in line (`ovpnmain.cgi` file) will be enough?

```auto
foreach my $key (sort { ncmp ($confighash{$a}[1],$confighash{$b}[1]) } keys %confighash) {

```

![obraz](https://community.ipfire.org/uploads/default/original/2X/7/79f1f0602f459b2d5101fc25adb3d2eaa6cba246.png)

* * *

to

```auto

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

```

Best regards

---

<div class="post-metadata">

**Author:** ![tphz](https://community.ipfire.org/user_avatar/community.ipfire.org/tphz/32/16551_2.png) [@tphz](https://community.ipfire.org/u/tphz)\
**Post date:** [12 June 2026 15:08 UTC](https://community.ipfire.org/t/openvpn-gui-bring-back-ip-pool-grouping/15310/11 "2026-06-12T15:08:18Z")

</div>

It seems that the above change has also worked in the version::  
Core-Update 203 Development Build: master/e9a5fbb3

 ![obraz](https://community.ipfire.org/uploads/default/original/2X/f/f6563034169d9645c08c0d73f2127382eb38655e.png)
