All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sylvan <sylvan@nids.com.nf>
To: Mail List - Netfilter <netfilter@vger.kernel.org>
Subject: [Fwd: Re: Another way of doing? --state NEW -j DROP]
Date: Mon, 03 Nov 2008 14:48:27 +1130	[thread overview]
Message-ID: <1225682307.2479.46.camel@sylv> (raw)


Thanks for your response Max.

I'm afraid it doesn't support rules using '--state ESTABLISHED,RELATED'
either. Apart from that it's a great router and does pretty much
everything else. Any other ideas/theory's ?

Thanks for your time.
Sylvan


Anno domini 2008 Sylvan scripsit:

Hi!

>  I am sure this might be an easy answer for someone. Could you please
> enlighten me ?

Let's see. :)

> I am using the rule below to drop any inbound connections into my .0.3
> Class which by default allows any Outbound connections. Plus if the
> connection is already established than those outside connections are ok
> as well.

> iptables -A INPUT -d 192.168.3.0/24 -m state --state NEW -j DROP

> However I am now using a router that doesn't support the -m state
> --state NEW rule.(crappy GUI thing) :-( Could someone please tell me another way using
> iptables to drop any new inbound connections but allow everything else
> outbound and the established connection replys to get back into the .0.3
> Class ? What is the most secure/easiest way ?

So you have to input all your rules via a GUI which does not acceppt
'--state NEW' right?
Asuming yes and the you catched all '--state ESTABLISHED,RELATED'
packet which are/could be answer packets to outbound connections, how
about just leaving '--state NEW' out and DROP'ing all packets
remaining? Obviously after all rules which should accept things.

Nearby:
 DROP'ing unwanted packets IMO is rather bad behavior as it makes
 debugging (possible) network problems a lot harder. If you just
 REJECT packets you don't want (with a appropriate limit) everybody
 knows he is not welcome. So IMO it would be nicer to use
 '-j REJECT --reject-with icmp-admin-prohibited'.

HTH
Ciao
Max


             reply	other threads:[~2008-11-03  3:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-03  3:18 Sylvan [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-11-03  3:31 [Fwd: Re: Another way of doing? --state NEW -j DROP] Sylvan

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=1225682307.2479.46.camel@sylv \
    --to=sylvan@nids.com.nf \
    --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.