<html>
<head>
<base href="https://bugzilla.netfilter.org/" />
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW - issue with -f fragment option"
href="https://bugzilla.netfilter.org/show_bug.cgi?id=1292">1292</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>issue with -f fragment option
</td>
</tr>
<tr>
<th>Product</th>
<td>nftables
</td>
</tr>
<tr>
<th>Version</th>
<td>unspecified
</td>
</tr>
<tr>
<th>Hardware</th>
<td>x86_64
</td>
</tr>
<tr>
<th>OS</th>
<td>Debian GNU/Linux
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Severity</th>
<td>normal
</td>
</tr>
<tr>
<th>Priority</th>
<td>P5
</td>
</tr>
<tr>
<th>Component</th>
<td>iptables over nftable
</td>
</tr>
<tr>
<th>Assignee</th>
<td>pablo@netfilter.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>arturo@debian.org
</td>
</tr></table>
<p>
<div>
<pre>From Debian BTS: <a href="https://bugs.debian.org/913088">https://bugs.debian.org/913088</a>
There seems to be some issues with the '-f' option in iptables-nft.
Apparently is not only in the printing code path but probably also in expr
generation code. See original bug report in debian for more tests and details.
==== 8< ====
Note the output of iptables-translate:
iptables-translate -A INPUT -f -j DROP
nft add rule ip filter INPUT ip frag-off & 0x1fff != 0 counter drop
However, if I execute this command:
iptables -A INPUT -f -j DROP
The following is added (output of 'nft list table filter'):
table ip filter {
chain INPUT {
...
ip frag-off & 65311 != 0 counter packets 0 bytes 0 drop
}
...
}
Note: 65311 (dec) = 0xff1f and not 0x1ffff. Could it be that the byte
order for the mask is somehow swapped?
==== 8< ====</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are watching all bug changes.</li>
</ul>
</body>
</html>