public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: "Peter Müller" <peter.mueller@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] netother.cgi: show content of routing table 220
Date: Sun, 08 Mar 2020 13:15:00 +0000	[thread overview]
Message-ID: <ed593e05-e25f-ec0a-9e9f-af55c44dc914@ipfire.org> (raw)
In-Reply-To: <36253712-E143-4794-84DA-A74562317C38@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 2005 bytes --]

Hello Michael,

> Hi,
> 
> I appreciate the thought, but I think the implementation might be very confusing.
> 
> I think the patch could be improved by:
> 
> * Removing the 220 number and simply call it “IPsec VPN Routing Table”

Okay, good point.

> 
> * Not show the box when the table is empty which it will be for all users that are not using IPsec

ACK.

> 
> And since it is basically a static table, I do not see what there is to gain for the user from this. How can this help with debugging?

For the same reasons we display contents of the routing table, I guess. The user is
able to do quick plausibility checks over it, without digging/using the search
engine of his/hers least distrust for the command that shows him the IPsec routing information.

Thanks, and best regards,
Peter Müller

> 
> -Michael
> 
>> On 7 Mar 2020, at 18:46, Peter Müller <peter.mueller(a)ipfire.org> wrote:
>>
>> Since IPsec routing information do not show up in the normal routing
>> table, also displaying the contents of table 220 on netother.cgi might
>> be useful for debugging purposes.
>>
>> Signed-off-by: Peter Müller <peter.mueller(a)ipfire.org>
>> ---
>> html/cgi-bin/netother.cgi | 6 ++++++
>> 1 file changed, 6 insertions(+)
>>
>> diff --git a/html/cgi-bin/netother.cgi b/html/cgi-bin/netother.cgi
>> index dde1b603a..ac02b8148 100644
>> --- a/html/cgi-bin/netother.cgi
>> +++ b/html/cgi-bin/netother.cgi
>> @@ -79,6 +79,12 @@ if ( $querry[0] =~ "fwhits"){
>> 	print "<pre>$output</pre>\n";
>> 	&Header::closebox();
>>
>> +	&Header::openbox('100%', 'left', "$Lang::tr{'routing table entries'} 220");
>> +	$output = `/sbin/ip route list table 220`;
>> +	$output = &Header::cleanhtml($output,"y");
>> +	print "<pre>$output</pre>\n";
>> +	&Header::closebox()
>> +
>> 	&Header::openbox('100%', 'left', $Lang::tr{'arp table entries'});
>> 	$output = `/sbin/ip neigh show`;
>> 	$output = &Header::cleanhtml($output,"y");
>> -- 
>> 2.16.4
> 

  reply	other threads:[~2020-03-08 13:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-07 18:46 Peter Müller
2020-03-08 11:42 ` Michael Tremer
2020-03-08 13:15   ` Peter Müller [this message]
2020-03-08 13:35     ` Michael Tremer
2020-03-21 16:03       ` [PATCH v2] " Peter Müller
2020-03-22  9:24         ` Michael Tremer
2020-03-30 17:38         ` Arne Fitzenreiter
2020-03-30 17:56           ` Peter Müller

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=ed593e05-e25f-ec0a-9e9f-af55c44dc914@ipfire.org \
    --to=peter.mueller@ipfire.org \
    --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