From: Robin Kuiper <kuiper.robin@gmail.com>
To: netfilter@vger.kernel.org
Subject: nftables drops related traffic
Date: Sat, 13 Jun 2020 23:21:48 +0200 [thread overview]
Message-ID: <4baae47f34b92314090a0cda3b7b50bb3f253b8d.camel@gmail.com> (raw)
Hi,
I'm running into an issue where nftables drops all related traffic,
even if it should accept it.
When using, for example, an [archwiki example nftables ruleset][1] it
contains the line `ct state established,related accept`. This is
supposed to accept related and established traffic.
Established works: otherwise, I wouldn't be able to browse the web!
Related however, doesn't appear to work.
My proof is my TFTP server: if you [look at the protocol][2], its a
simple example of related traffic. However, it only works when my
firewall is disabled. TCPdumping the server shows that my server sends
the data packet, but never receives an ACK. ([wiki example][2] image
R2/R3)
Any help would be greatly appreciated!
[1]: https://wiki.archlinux.org/index.php/Nftables#Workstation
[2]:
https://en.wikipedia.org/wiki/Trivial_File_Transfer_Protocol#Details
next reply other threads:[~2020-06-13 21:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-13 21:21 Robin Kuiper [this message]
2020-06-14 1:17 ` nftables drops related traffic kfm
2020-06-14 8:38 ` Robin Kuiper
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4baae47f34b92314090a0cda3b7b50bb3f253b8d.camel@gmail.com \
--to=kuiper.robin@gmail.com \
--cc=netfilter@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox