You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe The Problem
I installed Wireguard and WGDashboard into a Proxmox LXC machine and everything is working fine as expected, with one point where I don't get why it behaves so?!
Even when leaving PostUp/Down blank it works without any issues?!
Expected Error / Traceback
When defining PostUp and PostDown within $wg.conf file it should also use those rules, but even when I leave them blank everything is working, I can access WAN (Internet) and all local RFC1918 networks.
I actually want to block the VPN Clients accessing all local networks but as PostUp/PostDown doesn't have any effect I can do nothing to solve this issue.
Are you absolutely certain there are no running IPtables rules. Similar to an issue we had where the first time its applied it is not removed because the predown is not removing it.
Normally a WireGuard configuration with rules is applied like this:
activate -> apply the defined rules -> working state -> deactive -> delete the defined rules according to the config.
If you remove the predown lines and you do not manually remove the actual rules they will stay applied.
Can you check that?
Describe The Problem
I installed Wireguard and WGDashboard into a Proxmox LXC machine and everything is working fine as expected, with one point where I don't get why it behaves so?!
Even when leaving PostUp/Down blank it works without any issues?!
Expected Error / Traceback
When defining PostUp and PostDown within $wg.conf file it should also use those rules, but even when I leave them blank everything is working, I can access WAN (Internet) and all local RFC1918 networks.
I actually want to block the VPN Clients accessing all local networks but as PostUp/PostDown doesn't have any effect I can do nothing to solve this issue.
OS Information:
Sample of your
.conf
fileThe text was updated successfully, but these errors were encountered: