<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>I believe NAT66 should not be stimulated in any sense.<br>
One of the greatest things of IPv6 is to restore end to end
communication.</p>
<p>PDs should only change when there is a re-connection and the CPE
should be able able to handle that correctly updating its LAN
prefixes accordingly.<br>
Stimulating and making that easy for general usage is like a crime
against IPv6. If one really needs to use that "chewing gun" he
must know what he is doing and to manually for that exception
case.</p>
<p>Regards<br>
Fernando<br>
</p>
<div class="moz-cite-prefix">On 04/05/2020 17:52, Joel Wirāmu
Pauling wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAKiAkGQg-Hiqw6isSmJYyLRWrTOpE0BZm4m+DPJPXBcNbiZCJw@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div class="gmail_default"
style="font-family:verdana,sans-serif">I am all for exposing
Cone Nat in UCI / Firewall zones as an option to the
masquerading configuration in a zone.</div>
<div class="gmail_default"
style="font-family:verdana,sans-serif"><br>
</div>
<div class="gmail_default"
style="font-family:verdana,sans-serif">Also as much as I hate
it nat66 for IPv6 needs to be exposed in the same place -
specifically for mapping routable PD which change often to
ULA's. <br>
</div>
<div class="gmail_default"
style="font-family:verdana,sans-serif"><br>
</div>
<div class="gmail_default"
style="font-family:verdana,sans-serif">-Joel<br>
</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Tue, 5 May 2020 at 07:25,
Gracias Amigou <<a href="mailto:puchapapa01@gmail.com"
moz-do-not-send="true">puchapapa01@gmail.com</a>> wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div dir="ltr">Please add this package as official:<br>
<div><br>
</div>
<div><b>Posts:</b></div>
<div>
<ol>
<li><a
href="https://forum.openwrt.org/t/xt-fullconenat-implementing-rfc-3489-full-cone-snat-in-openwrt/14816"
target="_blank" moz-do-not-send="true">xt_FULLCONENAT
-- Implementing RFC 3489 full cone SNAT in OpenWrt</a></li>
<li><a
href="https://www.right.com.cn/forum/thread-319827-1-1.html"
target="_blank" moz-do-not-send="true">[12/8更新]OpenWrt
上实现 NAT1 (Full cone NAT) 的方法，无需 DMZ/UPnP - OPENWRT专版</a></li>
<li><a
href="https://blog.chionlab.moe/2018/02/09/full-cone-nat-with-linux/"
target="_blank" moz-do-not-send="true">从DNAT到netfilter内核子系统，浅谈Linux的Full
Cone NAT实现 | ChionLab</a></li>
</ol>
</div>
<div><b><br>
</b></div>
<div><b>Git:</b><br>
</div>
<div>• <a
href="https://github.com/LGA1150/openwrt-fullconenat"
target="_blank" moz-do-not-send="true">GitHub -
LGA1150/openwrt-fullconenat: Netfilter and iptables
extension for full cone NAT ported to OpenWrt.</a><br>
</div>
</div>
_______________________________________________<br>
openwrt-devel mailing list<br>
<a href="mailto:openwrt-devel@lists.openwrt.org"
target="_blank" moz-do-not-send="true">openwrt-devel@lists.openwrt.org</a><br>
<a
href="https://lists.openwrt.org/mailman/listinfo/openwrt-devel"
rel="noreferrer" target="_blank" moz-do-not-send="true">https://lists.openwrt.org/mailman/listinfo/openwrt-devel</a><br>
</blockquote>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
openwrt-devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:openwrt-devel@lists.openwrt.org">openwrt-devel@lists.openwrt.org</a>
<a class="moz-txt-link-freetext" href="https://lists.openwrt.org/mailman/listinfo/openwrt-devel">https://lists.openwrt.org/mailman/listinfo/openwrt-devel</a>
</pre>
</blockquote>
</body>
</html>