<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#c5">Comment # 5</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:pablo@netfilter.org" title="Pablo Neira Ayuso <pablo@netfilter.org>"> <span class="fn">Pablo Neira Ayuso</span></a>
</span></b>
<pre>(In reply to Eric Fahlgren from <a href="show_bug.cgi?id=1730#c3">comment #3</a>)
<span class="quote">> Yes, I duplicated your results, but was puzzled that the IPv4-mapped address
> was able to pass through the parser, which I would not expect if the same
> flex rule is used for all address tokens.</span >
Because it only supports for RFC-compliant IPv4-Mapped IPv6 addresses.
See:
commit fd513de78bc0133f6ba61087be168e2a8d067107
Author: Pablo Neira Ayuso <<a href="mailto:pablo@netfilter.org">pablo@netfilter.org</a>>
Date: Mon Oct 9 01:40:36 2017 +0200
scanner: IPv4-Mapped IPv6 addresses support</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are watching all bug changes.</li>
</ul>
</body>
</html>