46
first nas network struggle
(fedia.io)
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 19 Aug 2026
46 points (97.9% liked)
Selfhosted
61544 readers
1186 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.
-
No spam.
-
Posts are to be related to self-hosting.
-
Don't duplicate the full text of your blog or readme if you're providing a link.
-
Submission headline should match the article title.
-
No trolling.
-
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.
-
AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.
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 3 years ago
MODERATORS
I disabled ipv6 across the board. I don't want my internal devices to be individually routable from the outside. I don't have a million devices. It's complexity I don't want.
Is there anything I'm missing?
Do you not run a firewall? Because your concerns are 100% fixed with a statefull firewall.
I think I worded this poorly. My point about being individually routable is that, that's the only benefit IPv6 seems to have. Unless I'm missing something.
Or, just completely bypass any config by simply not using IP6 for an environment where it offers no advantage
I'd rather not perpetuate the 30 year mistake NAT has truely become.
I ended up having to. I'd have liked to keep IPv6 on, but my router wasn't letting me permanently route the IPv6 traffic to my nas. something about my ISP using dynamic addresses so it would change periodically, and the router wouldn't accept the format of IP addresses that I generated.
Some ISPs just have a broken IPv6 implementation. If they do it correctly, they should delegate a /56 prefix that doesn't change unless the DUID on your router changes or your PoP changes.
Well...
Ipv6 is needed for peer to peer networks, easier for vpn and full mndgoru if you want to have a vps...
With it, you can avoid Cgnats and home Nats and usually it is faster and more reliable than ipv4.
So, see it for yourself....
Every time I try to use Ipv6, I run into dozens of weird issues and bugs and my selfhosted stuff becomes unusable/unreliable.
I don't know where the issue exactly lies in the chain of networking, but it sure is annoying as a motherfucker to debug. As far as I can tell none of my stuff is the problem and the issue lies either with my ISP or VPS provider.
For now, I removed the AAAA entries and suddenly everything works without any hiccups. Wake me up when those issues are solved... maybe in 10 or 20 years...
yeah I also have issues leading back to my ISP
Don't know what to say,
I maintain a double stack since 5 years and apart of some small nuisance I never had a real problem.
Ipv6 has been with us for more than 20 years, and It is true that to have that fine grain control in ipv6 you will need to go to a prosumer devices, but those are not that expensive and if you have a home lab you should check on them anyway....
Things are mature despite your bad experiences
Not as mature as ipv4 apperantly.
ipv6 works fine on my intranet.
If big company A or B can't get their shit together don't blame the victim. But if you don't believe me, I invite you to a debugging session. Honestly I'd be happy to be proven wrong if it works in the end.
I think it varies massively by ISP. my ISP has not implemented IPv6 properly so it causes all sorts of grief for me
PBKAC
NAT is not a security feature. This is a poor recommendation. Just because something has a globally-routable address does not make it accessible from anywhere.
I didn't say it was a security feature. But I also don't really want my ISP knowing how many devices are in my house.
Depending on how your ISP is doing IPv6, the typical way would just route the entire prefix to your router, and the ISP would not know how many addresses are used, in the sense that there is no table (no neighbor discovery is needed). If your ISP is keeping data of flows from your prefix then it could start counting unique addresses, but there isn't really good a reason to and it wouldn't be accurate. Some devices pull and use more than one address, and quiet devices might not get picked up by flows which are typically sampled at a ratio.