From: "Steven Honson" <steven@honson.id.au>
To: wireguard@lists.zx2c4.com
Subject: Re: wireguard-hosts file
Date: Sat, 25 Jan 2020 17:51:45 +1100 [thread overview]
Message-ID: <06a605c4-8d84-487a-899e-fe7ed899189c@www.fastmail.com> (raw)
In-Reply-To: <674aac2b-1b4c-022c-0e4d-596529dce78f@viisauksena.de>
[-- Attachment #1.1: Type: text/plain, Size: 1999 bytes --]
Hi!
There was some work underway a while back for something along these lines in https://git.zx2c4.com/wireguard-monolithic-historical/commit/?h=lr/peer-names&id=f50ef1676fe5861c9071910d2caf64593a28d837, <https://git.zx2c4.com/wireguard-monolithic-historical/log/?h=lr/peer-names> but unfortunately that work stalled out.
There are a few workarounds/alternatives out there such as https://github.com/warner/wireguard-vanity-address, which will help you generate keypairs with a short defined string in the public key, but this isn't likely to be workable for a large number of peers.
Cheers,
Steven
On Sat, 25 Jan 2020, at 3:01 AM, 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
>
>
> *Attachments:*
> * 0x507EB93F6F6DEE01.asc
[-- Attachment #1.2: Type: text/html, Size: 3034 bytes --]
[-- Attachment #2: Type: text/plain, Size: 148 bytes --]
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
next prev parent reply other threads:[~2020-01-25 6:52 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
2020-01-25 6:51 ` Steven Honson [this message]
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=06a605c4-8d84-487a-899e-fe7ed899189c@www.fastmail.com \
--to=steven@honson.id.au \
--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).