My home ISP does CGNAT for IPv4, but provides native IPv6. I can use IPv6 just fine to access most of my resources, except for one specific server. I can access the server over IPv4 from my home network, and either over v4 or v6 from other networks I’ve tried. But I can’t access it over IPv6 from my home network.
What could be the problem here? Where do I begin to diagnose it
Are the other networks you’ve tried from the same or different?
I’d start with traceroute and see how far your IPv6 traffic gets before it fails. It could very well be some peering or routing issue between some of the ISPs in between you and wherever that IPv6 address lives. If this ends up identifying where the traffic dies, a lot of the tier 1 ISPs have BGP looking glass servers so you can get an idea of what they know about that subnet.
I’ve tried from networks outside my home and I can access the server from there. Looking at a traceroute, I stop getting anything somewhere between my ISP and the datacenter the server is in.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !selfhosted@lemmy.world
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
Couple questions:
I’d start with traceroute and see how far your IPv6 traffic gets before it fails. It could very well be some peering or routing issue between some of the ISPs in between you and wherever that IPv6 address lives. If this ends up identifying where the traffic dies, a lot of the tier 1 ISPs have BGP looking glass servers so you can get an idea of what they know about that subnet.
I’ve tried from networks outside my home and I can access the server from there. Looking at a traceroute, I stop getting anything somewhere between my ISP and the datacenter the server is in.