From: Elliot Saba <staticfloat@gmail.com>
To: jens <jens@viisauksena.de>,
WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: wireguard-hosts file
Date: Fri, 24 Jan 2020 12:22:45 -0800 [thread overview]
Message-ID: <CAGGi21Yybv=geihS0g_zWEgFFGQG7C=TH4_xxKgXsw4mQ7c3Bg@mail.gmail.com> (raw)
In-Reply-To: <674aac2b-1b4c-022c-0e4d-596529dce78f@viisauksena.de>
[-- Attachment #1.1: Type: text/plain, Size: 2769 bytes --]
Just as a point of reference, I manually implemented my own solution for
this. I have all my wireguard key files named as `<hostname>.pub` in a
directory, then I source the following as one of my dot files:
#!/usr/bin/env bash
# Don't do anything if `wg` doesn't exist
*if *[[ *-z* $(which wg) ]]; *then*
*return*
*fi*
# Otherwise, load in our mapping of public keys to hostnames:
# Otherwise, load in our mapping of public keys to hostnames:
*declare* -A WG_HOST_MAP
*for* f *in* ${HOMES_PATH}/etc/secure/wireguard/*.pub; *do*
HOST=$(basename *"*${f%.*}*"*)
KEY=$(cat *"*$f*"*)
WG_HOST_MAP["${KEY}"]="${HOST}"
*done*
function wg()
{
# Do some special parsing for `wg show`
*if *[[ *-z* "$1" ]] || [[ "$1" *==* "show" ]]; *then*
WG_OUTPUT=$(unbuffer sudo -n $(which wg))
*for* K *in* "${!WG_HOST_MAP[@]}"; *do*
V="${WG_HOST_MAP["${K}"]}"
WG_OUTPUT="${WG_OUTPUT/"${K}"/"${V}"}"
*done*
*echo* "${WG_OUTPUT}"
*else*
# Pass through to actual `wg` otherwise
sudo -n $(which wg) "$@"
*fi*
}
*export* -f wg
You’ll notice that it automatically calls `sudo -n` on things, and that it
requires `unbuffer`, which is usually installed alongside `expect`, so that
it can capture the output of `wg` retaining the color codes.
-E
On January 24, 2020 at 8:04:12 AM, 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?
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
[-- Attachment #1.2: Type: text/html, Size: 24255 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-28 10:39 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 [this message]
2020-01-25 2:28 ` Inrin
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='CAGGi21Yybv=geihS0g_zWEgFFGQG7C=TH4_xxKgXsw4mQ7c3Bg@mail.gmail.com' \
--to=staticfloat@gmail.com \
--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).