So I had something weird happen:

I opened up my laptop bringing it out of sleep. It connected to wiDailed loading. I then tried a 4th and it was fine. CLeared dns cache. Didn't fix it.

I finally realized the lan (ipv4) server had gone sideways, however SLAAC for #ipv6 was still working just fine. I only had ipv6 internet rather than the #dualstack I usually ran.

Connected to my DHCP server (which of course runs v6 as well) easily & restarted the service which fixed it.

#ipv6 FTW.

As countries like china and india ramp up #ipv6 rapid, #Enterprise may need also enterprise rollout of #dualstack or #ipv6 if they act global.
Any hints of already switched or soon planning #Enterprise because of that #business case.
Examples?

@yakkoj well, that doesn't work if #IPv6 is fucked and #IPv4 is the only stable option.

I think shit should properly do #DualStack and it should be up to the network admin to decide what to prefer...

#ripe86
#ipv6
#tutorial
#ipv6basics
#ipv6only
#ipv6transition
#dualstack
#uptodate
#nat64
#464xlat
#dslite
#video
https://ripe86.ripe.net/archives/video/993/
#pdf
https://ripe86.ripe.net/presentations/33-RIPE86-IPv6-Tutorial.pdf

@stanford @kobayashi90 IMHO #DualStack with static IPv4 + IPv6 should've been the norm for two decades ago and IPv4 should've been deprecated.

In fact I've the absurd opposite Problem:

My ISP will gladly give me a /29 of IPv4 but won't even offer me a /64 IPv6, and for some reason HE.net GIF-Tunnel to FRA gets mislocated to the USA, so I've had to disable that IPv6 tunnel as it bricks the Geoblocking shite many sites here pull....

@kobayashi90 @stanford personally, I do #DualStack everything!

@lamp weird...

Personally I think that proper #DualStack should be mandatory.

Otherwise we'd completed #IPv6 transitions, because #CGNAT + #DualStackLite reward #lazyness in terms of #IPv4.

Frage mich ob @lte_max, @fusl und andere schon solch weirden shit erlebt haben.

Und nein, angesichts dessen dass @tt mit #Vodafone nen #Downgrade erlebt und ich mein /29 nicht aufgeben sondern allenfalls auf nen /24 IPv4 upgraden will gibt's auch kein #DualStack von denen!

#DualStack per #GIF-Tunnel zu #HurricaneElectric in #FFM ist was feines.

Und dann gibt's verkorkste Webseiten wie https://egun.de die offensichtlich bricken wenn man #DualStack nutzt.

Weiß nicht ob das deren kaputtes #GeoIP-#Blocking ist oder wasauchimmer.

Ich habe jedenfalls #RIPE-konform meine #WHOIS-Daten für die Allokation des /48 angegeben...

@phil @digitalcourage wann gibt's #IPv6 bei euch auf mehr als 1 Server?

Weil ich inzwischen #DualStack für meine Listings vorschreibe.
https://github.com/greyhat-academy/lists.d/blob/main/dns.servers.list.tsv#L24

@Toasterson I'd recommend taking a look at #pfSense / #OPNsense for that task.

I've done Tunneling #IPv6 on #IPv4only WAN networks and had to deal with #CGNAT - #IPv4 + IPv6 and having to implement #DualStack on #WAN-side.

Yay...

I just took myself the time and patience to upgrad my Internet to proper #DualStack [or rather #IPv4 + #Tunneling of #IPv6 via HE.net

Was far easier and faster than I thought....
https://docs.netgate.com/pfsense/en/latest/recipes/ipv6-tunnel-broker.html

Seriously, consider setting up a free tunnel via https://www.tunnelbroker.net/ if you haven't yet.

@Cheatha @twiddern @chrisd @33dBm

Das Problem #CGNAT bei Endnutzern ist leider real.

Die Korrekte Lösung ist #DualStack firmenseitig einzurichten - das dauert maximal 1 Arbeitstag, eher wenige Minuten hands-on.

#IPv4 wird zwangsweise aussterben und #IPv6 unvermeidbar sein.

Und ja ich habe auch schon VPNs auf Dual-Stack migriert - das geht recht gut.

Der hässliche Hack wäre sowas wie OpenVPN über TCP was extrem laggy wäre.

@clerie Ja, und die Tatsache dass es keinen Zwang zu echtem #DualStack gibt!

@siegi @Daemon c'est #sunrise Au moins j'ai une #ipv4 routable automatiquement, mais pas d' #ipv6 en #dualstack 😭
J'ai eu #salt aussi dans le passé. Et c'était la souffrance. 2 mois pour activer une #ipv4 routable, un produit qui était noir sur blanc dans leur catalogue. J'ai du passer au moins 4 fois dans leur magasins et passer plusieurs appels. Et chaque fois que je leur demandait on ne me regardait comme si j'étais un extraterrestre.

@eckes wir kriegen's nichtmals hin flächendeckend #IPv6 im #DualStack anzubieten...

So I recently upgraded my small business service with #Comcast a very large American ISP. I have #StaticIPS both, v4 (/29) and #ipv6 (/56). My ipv4 #StaticIPS remained the same & the configuration was trasnferred to the new cable modem. Supposedly....in reality the ipv4 configuration transferred & I got a new block in #ipv6.

I filed a ticket with support via chat who said she can help with ipv4 but needs to escalate for #ipv6. Tier2 called me this morning and just wanted to understand what the issue was. I told him my #ipv6 block changed after service upgrade. and I needed the old block back so I didn't have to renumber.

His response: I've worked here 17 years and I've never had anyone ask to fix their static ipv6 block or call about their static ipv6 block. I understand the problem but I don't have a way to fix it. I need to get Tier3 involved....

Now waiting for a call from #Tier3

#Comcast #ipv6 #staticip #dualstack

You should set up and run #NAT64 + #DNS64 in you #dualstack environment. Benefits are that it allows #IPv6 only devices a way to connect to IPv4 only servers, and provides valuable experience with IPv6, with no downsides. It does mean that dual stack devices will use NAT64 instead of NAT44, but you are still using NAT either way (and IPv4 devices always have to use NAT). See my article for more details and network diagrams https://sgryphon.gamertheory.net/2022/12/14/running-nat64-in-a-dual-stack-network/

@aetios Yes, using @freedominternet They provide dualstack with a fixed IPv4/32 and fixed IPv6/48 :blobcatrainbow: .
Could even order a fixed IPv4 subnet if I would like :blobcheer:
#IPv4 #IPv6 #AccesProvider #ISP #Dualstack

Yay, ich hab mein Setup wieder in nem voll funktionstüchtigen #IPv4 & #IPv6 #DualStack mit #KVM Bridge und #Docker 🥳

Hab letztlich in mein Docker-Service die folgenden iptable Regeln hinzugefügt.