Kevin Karhan 
hallunke23 🇺🇦
Du tust mir leid. #IPv4only
@PhoebeEule @marquito solang' ich nicht #DualStack auf allen Anbindungen mit Statischen Addressen bekomme ist bei mir das LAN #IPv4only!
Wenn das stimmt, dann wäre AIS der erste ISP, der #ipv6only ist.
Etwas komisch an der Sache:
Deren Website ist immernoch #ipv4only . D. h. wenn der Zugang #ipv6only ist, dann wäre es nicht möglich, von einem AIS-Faser-Anschluss die AIS-Website zu erreichen, was ich mir etwas komisch vorstelle.
Magst du mal von AIS aus testen, ob du die Website erreichen kannst?
like obviously ipv4 is a pain, but it's also not that big a deal either it's a legacy thing
There are still devices & software being manufactured & sold that are #IPv4only and will refuse to work if they don't have a static #IPv4 on #WAN.
- And I'm not talking solely about #Devkits and #Enterprise-#Licensing…
#IPv6 is sadly not yet mandated otherwise #CGNAT & bs like #DualStackLite would've never been created.
@sodiboo I rather want #NAT46 aka. #IPv6+#IPv4 on #WAN and #IPv4only #LAN, because I don't have a provider-independent #IP-Address Space and my #ISP can't be assed to comply with §73 Section 3 Sentence 3 Telecommunications Act so proper Static-IPv6 configuration doesn't work!
- Granted they don't even get IPv6 to work on #WWAN (#LTE), so when #DOCSIS-#Cable is down, I have IPv4-only!
Needless to say the way most vendors implement it is fucking cursed!
If I was @BNetzA I'd mandate every Internet connection to be either #DualStack or at least have a /104 of static IPv6's with every #CGNAT'd device (whilst prosecuting every CGNAT using #RFC1918 address space as computer sabotage for bricking #VPN|s)…
- Alas, they don't…
goetz@bert_hubert
Thank you for sharing the stats.
Unfortunately your fediverse account lives on an #IPv4only instance.
@exponentialverteilt @clf name a competent #ISP that just works on that regard.
- AFAICT none of them do…
Plus I can't do #IPv6only because I still need access to #IPv4only resources.
- And right now all I want is #DualStack wthout exposing LAN hosts!
Kevin Karhan :verified: (@[email protected])
@[email protected] @[email protected] yes, due to lack of alternative options. - But *all* German mobile networks do #CGNAT in #RFC1918 address space (`10.0.0.0 /8`)…
Does anyone know how to setup #NAT46 on #pfSense within a #LAN?
The Problem is that I want to provide #IPv6-connectivity on #WAN without having to deal with IPv6 in #LAN.
- Right now I'm ponderig using
fc:: /7on #LAN with #DHCPv6 but the problem is that #Vodafone's shitbox connection is flaky af and the only #Fallback that I currently have is their shitty #LTE which is #IPv4only woth #CGNAT in #RFC1918 (10.0.0.0 /8) and no IPv6 connectivity, thus everytime shit flip-flops connectivity is completely gone on IPv6 and only #IPv4 is on that backup link.
So since I don't have a Provider-Independent IP space and my #ISP is so fucking incompetent that I hereby beg @BNetzA to finally seize their network and nationalize/socialize it I am basically stuck on IPv4 connectivity.
The only workarounds I know would necessitate using a #HurricaneElectric #GIF-Tunnel for IPv6 on fallback, which won't work because OFC Vodafone doesn't offer me a static IPv4 or even stazic IPv6-Subnet on their mobile network and I got #DualStack on #WAN on the primary network.
The problem re: routing exists for all #MultiWAN setups and I won't pay for #Vipritnet or setup my own #ASN and blow money on a @ripencc membership just to get PI Address Space and having to setup my own Gateway to VPN into through all my WAN & #WWAN connections.
Also the false premise of many sites to prefer IPv6 over IPv4 causes everything to break apart at the slightest disruption.
- IPv6 really annoys me because unlike IPv4, it just doesn't work and everytime I have to deal with it it's a pain in the ass...
Kevin Karhan :verified: (@[email protected])
#IPv6 is a mistake! - Noone needs #128bit address space! - 21+ years of protocol existance, yet no mandatory & widespread adoption… - You want to have more than 1 PC per line? We have a solution for it, it's called #NAT! - IPs should not have variable lenghts and hexadecimal digits!!! #SLAAC? #RouterAdvertisement?? #6rd??? - These are real #IPv6only mechanisms deployed in the real world! *"Yes, I'd love to have all my devices loose their #IP assignments everytime my #WAN connection resets/disconnects/…!"* - They have played us for absolute fools! #meme #shitpost #IPv4 #Enshittification
Öhm, Verständnisfrage:
Was passiert, wenn man das neue Outlook in einer Konstellation einsetzt, wo Server und Client inkompatible IP-Versionen nutzen? D. h. Server mit IPv4-only, Client mit IPv6-only, oder umgekehrt.
Tut Microsoft dann dazwischen vermitteln?
Wenn ja, dann gäbe es dafür tatsächlich einen Anwendungsfall.
Moralisch besser wird das Verhalten von M$ dadurch aber nicht.