TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

IPv6-only Network based on Jool

82 点作者 unclet5 个月前

13 条评论

throw0101a5 个月前
The UK IPv6 Council has a bunch of videos on running IPv6-mostly&#x2F;only networks:<p>* <a href="https:&#x2F;&#x2F;www.youtube.com&#x2F;@ukipv6council468&#x2F;videos" rel="nofollow">https:&#x2F;&#x2F;www.youtube.com&#x2F;@ukipv6council468&#x2F;videos</a><p>This includes at academic institutions where it&#x27;s basically all BYOD so they have to deal with a more &#x27;random&#x27; assortment of systems:<p>* <a href="https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=2B-liebzcOM" rel="nofollow">https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=2B-liebzcOM</a><p>And enterprise networks, like Jen Linkova at Google:<p>* <a href="https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=hb98hAb5_W8" rel="nofollow">https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=hb98hAb5_W8</a><p>Jen also had a presentation recently (2024-11) at RIPE87, &quot;Mission Possible: How Google Plans to Turn Off IPv4!&quot;, where they&#x27;ve managed to reclaim 300K IPv4 addresses:<p>* <a href="https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=UTRsi6mbAWM" rel="nofollow">https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=UTRsi6mbAWM</a><p>She&#x27;s currently co-chair of the IETF IPv6 Maintenance (6man) working group.
sgjohnson5 个月前
NAT64 covers most of the cases. However, in my homelab experiements I very quickly found out that IPv4 literal addresses are a bit problematic for me.<p>There are ways to fix that with 464XLAT&#x2F;CLAT, but I never got around to deploying it.<p>These days I&#x27;m just running dual-stack, with no NAT64. I hate NAT with a burning passion, so adding another layer of stateful NAT is a bit of a net negative in my eyes.<p>Someday I&#x27;ll go full IPv6 on my home network with 464XLAT. And then I&#x27;ll realize that some stupid IoT device or something is not CLAT aware. Obviously there are solutions around that too, but they require an intermediate device.
评论 #42610135 未加载
评论 #42611469 未加载
rendaw5 个月前
I used Jool! It worked great, but with some caveats.<p>My ISP does DS-lite which is some abomination where the shared (split by port) IPv4 address is calculated based on the IPv6 address? Using a fixed mapping table? Which is both very popular here and has zero linux support.<p>They had another option to do PPPoE IPv4 + SLAAC IPv6, but for this option they didn&#x27;t support DHCP prefix delegation. So I had to use this, and to work around that I needed to make my IPv6 network bridged.<p>The problem is Jool hooks into the linux routing table, and in the bridged network none of the outbound packets reach that table. So I had to 1. rewrite their RAs with my own DNS64 server and 2. mangle NAT64 packets to look as if they&#x27;re sent to the router directly so they hit the routing table (and get processed by Jool): <a href="https:&#x2F;&#x2F;github.com&#x2F;andrewbaxter&#x2F;portalino&#x2F;blob&#x2F;main&#x2F;source&#x2F;os&#x2F;ipv6_bridge_template_mangle_jool.nftables">https:&#x2F;&#x2F;github.com&#x2F;andrewbaxter&#x2F;portalino&#x2F;blob&#x2F;main&#x2F;source&#x2F;o...</a><p>Then I hit random MTU issues. MTU should be auto configured (and fixed when there&#x27;s issues) but I saw problems with Chrome&#x2F;Firefox refusing to load pages until I tried again at least 30s later until I forced the MTU lower.<p>So close, but still so far.
评论 #42625315 未加载
eqvinox5 个月前
It should be noted in-network DNS64 is a fallback for situations where end devices don&#x27;t have native support for NAT64 (either with a CLAT or with local DNS64). (Network side DNS64 breaks DNSsec)<p>RedHat is working to get CLAT on regular Linux hosts, where it has been direly missing.
评论 #42618997 未加载
fulafel5 个月前
It&#x27;s not immediately clear from the page but this is a NAT style hack for people who don&#x27;t have normal IPv6 connectivity, and NAT&#x27;ed connectivity is inferior to native.
评论 #42610938 未加载
ipython5 个月前
I have to admit, at first read I thought the headline was referring to the e-cig Juul and I was scratching my head wondering how one could build an ipv6 mesh network out of vapes.
evanjrowley5 个月前
I would love to do something like this except Verizon only provides IPv4 in my area. Some of the. Workarounds, like IPv6 tunnels, seem to have big drawbacks like being blocked by major providers.<p>I wish it were possible to force major operating systems to prefer IPv4 over IPv6, which might be a viable workaround to a less reliable IPv6 workaround, but such a configuration appears to be unfeasible for mobile phones, Windows, and perhaps MacOS too.
elnappo5 个月前
Would love to enable NAT64 on my OpenWRT router, sadly setting up Jool on OpenWRT feels to hacky to me. Based on option 2 described here: <a href="https:&#x2F;&#x2F;openwrt.org&#x2F;docs&#x2F;guide-user&#x2F;network&#x2F;ipv6&#x2F;nat64" rel="nofollow">https:&#x2F;&#x2F;openwrt.org&#x2F;docs&#x2F;guide-user&#x2F;network&#x2F;ipv6&#x2F;nat64</a>
gertrunde5 个月前
Not sure I entirely agree with :<p><i>&quot;Here is the classical topology of home network.&quot; ... &quot;And all the LAN hosts have one &#x2F;64 IPv6 prefix.&quot;</i><p>Are people really deploying IPv6 like this? Rather than a &#x2F;64 to a vlan?<p>(Personally, in the home, I&#x27;m just using DHCPv6-PD to delegate a different &#x2F;64 to each VLAN).
评论 #42609654 未加载
评论 #42609565 未加载
NewJazz5 个月前
Doesn&#x27;t openbsd do this without out of tree kernel modules? I&#x27;m kind of allergic to dkms and friends.
评论 #42608732 未加载
LorenDB5 个月前
I read Jool and expected something in Kerbal Space Program. For example, here&#x27;s some network setup around Jool: <a href="https:&#x2F;&#x2F;youtube.com&#x2F;watch?v=n2eBwgW6sig" rel="nofollow">https:&#x2F;&#x2F;youtube.com&#x2F;watch?v=n2eBwgW6sig</a>
throw0101d5 个月前
See also perhaps &quot;IPv6-mostly on OpenWRT&quot; from RIPE 87:<p>* <a href="https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=GZ6pxh6ukCg" rel="nofollow">https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=GZ6pxh6ukCg</a><p>* <a href="https:&#x2F;&#x2F;ripe87.ripe.net&#x2F;archives&#x2F;video&#x2F;1136&#x2F;" rel="nofollow">https:&#x2F;&#x2F;ripe87.ripe.net&#x2F;archives&#x2F;video&#x2F;1136&#x2F;</a><p>* <a href="https:&#x2F;&#x2F;ripe87.ripe.net&#x2F;wp-content&#x2F;uploads&#x2F;presentations&#x2F;8-IPv6-mostly_on_OpenWRT.pdf" rel="nofollow">https:&#x2F;&#x2F;ripe87.ripe.net&#x2F;wp-content&#x2F;uploads&#x2F;presentations&#x2F;8-I...</a><p>Ansible roles:<p>* <a href="https:&#x2F;&#x2F;github.com&#x2F;oskar456&#x2F;ansible-openwrt-ipv6-mostly">https:&#x2F;&#x2F;github.com&#x2F;oskar456&#x2F;ansible-openwrt-ipv6-mostly</a>
zorked5 个月前
Why do I need to even think about entering a contractual relationship with &quot;13 TCF vendor(s) and 64 ad partners&quot; before reading a blog post? The subject sounded interesting but the lack of respect for me is enormous.
评论 #42609108 未加载
评论 #42609164 未加载