med-mastodon.com is one of the many independent Mastodon servers you can use to participate in the fediverse.
Medical community on Mastodon

Administered by:

Server stats:

345
active users

#dualstack

0 posts0 participants0 posts today
Replied in thread

@pmevzek @landley I wish I had this luxury.

  • Cuz I often have to deal with fucked-up networks that are #IPv4only and sometimes going #DualStack is flatout not being allowed and even having #IPv6 at the public-facing side is seen as a problem.

And I'm more often than not not the guy who gets to make that decision.

  • I was only able to get IPv6 allowed WAN-side at one place after my employer encountered the problem that some workers have shitty #CGNAT that bricks #OpenVPN so they could not #VPN to the HQ.
Replied in thread

@landley @jschauma @ryanc @0xabad1dea yeah, the exhaustion problem would've been shoved back with a #64bit or sufficiently delayed by a 40bit number.

Unless we also hate #NAT and expect every device to have a unique static #IP (which is a #privacy nightmare at best that "#PrivacyExtensions" barely fixed.)

  • I mean they could've also gone the #DECnet approach and use the #EUI48 / #MAC-Address (or #EUI64) as static addressing system, but that would've made #vendors and not #ISPs the powerful forces of allocation. (Similar to how technically the #ICCID dictates #GSM / #4G / #5G access and not the #IMEI unless places like Australia ban imported devices.

I guess using a #128bit address space was inspired by #ZFS doing the same before, as the folks who designed both wanted to design a solution that clearly will outlive them (way harder than COBOL has outlived Grace Hopper)...

If I was @BNetzA I would've mandated #DualStack and banned #CGNAT (or at least the use of CGNAT in #RFC1918 address spaces) as well as #DualStackLite!

Replied in thread

@fusl @mnalis @0xF21D

I do that with #pfSense & #OPNsense (depending on the exact network in question) and have it merge multiple sources that get cached.

In total, I do may out the 30 DNS servers and whilst I have #IPv4only, I have everything ready for #DualStack (#IPv4 + #IPv6) once my ISP stops keeing it's thumbs um their ass...

List of useful things. Contribute to greyhat-academy/lists.d development by creating an account on GitHub.
GitHublists.d/dns.servers.list.tsv at main · greyhat-academy/lists.dList of useful things. Contribute to greyhat-academy/lists.d development by creating an account on GitHub.
Replied to Thomas Schäfer

@tschaefer fängt damit an dass bis heute nicht alle #IPv6 haben oder bekommen können...

  • Bspw.: Verweigert mein #ISP die Bereitstellung von echtem #DualStack. (Deshalb kann ich diesen Post auch nicht direkt aufrufen!)

Umgekehrt sind bis heute nicht alle #Diensteanbieter & Services von #IPv4 auf #IPv6 migriert worden.

Sorgt zwar für Henne-Ei-Problem, wäre aber durch die @BNetzA lösbar indem diese zwangsweise je IPv4 mindestens ein /64 an IPv6 vorschreibt und Bullshit wie #CGNAT [insbesondere mit #RFC1918-Addressraum] verbietet!

  • Besonders Bullshit wie #DualStackLite ist murks: Entweder korrekt Dual-Stack oder lasst es sein!!!
ipv6.socialThomas Schäfer (@tschaefer@ipv6.social)@kkarhan@infosec.space Du hast die Behauptung aufgestellt, dass IPv6 only vieles bricken würde. Also was?
Replied in thread

@baldur generally, #GeoIP and other #IP-based #Geolocation and #Geoblocking is just garbage.

I'm stuck on an #IPv4only conmection because my #ISP is unable and/or unwilling to provide proper #DualStack connectivity or even a /64 of #IPv6 (when in fact they could easily do a /48 if not /40 since they gave me a /28 of #IPv4's at no added cost).

  • And no, tunnelbroker.net doesn't work for me because then stuff will prefer IPv6 and a shitload of stuff does #GeoIP and then geoblocks me despite choosing the #PoP in #FRA because they Geolocate entire #ASN|s and not single allocations!
tunnelbroker.netHurricane Electric Free IPv6 Tunnel Broker

@stefano my #advice:

  • Replace set value="1.1.1.1,9.9.9.9" with set value="161.97.219.84,178.63.116.152,2001:470:4212:10:0:100:53:10,2a01:4f8:141:4281::999" for #DualStack-#DNS and not just #IPv4 if #IPv6 is available.

  • Otherwise just value="161.97.219.84,178.63.116.152," .

Reasons:

Whereas #OpenNIC has a proven track record of #integrity...

Replied in thread

@iX_Magazin es ist #Unwille seitens der #ISP|s da @BNetzA nicht #IPv6 vorschreibt.

Ich hab' nen /28 an #IPv4 aber nichtmals ein /64 an IPv6 und.mein ISP will mir auch kein IPv6 geben!

IMHO sollte echtes #DualStack oder zumindest nen /64 per IPv4 bzw. nen /48 bei IP-Blöcken vorgeschrieben werden!

Siehe Kommentare...

...besonders dieser!

heise onlineheise onlineNews und Foren zu Computer, IT, Wissenschaft, Medien und Politik. Preisvergleich von Hardware und Software sowie Downloads bei Heise Medien.
Serious questions for this Friday… Are we now at a point of time where we can safely drop legacy #IPv4 and can even use #IPv6 only for servers.

Sure, technically everything works fine on operating systems like #FreeBSD, #OpenBSD, #Debian, #Fedora etc. and all my monitoring, backup and admin infrastructure is #IPv6 only for years. But dealing with clients is something different. I think most clients already support #DualStack, especially within my circle but it could still be annoying for people that are forced to use #IPv4 only.