From: "Jason Opperisano" <Jopperisano@alphanumeric.com>
To: netfilter@lists.netfilter.org
Subject: RE: Odd question with source based blocking
Date: Fri, 27 Aug 2004 14:12:46 -0400 [thread overview]
Message-ID: <D5C9032B2B09C64EA2409D6214E91AC90512F4@asimail2.alphanumeric.com> (raw)
> Hope this provides a bit more Info
>
> On Thu, Aug 26, 2004 at 06:49:07PM -0400, Jason Opperisano wrote:
> >
> > you cannot set the "policy" of a custom chain, policies only apply to the built-in chains; i.e., iptables -P FORWARD DROP...etc...so i'm not sure what you mean by this.
>
> That would have been ideal, but I didn't think it was possible either.
>
> > if a packets jumps to a custom chain, and reaches the end of it--it returnsto the calling chain where it left off. in the above example--a packet with a destination ip of 192.168.1.1 and a src ip of 1.2.3.4 would match the second rule; traverse the BLOCKED chain, and if no rule matches return to the FORWARD chain at the next rule.
>
> I don't suspect there is anyway to change this, is there?
yeah--make the last rule of the chain BLOCKED a DROP rule:
iptables -A BLOCKED -j DROP
-j
next reply other threads:[~2004-08-27 18:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-27 18:12 Jason Opperisano [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-08-26 22:49 Odd question with source based blocking Jason Opperisano
2004-08-27 18:09 ` Michael Sconzo
2004-08-26 21:26 Change of ip addresses continues.... :( Jason Opperisano
2004-08-26 21:33 ` Eric Leblond
2004-08-26 21:57 ` Odd question with source based blocking Michael Sconzo
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=D5C9032B2B09C64EA2409D6214E91AC90512F4@asimail2.alphanumeric.com \
--to=jopperisano@alphanumeric.com \
--cc=netfilter@lists.netfilter.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