CRISPR to the rescue!
hayalci
joined 2 years ago
Random idea, continuously ping the router from the laptop so it doesn't "forget" that the laptop exists on the WLAN?
(I know you mention the laptop can still reach out when you try, but maybe the trick is to keep having traffic to-from the laptop continuously)
i also think that it's overkill, especially for a minimalistic tool like wireguard. That's why I mentioned "if you want to be extra paranoid". This forum is for learning, and this question is an open ended learning question, hence, an opportunity to learn about port knocking, even if the actual real life benefit of that would be minuscule.
+1 on not using containers.for Network routing stuff That way lies pain and misery.
Good point, kernel updates should be paired with reboots to get kernel patches applied quickly.
Yes wireguard would only accept connections clfrom clients with known certificates, but this is "belt and suspenders" approach. What happens if there's a bug in wireguards packet parsing or certificate processing? Using port knocking would protect against this —very remote— possibility.
VPN software usually is built strong to begin with, and any vulnerabilities discovered will be promptly fixed as well, so updating frequently should suffice. (Why not automate it with unattended-upgrades package?
Using a random high port number will probably hide it well enough for Internet-wide port scanners as well.
if you want to be extra paranoid, you can hide the VPN service behind a port knocker as well.
I recommend https://migadu.com. not free, but the lowest price tier has lots of features, unlimited mailboxes etc.
See https://lemm.ee/post/4593760 for a related post and more discussions about pros and cons of each.
keepass2android is worth a try as well.
You got an excellent short answer here, but for a more extensive article check out https://itsfoss.com/compile-linux-kernel/
A good answer to a "why?" question is "why not?" This can be a great learning or practice opportunity for redundant network links and other interface challenges.
Did you consider keeping the services closed to the outside world and using tailscale to access them? Doesn't work well if you want to give access to a bunch of people, though.