this post was submitted on 04 Mar 2026
22 points (89.3% liked)

Selfhosted

57169 readers
447 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

  7. No low-effort posts. This is subjective and will largely be determined by the community member reports.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS
 

So basically, I will be away from home for several weeks. Unfortunately, this became the perfect time for our home router to start acting out and factory resetting itself. We are awaiting a new router for replacement, but the time is tight.

My stuff is ethernetted in, so that connectivity isn't an issue - the issue is that I couldn't actually connect to the router to restore services even if it had internet by fixing all the settings including port forwarding.

What I would like would be the ability to have a VPN connected to my homelab, so I can hop on the router and restore the settings if this issue happens while I'm away. Any ideas?

you are viewing a single comment's thread
view the rest of the comments
[–] Onomatopoeia@lemmy.cafe 0 points 11 hours ago (1 children)

The more open ports, the larger the attack surface.

That's all.

And today with the script kiddies out there, port scans happen all the time.

I've had a consumer router become almost useless from all the attempted connections on an open port someone found that I had up for a week.

Months later I'd still get hits on that port though it had been closed.

[–] spaghettiwestern@sh.itjust.works 1 points 8 hours ago* (last edited 8 hours ago)

There are ~50,000-60,000+ available IP ports. If you had Wireguard configured correctly and running on every single one of them a port scanner would get exactly the same result as if every port was closed. Wireguard is completely silent unless the correct key is provided.

The "script kiddies" could scan every port for months and they'd get the same result. There is known no way to even know there's an open port much less know that Wireguard is running on it AND have the correct key for access.

I understand being gun shy after your experience (I would be too), but that experience has nothing to do with what happens when you open a port for Wireguard.