From: Michael Sconzo <msconzo@net.tamu.edu>
To: Jason Opperisano <Jopperisano@alphanumeric.com>
Cc: netfilter@lists.netfilter.org
Subject: Re: Odd question with source based blocking
Date: Fri, 27 Aug 2004 13:09:37 -0500 [thread overview]
Message-ID: <20040827130936.K1111@net.tamu.edu> (raw)
In-Reply-To: <D5C9032B2B09C64EA2409D6214E91AC906420A@asimail2.alphanumeric.com>; from Jopperisano@alphanumeric.com on Thu, Aug 26, 2004 at 06:49:07PM -0400
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 returns to 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?
>
> without seeing the output of:
>
> iptables -vnL && iptables -t nat -vnL && iptables -t mangle -vnL
Chain INPUT (policy ACCEPT 27895 packets, 3015K bytes)
pkts bytes target prot opt in out source destination
Chain FORWARD (policy DROP 0 packets, 0 bytes)
pkts bytes target prot opt in out source destination
0 0 ACCEPT udp -- * * 0.0.0.0/0 0.0.0.0/0 multiport ports 67,68
0 0 ACCEPT udp -- * * 0.0.0.0/0 0.0.0.0/0 multiport ports 53
0 0 ACCEPT tcp -- * * 0.0.0.0/0 0.0.0.0/0 multiport ports 53
0 0 BLOCKED all -- * * 0.0.0.0/0 192.168.0.0/16
0 0 BLOCKED all -- * * 192.168.0.0/16 0.0.0.0/0
Chain OUTPUT (policy ACCEPT 27999 packets, 31M bytes)
pkts bytes target prot opt in out source destination
Chain BLOCKED (4 references)
pkts bytes target prot opt in out source destination
Chain PREROUTING (policy ACCEPT 512K packets, 702M bytes)
pkts bytes target prot opt in out source destination
Chain POSTROUTING (policy ACCEPT 1 packets, 74 bytes)
pkts bytes target prot opt in out source destination
Chain OUTPUT (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source destination
Nothing in the Mangle table, and the nat table only has enteries in it
when the blocked table does
--
_
_ Michael J. Sconzo
_ Computing & Information Services, Texas A&M University
The New Testament offers the basis for modern computer coding theory,
in the form of an affirmation of the binary number system.
But let your communication be Yea, yea; nay, nay: for
whatsoever is more than these cometh of evil.
-- Matthew 5:37
next prev parent reply other threads:[~2004-08-27 18:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-26 22:49 Odd question with source based blocking Jason Opperisano
2004-08-27 18:09 ` Michael Sconzo [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-08-27 18:12 Jason Opperisano
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=20040827130936.K1111@net.tamu.edu \
--to=msconzo@net.tamu.edu \
--cc=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