MastodonTech.de

goetz<a href="https://ipv6.social/@tschaefer" class="u-url mention" rel="nofollow noopener" target="_blank">@tschaefer</a> 1&1 with Roaming <a href="https://ipv6.social/tags/VodafoneNL" class="mention hashtag" rel="nofollow noopener" target="_blank">#VodafoneNL</a> <a href="https://ipv6.social/tags/Dualstack" class="mention hashtag" rel="nofollow noopener" target="_blank">#Dualstack</a> works. <a href="https://ipv6.social/tags/IPv6only" class="mention hashtag" rel="nofollow noopener" target="_blank">#IPv6only</a> without <a href="https://ipv6.social/tags/NAT64" class="mention hashtag" rel="nofollow noopener" target="_blank">#NAT64</a> works too.

goetzFor <a href="https://ipv6.social/@tschaefer" class="u-url mention" rel="nofollow noopener" target="_blank">@tschaefer</a> <a href="https://ipv6.social/tags/Telekom" class="mention hashtag" rel="nofollow noopener" target="_blank">#Telekom</a> <a href="https://ipv6.social/tags/Roaming" class="mention hashtag" rel="nofollow noopener" target="_blank">#Roaming</a> in NL with <a href="https://ipv6.social/tags/Odido" class="mention hashtag" rel="nofollow noopener" target="_blank">#Odido</a> Only <a href="https://ipv6.social/tags/DualStack" class="mention hashtag" rel="nofollow noopener" target="_blank">#DualStack</a> works. <a href="https://ipv6.social/tags/IPv6only" class="mention hashtag" rel="nofollow noopener" target="_blank">#IPv6only</a> is not possible.<a href="https://ipv6.social/tags/bgptools" class="mention hashtag" rel="nofollow noopener" target="_blank">#bgptools</a>

Kevin Karhan :verified:<a href="https://framapiaf.org/@pmevzek" class="u-url mention" rel="nofollow noopener" target="_blank">@pmevzek</a> <a href="https://mstdn.jp/@landley" class="u-url mention" rel="nofollow noopener" target="_blank">@landley</a> I wish I had this luxury.<ul><li>Cuz I often have to deal with fucked-up networks that are <a href="https://infosec.space/tags/IPv4only" class="mention hashtag" rel="nofollow noopener" target="_blank">#IPv4only</a> and sometimes going <a href="https://infosec.space/tags/DualStack" class="mention hashtag" rel="nofollow noopener" target="_blank">#DualStack</a> is flatout not being allowed and even having <a href="https://infosec.space/tags/IPv6" class="mention hashtag" rel="nofollow noopener" target="_blank">#IPv6</a> at the public-facing side is seen as a problem.</li></ul>And I'm more often than not not the guy who gets to make that decision.<ul><li>I was only able to get IPv6 allowed WAN-side at one place after my employer encountered the problem that some workers have shitty <a href="https://infosec.space/tags/CGNAT" class="mention hashtag" rel="nofollow noopener" target="_blank">#CGNAT</a> that bricks <a href="https://infosec.space/tags/OpenVPN" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenVPN</a> so they could not <a href="https://infosec.space/tags/VPN" class="mention hashtag" rel="nofollow noopener" target="_blank">#VPN</a> to the HQ.</li></ul>

Kevin Karhan :verified:<a href="https://oldbytes.space/@drscriptt" class="u-url mention" rel="nofollow noopener" target="_blank">@drscriptt</a> again: I'd see this as more error-prone than <a href="https://infosec.space/tags/DNSSEC" class="mention hashtag" rel="nofollow noopener" target="_blank">#DNSSEC</a> and only hindering the transition from <a href="https://infosec.space/tags/IPv4" class="mention hashtag" rel="nofollow noopener" target="_blank">#IPv4</a> to <a href="https://infosec.space/tags/IPv6" class="mention hashtag" rel="nofollow noopener" target="_blank">#IPv6</a> if not bricking proper <a href="https://infosec.space/tags/DualStack" class="mention hashtag" rel="nofollow noopener" target="_blank">#DualStack</a>…

Kevin Karhan :verified:<a href="https://mastodon.ip6.li/@net_gremlin" class="u-url mention" rel="nofollow noopener" target="_blank">@net_gremlin</a> <code>1.</code> Obviously... <code>2.</code> Not gonna argue with that. <code>3.</code> as long as there are <a href="https://infosec.space/tags/IPv4only" class="mention hashtag" rel="nofollow noopener" target="_blank">#IPv4only</a> services and applications, I do at least need proper <a href="https://infosec.space/tags/DualStack" class="mention hashtag" rel="nofollow noopener" target="_blank">#DualStack</a>. Regulators like <a href="https://social.bund.de/@BNetzA" class="u-url mention" rel="nofollow noopener" target="_blank">@BNetzA</a> refuse to mandate <a href="https://infosec.space/tags/IPv6" class="mention hashtag" rel="nofollow noopener" target="_blank">#IPv6</a> connectivity and I only get <a href="https://infosec.space/tags/IPv4" class="mention hashtag" rel="nofollow noopener" target="_blank">#IPv4</a> from my <a href="https://infosec.space/tags/ISP" class="mention hashtag" rel="nofollow noopener" target="_blank">#ISP</a>. <ul><li>I guess some day I'll be forced to get a <a href="https://mastodon.social/@ripencc" class="u-url mention" rel="nofollow noopener" target="_blank">@ripencc</a> membership just to get a Provider-Independent allocation.</li></ul>

Kevin Karhan :verified:<a href="https://chaos.social/@dickenhobelix" class="u-url mention" rel="nofollow noopener" target="_blank">@dickenhobelix</a> ich hätte auch gern mindestens nen /64 zu.meinrm /28.<ul><li>Kriege aber kein <a href="https://infosec.space/tags/DualStack" class="mention hashtag" rel="nofollow noopener" target="_blank">#DualStack</a> vom <a href="https://infosec.space/tags/ISP" class="mention hashtag" rel="nofollow noopener" target="_blank">#ISP</a>!</li></ul>

Marius BiebelFinally found the time to make our student council website <a href="https://infosec.exchange/tags/IPv6" class="mention hashtag" rel="nofollow noopener" target="_blank">#IPv6</a> <a href="https://infosec.exchange/tags/dualstack" class="mention hashtag" rel="nofollow noopener" target="_blank">#dualstack</a> <a href="https://fs.cs.hm.edu/" rel="nofollow noopener" translate="no" target="_blank">https://fs.cs.hm.edu/</a> 😅

Kevin Karhan :verified:<a href="https://mstdn.jp/@landley" class="u-url mention" rel="nofollow noopener" target="_blank">@landley</a> <a href="https://mstdn.social/@jschauma" class="u-url mention" rel="nofollow noopener" target="_blank">@jschauma</a> <a href="https://infosec.exchange/@ryanc" class="u-url mention" rel="nofollow noopener" target="_blank">@ryanc</a> <a href="https://infosec.exchange/@0xabad1dea" class="u-url mention" rel="nofollow noopener" 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" 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" 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" target="_blank">#IP</a> (which is a <a href="https://infosec.space/tags/privacy" class="mention hashtag" rel="nofollow noopener" target="_blank">#privacy</a> nightmare at best that "<a href="https://infosec.space/tags/PrivacyExtensions" class="mention hashtag" rel="nofollow noopener" 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" target="_blank">#DECnet</a> approach and use the <a href="https://infosec.space/tags/EUI48" class="mention hashtag" rel="nofollow noopener" target="_blank">#EUI48</a> / <a href="https://infosec.space/tags/MAC" class="mention hashtag" rel="nofollow noopener" target="_blank">#MAC</a>-Address (or <a href="https://infosec.space/tags/EUI64" class="mention hashtag" rel="nofollow noopener" 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" target="_blank">#vendors</a> and not <a href="https://infosec.space/tags/ISPs" class="mention hashtag" rel="nofollow noopener" 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" target="_blank">#ICCID</a> dictates <a href="https://infosec.space/tags/GSM" class="mention hashtag" rel="nofollow noopener" target="_blank">#GSM</a> / <a href="https://infosec.space/tags/4G" class="mention hashtag" rel="nofollow noopener" target="_blank">#4G</a> / <a href="https://infosec.space/tags/5G" class="mention hashtag" rel="nofollow noopener" target="_blank">#5G</a> access and not the <a href="https://infosec.space/tags/IMEI" class="mention hashtag" rel="nofollow noopener" 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" target="_blank">#128bit</a> address space was inspired by <a href="https://infosec.space/tags/ZFS" class="mention hashtag" rel="nofollow noopener" 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" target="_blank">#IPv6</a> because not only do I only have <a href="https://infosec.space/tags/IPv4only" class="mention hashtag" rel="nofollow noopener" target="_blank">#IPv4only</a> <a href="https://infosec.space/tags/Internet" class="mention hashtag" rel="nofollow noopener" target="_blank">#Internet</a> but my <a href="https://infosec.space/tags/ISP" class="mention hashtag" rel="nofollow noopener" 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" 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" target="_blank">#HurricaneElectric</a> / <a href="https://infosec.space/tags/HEnet" class="mention hashtag" rel="nofollow noopener" target="_blank">#HEnet</a>'s <a href="https://infosec.space/tags/Tunnelbroker" class="mention hashtag" rel="nofollow noopener" target="_blank">#Tunnelbroker</a> fail face first due to <a href="https://infosec.space/tags/Geoblocking" class="mention hashtag" rel="nofollow noopener" target="_blank">#Geoblocking</a> and the fact that <a href="https://infosec.space/tags/ASNs" class="mention hashtag" rel="nofollow noopener" target="_blank">#ASNs</a> get geolocated, not their <a href="https://infosec.space/tags/PoPs" class="mention hashtag" rel="nofollow noopener" target="_blank">#PoPs</a>... </li></ul>If I was <a href="https://social.bund.de/@BNetzA" class="u-url mention" rel="nofollow noopener" target="_blank">@BNetzA</a> I would've mandated <a href="https://infosec.space/tags/DualStack" class="mention hashtag" rel="nofollow noopener" target="_blank">#DualStack</a> and banned <a href="https://infosec.space/tags/CGNAT" class="mention hashtag" rel="nofollow noopener" 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" target="_blank">#RFC1918</a> address spaces) as well as <a href="https://infosec.space/tags/DualStackLite" class="mention hashtag" rel="nofollow noopener" target="_blank">#DualStackLite</a>!

Kevin Karhan :verified:<a href="https://awawa.meo.ws/@fusl" class="u-url mention" rel="nofollow noopener" target="_blank">@fusl</a> <a href="https://mastodon.online/@mnalis" class="u-url mention" rel="nofollow noopener" target="_blank">@mnalis</a> <a href="https://infosec.exchange/@0xF21D" class="u-url mention" rel="nofollow noopener" target="_blank">@0xF21D</a> I do that with <a href="https://infosec.space/tags/pfSense" class="mention hashtag" rel="nofollow noopener" target="_blank">#pfSense</a> & <a href="https://infosec.space/tags/OPNsense" class="mention hashtag" rel="nofollow noopener" target="_blank">#OPNsense</a> (depending on the exact network in question) and have it merge <a href="https://github.com/greyhat-academy/lists.d/blob/main/dns.servers.list.tsv" rel="nofollow noopener" target="_blank">multiple sources</a> that get cached.In total, I do may out the 30 DNS servers and whilst I have <a href="https://infosec.space/tags/IPv4only" class="mention hashtag" rel="nofollow noopener" target="_blank">#IPv4only</a>, I have everything ready for <a href="https://infosec.space/tags/DualStack" class="mention hashtag" rel="nofollow noopener" target="_blank">#DualStack</a> (<a href="https://infosec.space/tags/IPv4" class="mention hashtag" rel="nofollow noopener" target="_blank">#IPv4</a> + <a href="https://infosec.space/tags/IPv6" class="mention hashtag" rel="nofollow noopener" target="_blank">#IPv6</a>) once my ISP stops keeing it's thumbs um their ass...<a href="https://infosec.space/tags/sarcasm" class="mention hashtag" rel="nofollow noopener" target="_blank">#sarcasm</a>

krithinAnyone know why opening <a href="https://sfba.social/tags/IPv6" class="mention hashtag" rel="nofollow noopener" target="_blank">#IPv6</a> ports on <a href="https://sfba.social/tags/GoogleWifi" class="mention hashtag" rel="nofollow noopener" target="_blank">#GoogleWifi</a> might be failing for me? I have IPv6 service from my ISP (sonic.net - they're awesome!) and have a web server set up on my <a href="https://sfba.social/tags/RaspberryPi" class="mention hashtag" rel="nofollow noopener" target="_blank">#RaspberryPi</a>.Requests from outside my network sent to the pi's IPv6 GUA keep failing, even though I have ports 80 and 443 open for the pi in the "Port Management" section of the google home app. Requests made to that same IPv6 GUA work fine within my network.(I also have IPv4 port forwarding set up on that same page, and that seems to work fine to forward requests made to my router's external IPv4 address to the pi, so I could simply not set up an AAAA record and move forward with only IPv4 access to my server, but I'd prefer having a working dual-stack setup!)<a href="https://sfba.social/tags/networking" class="mention hashtag" rel="nofollow noopener" target="_blank">#networking</a> <a href="https://sfba.social/tags/HomeLab" class="mention hashtag" rel="nofollow noopener" target="_blank">#HomeLab</a> <a href="https://sfba.social/tags/IPv6" class="mention hashtag" rel="nofollow noopener" target="_blank">#IPv6</a> <a href="https://sfba.social/tags/Google" class="mention hashtag" rel="nofollow noopener" target="_blank">#Google</a> <a href="https://sfba.social/tags/techsupport" class="mention hashtag" rel="nofollow noopener" target="_blank">#techsupport</a> <a href="https://sfba.social/tags/DualStack" class="mention hashtag" rel="nofollow noopener" target="_blank">#DualStack</a>

Kevin Karhan :verified:<a href="https://digitalcourage.social/@krzym" class="u-url mention" rel="nofollow noopener" target="_blank">@krzym</a> <a href="https://oxytodon.com/@fuchsiii" class="u-url mention" rel="nofollow noopener" target="_blank">@fuchsiii</a> solange <a href="https://social.bund.de/@BNetzA" class="u-url mention" rel="nofollow noopener" target="_blank">@BNetzA</a> nicht mindestens ein /64 an <a href="https://infosec.space/tags/IPv6" class="mention hashtag" rel="nofollow noopener" target="_blank">#IPv6</a> pro <a href="https://infosec.space/tags/IPv4" class="mention hashtag" rel="nofollow noopener" target="_blank">#IPv4</a> vorschreibt wird sich nix dran ändern.<ul><li>Erst wenn <a href="https://infosec.space/tags/DualStack" class="mention hashtag" rel="nofollow noopener" target="_blank">#DualStack</a> flächendeckend ist kann IPv4 abgeschaltet werden!</li></ul>

Kevin Karhan :verified:Shitpost, not to be taken serious, Networking

Kevin Karhan :verified:<a href="https://ipv6.social/@tschaefer" class="u-url mention" rel="nofollow noopener" 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" 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" target="_blank">#ISP</a> die Bereitstellung von echtem <a href="https://infosec.space/tags/DualStack" class="mention hashtag" rel="nofollow noopener" target="_blank">#DualStack</a>. (Deshalb kann ich <a href="https://ipv6.social/@tschaefer/113453220246374691" rel="nofollow noopener" 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" target="_blank">#Diensteanbieter</a> & Services von <a href="https://infosec.space/tags/IPv4" class="mention hashtag" rel="nofollow noopener" target="_blank">#IPv4</a> auf <a href="https://infosec.space/tags/IPv6" class="mention hashtag" rel="nofollow noopener" target="_blank">#IPv6</a> migriert worden.<ul><li><a href="https://infosec.space/tags/IPv6only" class="mention hashtag" rel="nofollow noopener" target="_blank">#IPv6only</a> ist anders als ein <a href="https://infosec.space/tags/Windows" class="mention hashtag" rel="nofollow noopener" target="_blank">#Windows</a>-Verbot (was <a href="https://infosec.space/tags/BDSG" class="mention hashtag" rel="nofollow noopener" target="_blank">#BDSG</a> & <a href="https://infosec.space/tags/DSGVO" class="mention hashtag" rel="nofollow noopener" 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" 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" target="_blank">#CGNAT</a> [insbesondere mit <a href="https://infosec.space/tags/RFC1918" class="mention hashtag" rel="nofollow noopener" target="_blank">#RFC1918</a>-Addressraum] verbietet!<ul><li>Besonders Bullshit wie <a href="https://infosec.space/tags/DualStackLite" class="mention hashtag" rel="nofollow noopener" target="_blank">#DualStackLite</a> ist murks: Entweder korrekt Dual-Stack oder lasst es sein!!!</li></ul>

DavidFunktioniert <a href="https://ipv6-test.com/" rel="nofollow noopener" translate="no" target="_blank">https://ipv6-test.com/</a> nur bei mir nicht oder ist das allgemein kaputt? Zeigt bei mir nur <a href="https://hachyderm.io/tags/ipv4" class="mention hashtag" rel="nofollow noopener" target="_blank">#ipv4</a> als funktionierend an, laut anderer Tests und `ping6` ist mein <a href="https://hachyderm.io/tags/dualstack" class="mention hashtag" rel="nofollow noopener" target="_blank">#dualstack</a> aber okay. 🤔

Kevin Karhan :verified:<a href="https://troet.cafe/@jue" class="u-url mention" rel="nofollow noopener" target="_blank">@jue</a> <a href="https://chaos.social/@goetz" class="u-url mention" rel="nofollow noopener" target="_blank">@goetz</a> <a href="https://chaos.social/@fluepke" class="u-url mention" rel="nofollow noopener" target="_blank">@fluepke</a> Until you have some <a href="https://infosec.space/tags/remote" class="mention hashtag" rel="nofollow noopener" target="_blank">#remote</a> workers who only have <a href="https://infosec.space/tags/CGNAT" class="mention hashtag" rel="nofollow noopener" target="_blank">#CGNAT</a> + pseudo-static <a href="https://infosec.space/tags/IPv6" class="mention hashtag" rel="nofollow noopener" target="_blank">#IPv6</a> addresses on a <a href="https://infosec.space/tags/consumer" class="mention hashtag" rel="nofollow noopener" target="_blank">#consumer</a> line...Then it's not an option and you'll have to resort to <a href="https://infosec.space/tags/RFC1918" class="mention hashtag" rel="nofollow noopener" target="_blank">#RFC1918</a> and <a href="https://infosec.space/tags/DualStack" class="mention hashtag" rel="nofollow noopener" target="_blank">#DualStack</a> <a href="https://infosec.space/tags/WAN" class="mention hashtag" rel="nofollow noopener" target="_blank">#WAN</a>-side, as I had to setup for a fmr. employer / client...

Thomas Schäfer<a href="https://infosec.space/@kkarhan" class="u-url mention" rel="nofollow noopener" target="_blank">@kkarhan</a> "mandate proper <a href="https://ipv6.social/tags/DualStack" class="mention hashtag" rel="nofollow noopener" target="_blank">#DualStack</a> support" (for all) is nonsense

Kevin Karhan :verified:<a href="https://chaos.social/@fluepke" class="u-url mention" rel="nofollow noopener" target="_blank">@fluepke</a> sadly the only way this could be changed if <a href="https://social.bund.de/@BNetzA" class="u-url mention" rel="nofollow noopener" target="_blank">@BNetzA</a> would mandate proper <a href="https://infosec.space/tags/DualStack" class="mention hashtag" rel="nofollow noopener" target="_blank">#DualStack</a> support.<ul><li>And I'd welcome it if they were to mandate a /64 per IPv4 if not a /48 of <a href="https://infosec.space/tags/IPv6" class="mention hashtag" rel="nofollow noopener" target="_blank">#IPv6</a>'s per <a href="https://infosec.space/tags/IPv4" class="mention hashtag" rel="nofollow noopener" target="_blank">#IPv4</a> block allocation...</li></ul>I just don't expect this to happen from the same agency that would rather <a href="https://infosec.space/tags/subsidize" class="mention hashtag" rel="nofollow noopener" target="_blank">#subsidize</a> <a href="https://infosec.space/tags/Starlink" class="mention hashtag" rel="nofollow noopener" target="_blank">#Starlink</a> that mandate <a href="https://infosec.space/tags/FTTB" class="mention hashtag" rel="nofollow noopener" target="_blank">#FTTB</a> & <a href="https://infosec.space/tags/FTTH" class="mention hashtag" rel="nofollow noopener" target="_blank">#FTTH</a> coverage and installations...

goetz 🚲Using SIM Plans for connectivity abroad shows, draws an interesting picture in terms of <a href="https://chaos.social/tags/IPv6" class="mention hashtag" rel="nofollow noopener" target="_blank">#IPv6</a> connectivity. My favorite <a href="https://chaos.social/tags/AIS" class="mention hashtag" rel="nofollow noopener" target="_blank">#AIS</a> Sim2Fly Sim and dataplan has <a href="https://chaos.social/tags/Dualstack" class="mention hashtag" rel="nofollow noopener" target="_blank">#Dualstack</a> connectivity. The really easy to use, no app, <a href="https://chaos.social/tags/esim" class="mention hashtag" rel="nofollow noopener" target="_blank">#esim</a> from <a href="https://chaos.social/tags/betterroaming" class="mention hashtag" rel="nofollow noopener" target="_blank">#betterroaming</a> aka <a href="https://chaos.social/tags/truphone" class="mention hashtag" rel="nofollow noopener" target="_blank">#truphone</a> has only <a href="https://chaos.social/tags/IPv4" class="mention hashtag" rel="nofollow noopener" target="_blank">#IPv4</a> connectivity. Looking at the <a href="https://chaos.social/tags/ASN" class="mention hashtag" rel="nofollow noopener" target="_blank">#ASN</a> shows they do not have any <a href="https://chaos.social/tags/IPv6" class="mention hashtag" rel="nofollow noopener" target="_blank">#IPv6</a> prefixes at all. <a href="https://bgp.tools/as/30967#asinfo" rel="nofollow noopener" translate="no" target="_blank">https://bgp.tools/as/30967#asinfo</a>

Sly GryphonA good <a href="https://qoto.org/tags/dualstack" class="mention hashtag" rel="nofollow noopener" target="_blank">#dualstack</a> network should still run <a href="https://qoto.org/tags/dns64" class="mention hashtag" rel="nofollow noopener" target="_blank">#dns64</a> and <a href="https://qoto.org/tags/nat64" class="mention hashtag" rel="nofollow noopener" target="_blank">#nat64</a>, so that it can fully support <a href="https://qoto.org/tags/ipv6" class="mention hashtag" rel="nofollow noopener" target="_blank">#ipv6</a> only devices and allow them a way to connect to legacy (ipv4) internet sites. <a href="https://sgryphon.gamertheory.net/2022/12/running-nat64-in-a-dual-stack-network/" rel="nofollow noopener" target="_blank">https://sgryphon.gamertheory.net/2022/12/running-nat64-in-a-dual-stack-network/</a>

Kevin Karhan :verified:<a href="https://toot.cafe/@baldur" class="u-url mention" rel="nofollow noopener" target="_blank">@baldur</a> generally, <a href="https://infosec.space/tags/GeoIP" class="mention hashtag" rel="nofollow noopener" target="_blank">#GeoIP</a> and other <a href="https://infosec.space/tags/IP" class="mention hashtag" rel="nofollow noopener" target="_blank">#IP</a>-based <a href="https://infosec.space/tags/Geolocation" class="mention hashtag" rel="nofollow noopener" target="_blank">#Geolocation</a> and <a href="https://infosec.space/tags/Geoblocking" class="mention hashtag" rel="nofollow noopener" target="_blank">#Geoblocking</a> is just garbage.I'm stuck on an <a href="https://infosec.space/tags/IPv4only" class="mention hashtag" rel="nofollow noopener" target="_blank">#IPv4only</a> conmection because my <a href="https://infosec.space/tags/ISP" class="mention hashtag" rel="nofollow noopener" target="_blank">#ISP</a> is unable and/or unwilling to provide proper <a href="https://infosec.space/tags/DualStack" class="mention hashtag" rel="nofollow noopener" target="_blank">#DualStack</a> connectivity or even a /64 of <a href="https://infosec.space/tags/IPv6" class="mention hashtag" rel="nofollow noopener" target="_blank">#IPv6</a> (when in fact they could easily do a /48 if not /40 since they gave me a /28 of <a href="https://infosec.space/tags/IPv4" class="mention hashtag" rel="nofollow noopener" target="_blank">#IPv4</a>'s at no added cost).<ul><li>And no, <a href="https://tunnelbroker.net" rel="nofollow noopener" translate="no" target="_blank">https://tunnelbroker.net</a> doesn't work for me because then stuff will prefer IPv6 and a shitload of stuff does <a href="https://infosec.space/tags/GeoIP" class="mention hashtag" rel="nofollow noopener" target="_blank">#GeoIP</a> and then geoblocks me despite choosing the <a href="https://infosec.space/tags/PoP" class="mention hashtag" rel="nofollow noopener" target="_blank">#PoP</a> in <a href="https://infosec.space/tags/FRA" class="mention hashtag" rel="nofollow noopener" target="_blank">#FRA</a> because they Geolocate entire <a href="https://infosec.space/tags/ASN" class="mention hashtag" rel="nofollow noopener" target="_blank">#ASN</a>|s and not single allocations!</li></ul>

Frühere Suchanfragen

Suchoptionen

Verwaltet von:

Serverstatistik:

#dualstack