Selfhosted
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:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
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.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
view the rest of the comments
A lot of people are saying WOL doesn't work over the internet, but I've got it working.
Basically port forward UDP 9 to your broadcast address (the last possible IP in your subnet), eg.
192.168.1.255. Then send the WOL to your public IP which will then get broadcasted out over your network by your router.Typing this out, I realised this seems like a horrible security practice, so I'll probably disable it soon anyway, now that I've got multiple servers and a failover VPN.
yeah, tunneling into your local network and then calling WoL from there is the way to go.
Yeah, I only really used it when the computer running my tunnel wasn't on, but that's not an issue for me anymore.
It's not that it doesn't work, it's that it's anybody's guess if any of the hops will pass it along. The odds are overwhelmingly in favor of it getting snagged somewhere along the way.
Well it's just UDP so isn't that just how the internet works, but yeah when I did do it, I'd often spam a bunch of packets, sometimes just sending one didn't work, but multiple always worked.
I mean... just because a packet can be routed doesn't mean it will be. Don't be fooled by "mainstream" packets like TCP on 443 which is practically guaranteed to be routed everywhere and prioritized because it's HTTP. Not all packets get the VIP treatment (if they're even routed at all), and WoL is a pretty obscure one.
That's sort of what I mean by "just how the internet works" where "it's that it's anybody's guess if any of the hops will pass it along."
Like yeah I understand TCP has protections against dropped packets, but that's only because it re-requests the packets it thinks are lost or corrupt.
Also HTTP and WOL are at a different layer, they're both TCP and UDP respectively, so it shouldn't matter whether if the App layer is obscure or not. Heck the routers of the internet only look at the IP layer, so it can't even tell if it's TCP 443, and you could probably even write your own Transport layer protocol and route it over the internet.
Although I guess firewalls could do some prioritisation, and wouldn't like this new transport layer, but they're usually near the ends of the connection, not in the middle, and I was taught to prioritise VoIP stuff anyway.
TCP/IP model for reference:
*I have not much experience so I may have made some mistakes, but I'm currently completing a CCNA so it should be somewhat correct.