Re: Packet Marks with UDP and portforwarding

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: Re: Packet Marks with UDP and portforwarding
From: Philip Schaten <philip@xxxxxxxxxxxxxx>
Date: Sun, 25 Aug 2019 19:02:21 +0200
Cc: netfilter@xxxxxxxxxxxxxxx
In-reply-to: <20190825161555.GQ20113@breakpoint.cc>
References: <dea840fa-f8d9-6cd0-1dce-62ce4f3988ac@noerdcampus.de> <20190825124318.GO20113@breakpoint.cc> <801c0e32-c210-79d3-5298-22381507805f@noerdcampus.de> <20190825161555.GQ20113@breakpoint.cc>

Hi,
nft version is 9.0.
On a closer look I see it's a different error. Sorry for the confusion.
# nft add rule inet filter forward ct state dnat accept
Error: Could not parse conntrack state
add rule inet filter forward ct state dnat accept
                                      ^^^^

Follow-Ups:
- Re: Packet Marks with UDP and portforwarding
  - From: Florian Westphal

References:
- Packet Marks with UDP and portforwarding
  - From: Philip Schaten
- Re: Packet Marks with UDP and portforwarding
  - From: Florian Westphal
- Re: Packet Marks with UDP and portforwarding
  - From: Philip Schaten
- Re: Packet Marks with UDP and portforwarding
  - From: Florian Westphal

Prev by Date: Re: Packet Marks with UDP and portforwarding
Next by Date: Re: Packet Marks with UDP and portforwarding
Previous by thread: Re: Packet Marks with UDP and portforwarding
Next by thread: Re: Packet Marks with UDP and portforwarding
Index(es):
- Date
- Thread

[Index of Archives] [Linux Netfilter Development] [Linux Kernel Networking Development] [Netem] [Berkeley Packet Filter] [Linux Kernel Development] [Advanced Routing & Traffice Control] [Bugtraq]

Powered by Linux