Create accountLogin

Recent searches

No recent searches

Search options

Only available when logged in.
mstdn.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A general-purpose Mastodon server with a 500 character limit. All languages are welcome.

Administered by:

Server stats:

16K
active users

mstdn.social: AboutStatusProfiles directoryPrivacy policy

Mastodon: AboutGet the appKeyboard shortcutsView source codev4.3.4

#ipv6mostly

0 posts0 participants0 posts today
Habr<p>[Перевод] Развёртывание сетей доступа преимущественно на основе IPv6</p><p>Изначальной моей задачей было получить сеть на базе протокола IPv6, где клиенты могли по желанию отказаться от использовать IPv4. Задача оказалась не самой тривиальной. В процессе поиска решения наткнулся на очень полезную заметку, которая по сути вобрала в себя всё то, что мне удалось выяснить. Представляю вашему внимаю перевод этой статьи с моими дополнениями по поводу настройки подобной сети на практике. Читать</p><p><a href="https://habr.com/ru/articles/886760/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="">habr.com/ru/articles/886760/</span><span class="invisible"></span></a></p><p><a href="https://zhub.link/tags/ipv6" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ipv6</span></a> <a href="https://zhub.link/tags/ipv6mostly" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ipv6mostly</span></a></p>
goetz 🚲<p><span class="h-card" translate="no"><a href="https://social.stefanberger.net/@stefan" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>stefan</span></a></span> <span class="h-card" translate="no"><a href="https://burningboard.net/@Larvitz" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>Larvitz</span></a></span> running my main wifi and guest wifi since month <a href="https://chaos.social/tags/ipv6mostly" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ipv6mostly</span></a> <br>Family accepted. Only if I take the streaming devices the <a href="https://chaos.social/tags/IPv4" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>IPv4</span></a> away, they break.<br>Home Assistant runs fine IPv6only. Wish that ESPhome could get rid of dual stack as well.</p><p>We need proper <a href="https://chaos.social/tags/IPv6" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>IPv6</span></a> support in <a href="https://chaos.social/tags/lwip" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>lwip</span></a> Anyone knowing how to support this?</p>
goetz 🚲<p><span class="h-card" translate="no"><a href="https://infosec.exchange/@alexhaydock" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>alexhaydock</span></a></span><br>Thank you for this article. Describes very much the road I took.</p><p><a href="https://chaos.social/tags/IPv6mostly" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>IPv6mostly</span></a> </p><p><span class="h-card" translate="no"><a href="https://mastodon.social/@nixCraft" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>nixCraft</span></a></span></p>
Knut Karevoll<p><span class="h-card" translate="no"><a href="https://soc.feditime.com/users/Tubsta" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>Tubsta</span></a></span> Anyone who want to try <a href="https://snabelen.no/tags/IPv6only" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>IPv6only</span></a> can just disable IPv4 with any ISP that provides native IPv6. So there is no appetite for such an ISP. It is more the ISPs that reject dual stack and switch to <a href="https://snabelen.no/tags/464xlat" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>464xlat</span></a> and <a href="https://snabelen.no/tags/IPv6mostly" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>IPv6mostly</span></a></p>
Colin Cogle :verified:<p>How I feel when dealing with DHCP scope exhaustion, propose the ideal solution, and am forced to drop the DHCPv4 lease time even further.</p><p><a href="https://mastodon.colincogle.name/tags/IPv6" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>IPv6</span></a> <a href="https://mastodon.colincogle.name/tags/IPv6Only" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>IPv6Only</span></a> <a href="https://mastodon.colincogle.name/tags/IPv6Mostly" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>IPv6Mostly</span></a> <a href="https://mastodon.colincogle.name/tags/IPv6IsNow" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>IPv6IsNow</span></a> <a href="https://mastodon.colincogle.name/tags/sysadmin" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>sysadmin</span></a></p>
T_X<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/@ffhl" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>ffhl</span></a></span> I needed a while to figure out what practical benefit we would have. One thing that came to my mind: Avoiding <a href="https://chaos.social/tags/ARP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ARP</span></a> on supporting devices completely if I understand <a href="https://chaos.social/tags/ipv6mostly" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ipv6mostly</span></a> correctly. We do have a DHT for ARP in <a href="https://chaos.social/tags/batman_adv" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>batman_adv</span></a>. And could reduce broadcasts a lot with it. But it's still not zero. <a href="https://chaos.social/tags/IPv6" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>IPv6</span></a> is so much smarter for Neighbor Discovery as it uses <a href="https://chaos.social/tags/multicast" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>multicast</span></a> properly with its solicited mcast addresses and not like broadcasts. And we have <a href="https://chaos.social/tags/MLD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>MLD</span></a> snooping in our <a href="https://chaos.social/tags/mesh" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>mesh</span></a>.</p>
goetz 🚲<p><span class="h-card" translate="no"><a href="https://chaos.social/@T_X" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>T_X</span></a></span><br>How about <a href="https://chaos.social/tags/ipv6mostly" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ipv6mostly</span></a> ? <br><span class="h-card" translate="no"><a href="https://chaos.social/@ffhl" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>ffhl</span></a></span></p>
goetz 🚲<p><span class="h-card" translate="no"><a href="https://snabelen.no/@Gnonthgol" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>Gnonthgol</span></a></span><br>Yes and start with <a href="https://chaos.social/tags/IPv6mostly" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>IPv6mostly</span></a> in the access networks.</p><p><a href="https://ripe87.ripe.net/archives/video/1160" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">ripe87.ripe.net/archives/video</span><span class="invisible">/1160</span></a><br><a href="https://ripe88.ripe.net/archives/video/1355/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">ripe88.ripe.net/archives/video</span><span class="invisible">/1355/</span></a><br><a href="https://youtu.be/Zr-rdfx7VD0?si=udKc176cdQlW0VMj" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">youtu.be/Zr-rdfx7VD0?si=udKc17</span><span class="invisible">6cdQlW0VMj</span></a></p><p><span class="h-card" translate="no"><a href="https://social.meenzen.net/@samuel" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>samuel</span></a></span></p>
goetz 🚲<p><span class="h-card" translate="no"><a href="https://infosec.exchange/@paul_ipv6" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>paul_ipv6</span></a></span><br>As the Google campus network is <a href="https://chaos.social/tags/IPv6mostly" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>IPv6mostly</span></a> these days, I cannot believe that using <a href="https://chaos.social/tags/IPv6" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>IPv6</span></a> printing from <a href="https://chaos.social/tags/Android" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Android</span></a> is not possible.<br><span class="h-card" translate="no"><a href="https://lemmy.ml/c/googlepixel" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>googlepixel</span></a></span></p>
Thomas Schäfer<p>A further talk about <a href="https://ipv6.social/tags/ipv6mostly" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ipv6mostly</span></a> </p><p><a href="https://ipv6.social/tags/ipv6" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ipv6</span></a> </p><p>Be warned the slides move very fastly.😬</p><p><a href="https://m.youtube.com/watch?v=Zr-rdfx7VD0" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">m.youtube.com/watch?v=Zr-rdfx7</span><span class="invisible">VD0</span></a></p>
goetz 🚲<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><br>I was thinking how this title would continue. Knowing here previous talks and her area of work it was clear to me how it would continue and I was right. <a href="https://chaos.social/tags/DNS64" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>DNS64</span></a></p><p>Using an <a href="https://chaos.social/tags/IPv6mostly" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>IPv6mostly</span></a> setup I can clearly see why.</p>
Thomas Schäfer<p>Is someone using the combination: <a href="https://ipv6.social/tags/IPv6only" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>IPv6only</span></a> / <a href="https://ipv6.social/tags/ipv6mostly" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ipv6mostly</span></a> network printer + cups, airprint, MacOS? <br>(Macbook should discover and configure the printer by just a simple "add")</p><p>Today I thought about IPv6mostly at work, but I forgot some of my ugly IPv4 dependencies 😢</p>
Ray Robertson<p>This draft has now been officially adopted by the v6ops IETF working group and renamed to:<br>draft-ietf-v6ops-6mops</p><p><a href="https://datatracker.ietf.org/doc/draft-ietf-v6ops-6mops/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">datatracker.ietf.org/doc/draft</span><span class="invisible">-ietf-v6ops-6mops/</span></a></p><p>Also, a related 464XLAT / CLAT draft to keep an eye on:<br><a href="https://datatracker.ietf.org/doc/draft-ietf-v6ops-claton/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">datatracker.ietf.org/doc/draft</span><span class="invisible">-ietf-v6ops-claton/</span></a></p><p><a href="https://mastodon.social/tags/IPv6" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>IPv6</span></a> <a href="https://mastodon.social/tags/IPv6Mostly" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>IPv6Mostly</span></a> <a href="https://mastodon.social/tags/CLAT" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>CLAT</span></a></p>
Thomas Schäfer<p>Hat eigentlich schon irgendeine <a href="https://ipv6.social/tags/Freifunk" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Freifunk</span></a>|gemeinde <a href="https://ipv6.social/tags/ipv6mostly" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ipv6mostly</span></a> oder <a href="https://ipv6.social/tags/ipv6only" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ipv6only</span></a> dauerhaft im Einsatz?</p>
Colin Cogle :verified:<p>I opted to test Windows 11 24H2 for my company. Good news, Wi-Fi 7 works great. I’m connected to my U7-Pro at 5.8 Gbps — not that that will get me too far with the AP connected with 2.5GBaseT and 1 Gbps Internet (download, a pathetic 0.035 Gbps upload over DOCSIS). But hey, it looks nice.</p><p>Bad news, <span class="h-card" translate="no"><a href="https://mspsocial.net/@jima" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>jima</span></a></span> and <span class="h-card" translate="no"><a href="https://infosec.exchange/@paulos" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>paulos</span></a></span>: the promised “future version of Windows 11” with CLAT support isn’t this one. Windows 11 still insists on using legacy IP despite me shoving DHCPv4 option 108 down its throat. </p><p><a href="https://mastodon.colincogle.name/tags/Windows" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Windows</span></a> <a href="https://mastodon.colincogle.name/tags/Win11" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Win11</span></a> <a href="https://mastodon.colincogle.name/tags/Windows11" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Windows11</span></a> <a href="https://mastodon.colincogle.name/tags/24H2" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>24H2</span></a> <a href="https://mastodon.colincogle.name/tags/IPv6" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>IPv6</span></a> <a href="https://mastodon.colincogle.name/tags/LegacyIP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>LegacyIP</span></a> <a href="https://mastodon.colincogle.name/tags/IPv6mostly" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>IPv6mostly</span></a> <a href="https://mastodon.colincogle.name/tags/IPv6only" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>IPv6only</span></a> <a href="https://mastodon.colincogle.name/tags/464XLAT" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>464XLAT</span></a> <a href="https://mastodon.colincogle.name/tags/CLAT" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>CLAT</span></a> <a href="https://mastodon.colincogle.name/tags/UniFi" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>UniFi</span></a> <a href="https://mastodon.colincogle.name/tags/WiFi7" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>WiFi7</span></a> <a href="https://mastodon.colincogle.name/tags/sysadmin" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>sysadmin</span></a> <a href="https://mastodon.colincogle.name/tags/EarlyAdopter" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>EarlyAdopter</span></a></p>
Thomas Schäfer<p><a href="https://ipv6.social/tags/ipv6" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ipv6</span></a> <br><a href="https://ipv6.social/tags/podcast" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>podcast</span></a> <br><a href="https://ipv6.social/tags/ipv6mostly" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ipv6mostly</span></a> </p><p><a href="https://packetpushers.net/podcasts/ipv6-buzz/ipb158-ipv6-mostly-a-strategy-to-balance-legacy-and-modern-networking-needs/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">packetpushers.net/podcasts/ipv</span><span class="invisible">6-buzz/ipb158-ipv6-mostly-a-strategy-to-balance-legacy-and-modern-networking-needs/</span></a></p><p>IPB158: “IPv6 Mostly”: A Strategy to Balance Legacy and Modern Networking Needs</p>
Thomas Schäfer<p>Nice changes:</p><p>464XLAT-7: If the IPv6 Transition CE Router performs CLAT functions<br> it SHOULD also include the PLAT prefix in Router Advertisements<br> ([RFC8781]) sent via the LAN interfaces. If the IPv6 Transition CE<br> Router acts as a DHCP server it SHOULD enable DHCP Option 108<br> ([RFC8925]) processing.</p><p><a href="https://datatracker.ietf.org/doc/draft-ietf-v6ops-claton/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">datatracker.ietf.org/doc/draft</span><span class="invisible">-ietf-v6ops-claton/</span></a></p><p>Unfortunately, even Android doesn't do it yet.😭</p><p><a href="https://ipv6.social/tags/IPv6only" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>IPv6only</span></a> <br><a href="https://ipv6.social/tags/ipv6mostly" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ipv6mostly</span></a> <br><a href="https://ipv6.social/tags/ipv6" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ipv6</span></a></p>
🌈 Kerblambuli 🦄<p>Alright <a href="https://chaos.social/tags/DNS64" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>DNS64</span></a> and <a href="https://chaos.social/tags/NAT64" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>NAT64</span></a> finally have been set up on my journey to <a href="https://chaos.social/tags/IPv6mostly" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>IPv6mostly</span></a> ;c)</p><p>How it works: either dual stack or <a href="https://chaos.social/tags/IPv6only" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>IPv6only</span></a> clients ask the DNS server running on my firewall for name resolution; if there exist only IPv4 answers (A records) upstream the DNS64 kicks in and synthesizes IPv6 (<a href="https://chaos.social/tags/AAAA" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>AAAA</span></a> records) using a special v6 subnet. Then my clients try to connect to those fake v6 addresses and the NAT64 translates v6 back to v4 transparently.</p><p>This forces clients to *use* IPv6 only. 🤤</p>
Thomas Schäfer<p><a href="https://ipv6.social/tags/ipv6mostly" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ipv6mostly</span></a> <br><a href="https://ipv6.social/tags/ipv6" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ipv6</span></a> <br><a href="https://ipv6.social/tags/ipv6only" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ipv6only</span></a> <br><a href="https://ipv6.social/tags/ripe88" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ripe88</span></a> <br>update by Jen Linkova<br><a href="https://ripe88.ripe.net/wp-content/uploads/presentations/102-RIPE88-IPv6WG-Linkova.pdf" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">ripe88.ripe.net/wp-content/upl</span><span class="invisible">oads/presentations/102-RIPE88-IPv6WG-Linkova.pdf</span></a></p><p>now live </p><p><a href="https://ripe88.ripe.net/live/main/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="">ripe88.ripe.net/live/main/</span><span class="invisible"></span></a></p>
Thomas Schäfer<p>Weil's auf dem denog15 so schön war...</p><p><a href="https://www.dfn.de/event/80-betriebstagung/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">dfn.de/event/80-betriebstagung</span><span class="invisible">/</span></a><br><a href="https://www.dfn.de/wp-content/uploads/2023/10/IPv6-Mostly_DFNBT80_v2.pdf" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">dfn.de/wp-content/uploads/2023</span><span class="invisible">/10/IPv6-Mostly_DFNBT80_v2.pdf</span></a><br>Einsatz von IPv6-Mostly im Campus-Netz der Ruhr-Universität Bochum <br>R. Därmann | Ruhr-Universität Bochum</p><p><a href="https://ipv6.social/tags/ipv6mostly" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ipv6mostly</span></a></p>
ExploreLive feeds
About