From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: VPN Graphs
Date: Wed, 01 Apr 2020 09:34:41 +0100 [thread overview]
Message-ID: <38C20EE9-CFD4-4CF4-A425-EAE15CADB25F@ipfire.org> (raw)
In-Reply-To: <AE2496A1-AF38-4964-97D1-0442DE2EF1DF@rymes.com>
[-- Attachment #1: Type: text/plain, Size: 1313 bytes --]
Hey Tom,
> On 31 Mar 2020, at 21:36, Tom Rymes <trymes(a)rymes.com> wrote:
>
> I noticed that graphs for OpenVPN connections have been added to the WUI, and with all of the added VPN usage in the last weeks, it sure would be nice to have similar graphs for IPsec Roadwarriors and Net-to-Net connections. I’m not certain if the nature of IPSec will prevent that from being possible, but it sure would be nice.
I agree. I would like those, too.
However, we currently have no efficient way to collect this data.
Running iftop or any other user-space process counting packets is heavily inefficient.
OpenVPN is being realised by having an interface where we can simply read packet counters from the kernel. We could in theory do this for IPsec tunnels that use VTI or GRE. But I would not feel comfortable adding that without the regular tunnels, because that is the vast majority.
Best,
-Michael
> Tom
>
> PS: In the meantime, and in the event it might be handy for anyone in a similar situation, I have been using the following commands for ‘iftop’ to get a handle on any VPN users that are hogging bandwidth:
>
> iftop -i red0 -nP
>
> iftop -n -i green0 -F x.x.x.x/y (place in a subnet you want to restrict results to, I use the IPSec RoadWarrior address block).
>
>
parent reply other threads:[~2020-04-01 8:34 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <AE2496A1-AF38-4964-97D1-0442DE2EF1DF@rymes.com>]
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=38C20EE9-CFD4-4CF4-A425-EAE15CADB25F@ipfire.org \
--to=michael.tremer@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