103
ISP put me behind NAT
(lemmy.world)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 11 Nov 2023
103 points (92.6% liked)
Selfhosted
40383 readers
488 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:
-
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:
- selfh.st Newsletter and index of selfhosted software and apps
- 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!
founded 2 years ago
MODERATORS
ISPs in Canada usually include a clause in their TOS that explicitly prohibits selfhosting. Don't move here, it sucks.
🫤 that does suck. Probably so they can charge more for a hosted package?
It's to push users into getting commercial accounts.
I dunno. The IPv4 address space is getting pretty tight, and aside from rejiggering existing inefficient allocations, there's not a lot you can do beyond NAT.
In the US, we had it pretty good for a long time, because we had a rather disproportionate chunk of the IPv4 address space -- Ford, MIT, and Apple alone each had their own Class A netblock, about half a percent of the IPv4 address space each, for example.
But things have steadily gotten tighter as more and more of the world uses the Internet more and more.
https://whatismyipaddress.com/ipv6-ready
Like, there's real scarcity of the resource. It doesn't require the scarcity to be artificially-induced.
My ISP used to let one get a /29 IPv4 block for residential users, though they stopped that years ago. Always have had a way to get publicly-facing IPv6 addresses, though.
End of the day, the real fix is to get the world on IPv6.
Not even offered in my area 🤡
I don't know Canada laws but does it only apply if you make money off it (or intend to). Self hosting Jellyfin server is basically just delayed uploading.
Afaik it's at the ISP's digression. Up until I switched, Bell would block ports 21, 22, 53, 80 and 443.
That's pretty nice compromise. 80 and 443 are the ones mainly used commercially
It's kinda shitty of them to block the ports that makes up +30 years of what the internet IS. Bell/Rogers want your internet connection to be unidirectional, when you host your own content you don't consume theirs.
Yeah, not arguing that, it doesn't cost them extra to allow those. Still, you can use 8080, 8989, 5000, 7878 etc, for plex, Jellyfin, nextcloud and so on.
You can even workaround it by using cloudflare functions that forward requests to your specific port, DNS it to cloudflare and run a commercial webapp out of your garage anyway.*
*Except if you want to honor whatever ToS they had you agree to.