Wishlist for Improvements about wgadmin HOT 5 OPEN

What os and architecture are you using?
i.e. cat /etc/os-release

from wgadmin.

PRETTY_NAME="Debian GNU/Linux 12 (bookworm)"
NAME="Debian GNU/Linux"
VERSION_ID="12"
VERSION="12 (bookworm)"
VERSION_CODENAME=bookworm
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"

from wgadmin.

Interesting... I had not tested on Debian 12 as 11 was current when I first wrote this... I think I should test. The original target was RaspberryPiOS.

The Debian control file contains e.g.:

Version: 0.1.2-231124.1857
Architecture: amd64
Depends: wireguard, wireguard-tools, nftables
Maintainer: [email protected]
Description: WireGuard Administration App
Homepage: https://netrinos.com/wgtools/wireguard-admin-app
Section: base
Priority: optional 

I have not included openresolv as I had not encountered a system yet that did not have something running already. And if that's not openresolv, I don't want to make a mess. Although Debian can be a bit stripped down compared to others.

The ports for the server and peers are meant to be independent. If you leave it blank it will end up being a random high port as per wireguard norms. But, specifying it makes things a little easier to understand imho. If you change the server port and look in the client, you will see the server endpoint has the right port.

For the traffic per user, I am just relying on what wireguard give me. Wireguard resets the counters when the connections drop.

On the IP Forwarding commands... I don't see the difference. I'm pretty sure I just cut and pasted these from a terminal when I wrote it. And the quotes do not make a difference as far as I can tell. At least not on Debian 11... What am I missing? I did not include IPv6 as I am not dealing with IPv6 otherwise.

When I wrote it, the PostUp, PostDown, and PresharedKey seemed beyond what I considered "keep it simple". But maybe they should be added anyway. What specific use cases do you have in mind?

On the panic... Did it do this every time? Or was it a one-time event? I will do some testing on Debian 12 and see if I can reproduce it...

If it does it on the build I uploaded tonight, can you send me the panic again? After making my changes, the line numbers have changed.

You are in Debian 11. What architecture? i.e. uname -a. What scenario is this? Is it a PC, virtual server, single-board computer?

Thanks

from wgadmin.

I just uploaded v0.1.3 with the PostUp and PreDown added.

The error on Debian 12 is related to some permissions specific to that distro. It should be good now.

Please let me know if you have any more issues.

Peter

from wgadmin.

@Gill-Bates as for packages, you actually only need wireguard-tools as most modern distros these days has wireguard compiled into the kernel.

@precisionpete increment doesn't apear to be working.

Say you have 10.23.10.1/32 as your server node, the second peer you add should automaticly be 10.23.10.2/32 but it will give you 10.23.10.1 instead even though its in use.

from wgadmin.