Mathias Fredriksson
Mathias Fredriksson
@SlothCroissant yeah, that's correct.
What does your current (active) WireGuard configuration look like (`show interfaces wireguard`, feel free to sensor your keys)? A reboot might help too.
Actually, I just noticed you are using `sudo` for the script, so the issue here is probably fixed by #16 but it won't work until those permissions issues are fixed...
Thanks for linking the thread @BrianG61UK. Judging from what I've read there I'm starting to suspect it's the use of both IPv4 and IPv6 that's causing issues here. Like karog...
@BrianG61UK if you want to test the theory, you could `configure`, delete the IPv6 `address` from `wg0` and from `peers -> allowed-ips`, `commit` (no need to save). Then run `upgrade`...
Did you try the manual configure steps to delete the IPv6 addresses I suggested? By doing those, followed by an upgrade via the script, what essentially happens is: 1. IPv6...
Do you mean a `.deb` you manually download onto the device or from the `cache` folder? Currently the `cache` folder is wiped on every upgrade to prevent piling up files...
@JiriPodhorny thanks. I recently became aware of (some) of these while digging through the USG rootfs files, and indeed, I believe these work the same on the USG as well....
@Sean-Der sure thing, done!
Thanks for the suggestion! I have considered this method in the past, but the reasons for abandoning it escape me. (At least one reason is that I did not know...