From: Florian Westphal <fw@strlen.de>
To: mudrunka@spoje.net
Cc: netfilter-devel@vger.kernel.org
Subject: Re: Easy way to set NOTRACK for INPUT, FORWARD and OUTPUT independently
Date: Sat, 17 Dec 2016 13:29:22 +0100 [thread overview]
Message-ID: <20161217122922.GC13094@breakpoint.cc> (raw)
In-Reply-To: <c84a9319f8b1f2bb0554d5a4a942e3b1@spoje.net>
mudrunka@spoje.net <mudrunka@spoje.net> wrote:
> >It would be super useful if one can simply use "-j CT --notrack" in
> >INPUT and FORWARD. (it already works in OUTPUT)
> >
> >If it's impossible to postpone conntrack after routing decision, it
> >might be possible to add some macro that would match any of local
> >adresses that are currently on any of interfaces. like "--src local"
> >or "--dst local".
conntrack hook is in PREROUTING so by time INPUT/FORWARD hooks are
invokes conntrack already picked the packet up.
> >with all these adresses parsed from "ip a s". But that's far from
> >being elegant or reliable.
I suggest to use the addrtype match for this:
addrtype --dst-type LOCAL should do what you want.
> >I am planning to switch over to nftables, so it might be another
> >solution...
> >Is this planned to be fixed in nftables? If not can you please
> >consider fixing it?
The fib expression can be used in nft. ("fib daddr type local").
next prev parent reply other threads:[~2016-12-17 12:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-06 5:54 Easy way to set NOTRACK for INPUT, FORWARD and OUTPUT independently mudrunka
2016-12-06 5:56 ` mudrunka
2016-12-17 12:29 ` Florian Westphal [this message]
2016-12-17 14:27 ` mudrunka
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=20161217122922.GC13094@breakpoint.cc \
--to=fw@strlen.de \
--cc=mudrunka@spoje.net \
--cc=netfilter-devel@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;
as well as URLs for NNTP newsgroup(s).