Konto erstellenAnmelden

Frühere Suchanfragen

Keine früheren Suchanfragen

Suchoptionen

Nur verfügbar, wenn angemeldet.
sueden.social ist einer von vielen unabhängigen Mastodon-Servern, mit dem du dich im Fediverse beteiligen kannst.
Eine Community für alle, die sich dem Süden hingezogen fühlen. Wir können alles außer Hochdeutsch.

Verwaltet von:

Serverstatistik:

1,9 Tsd.
aktive Profile

sueden.social: ÜberStatusProfilverzeichnisDatenschutzerklärung

Mastodon: ÜberApp herunterladenTastenkombinationenQuellcode anzeigenv4.3.8

#howipv6helpedmethisweek

0 Beiträge0 Beteiligte0 Beiträge heute
kasperd<p>While I was away from home for a few days I was able to access data on a machine at home using ssh. Thanks to having IPv6 both at home and in the place I was staying this worked without needing to mess with fragile NAT or port-forwarding setups.</p><p><a class="hashtag" href="https://westergaard.social/tag/howipv6helpedmethisweek" rel="nofollow noopener noreferrer" target="_blank">#HowIPv6HelpedMeThisWeek</a></p>
Jima :Compromise_bi_flag:<p>And another <a href="https://mspsocial.net/tags/HowIPv6HelpedMeThisWeek" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>HowIPv6HelpedMeThisWeek</span></a> (from another week) related to this toot, I have a BIND nameserver in my homelab with 112 views (for shenanigans reasons), and I can't expose that construct to the internet without either <a href="https://mspsocial.net/tags/IPv6" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>IPv6</span></a>, or some truly hideous port-based NAT hijinks (which, ugh, no thank you).</p><p>(And worse: I actually have two of them now. 😂)<br><a href="https://mspsocial.net/@jima/114354031715285418" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">mspsocial.net/@jima/1143540317</span><span class="invisible">15285418</span></a></p>
Jima :Compromise_bi_flag:<p><span class="h-card" translate="no"><a href="https://tech.lgbt/@becomethewaifu" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>becomethewaifu</span></a></span> <span class="h-card" translate="no"><a href="https://social.jsteuernagel.de/@jana" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>jana</span></a></span> Plus, if you actually needed to reach something over the tunnel that's stuck IPv4-only, there's always NAT64. 😀</p><p>(And here we hint at the only context in which I like DoH: the ability to make one browser use DNS64, but not force the rest of the operating system to also use it.)</p><p><a href="https://mspsocial.net/tags/HowIPv6HelpedMeThisWeek" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>HowIPv6HelpedMeThisWeek</span></a> (but it was a different week)</p>
Jana<p>A lingering problem I had was my Wireguard tunnel for client devices.<br>I have multiple times added some subnet and then had to individually add it to the allowed IPs on each device. I didn't want to just preemptively forward the entire 10.0.0.0/8 block, because that would be asking for trouble.</p><p>Now it just dawned on me that if I only use IPv6, that problem is gone. Not once did I have to change the v6 prefix, because I can easily leave enough room to grow.</p><p><a href="https://social.jsteuernagel.de/tags/HowIPv6HelpedMeThisWeek" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>HowIPv6HelpedMeThisWeek</span></a></p>
goetz 🚲<p>Configuring an <a href="https://chaos.social/tags/unbound" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>unbound</span></a> DNS Server I learned that it has a <a href="https://chaos.social/tags/NAT64" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>NAT64</span></a> mode.</p><p>Saved me from having to configure this server dual stacked to reach <a href="https://chaos.social/tags/IPv4only" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>IPv4only</span></a> authoritative nameserver. </p><p>Looking at you <span class="h-card" translate="no"><a href="https://zdf.social/@ZDF" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>ZDF</span></a></span>!</p><p><a href="https://chaos.social/tags/IPv6" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>IPv6</span></a> </p><p><a href="https://chaos.social/tags/HowIPv6HelpedMeThisWeek" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>HowIPv6HelpedMeThisWeek</span></a></p>
kasperd<p>I am considering the idea of writing a weekly post <a class="hashtag" href="https://westergaard.social/tag/howipv6helpedmethisweek" rel="nofollow noopener noreferrer" target="_blank">#HowIPv6HelpedMeThisWeek</a> giving one example of something useful IPv6 has done for me in the past week.</p><p>I am aware that it may be challenging to come up with a novel example each week. And really it does not necessarily have to be novel in order to count. Doing the same useful thing each week is still useful. But the posts will obviously be more interesting, if I don't repeat the same thing week after week.</p><p>It may also be challenging to notice each time IPv6 does something useful because we tend to notice things which are broken rather than things which are working. And IPv6 just working is the experience I have most of the time when connected to networks with native IPv6.</p><p>It would probably have been easier to come up with a weekly post about how IPv4 annoyed me in the past week. But if I want to make this a regular thing, I should focus on the positive things and not turn this into IPv4 bashing.</p><p>The hashtag is of course not only for me to use. I am not the only person who have had positive experiences with IPv6.</p>
EntdeckenLive-Feeds
Über