Dealing with DSLite (Dual Stack Lite)

[ThunderPerfectWitchcraft]

Since moving I have to use a DSLite connection, meaning I only have a shared external IPV4 IP, and an unique IPV6 IP. This makes selfhosting somewhat difficult - a DynDNS isn't enough anymore, since IPV4 only connections (and most of my friends seemingly don't have IPV6...) can't access your server.

My workaround was using a "Portmapper" service that allows to redirect IPV4 requests. However, for this, the traffic needs to be rerouted over an external server - in my case, I used IPV64 - I can't say that I'm overly happy about this, but at least my Mumble server that I use for voice chatting with friends and siblings is available again - it is, however, not fully stable (the service had an outage right after I managed to configure it correctly - which was surprisingly difficult, as it involved some rather esoteric config changes on my Pi* - and I didn't got in instantly, and thought the config that I made working might have went back to hell again). Besides these problems, it is - ofc - not perfect in terms of privacy and autonomy.

Did you have to deal with DSLite? What solutions did you find?


*
If your Pi is behind a FritzBox (maybe other routers are also affected) and DSLite, and you can't access it from the outside no matter what, try adding:

Code

[connection]

[connection]
ipv6.ip6-privacy=0
ipv6.addr-gen-mode=0

to your netconf, in case anybody else struggles with this.

[mrparker]

It sounds like you are behind a CG NAT (Carrier Grade Network Address Translation) - which basically is deployed by ISPs cause they have limited IPv4 space - since IPv4 has ran out in 2015 (ARIN, RIPE NCC ran out in 2019 - other regions later) officially.

Unfortunately there's not many options when dealing with CG NAT - If you can, you can use a VPN service which allows ports to be opened - this is easier than doing it yourself, which is the other option. I believe Windscribe can be used for this purpose.

Another is to use something like cloudflare tunnels, but this assumes you're using traffic that can work over HTTP/S - as using this with a service that relies on TCP/UDP directly isn't supported - not without everyone using the service also installing cloudflare tunnels on their devices, too.

Outside these options, your only real option is to use a cloud provider to host services - which at that point depending on what you're hosting, you might as well use the VPN setup I suggested if you're capable of DIY'ing it depending on what you're hosting.