The company behind pfSense is shady as hell:
https://opnsense.org/opnsense-com/
Also the complete and utter clusterfuck of an attempt to bring Wireguard into the FreeBSD kernel:
The company behind pfSense is shady as hell:
https://opnsense.org/opnsense-com/
Also the complete and utter clusterfuck of an attempt to bring Wireguard into the FreeBSD kernel:
Gnomes built-in RDP should work. There’s also RustDesk which offers proper Wayland support.
What kind of ISP are you dealing with?
And maybe PPPoE.
traceroute --mtu 1.1.1.1
Pick the lowest value displayed for F=xxxx
like e.g F=1492
and subtract 80.
For my DSL connection the optimal value is 1412.
nonfree drivers accessible right away
Non-free firmware is included in the Debian installer since Bookworm.
Do you really know how Wireguard works?
Updating without a reboot only works for wireguard-go. The default implementation runs in the kernel. An update to it would require kernel live patching.
Wireguard doesn’t answer to unsigned packets. Using obscure ports or even port knocking is rather pointless. It’s indistinguishable from a closed port.
I’d rather take Casaos out of the equation and target Ubuntus’ Wireguard stack instead.
Did you enable forwarding via sysctl?
sysctl net.ipv4.ip_forward
This should report 1
You only need the masquerade rule.
iptables -t nat -A POSTROUTING -s 10.11.13.0/24 -o enp3s0 -j MASQUERADE
ext4 + mdadm + dm-integrity would solve the bit rot problem. But you’d end up with a lot of parts bolted together and still miss out on the features that btrfs/zfs provide.
OpenOffice is a zombie at this point.