sigmoid.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A social space for people researching, working with, or just interested in AI!

Server stats:

595
active users

#ipv6

25 posts22 participants0 posts today
Christoffer S.<p>This may sound like a dumb question, but with IPv6 am I supposed to ... learn the addresses like I have for IPv4?</p><p>With IPv4 I feel as if I have had a reasonable chance of learning some of the important blocks, but with IPv6... I genuinely hesitate to "adopt" because I fear having to learn the new addressing scheme.</p><p>If not, how should I ... "think" about IPv6 coming from the perspective of actually knowing IPv4-addresses?</p><p><a href="https://swecyb.com/tags/Networking" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Networking</span></a> <a href="https://swecyb.com/tags/IPv6" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IPv6</span></a> <a href="https://swecyb.com/tags/IPv4" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IPv4</span></a></p>
mkj<p><span class="h-card" translate="no"><a href="https://mastodon.km6g.us/@kevin" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>kevin</span></a></span> In that situation, I strongly suspect that the /64 ULA prefix being included in RAs would be superfluous, as the hosts are already aware of that network because they are already on it. I don't see any *harm* to the prefix being announced, but I don't really see any obvious benefit either.</p><p><a href="https://social.mkj.earth/tags/IPv6" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IPv6</span></a></p>
mkj<p><span class="h-card" translate="no"><a href="https://mastodon.km6g.us/@kevin" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>kevin</span></a></span> I'm not an expert, but I suspect the answer depends quite a lot on the answer to "will all hosts on the network always have statically configured addresses?".</p><p><a href="https://social.mkj.earth/tags/IPv6" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IPv6</span></a></p>
Kevin P. Fleming<p>IPv6 question:</p><p>There's a /64 subnet (using ULAs, so addresses are stable). All hosts on the subnet have static addresses, there is no SLAAC or DHCPv6. Those hosts have their addresses configured with /64 masks so they are able to communicate with each other directly.</p><p>There's also a router attached to that subnet, which provides access to other networks. That router emits RAs as a good IPv6 router should 🙂 </p><p>The question is: is there any value to including this ULA prefix in the RAs themselves? Since the "M", "O", and "Autonomous" bits will all be 'false', how would the hosts benefit from the prefix being included in the RAs?</p><p>(This subnet is already alive and traffic is flowing as planned, so this question is mostly about "have I missed something", not "how do I make this work")</p><p><a href="https://mastodon.km6g.us/tags/IPv6" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IPv6</span></a></p>
Tommaso Gagliardoni<p>This made me chuckle.</p><p><a href="https://infosec.exchange/tags/debian" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>debian</span></a> <a href="https://infosec.exchange/tags/humor" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>humor</span></a> <a href="https://infosec.exchange/tags/ipv6" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ipv6</span></a> <a href="https://infosec.exchange/tags/y2k38" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>y2k38</span></a> <a href="https://infosec.exchange/tags/hackernews" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>hackernews</span></a></p>
Erik Nygren :verified:<p>We are hiring for both a Director of Product Management and a Senior Product Architect for Cloud Networking (eg, within <a href="https://hachyderm.io/tags/Linode" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Linode</span></a> / <a href="https://hachyderm.io/tags/akamai_technologies" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>akamai_technologies</span></a> Cloud). The former is a remote US position while the latter is a remote Czechia/Poland position. </p><p>Come help specify and design a modern cloud networking platform (eg, utilizing IPv6-centric design patterns, while also meeting legacy IPv4 needs).</p><p><a href="https://jobs.akamai.com/en/sites/CX_1/job/152/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">jobs.akamai.com/en/sites/CX_1/</span><span class="invisible">job/152/</span></a></p><p><a href="https://jobs.akamai.com/en/sites/CX_1/job/1049" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">jobs.akamai.com/en/sites/CX_1/</span><span class="invisible">job/1049</span></a></p><p>I love working at Akamai which is why I've been at the company for 26 years now. We have lots of great employees, a global culture that values diversity and inclusivity, and no shortage of fun problems to solve.</p><p><a href="https://hachyderm.io/tags/FediHire" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>FediHire</span></a> <a href="https://hachyderm.io/tags/IPv6" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IPv6</span></a></p>
Peter WemmI have a strange issue when enabling dhcp option 108 / nat64 / etc on my <a class="hashtag" href="https://soc.crashed.org/tag/ipv6" rel="nofollow noopener" target="_blank">#ipv6</a>-mostly home network. I don't quite know what to make of it. <br><br>I use the apalrd fork of tayga to do NAT64. This is working great. Of note: my nat64 translator is using the well known prefix and is configured to allow access to my internal rfc1918 network. I'm using kea-3.0 for dhcp option 108 support. As a result, no ipv4 addresses are assigned to apple/android devices and they activate their clat to use with my nat64 translator. dns64 is available as well for my <a class="hashtag" href="https://soc.crashed.org/tag/freebsd" rel="nofollow noopener" target="_blank">#FreeBSD</a> jails etc (which also have no ipv4 but may need to reach github etc). This is all working fine.<br><br>EXCEPT.. I have a couple of tp-link tapo C125 cameras in homekit-secure-video mode. Mostly for pet doors etc. They don't seem to like to work in ipv6-only mode even though they did acquire an ipv6 address. These are working fine with apple home and do the motion detection / record video / etc thing. I can browse the recorded video just fine. So far so good..<br><br>However, if I try to check *live video* (vs icloud recorded), then the apple gear seems to try to talk to it via ipv4 directly - without having an ipv4 address on that vlan. When looking at a phone that is involved, I see the local clat (on 192.0.0.2) and all the ipv6 addresses. And yet, it seems to be sending direct 192.0.0.2 -&gt; 10.0.0.41 (the camera) packets on the network. Which of course, replies and the replies go to the freebsd router which drops them because they're garbage.<br><br>Thoughts:<br><br>* I know I'm not supposed to allow a nat64 on the private well-known prefix to reach back into rfc1918 space. That's fine for carrier stuff really dumb for a home network.<br><br>* Everything in the apple universe seems perfectly happy with this arrangement and uses clat/nat64 just fine.. EXCEPT live video on those couple of cameras. Is this just apple being weird?<br><br>* Kea is giving a dhcp4 reply of: "dns: 10.0.0.1, subnet mask: 255.255.255.0, option 108: 1800 seconds.". This is a bit strange. It's not assigning a pool address, nor a fixed reservation.. so why the subnet mask?<br><br>* I am wondering if perhaps the apple stuff has some workaround kludges for the nat64 spec's handing of well-known-prefix vs rfc1918 space? Maybe it is doing something like sniffing mdns or dhcp replies for other devices and using that to infer what the local network is?<br><br>* Older versions of Kea don't do dhcp option 108 properly - they tell the client to "turn off the ipv4 stack but also use this ipv4 address". Maybe apple inadvertently rely on this kind of quirk? I'm wondering if homekit secure video might have used the ipv4 address that older kea would have assigned anyway. I'll check that out in a while.<br><br>Does anyone recognize this? I'm going to tinker with the stuff I mentioned above. I figure its a long shot but maybe somebody might have an "AHA! that's easy, just do X, Y and Z!"
Jeff Fortin T. (風の庭園のNekohayo)<p>Spent nearly 3 hours chatting with <span class="h-card" translate="no"><a href="https://toot.aquilenet.fr/@s3phy" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>s3phy</span></a></span> trying to understand the distinctions between various types of IPv6 addresses.<br>Networks are confusing as heck :blobsweats:</p><p>Thanks to their patient proofreading I was also able to make this suggestion to clarify the UI in <a href="https://mastodon.social/tags/GNOME" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>GNOME</span></a> Settings' "Network" info dialog (in gnome-control-center): <a href="https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/3052#note_2505889" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">gitlab.gnome.org/GNOME/gnome-c</span><span class="invisible">ontrol-center/-/issues/3052#note_2505889</span></a></p><p>I'm hoping such labels can be added to make it a little bit clearer for users like me.</p><p><a href="https://mastodon.social/tags/IPv6" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IPv6</span></a> <a href="https://mastodon.social/tags/networking" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>networking</span></a> <a href="https://mastodon.social/tags/sysadmin" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>sysadmin</span></a> <a href="https://mastodon.social/tags/r%C3%A9seau" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>réseau</span></a> <a href="https://mastodon.social/tags/r%C3%A9seautique" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>réseautique</span></a> <a href="https://mastodon.social/tags/UX" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>UX</span></a></p>
Larvitz :fedora: :redhat:<p>Did some really good progress on my FreeBSD server, running on OVHCloud:</p><p>- Re-Installed with ZFS instead of UFS via OVH rescue-system:</p><p>cat FreeBSD-14.3-RELEASE-amd64-zfs-rebuilt.raw.xz | ssh root@w.x.y.z "xz -dc | dd of=/dev/sdb bs=1M"</p><p>- Configured IPv4 and IPv6 networking in rc.conf</p><p>- Configured BastilleBSD to manage bridged VNET Jails </p><p>- Jail IPv6 networking via NAT66 and ULA addresses</p><p>- Solid firewall setup for NAT and packet-filtering via pf </p><p>Amazing 🙂 :freebsd: </p><p><a href="https://burningboard.net/tags/freebsd" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>freebsd</span></a> <a href="https://burningboard.net/tags/unix" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>unix</span></a> <a href="https://burningboard.net/tags/ipv6" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ipv6</span></a> <a href="https://burningboard.net/tags/jails" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>jails</span></a> <a href="https://burningboard.net/tags/bastilleBSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>bastilleBSD</span></a> <span class="h-card" translate="no"><a href="https://fosstodon.org/@BastilleBSD" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>BastilleBSD</span></a></span></p>
Christian Lins<p>If you happen to be on a system with IPv6-only connectivity and you have to use a <a href="https://norden.social/tags/Java" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Java</span></a> software, you may want to add -Djava.net.preferIPv6Addresses=true as param to force Java to use <a href="https://norden.social/tags/IPv6" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IPv6</span></a>. Java still uses <a href="https://norden.social/tags/IPv4" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IPv4</span></a> as default which will not work on IPv6-only systems.</p>
Larvitz :fedora: :redhat:<p>Fun-Fact: Our Mastodon instance "burningboard.net" doesn't just have the IPv6 address 2a01:4f8:1c1c:4d2::1 but is also reachable via 2a01:4f8:1c1c:4d2::fed1 <br>as well as<br>2a01:4f8:1c1c:4d2:fed1:fed1:fed1:fed1</p><p>Might not make much sense, but it's funny :) </p><p><a href="https://burningboard.net/tags/mastodon" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>mastodon</span></a> <a href="https://burningboard.net/tags/ipv6" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ipv6</span></a> <a href="https://burningboard.net/tags/mastoadmin" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>mastoadmin</span></a> <a href="https://burningboard.net/tags/networking" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>networking</span></a> <span class="h-card" translate="no"><a href="https://burningboard.net/@tux" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>tux</span></a></span></p>
Albrecht<p>New TV with Google TV as main OS always „forgets“ its <a href="https://masto.a0s.de/tags/IPv6" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IPv6</span></a> addresses after a while, effectively losing all IPv6 connectivity. Why is Android’s IPv6 implementation such a pile of shit in so many areas? Doesn’t Google test their stuff?</p>
Thomas Schäfer<p><a href="https://ipv6.social/tags/china" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>china</span></a> <a href="https://ipv6.social/tags/ipv6" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ipv6</span></a> </p><p><a href="https://www.chinadaily.com.cn/a/202507/25/WS6882ead7a310ad07b5d91f34.html" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">chinadaily.com.cn/a/202507/25/</span><span class="invisible">WS6882ead7a310ad07b5d91f34.html</span></a></p>
Thomas Schäfer<p><a href="https://ipv6.social/tags/aws" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>aws</span></a> <a href="https://ipv6.social/tags/ipv6" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ipv6</span></a> </p><p>Amazon CloudWatch adds IPv6 support<br>Posted on: Jul 24, 2025 </p><p><a href="https://aws.amazon.com/about-aws/whats-new/2025/07/amazon-cloudwatch-adds-ipv6-support/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">aws.amazon.com/about-aws/whats</span><span class="invisible">-new/2025/07/amazon-cloudwatch-adds-ipv6-support/</span></a></p>
RIPE NCC<p>Claim your FREE certification voucher by 31 August! Complete any course on RIPE NCC Academy and receive a voucher to become a RIPE NCC Certified Professional for free! Interested? Visit <a href="https://academy.ripe.net/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="">academy.ripe.net/</span><span class="invisible"></span></a> <a href="https://mastodon.social/tags/elearning" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>elearning</span></a> <a href="https://mastodon.social/tags/certification" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>certification</span></a> <a href="https://mastodon.social/tags/voucher" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>voucher</span></a> <a href="https://mastodon.social/tags/ipv6" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ipv6</span></a> <a href="https://mastodon.social/tags/bgp" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>bgp</span></a></p>
Erik Nygren :verified:<p>Cool set of tools linked to today in a presentation in the <a href="https://hachyderm.io/tags/IETF" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IETF</span></a> <a href="https://hachyderm.io/tags/HAPPYWG" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>HAPPYWG</span></a> session:</p><p><a href="https://www.happy-eyeballs.net/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="">happy-eyeballs.net/</span><span class="invisible"></span></a></p><p>It allows you to characterize the Happy Eyeballs behavior of a client, such as to see how much of a delay in DNS resolution or TCP connection response triggers a failback from IPv6 to IPv4.</p><p>See more details in Dave Plonka's talk: </p><p><a href="https://datatracker.ietf.org/meeting/123/materials/slides-123-happy-hackathon-maprg-happy-eyeballs-and-ipv6-test-pod-open-testing-00" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">datatracker.ietf.org/meeting/1</span><span class="invisible">23/materials/slides-123-happy-hackathon-maprg-happy-eyeballs-and-ipv6-test-pod-open-testing-00</span></a></p><p><a href="https://hachyderm.io/tags/HappyEyeballs" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>HappyEyeballs</span></a> <a href="https://hachyderm.io/tags/IPv6" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IPv6</span></a> <a href="https://hachyderm.io/tags/IETF123" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IETF123</span></a></p>
Thomas Schäfer<p>There are still LIRs without <a href="https://ipv6.social/tags/IPv6" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IPv6</span></a> . 😕</p><p>~1000 LIRs still begging for <a href="https://ipv6.social/tags/IPv4" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IPv4</span></a> addresses 🤔</p><p><a href="https://ipv6.social/tags/ripe" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ripe</span></a> region </p><p><a href="https://www.ripe.net/about-us/news/member-update-july-2025/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">ripe.net/about-us/news/member-</span><span class="invisible">update-july-2025/</span></a></p>
Nivex 🐧 📻<p>What I want from <a href="https://tenforward.social/tags/Mozilla" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Mozilla</span></a>: Overhaul their infrastructure so I can reach all[1] of their resources via <a href="https://tenforward.social/tags/IPv6" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IPv6</span></a> </p><p>What we get from Mozilla: AI 😔 </p><p>[1] It only took them 7 years to get addons.mozilla.org working: <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1354049" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">bugzilla.mozilla.org/show_bug.</span><span class="invisible">cgi?id=1354049</span></a> . firefox.com now answers on IPv6 but links to download.mozilla.org which does not. Their infra is such a hodge-podge.</p>
O Slovensku<p>Vláda projednala dne 9. července 2025 zprávu předloženou Ministerstvem průmyslu a obchodu, která hodnotí pokrok při zavádění technologií IPv6</p><p>Tón: : mírně pozitivní<br><a href="https://rockosbasilisk.com/tags/%C4%8Desko" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>česko</span></a> <a href="https://rockosbasilisk.com/tags/gdelt" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>gdelt</span></a> <a href="https://rockosbasilisk.com/tags/ipv6" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ipv6</span></a> <a href="https://rockosbasilisk.com/tags/dnssec" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>dnssec</span></a> <a href="https://rockosbasilisk.com/tags/ministerstvo" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ministerstvo</span></a><br> </p><p><a href="https://mpo.gov.cz/cz/e-komunikace-a-posta/elektronicke-komunikace/zprava-o-podpore-protokolu-ipv6-a-technologie-dnssec-ve-statni-sprave-ceske-republiky--288703/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">mpo.gov.cz/cz/e-komunikace-a-p</span><span class="invisible">osta/elektronicke-komunikace/zprava-o-podpore-protokolu-ipv6-a-technologie-dnssec-ve-statni-sprave-ceske-republiky--288703/</span></a></p>
Jeroen Habets<p><span class="h-card" translate="no"><a href="https://ipv6.social/@tschaefer" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>tschaefer</span></a></span> <span class="h-card" translate="no"><a href="https://mastodon.offerman.com/@adrian" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>adrian</span></a></span> <span class="h-card" translate="no"><a href="https://mastodon.nl/@internet_nl" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>internet_nl</span></a></span> <span class="h-card" translate="no"><a href="https://mastodon.nl/@SIDN" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>SIDN</span></a></span> <span class="h-card" translate="no"><a href="https://eupolicy.social/@bert_hubert" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>bert_hubert</span></a></span> </p><p>Anyone have any idea why in March/April 2022 <a href="https://mastodon.habets.dev/tags/IPv6" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IPv6</span></a> use in <a href="https://mastodon.habets.dev/tags/NL" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>NL</span></a> collapsed?</p><p>- A month after <a href="https://mastodon.habets.dev/tags/Russia" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Russia</span></a> invaded the <a href="https://mastodon.habets.dev/tags/Ukraine" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Ukraine</span></a>.<br>- KPN stops their 3G network<br>- IPv6TeamOverheidNL stopped<br>- Staat van het Internet 2022</p><p>Source: <a href="https://www.vyncke.org/ipv6status/compare.php?metric=p&amp;countries=nl,de,be" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">vyncke.org/ipv6status/compare.</span><span class="invisible">php?metric=p&amp;countries=nl,de,be</span></a></p>