-
I edited the portion of the code to give me 53 for a random lookup so my final config has port 53 in it:
`function get_free_udp_port
{
local port=$(shuf -i 053-053 -n 1)
ss -lau | grep $…
-
Things to include with your process proposal (delete this text):
* Expected benefits. Who gains the benefits? Why will they benefit?
Both Client WG and Functions WG represent a portion of Knativ…
-
I would like to manage remote wireguard installs without having to copy the wireguard config files there and reloading wg.
wg-api seems to be a perfect fit for this usecase as it allows to create a…
-
I have `wireguard-pia` and `transmission` working fine, but I'm not sure what the best practice is for using the `port.dat` to allow incoming connections to Transmission. My Docker-compose is like th…
-
If you would be so kind we have a question about the restart process.
Our Wireguard Server is running and we use your UI. But if we create new profiles and apply them, our clients get disconnected f…
-
Patching wg-quick with the command ``` sed -i /net\.ipv4\.conf\.all\.src_valid_mark/d `which wg-quick` ``` allows this container to be run without `privileged=true` when using WireGuard. Docker option…
-
### Expected behavior:
WireGuard client should connect to Streisand server and works fine.
### Actual Behavior:
WireGuard client connection is activated but could not work.
### Steps to Reprod…
-
After some digging around I found [this issue](https://gitlab.com/postmarketOS/pmaports/-/issues/923) for another kernel. It appears `CONFIG_NFT_FIB_IPV6` must be set.
```
withinboredom@Legion:~$ …
-
Wireguard works very well, but I'm missing the `wg-autostart` command. With `wg-quick up wg0` the tunnel comes up.
```
user@Server:~# sudo wg-quick up wg0
[#] ip link add wg0 type wireguard
[#] …
-
**systemd version the issue has been seen with**
> systemd 250 (250.4-1-arch)
**Used distribution**
> Arch Linux
**Linux kernel version used** (`uname -a`)
> `Linux myhostname 5.15.27-hard…
knthm updated
4 months ago