mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Hannes Frederic Sowa <hannes@stressinduktion.org>
To: Matteo Croce <matteo@openwrt.org>, Valdis.Kletnieks@vt.edu
Cc: Nicolas Dichtel <nicolas.dichtel@6wind.com>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] add stealth mode
Date: Tue, 07 Jul 2015 10:07:53 +0200	[thread overview]
Message-ID: <1436256473.3809610.317083993.4E2A41A3@webmail.messagingengine.com> (raw)
In-Reply-To: <CAFnufp3xP3xjd8zy0uLKEGgbBAb0motLva=f1EbMJCfcKG=Y-w@mail.gmail.com>



On Mon, Jul 6, 2015, at 21:44, Matteo Croce wrote:
> 2015-07-06 12:49 GMT+02:00  <Valdis.Kletnieks@vt.edu>:
> > On Thu, 02 Jul 2015 10:56:01 +0200, Matteo Croce said:
> >> 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.
> >
> > A few notes.....
> >
> > 1) Do you have an actual use case where an iptables '-j DROP' isn't usable?
> 
> If you mean using a default DROP policy and allowing only the traffic
> do you want,
> then the use case is where the port can change at runtime and you may not
> want
> to update the firewall every time

Can't you use socket match in netfilter to accomplish exactly that?

  parent reply	other threads:[~2015-07-07  8:08 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-02  8:56 Matteo Croce
2015-07-06 10:49 ` Valdis.Kletnieks
2015-07-06 19:44   ` Matteo Croce
2015-07-07  2:34     ` David Miller
2015-07-07  8:07     ` Hannes Frederic Sowa [this message]
2015-07-07 15:27       ` Matteo Croce
2015-07-08  8:02         ` Hannes Frederic Sowa
2015-07-08 13:32     ` Austin S Hemmelgarn
2015-07-12 23:13       ` Matteo Croce
2015-07-13 13:03         ` Austin S Hemmelgarn
2015-07-14 14:51           ` Matteo Croce
2015-07-07  7:01   ` Clemens Ladisch
2015-07-07 15:24     ` Matteo Croce

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=1436256473.3809610.317083993.4E2A41A3@webmail.messagingengine.com \
    --to=hannes@stressinduktion.org \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matteo@openwrt.org \
    --cc=netdev@vger.kernel.org \
    --cc=nicolas.dichtel@6wind.com \
    /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

all inboxes | Powered by JetHome®