Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Barry Scott <barry@barrys-emacs.org>
To: jens <jens@viisauksena.de>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: wireguard-hosts file
Date: Mon, 27 Jan 2020 21:45:20 +0000	[thread overview]
Message-ID: <8BABCA2C-771B-41F7-BEC0-ADF779C6A8FB@barrys-emacs.org> (raw)
In-Reply-To: <674aac2b-1b4c-022c-0e4d-596529dce78f@viisauksena.de>



> On 24 Jan 2020, at 16:01, jens <jens@viisauksena.de> 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?

I thought about this problem as well. I was thinking along the lines
of having a user-defined string field that could be used as the
friendly client name instead of the client public key.

But since I concluded that I needed my own tooling on top of
what wireguard provides at the server end. At that point
I can replace the wg command with my own that does what
I want.

I use the client public key as the key into my client database.

I have a python script that added clients to the database,
generates a new server wg0.conf and a wg0.conf for each client.
It takes care of allocating the next free IP address in the VPN pool
for example.

Another python script takes the output of "wg show wg0 dump" and
the database to create a status output that uses the client names.

Barry



> 
> thx for answers.
> fuzzle
> 
> -- 
> make the world nicer, please use PGP encryption
> <0x507EB93F6F6DEE01.asc>_______________________________________________
> 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

  parent reply	other threads:[~2020-01-28 10:34 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
2020-01-27 21:45 ` Barry Scott [this message]
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=8BABCA2C-771B-41F7-BEC0-ADF779C6A8FB@barrys-emacs.org \
    --to=barry@barrys-emacs.org \
    --cc=jens@viisauksena.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).