<html>
<head>
<base href="https://bugzilla.netfilter.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - nft does not handle IPv6 addresses with embedded IPv4 addresses"
href="https://bugzilla.netfilter.org/show_bug.cgi?id=1730#c2">Comment # 2</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - nft does not handle IPv6 addresses with embedded IPv4 addresses"
href="https://bugzilla.netfilter.org/show_bug.cgi?id=1730">bug 1730</a>
from <span class="vcard"><a class="email" href="mailto:antonio.ojea.garcia@gmail.com" title="Antonio Ojea <antonio.ojea.garcia@gmail.com>"> <span class="fn">Antonio Ojea</span></a>
</span></b>
<pre>::ffff:10.0.0.1 is a IPv4-Mapped IPv6 Address
<a href="https://datatracker.ietf.org/doc/html/rfc4291#section-2.5.5.2">https://datatracker.ietf.org/doc/html/rfc4291#section-2.5.5.2</a>
That is well defined, try with fd00::10.0.0.1/128
It seems that Section 5 in rfc5952 leaves the representation using mixed
notation open so theoretically it should be possible
<a href="https://datatracker.ietf.org/doc/html/rfc5952#section-5">https://datatracker.ietf.org/doc/html/rfc5952#section-5</a>
This is an edge case, but for compatibility reasons, I think that all the
representations that work with iptables user space tools should be allowed to
work with the nftables one, so migration and portability is simpler for end
users and consumers</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are watching all bug changes.</li>
</ul>
</body>
</html>