Paul 101b5564c2 Fix for fwmark ... Evidently, wireguard's (use of) fwmark is not well understood. In short, it determines which routing table to use for a tunnel's packets. Adding a fwmark to a roadwarrior client config won't do anything to the actual packets sent to a peer: Packets do not get marked. A QRCode with `FwMark = ...` in it is invalid. FwMark is now excluded from client configs (but is written to the server config /etc/wireguard/wgX.conf). Potential breaking change of `WGUI_FORWARD_MARK` to `WGUI_FIREWALL_MARK` But this has the effect of making users eventually notice that it probably does not do what they want/think. See: https://ro-che.info/articles/2021-02-27-linux-routing https://casavant.org/2020/10/10/wireguard-fwmark.html https://www.blinkenlights.ch/ccms/posts/source-based-routing/		2023-02-16 20:07:15 +01:00
..
about.html	About page (#296)	2023-02-16 17:31:24 +01:00
base.html	About page (#296)	2023-02-16 17:31:24 +01:00
clients.html	Fix for fwmark	2023-02-16 20:07:15 +01:00
global_settings.html	Fix for fwmark	2023-02-16 20:07:15 +01:00
login.html	Add favicon (#288)	2023-02-16 17:09:24 +01:00
profile.html	feat: update user profile (#280)	2022-12-21 21:52:00 +01:00
server.html	Fix doubled tags on reload (#277)	2022-12-21 21:55:49 +01:00
status.html	Status show IP's (#291)	2023-02-16 17:10:11 +01:00
wake_on_lan_hosts.html	Fixed the problem that Wake On Lan does not work when BASE_PATH is set. (#229)	2022-09-30 10:39:12 +02:00
wg.conf	PresharedKey is now only included if set (#141)	2022-01-29 09:11:50 +01:00