Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://mstdn.jp/@landley" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>landley</span></a></span> <span class="h-card" translate="no"><a href="https://mstdn.social/@jschauma" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>jschauma</span></a></span> <span class="h-card" translate="no"><a href="https://infosec.exchange/@ryanc" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>ryanc</span></a></span> <span class="h-card" translate="no"><a href="https://infosec.exchange/@0xabad1dea" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>0xabad1dea</span></a></span> 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">#<span>64bit</span></a> or sufficiently delayed by a 40bit number.</p><p>Unless we also hate <a href="https://infosec.space/tags/NAT" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>NAT</span></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">#<span>IP</span></a> (which is a <a href="https://infosec.space/tags/privacy" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>privacy</span></a> nightmare at best that <em>"<a href="https://infosec.space/tags/PrivacyExtensions" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>PrivacyExtensions</span></a>"</em> barely fixed.) </p><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">#<span>DECnet</span></a> approach and use the <a href="https://infosec.space/tags/EUI48" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>EUI48</span></a> / <a href="https://infosec.space/tags/MAC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>MAC</span></a>-Address (or <a href="https://infosec.space/tags/EUI64" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>EUI64</span></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">#<span>vendors</span></a> and not <a href="https://infosec.space/tags/ISPs" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ISPs</span></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">#<span>ICCID</span></a> dictates <a href="https://infosec.space/tags/GSM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>GSM</span></a> / <a href="https://infosec.space/tags/4G" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>4G</span></a> / <a href="https://infosec.space/tags/5G" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>5G</span></a> access and not the <a href="https://infosec.space/tags/IMEI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>IMEI</span></a> unless places like Australia ban imported devices.</li></ul> <p>I guess using a <a href="https://infosec.space/tags/128bit" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>128bit</span></a> address space was inspired by <a href="https://infosec.space/tags/ZFS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ZFS</span></a> doing the same <em>before</em>, as the folks who designed both wanted to design a solution that clearly will outlive them (<em>way harder</em> than COBOL has outlived Grace Hopper)...</p><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">#<span>IPv6</span></a> because not only do I only have <a href="https://infosec.space/tags/IPv4only" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>IPv4only</span></a> <a href="https://infosec.space/tags/Internet" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Internet</span></a> but my <a href="https://infosec.space/tags/ISP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ISP</span></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">#<span>IPv4</span></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">#<span>HurricaneElectric</span></a> / <a href="https://infosec.space/tags/HEnet" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>HEnet</span></a>'s <a href="https://infosec.space/tags/Tunnelbroker" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Tunnelbroker</span></a> fail face first due to <a href="https://infosec.space/tags/Geoblocking" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Geoblocking</span></a> and the fact that <a href="https://infosec.space/tags/ASNs" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ASNs</span></a> get geolocated, not their <a href="https://infosec.space/tags/PoPs" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>PoPs</span></a>... </li></ul><p>If I was <span class="h-card" translate="no"><a href="https://social.bund.de/@BNetzA" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>BNetzA</span></a></span> I would've mandated <a href="https://infosec.space/tags/DualStack" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>DualStack</span></a> and banned <a href="https://infosec.space/tags/CGNAT" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>CGNAT</span></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">#<span>RFC1918</span></a> address spaces) as well as <a href="https://infosec.space/tags/DualStackLite" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>DualStackLite</span></a>!</p>
Recent searches
No recent searches
Search options
Only available when logged in.
social.bund.de is one of the many independent Mastodon servers you can use to participate in the fediverse.
Dies ist der Mastodon-Server der Bundesbeauftragten für den Datenschutz und die Informationsfreiheit (BfDI).
Administered by:
Server stats:
96active users
social.bund.de: About · Profiles directory · Privacy policy
Mastodon: About · Get the app · Keyboard shortcuts · View source code · v4.3.7
#IPv4
0 posts · 0 participants · 0 posts today
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://mstdn.jp/@landley" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>landley</span></a></span> <span class="h-card" translate="no"><a href="https://mstdn.social/@jschauma" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>jschauma</span></a></span> <span class="h-card" translate="no"><a href="https://infosec.exchange/@ryanc" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>ryanc</span></a></span> <span class="h-card" translate="no"><a href="https://infosec.exchange/@0xabad1dea" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>0xabad1dea</span></a></span> I think <a href="https://infosec.space/tags/IPv6" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>IPv6</span></a> would've gotten more acceptance if it was merely a 4x long <a href="https://infosec.space/tags/IPv4" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>IPv4</span></a> annotation instead of doing hexadecimals.</p><ul><li>I mean, worse would've only been <a href="https://infosec.space/tags/base32hex" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>base32hex</span></a> or <a href="https://infosec.space/tags/base64hex" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>base64hex</span></a> for IPv6 addresses...</li></ul>
Ex<p>Bei manchen Dinge merkt man erst was man hat, wenn es fehlt.</p><p>Heute: <a href="https://chaos.social/tags/IPv4" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>IPv4</span></a></p>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://digitalcourage.social/@krzym" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>krzym</span></a></span> <span class="h-card" translate="no"><a href="https://oxytodon.com/@fuchsiii" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>fuchsiii</span></a></span> <span class="h-card" translate="no"><a href="https://social.bund.de/@BNetzA" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>BNetzA</span></a></span> und wie <a href="https://infosec.space/tags/Diesel" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Diesel</span></a> funktioniert <a href="https://infosec.space/tags/IPv4" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>IPv4</span></a>...</p><p><a href="https://www.youtube.com/watch?v=myXi1KMyClc" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="">youtube.com/watch?v=myXi1KMyClc</span><span class="invisible"></span></a></p><p><a href="https://infosec.space/tags/Sarkasmus" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Sarkasmus</span></a></p>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://digitalcourage.social/@krzym" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>krzym</span></a></span> <span class="h-card" translate="no"><a href="https://oxytodon.com/@fuchsiii" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>fuchsiii</span></a></span> solange <span class="h-card" translate="no"><a href="https://social.bund.de/@BNetzA" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>BNetzA</span></a></span> nicht mindestens ein /64 an <a href="https://infosec.space/tags/IPv6" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>IPv6</span></a> pro <a href="https://infosec.space/tags/IPv4" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>IPv4</span></a> vorschreibt wird sich nix dran ändern.</p><ul><li>Erst wenn <a href="https://infosec.space/tags/DualStack" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>DualStack</span></a> flächendeckend ist kann IPv4 abgeschaltet werden!</li></ul>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://mastodon.catgirl.cloud/@xyno" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>xyno</span></a></span> +9001%</p><p><span class="h-card" translate="no"><a href="https://social.bund.de/@BNetzA" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>BNetzA</span></a></span> should mandate a /64 of <a href="https://infosec.space/tags/IPv6" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>IPv6</span></a> for every single <a href="https://infosec.space/tags/IPv4" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>IPv4</span></a> if not a /56 - /48 as minimum for bigger allocations.</p><ul><li><a href="https://infosec.space/tags/IPv4only" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>IPv4only</span></a> should not be accepted as <a href="https://infosec.space/tags/InternetAcces" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>InternetAcces</span></a> and until everything works on <a href="https://infosec.space/tags/IPv6only" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>IPv6only</span></a>, shits gonna remain shit!</li></ul>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://mastodon.social/@marquito" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>marquito</span></a></span> <span class="h-card" translate="no"><a href="https://astronomy.social/@admin" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>admin</span></a></span> Alter, wenn du dir <a href="https://infosec.space/tags/IPv6" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>IPv6</span></a> besser merken kannst als <a href="https://infosec.space/tags/DNS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>DNS</span></a> dann haste nen <a href="https://infosec.space/tags/GalxyBrainChair" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>GalxyBrainChair</span></a>... </p><ul><li><a href="https://infosec.space/tags/DNS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>DNS</span></a> erlaubt viel einfacher transparente Skalierung ohne Zwischenschritte wie <a href="https://infosec.space/tags/CARP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>CARP</span></a>...<br></li></ul><p>Das Problem ist dass leider es von der <span class="h-card" translate="no"><a href="https://social.bund.de/@BNetzA" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>BNetzA</span></a></span> keine Vorgabe gibt, jedem Internetanschluss mindestens ein /64 - Präfix an IPv6 mitzugeben.</p><ul><li>Und so häng' ich mit nem /28 an <a href="https://infosec.space/tags/IPv4" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>IPv4</span></a>-only fest!</li></ul>
Richard "RichiH" Hartmann<p><span class="h-card" translate="no"><a href="https://fosstodon.org/@fosdem" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>fosdem</span></a></span> I just announced our temporary <a href="https://chaos.social/tags/IPv4" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>IPv4</span></a> PI space 151.216.128.0/17 for <a href="https://chaos.social/tags/FOSDEM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>FOSDEM</span></a>. If you want, you can follow it starting to become visible over the next hours and days on any <a href="https://chaos.social/tags/BGP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>BGP</span></a> <a href="https://chaos.social/tags/lookingglass" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>lookingglass</span></a>, e.g. <a href="https://lg.de-cix.net/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="">lg.de-cix.net/</span><span class="invisible"></span></a> has quite a few globally so you can see it spread.</p><p>As of this writing, <a href="https://lg.de-cix.net/search?q=151.216.128.0%2F17" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">lg.de-cix.net/search?q=151.216</span><span class="invisible">.128.0%2F17</span></a> has it in Frankfurt and Marseille, and nowhere else. Usually for new BGP announcements from EU, they show up in LATAM last, with a delay of up to three days.</p>
goetz 🚲<p>Hier ein <a href="https://chaos.social/tags/CGNAT" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>CGNAT</span></a> Beispiel eines regionalen Glasfasernetzbetreibers <a href="https://radar.cloudflare.com/adoption-and-usage/as30766" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">radar.cloudflare.com/adoption-</span><span class="invisible">and-usage/as30766</span></a> <br>Selbst der Wireguard Tunnel ist nicht stabil. <br>Dieser <a href="https://chaos.social/tags/LegacynetServiceProvider" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>LegacynetServiceProvider</span></a> bietet nichtmal <a href="https://chaos.social/tags/IPv6" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>IPv6</span></a> an. Betrieb von Diensten für die Familie ohne Relay Server nicht möglich.</p><p>Zu dem Leserbrief über Glasfaser Anschlüsse aus dem <span class="h-card" translate="no"><a href="https://social.heise.de/@ct_Magazin" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>ct_Magazin</span></a></span> </p><p>~1000 <a href="https://chaos.social/tags/IPv4" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>IPv4</span></a> Adressen müssen für ca. 15k Kunden reichen.</p>
jesterchen42<p><span class="h-card" translate="no"><a href="https://rollenspiel.social/@ArneBab" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>ArneBab</span></a></span> Äääähhh... Ich habe gerade glücklich einen (full) Dual Stack über Kupfer. Ist das bei Glasfaser nicht üblich? Dann behalte ich meinen aktuellen Anschluß nämlich so lange wie möglich!</p><p><a href="https://social.tchncs.de/tags/ipv4" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ipv4</span></a> <a href="https://social.tchncs.de/tags/ipv6" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ipv6</span></a> <a href="https://social.tchncs.de/tags/glasfaser" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>glasfaser</span></a></p>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://alyx.social/@alyx" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>alyx</span></a></span> I know, but since I am pissed about my <a href="https://infosec.space/tags/ISP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ISP</span></a> in <a href="https://infosec.space/tags/Germany" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Germany</span></a> who's unwilling to assign me even a single /64 of <a href="https://infosec.space/tags/IPv6" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>IPv6</span></a> whilst I have a whole /28 of <a href="https://infosec.space/tags/IPv4" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>IPv4</span></a>'s and they'd gladly offer me more of those I do want to get regularoy action ( <span class="h-card" translate="no"><a href="https://social.bund.de/@BNetzA" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>BNetzA</span></a></span> ) <em>BEFORE</em> I'd have to spin my own <a href="https://infosec.space/tags/ASN" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ASN</span></a> via <span class="h-card" translate="no"><a href="https://mastodon.social/@ripencc" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>ripencc</span></a></span> ...</p><ul><li>I'm frustrated of havin <a href="https://infosec.space/tags/IPv4only" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>IPv4only</span></a> <a href="https://infosec.space/tags/Internet" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Internet</span></a> access and until <a href="https://infosec.space/tags/IPv6" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>IPv6</span></a> is mandatory and fully rolled out, <a href="https://infosec.space/tags/Ipv6only" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Ipv6only</span></a> won't be possible or feasible <em>at all</em>!</li></ul>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://alyx.social/@alyx" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>alyx</span></a></span> <span class="h-card" translate="no"><a href="https://chaos.social/@cr" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>cr</span></a></span> and I do think that <a href="https://infosec.space/@kkarhan/113612034602788617" rel="nofollow noopener noreferrer" target="_blank">before</a> I've to fough up <span class="h-card" translate="no"><a href="https://mastodon.social/@ripencc" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>ripencc</span></a></span> membership fees, it'll be ratger more effective to complain at <span class="h-card" translate="no"><a href="https://social.bund.de/@BNetzA" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>BNetzA</span></a></span> so that they'll mandate a /64 of <a href="https://infosec.space/tags/IPv6" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>IPv6</span></a>'s for every <a href="https://infosec.space/tags/IPv4" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>IPv4</span></a> assigned at minimum!</p>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://techhub.social/@leeloo" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>leeloo</span></a></span> Until regulators like <span class="h-card" translate="no"><a href="https://social.bund.de/@BNetzA" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>BNetzA</span></a></span> 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">#<span>IPv6</span></a> to be supplied to <em>every <a href="https://infosec.space/tags/internet" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>internet</span></a> connection</em> with no exceptioms or charges <em>and</em> 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">#<span>IPv4</span></a>.</p><ul><li>Worse is only <a href="https://infosec.space/tags/DualStackLite" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>DualStackLite</span></a> and having to do unreliable (due to <a href="https://infosec.space/tags/Geoblocking" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Geoblocking</span></a>) hacks like <a href="https://infosec.space/tags/6in4" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>6in4</span></a> / <a href="https://infosec.space/tags/6over4" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>6over4</span></a> with <a href="https://tunnelbroker.net" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="">tunnelbroker.net</span><span class="invisible"></span></a> ...</li></ul><p>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...</p>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://ipv6.social/@tschaefer" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>tschaefer</span></a></span> nein, aber die <span class="h-card" translate="no"><a href="https://social.bund.de/@BNetzA" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>BNetzA</span></a></span> könnte <a href="https://infosec.space/tags/IPv6" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>IPv6</span></a>-Support vorschreiben und durchboxen, damit die Notwendige Versorgung endlich sichergestellt ist, damit die <a href="https://infosec.space/tags/Umstellung" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Umstellung</span></a> bzw. <a href="https://infosec.space/tags/Transition" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Transition</span></a> von <a href="https://infosec.space/tags/IPv4" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>IPv4</span></a> zu IPv6 möglich wird...</p>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://ipv6.social/@tschaefer" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>tschaefer</span></a></span> 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">#<span>IPv6</span></a> haben oder bekommen können...</p><ul><li>Bspw.: Verweigert mein <a href="https://infosec.space/tags/ISP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ISP</span></a> die Bereitstellung von echtem <a href="https://infosec.space/tags/DualStack" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>DualStack</span></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><p>Umgekehrt sind bis heute nicht alle <a href="https://infosec.space/tags/Diensteanbieter" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Diensteanbieter</span></a> & Services von <a href="https://infosec.space/tags/IPv4" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>IPv4</span></a> auf <a href="https://infosec.space/tags/IPv6" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>IPv6</span></a> migriert worden.</p><ul><li><a href="https://infosec.space/tags/IPv6only" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>IPv6only</span></a> ist anders als ein <a href="https://infosec.space/tags/Windows" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Windows</span></a>-Verbot (was <a href="https://infosec.space/tags/BDSG" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>BDSG</span></a> & <a href="https://infosec.space/tags/DSGVO" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>DSGVO</span></a> eigentlich verlangen!) illusorisch.</li></ul><p>Sorgt zwar für Henne-Ei-Problem, wäre aber durch die <span class="h-card" translate="no"><a href="https://social.bund.de/@BNetzA" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>BNetzA</span></a></span> 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">#<span>CGNAT</span></a> [insbesondere mit <a href="https://infosec.space/tags/RFC1918" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>RFC1918</span></a>-Addressraum] verbietet!</p><ul><li>Besonders Bullshit wie <a href="https://infosec.space/tags/DualStackLite" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>DualStackLite</span></a> ist murks: Entweder korrekt Dual-Stack oder lasst es sein!!!</li></ul>
hallunke23 🇺🇦<p>In ST ist es nicht besser. ICh war letztens auf dem Glasfasertag der Landsregierung ST. Da musste man sich vorher per <a href="https://troet.cafe/tags/IPv4" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>IPv4</span></a> (!) anmelden. Auf der Veranstaltung wurde dann das Wort „IPv6“ kein einziges Mal auch nur erwähnt. Und ein Mitarbeiter von Dataport, mit dem ich versucht habe, zu reden, hatte von der Materie keine Ahnung.<br><span class="h-card" translate="no"><a href="https://ipv6.social/@tschaefer" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>tschaefer</span></a></span> <span class="h-card" translate="no"><a href="https://chaos.social/@goetz" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>goetz</span></a></span> <span class="h-card" translate="no"><a href="https://mastodon.social/@ComputerBase" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>ComputerBase</span></a></span> <span class="h-card" translate="no"><a href="https://social.bund.de/@BNetzA" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>BNetzA</span></a></span> <span class="h-card" translate="no"><a href="https://social.bund.de/@bmdv" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>bmdv</span></a></span> <a href="https://troet.cafe/tags/ipv6" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ipv6</span></a></p>
Thomas Schäfer<p><span class="h-card" translate="no"><a href="https://chaos.social/@goetz" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>goetz</span></a></span> <span class="h-card" translate="no"><a href="https://mastodon.social/@ComputerBase" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>ComputerBase</span></a></span> <span class="h-card" translate="no"><a href="https://social.bund.de/@BNetzA" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>BNetzA</span></a></span> </p><p>Das ist ja ein Saftladen. Gefördert von Bund und Land.</p><p>Liebes <span class="h-card" translate="no"><a href="https://social.bund.de/@bmdv" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>bmdv</span></a></span> schaut ihr nicht nach, wie (schlecht) eure Förderung umgesetzt wird?</p><p><a href="https://ipv6.social/tags/ipv6" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ipv6</span></a> fehlt und <a href="https://ipv6.social/tags/ipv4" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ipv4</span></a> ist unfassbar schlecht oder wahlweise teuer</p>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://chaos.social/@goetz" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>goetz</span></a></span> <span class="h-card" translate="no"><a href="https://chaos.social/@fluepke" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>fluepke</span></a></span> </p><p><a href="https://infosec.space/tags/Fact" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Fact</span></a> is my <a href="https://infosec.space/tags/ISP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ISP</span></a> won't even issue me a single /64 of <a href="https://infosec.space/tags/IPv6" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>IPv6</span></a>'s but had no problem allocating me a whole /28 of <a href="https://infosec.space/tags/IPv4" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>IPv4</span></a>'s...</p><p>And since they seem unwilling to even offer me a /64 (not even talking about a /48) I'm stuck on <a href="https://infosec.space/tags/IPv4only" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>IPv4only</span></a> internet until I can afford the overhead of €500 p.a. just for a @RIPE_NCC membership, not even accounting for the cost of having to setup and maintain my own <a href="https://infosec.space/tags/ASN" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ASN</span></a> and acquiring a /24 of IPv4's + /48 of IPv6's...</p><p>If <span class="h-card" translate="no"><a href="https://social.bund.de/@BNetzA" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>BNetzA</span></a></span> actually cared they'd mandate a <a href="https://infosec.space/tags/free" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>free</span></a> /64 with every single IPv4 allocation.</p>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://chaos.social/@fluepke" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>fluepke</span></a></span> sadly the only way this could be changed if <span class="h-card" translate="no"><a href="https://social.bund.de/@BNetzA" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>BNetzA</span></a></span> would mandate proper <a href="https://infosec.space/tags/DualStack" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>DualStack</span></a> support.</p><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 noreferrer" target="_blank">#<span>IPv6</span></a>'s per <a href="https://infosec.space/tags/IPv4" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>IPv4</span></a> block allocation...</li></ul><p>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 noreferrer" target="_blank">#<span>subsidize</span></a> <a href="https://infosec.space/tags/Starlink" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Starlink</span></a> that mandate <a href="https://infosec.space/tags/FTTB" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>FTTB</span></a> & <a href="https://infosec.space/tags/FTTH" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>FTTH</span></a> coverage and installations...</p>
hallunke23 🇺🇦<p><span class="h-card" translate="no"><a href="https://social.bund.de/@itteam" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>itteam</span></a></span> Könnt ihr mal schaun, was mit euerm Mastodon-Server los ist? ICh glaube, dass da der IPv6-Stack gestört sein könnte. Jedenfalls komme ich nur per <a href="https://troet.cafe/tags/ipv4" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ipv4</span></a> drauf, nicht per IPv6.</p>
ExploreLive feeds
Mastodon is the best way to keep up with what's happening.
Follow anyone across the fediverse and see it all in chronological order. No algorithms, ads, or clickbait in sight.
LoginDrag & drop to upload