All of lore.kernel.org
 help / color / mirror / Atom feed
From: Florian Westphal <fw@strlen.de>
To: Matteo Croce <matteo@openwrt.org>
Cc: David Miller <davem@davemloft.net>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4] add stealth mode
Date: Wed, 16 Sep 2015 13:06:29 +0200	[thread overview]
Message-ID: <20150916110629.GP24810@breakpoint.cc> (raw)
In-Reply-To: <1442397259-28894-1-git-send-email-matteo@openwrt.org>

Matteo Croce <matteo@openwrt.org> wrote:
> Add option to disable any reply not related to a listening socket,
> like RST/ACK for TCP and ICMP Port-Unreachable for UDP.
> Also disables ICMP replies to echo request and timestamp.
> The stealth mode can be enabled selectively for a single interface.

I think it would make more sense to extend the socket match
in xtables if it can't be used to achive this already.

seems like
*filter
:INPUT ACCEPT [0:0]
-A INPUT -p tcp -m socket --nowildcard -j ACCEPT
-A INPUT -p tcp -j DROP
COMMIT

Already does what you want for tcp, udp should work too.
I'd much rather see xtables and/or nftables to be extended
with whatever feature(s) are needed to configure such a policy
rather than pushing this into the core network stack.

  parent reply	other threads:[~2015-09-16 11:06 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-02  8:47 [PATCH] [PATCH v3] add stealth mode Matteo Croce
2015-09-15 19:00 ` David Miller
2015-09-16  9:54   ` [PATCH v4] " Matteo Croce
2015-09-16 10:26     ` Daniel Borkmann
2015-09-16 10:45       ` Matteo Croce
2015-09-16 11:11         ` Daniel Borkmann
2015-09-16 11:06     ` Florian Westphal [this message]
2015-09-23 16:36       ` Matteo Croce
2015-09-23 17:29         ` Eric Dumazet
2015-09-23 18:16           ` David Miller
2015-09-23 18:15         ` David Miller
2015-09-16 11:11     ` Eric Dumazet
2015-09-23 16:32       ` Matteo Croce
2015-09-23 18:15         ` David Miller

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=20150916110629.GP24810@breakpoint.cc \
    --to=fw@strlen.de \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matteo@openwrt.org \
    --cc=netdev@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.