All of lore.kernel.org
 help / color / mirror / Atom feed
From: Florian Westphal <fw@strlen.de>
To: "Marek Greško" <mgresko8@gmail.com>
Cc: netfilter@vger.kernel.org
Subject: Re: nftables and connection tracking
Date: Sun, 21 Jun 2020 10:06:14 +0200	[thread overview]
Message-ID: <20200621080614.GK26990@breakpoint.cc> (raw)
In-Reply-To: <CAChjPdRd1xePA2fesrj8imCo9gfP_B5bko95MEGEwsAWVX6fjw@mail.gmail.com>

Marek Gre¨ko <mgresko8@gmail.com> wrote:
> I have problem to get connection tracking work when using nftables. I
> have this setup on my fedora 32:
> 
> table ip raw {
>         chain PREROUTING {
>                 type filter hook prerouting priority raw; policy accept;
>                 meta l4proto udp udp dport 5060 # CT helper sip
>         }
> 
>         chain OUTPUT {
>                 type filter hook output priority raw; policy accept;
>                 meta l4proto udp udp dport 5060 # CT helper sip
>         }

These rules don't do anything (it matches udp 5060, but no action is
given).  I suspect this from xtables-translate, which did not understand
the -j CT --helper sip rule.

This needs something like:
table ip raw {
   ct helper sip {
     type "sip" protocol udp
   }
   chain prerouting {
       meta l4proto udp udp dport 5060 ct helper set "sip"
   }

# same for output
}

  reply	other threads:[~2020-06-21  8:06 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-21  5:54 nftables and connection tracking Marek Greško
2020-06-21  8:06 ` Florian Westphal [this message]
     [not found]   ` <CAChjPdQtKBGuUvdveCVc5kmhA+fgP4DUDNKhNd11KUVCKNUZLg@mail.gmail.com>
     [not found]     ` <20200621090142.GL26990@breakpoint.cc>
2020-06-21  9:39       ` Marek Greško
2020-06-21 10:45         ` Florian Westphal
2020-06-21 11:33           ` Marek Greško
2020-07-01 20:01           ` Marek Greško
2020-07-01 22:48             ` Florian Westphal
2020-07-02 19:33               ` Marek Greško
2020-07-02 19:47                 ` Pablo Neira Ayuso
     [not found]                   ` <CAChjPdQb5wUP7Qbz=D-0jg-YFC0cWgV4oPJQD9-G7evi3SupAw@mail.gmail.com>
     [not found]                     ` <YUk8dCSHCUcKn+Xy@salvia>
     [not found]                       ` <CAChjPdREO=jtTNGc32H3mv+Zv8AHKbujb_a8=tkwC0+b2sbVCQ@mail.gmail.com>
2021-09-24  5:21                         ` Fwd: " Marek Greško
2021-09-24  7:19                           ` Daniel
2020-06-22 12:06 ` Pablo Neira Ayuso
2020-06-22 17:18   ` Marek Greško
2020-06-22 21:35     ` Marek Greško

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=20200621080614.GK26990@breakpoint.cc \
    --to=fw@strlen.de \
    --cc=mgresko8@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.