From: Ramin Dousti <ramin@cannon.eng.us.uu.net>
To: Pascal Italiaander <pc-secure@home.nl>
Cc: netfilter@lists.netfilter.org
Subject: Re: Ip handling
Date: Thu, 19 Jun 2003 09:30:45 -0400 [thread overview]
Message-ID: <20030619133045.GA7161@cannon.eng.us.uu.net> (raw)
In-Reply-To: <200306191008.54741.pc-secure@home.nl>
On Thu, Jun 19, 2003 at 10:08:54AM +0200, Pascal Italiaander wrote:
> Op donderdag 19 juni 2003 06:02, schreef Ramin Dousti:
> > On Thu, Jun 19, 2003 at 02:01:21AM +0200, Pascal Italiaander wrote:
> > > small errors were in it, fixed:
> > >
> > > iptables -I INPUT -p all -m mac --mac-source 10:20:30:40:05:06 -m \
> > > state --state NEW -j ACCEPT
> > > iptables -I OUTPUT -p all -m state --state ESTABLISHED,RELATED -j ACCEPT
> >
> > Just a performance note. Since a high percentage of the packets are
> > ESTABLISHED,RELATED it is recommended to have this rule at the
> > beginning of the rule set prior to any other rule and also "-p all"
> > is redundant...
> >
> > Ramin
> >
> > > Pascal
>
>
> huhum.... , did you notice the -I insert rule ?
>
> The -I rule means that the rule is placed at the beginning of the chain. :-)
Yes, sorry. I'm used to -A... which gives you a chronological order of
the rule setup. With -I you have to read the rules in the reverse order ;-)
Ramin
>
> Pascal
>
>
>
next prev parent reply other threads:[~2003-06-19 13:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-18 17:37 Ip handling Daniel Chemko
2003-06-18 23:51 ` Pascal Italiaander
2003-06-19 0:01 ` Pascal Italiaander
2003-06-19 4:02 ` Ramin Dousti
2003-06-19 8:08 ` Pascal Italiaander
2003-06-19 13:30 ` Ramin Dousti [this message]
2003-06-19 3:31 ` Ramin Dousti
2003-06-19 8:00 ` Pascal Italiaander
2003-06-19 13:32 ` Ramin Dousti
2003-06-19 8:18 ` Pascal Italiaander
2003-06-19 13:02 ` Julian Gomez
2003-06-19 13:59 ` Ramin Dousti
2003-06-19 17:16 ` Pascal Italiaander
2003-06-19 23:06 ` Arnt Karlsen
-- strict thread matches above, loose matches on Subject: below --
2003-06-18 17:09 Paul Albert
2003-06-18 16:53 mick
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=20030619133045.GA7161@cannon.eng.us.uu.net \
--to=ramin@cannon.eng.us.uu.net \
--cc=netfilter@lists.netfilter.org \
--cc=pc-secure@home.nl \
/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