public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Peer Dietzmann <dietzmann@brecht-schule.hamburg>
To: development@lists.ipfire.org
Cc: Peer Dietzmann <dietzmann@brecht-schule.hamburg>
Subject: [PATCH] ovpnmain.cgi: Add collumn for subnet
Date: Mon,  1 Jun 2026 21:57:31 +0200	[thread overview]
Message-ID: <20260601195732.32783-1-dietzmann@brecht-schule.hamburg> (raw)

Hello,

in an earlier version of IPFire the main OVPN page of the WUI showed the subnet of each client in separate tables. Since the upgrade of OpenVPN 2.6 this feature has been removed.

As I find it very useful to see directly on the first page to which subnet a client belongs, this patch should bring back this feature.
I think this is also something users requested multiple timesin the forum.

There is just one thing I am currently unsure how to handle: When a client belongs to the dynamic subnet, the current patch would display "dynamic" independent from the language of the WUI. Maybe this could be adjusted?

Best regards
Peer

Signed-off-by: Peer Dietzmann <dietzmann@brecht-schule.hamburg>
---
 html/cgi-bin/ovpnmain.cgi | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/html/cgi-bin/ovpnmain.cgi b/html/cgi-bin/ovpnmain.cgi
index 4e3cc7f50..0490c0112 100644
--- a/html/cgi-bin/ovpnmain.cgi
+++ b/html/cgi-bin/ovpnmain.cgi
@@ -5223,6 +5223,9 @@ END
 				<th>
 					$Lang::tr{'remark'}
 				</th>
+				<th width='10%'>
+					$Lang::tr{'ccd subnet'}
+				</th>
 				<th width='10%'>
 					$Lang::tr{'status'}
 				</th>
@@ -5291,6 +5294,9 @@ END
 		# Show remarks
 		print "<td>$confighash{$key}[25]</td>";
 
+		# Show subnet
+		print "<td class='text-center'>$confighash{$key}[32]</td>";
+
 		my $connstatus = "DISCONNECTED";
 
 		# Disabled Connections
-- 
2.43.0



                 reply	other threads:[~2026-06-01 19:57 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20260601195732.32783-1-dietzmann@brecht-schule.hamburg \
    --to=dietzmann@brecht-schule.hamburg \
    --cc=development@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox