phragma

3 ms·

1. 1.▲
   by phragma 9y ago

   Or maybe a sub-interface per peer: # ip link add dev wg0 type wireguard # wg set wg0 listen 0.0.0.0:51820 listen ::/0:51820 private-key /path/to/private-key # ip link add dev wg0-peer1 type wireguard-peer
2. 2.▲
   by phragma 9y ago

   Quick follow-up. If the premise "the peer public key is sort of the peer's lladdr" is correct, here's an idea off my chest. (Beware that I am blissfully unaware of wireguard internals, just brainstorming.) If the peer p
3. 3.▲
   by phragma 9y ago

   > Looks real nice. Thanks! > Any plans to open source that? Not opposed to it, but on the other hand I have no idea how to package it? I ended up implementing daemons for eg. setting up all the interfaces and routing on the box, b
4. 4.▲
   by phragma 9y ago

   Yeah for sure. Here are some screenshots: https://imgur.com/a/aT8TU There are additional settings on the various detail screens (not shown), such as wg peers. Vuejs turned out to be quite cool. If you plug in a new li
5. 5.▲
   by phragma 9y ago

   I did a vuejs/html5 web interface for wireguard recently and found it delightful to work with. There was a few pain points on the way, if anyone is interested in learning from my mistakes. - there is no option to specify listener ip+po