hayalci

joined 2 years ago
[–] [email protected] 2 points 2 years ago

You can use Snikket with other servers too, there is no restriction or special sauce. It's mostly a fork of Conversations.

[–] [email protected] 2 points 2 years ago

The same author talks about load balancing in one article and retries in the other one ¯⁠\⁠_⁠(⁠ツ⁠)⁠_⁠/⁠¯

[–] [email protected] 4 points 2 years ago

in addition to "dedicated Nas + compute node" and "just use a desktop" suggestions, there's the microserver option in between. Small, but has enough power to run stuff other than storage.

Hp proliant microserver is what I use, you can try getting a previous generation from second hand market.

https://www.hpe.com/us/en/product-catalog/compute/proliant-servers/pip.proliant-microserver.1014673551.html

[–] [email protected] 2 points 2 years ago

"underpowered" routers are usually underpowered for multiple high bandwidth wireless connections. if you disable the wireless, shoving bits over copper would -usually- be efficient enough to not be the bottleneck.

[–] [email protected] 2 points 2 years ago (1 children)

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.

[–] [email protected] 6 points 2 years ago

CRISPR to the rescue!

[–] [email protected] 2 points 2 years ago (1 children)

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)

[–] [email protected] 1 points 2 years ago

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.

[–] [email protected] 5 points 2 years ago (1 children)

+1 on not using containers.for Network routing stuff That way lies pain and misery.

[–] [email protected] 3 points 2 years ago (2 children)

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.

[–] [email protected] 3 points 2 years ago (4 children)

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.

[–] [email protected] 1 points 2 years ago

I recommend https://migadu.com. not free, but the lowest price tier has lots of features, unlimited mailboxes etc.

view more: ‹ prev next ›