<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 - nft: Syntax error with dnat as ct state"
href="https://bugzilla.netfilter.org/show_bug.cgi?id=1056">1056</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>nft: Syntax error with dnat as ct state
</td>
</tr>
<tr>
<th>Product</th>
<td>nftables
</td>
</tr>
<tr>
<th>Version</th>
<td>unspecified
</td>
</tr>
<tr>
<th>Hardware</th>
<td>All
</td>
</tr>
<tr>
<th>OS</th>
<td>All
</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>nft
</td>
</tr>
<tr>
<th>Assignee</th>
<td>pablo@netfilter.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>karol@babioch.de
</td>
</tr></table>
<p>
<div>
<pre>According to a disucssion in IRC dnat (and snat) should be valid states for the
connection tracking , so a rule like the following should actually work:
ct state dnat accept
Apparently this is already implemented. However, right now with nftables
version 0.5 this results in an error:
[root@kvm2 ~]# nft -f /etc/nftables.conf
/etc/nftables.conf:115:18-21: Error: syntax error, unexpected dnat
ct state dnat accept ^^^^
According to fw in the #netfilter IRC this is due to a parser ambiguity:
<aborrero> kbabioch: that seems like a bug, I see support for it in the current
source tree
<fw> aborrero: its because of parser ambiguity
These virtual states are also available in iptables and do work like expected.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are watching all bug changes.</li>
</ul>
</body>
</html>