@sindarina Personally, I think violating #RFCs should be a criminal offense, since I've also experienced the #VPN-breaking use of #RFC1918 adresses for #CGNAT!

@sans_isc AFAICT they don't and even if they would that would violate RFCs and make them liable to @BNetzA fines.

Speaking of shitty #CGNAT:
I should protest of them using #RFC1918 address space [10.0.0.0/8] when #RFC6598 states they must use 100.64.0.0/10 instead...

https://en.wikipedia.org/wiki/Carrier-grade_NAT
https://datatracker.ietf.org/doc/html/rfc6598

I expetience some strange behaviour with @torproject #TorBrowser on a (throttled) mobile connection:

Neither bridges (obfs4, meek-azure nor snowflake) nor without with get some.stable.connection and just contantly have circuits dying before it can even load the homepage to show it's connected.

Is it just me or do #MVNO's using #CGNAT on #RFC1918 adress spaces also try to prevent and block #Tor useage?

@lobingera @LunaRogue

Not to mention a lot of woes apply due to shitty #CGNAT on #RFC1918 adress spaces and other crap, like wannabe-geolocation that results in moving devices changing their [WAN-sided] IP-Adresses [whilst retaining the one on the aerial interface] causing reconnects.

And OFC a least-cost MVNO will get lower priority and worse service than an enterprise-contract M2M data-only SIM with guaranteed SLAs.

@HopelessDemigod not really, but I have issues with other mobile networks which - in violation of #RFC6598 - use #RFC1918 adress space for #CGNAT.

https://en.wikipedia.org/wiki/Carrier-grade_NAT

I'm shure that @stux runs mstdn.social as dual-stack, so even NAT & PAT should not be the problem...

@jwildeboer @EU_Commission that being said, I fully agree and think everyone should have a free, provider-independent #IPv6 /64 assignment and shit like #CGNAT, espechally those violating standards and using #RFC1918 adress spaces (like #mobile networks routinely do) should be abolished and forcibly disconnecting limes each 24 hours as well as trying to restrict peoples' use should be abolished.
https://social.wildeboer.net/@jwildeboer/110250521163940486

#NAT #is #evil

It took me 20 minutes to connect to #OEBB #railnet just now. The reason for the problems that I experienced is that #OEBB and I use the same #RFC1918 subnet. For me it's a #wireguard #VPN network and #OEBB ueses it for its onboard WIFI service.
I had to turn remove the route that came with #VPN to be able to activate WIFI. Too bad we still have to use #NAT for all these things just because #IPv6 is still not widely available 😢

@dlakelan @forwardingplane @kd9cpb @tracketpacer

I just can't understand it either. I don't understand the hate. It make no sense.

SO my work has a couple of disjointed /22s for ipv4 and a single /48.

I can never remember our public ips 1) They are disjointed and 2) I mostly work in #RFC1918 space (as I figure most organizations do). I can ALWAYS remember the #ipv6 address space easily:

nible 1-8 always the same (only need to memorize this)

nibble 9-12: siteid

nibble 13-16: vlan in hex

The rest - host address

Meanwhile back in the world of #ipv4 i have port forwardings, twice nat, single nat, and then rfc1918 to rfc1918 nats for when we deal with vendors. It's an absolute nightmare.

@puddha you know that #RFC1918 IPv4 adresses don't work outside of your LAN, do you?

@rsalas

I just started using @tailscale funnels for this purpose (ingress through a NAT). Seems to work fine on the very light duty use case I have for it. The feature is in alpha, which in this case does mean there are some known issues. https://tailscale.com/blog/introducing-tailscale-funnel/

Alex Ellis (not in Mastodon, yet?) has "Inlets" which fits the same task and has some purpose-built Kubernetes tooling. https://docs.inlets.dev

I don't know enough about Argo tunnels to have an opinion.

[ #rfc1918 #NAT #ingress ]

RT @AlexArchambault@twitter.com

Dans le même genre, on a bien eu ici des réquisitions judiciaires demandant l’identification d’une IP en 192.168. #RFC1918 https://twitter.com/davlgd/status/1424602258487091203

🐦🔗: https://twitter.com/AlexArchambault/status/1424604274059792386