andrianbdn / wg-cmd Goto Github PK

Describe the bug
NAT options don't work

To Reproduce
Steps to reproduce the behavior:

1. Create a new tunnel & client
2. Enable NAT
3. Try and use tunnel
4. Client can't route

Expected behavior
Client should be able to route

Environment (please complete the following information):

• OS: Linux
• Distribution Debian 12
• Current

Additional context

I fixed this by adding "iptables -A FORWARD -o wg0 -j ACCEPT" to PostUp, so the 2 lines for me now look like:

PostUp = iptables -A FORWARD -i wg0 -j ACCEPT; iptables -t nat -A POSTROUTING -o ens18 -j MASQUERADE; iptables -A FORWARD -o wg0 -j ACCEPT
PostDown = iptables -D FORWARD -i wg0 -j ACCEPT; iptables -t nat -D POSTROUTING -o ens18 -j MASQUERADE; iptables -D FORWARD -o wg0 -j ACCEPT

Is your feature request related to a problem? Please describe.
On machine with IPv6, the DNS settings only reflect an IPv4 address, not the IPv6.

Describe the solution you'd like
Include the v4 and v6 addresses for DNS

Describe alternatives you've considered
Manually retrieved the IPv6 DNS addresses and added them to the configuration.

Additional context
Would enable the internet transition to v6. Love the commander!

Is your feature request related to a problem? Please describe.
I have a server (a) and 2 clients (b,c). Client b sits on a LAN with many other devices (192.168.1.0/24). I'd like to access those devices (in which WG can't be installed) from client c (via the server). To do this in a typical Wireguard configuration (skipping iptables and systcl config for now) you would append the subnet (192.168.1.0/24) to AllowedIPs in the server config file for the peer that sits on the LAN (b).

Describe the solution you'd like
A way to define AllowedIPs for peers, but in the server config file.

Describe alternatives you've considered
N/A

Additional context
Thank you for this excellent project!

Add MTU setting Client and Server

WG-server

[Interface]
...
MTU = 1420

WG-peer

[Interface]
...
MTU = 1384