Shakedown Social

0 posts0 participants0 posts today

Kevin Karhan :verified:<a href="https://mstdn.jp/@landley" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@landley</a> <a href="https://mstdn.social/@jschauma" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@jschauma</a> <a href="https://infosec.exchange/@ryanc" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@ryanc</a> <a href="https://infosec.exchange/@0xabad1dea" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@0xabad1dea</a> yeah, the exhaustion problem would've been shoved back with a <a href="https://infosec.space/tags/64bit" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#64bit</a> or sufficiently delayed by a 40bit number.Unless we also hate <a href="https://infosec.space/tags/NAT" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#NAT</a> and expect every device to have a unique static <a href="https://infosec.space/tags/IP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IP</a> (which is a <a href="https://infosec.space/tags/privacy" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#privacy</a> nightmare at best that "<a href="https://infosec.space/tags/PrivacyExtensions" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#PrivacyExtensions</a>" barely fixed.) <ul><li>I mean they could've also gone the <a href="https://infosec.space/tags/DECnet" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DECnet</a> approach and use the <a href="https://infosec.space/tags/EUI48" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#EUI48</a> / <a href="https://infosec.space/tags/MAC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#MAC</a>-Address (or <a href="https://infosec.space/tags/EUI64" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#EUI64</a>) as static addressing system, but that would've made <a href="https://infosec.space/tags/vendors" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#vendors</a> and not <a href="https://infosec.space/tags/ISPs" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ISPs</a> the powerful forces of allocation. (Similar to how technically the <a href="https://infosec.space/tags/ICCID" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ICCID</a> dictates <a href="https://infosec.space/tags/GSM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GSM</a> / <a href="https://infosec.space/tags/4G" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#4G</a> / <a href="https://infosec.space/tags/5G" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#5G</a> access and not the <a href="https://infosec.space/tags/IMEI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IMEI</a> unless places like Australia ban imported devices.</li></ul> I guess using a <a href="https://infosec.space/tags/128bit" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#128bit</a> address space was inspired by <a href="https://infosec.space/tags/ZFS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ZFS</a> 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)...<ul><li>Personally I've only had headaches with <a href="https://infosec.space/tags/IPv6" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IPv6</a> because not only do I only have <a href="https://infosec.space/tags/IPv4only" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IPv4only</a> <a href="https://infosec.space/tags/Internet" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Internet</a> but my <a href="https://infosec.space/tags/ISP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ISP</a> refuses to allocate even a singe /64 to me (but has no problem throwing in a free /29 of <a href="https://infosec.space/tags/IPv4" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IPv4</a>'s in with my contract!)and stuff like <a href="https://infosec.space/tags/HurricaneElectric" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#HurricaneElectric</a> / <a href="https://infosec.space/tags/HEnet" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#HEnet</a>'s <a href="https://infosec.space/tags/Tunnelbroker" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Tunnelbroker</a> fail face first due to <a href="https://infosec.space/tags/Geoblocking" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Geoblocking</a> and the fact that <a href="https://infosec.space/tags/ASNs" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ASNs</a> get geolocated, not their <a href="https://infosec.space/tags/PoPs" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#PoPs</a>... </li></ul>If I was <a href="https://social.bund.de/@BNetzA" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@BNetzA</a> I would've mandated <a href="https://infosec.space/tags/DualStack" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DualStack</a> and banned <a href="https://infosec.space/tags/CGNAT" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CGNAT</a> (or at least the use of CGNAT in <a href="https://infosec.space/tags/RFC1918" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RFC1918</a> address spaces) as well as <a href="https://infosec.space/tags/DualStackLite" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DualStackLite</a>!

Kevin Karhan :verified:<a href="https://techhub.social/@leeloo" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@leeloo</a> Until regulators like <a href="https://social.bund.de/@BNetzA" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@BNetzA</a> get their shit together and mandate a /64 of <a href="https://infosec.space/tags/IPv6" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IPv6</a> to be supplied to every <a href="https://infosec.space/tags/internet" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#internet</a> connection with no exceptioms or charges and mandates services and devices to support it as well, we'll not he above to get rid of <a href="https://infosec.space/tags/IPv4" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IPv4</a>.<ul><li>Worse is only <a href="https://infosec.space/tags/DualStackLite" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DualStackLite</a> and having to do unreliable (due to <a href="https://infosec.space/tags/Geoblocking" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Geoblocking</a>) hacks like <a href="https://infosec.space/tags/6in4" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#6in4</a> / <a href="https://infosec.space/tags/6over4" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#6over4</a> with <a href="https://tunnelbroker.net" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://tunnelbroker.net</a> ...</li></ul>Meanwhile it would be cheaper and easier for me to literally get my own private /24 of IPv4s than to convince my ISP to offer me even a single /48 of IPv6s...

Kevin Karhan :verified:<a href="https://ipv6.social/@tschaefer" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@tschaefer</a> fängt damit an dass bis heute nicht alle <a href="https://infosec.space/tags/IPv6" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IPv6</a> haben oder bekommen können...<ul><li>Bspw.: Verweigert mein <a href="https://infosec.space/tags/ISP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ISP</a> die Bereitstellung von echtem <a href="https://infosec.space/tags/DualStack" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DualStack</a>. (Deshalb kann ich <a href="https://ipv6.social/@tschaefer/113453220246374691" rel="nofollow noopener noreferrer" target="_blank">diesen Post</a> auch nicht direkt aufrufen!)</li></ul>Umgekehrt sind bis heute nicht alle <a href="https://infosec.space/tags/Diensteanbieter" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Diensteanbieter</a> & Services von <a href="https://infosec.space/tags/IPv4" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IPv4</a> auf <a href="https://infosec.space/tags/IPv6" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IPv6</a> migriert worden.<ul><li><a href="https://infosec.space/tags/IPv6only" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IPv6only</a> ist anders als ein <a href="https://infosec.space/tags/Windows" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Windows</a>-Verbot (was <a href="https://infosec.space/tags/BDSG" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#BDSG</a> & <a href="https://infosec.space/tags/DSGVO" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DSGVO</a> eigentlich verlangen!) illusorisch.</li></ul>Sorgt zwar für Henne-Ei-Problem, wäre aber durch die <a href="https://social.bund.de/@BNetzA" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@BNetzA</a> lösbar indem diese zwangsweise je IPv4 mindestens ein /64 an IPv6 vorschreibt und Bullshit wie <a href="https://infosec.space/tags/CGNAT" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CGNAT</a> [insbesondere mit <a href="https://infosec.space/tags/RFC1918" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RFC1918</a>-Addressraum] verbietet!<ul><li>Besonders Bullshit wie <a href="https://infosec.space/tags/DualStackLite" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DualStackLite</a> ist murks: Entweder korrekt Dual-Stack oder lasst es sein!!!</li></ul>

Recent searches

Search options

Administered by:

Server stats:

#dualstacklite