From: Inrin <inrin@jikken.de>
To: wireguard@lists.zx2c4.com
Subject: Re: wireguard-hosts file
Date: Sat, 25 Jan 2020 03:28:14 +0100 [thread overview]
Message-ID: <20200125022814.wnoxrqymgf447ib2@nisshoku> (raw)
In-Reply-To: <674aac2b-1b4c-022c-0e4d-596529dce78f@viisauksena.de>
Maybe instead of an external file, why not add an option like Alias/Nick/Displayname/Peername?
This would have the benefit of keeping the public key in display.
For the get going you might use (GNU) sed or similar to achieve this feature.
Create a file peernames as follows:
s|<BASE64>|my nice peername|
s|<BASE64>|my other peername|
and pipe wg through sed:
wg | sed -f peernames
Of course you can get more creative. Maybe keep the public key there.
I'm not sure how to keep the colouring though.
PS:
I'm not sure if BSDs or others SED support changing / in substitutions.
On Fri, Jan 24, 2020 at 05:01:49PM +0100, jens wrote:
>i really would love to have a feature like wireguard-hosts file.
>whereas wg command would print given "name" instead of key - so the
>output would be more meaningfull
>We have some wireguard running in server like infrastructure, where one
>server serves dozens of "clients"
>
>so instead of
>peer: l9FxaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaU=
>we would have something alike
>peer: superhero downtown
>
>some of you may be familar with batman-adv layer2 routing protocol,
>there they also have a batctl which is working pretty similar to wg tool.
>there you can add a bat-hosts file which is doing the job, which totaly
>works likes any hosts file
>a normal hosts file maps ip to name,
>a bat-hosts file maps mac addresses to name,
>a wg-hosts file would map keys to name.
>
>i found the sources for bat-hosts ( .c .h .sample ) here
>https://downloads.open-mesh.org/batman/releases/batman-adv-2019.5/batctl-2019.5.tar.gz
>
>is this something maybe usefull to other also?
>is there a chance to have this implemented by default?
>
>thx for answers.
>fuzzle
>
>--
>make the world nicer, please use PGP encryption
>_______________________________________________
>WireGuard mailing list
>WireGuard@lists.zx2c4.com
>https://lists.zx2c4.com/mailman/listinfo/wireguard
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
next prev parent reply other threads:[~2020-01-30 1:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-24 16:01 jens
2020-01-24 20:22 ` Elliot Saba
2020-01-25 2:28 ` Inrin [this message]
2020-01-25 6:51 ` Steven Honson
2020-01-27 21:45 ` Barry Scott
2020-01-28 10:50 ` Kai Haberzettl
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=20200125022814.wnoxrqymgf447ib2@nisshoku \
--to=inrin@jikken.de \
--cc=wireguard@lists.zx2c4.com \
/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;
as well as URLs for NNTP newsgroup(s).