From: "John A. Sullivan III" <john.sullivan@nexusmgmt.com>
To: Mail Lists <lists@sapience.com>
Cc: netfilter@lists.netfilter.org
Subject: Re: subnet problem
Date: Mon, 19 Jul 2004 06:52:55 -0400 [thread overview]
Message-ID: <1090234347.27794.13.camel@localhost> (raw)
In-Reply-To: <20040718221008.GB7576@sapience.com>
On Sun, 2004-07-18 at 18:10, Mail Lists wrote:
> Right - thanks for any insights - more details below.
>
> On Sun, Jul 18, 2004 at 10:02:20PM +0100, Antony Stone wrote:
> > On Sunday 18 July 2004 9:50 pm, Mail Lists wrote:
> >
> > > cRES_LDROP all -- 172.16.0.0/12 0.0.0.0/0
> > > which I would expect to block 172.16 to 172.31.
> > > ... blocked on 172.139.140.122
> > > ...
> > Please post your ruleset so we can see everything relating to cRES_LDROP.
> >
>
> Hi:
>
> More details - firewall generated by a script - this is the
> what the script actually runs ... I've removed some (hopefully)
> not relevant bits and heres the remainder of script output.
>
> If its easier I'm happy to post the script itself.
>
> #Starting iptables firewall ...
> # Initializing Iptables Firewall ...
> # ** Entering Test mode - nothing is actually run now
>
> iptables -F
> iptables -F -t nat
> iptables -F -t mangle
> iptables -X # Remove any existing user-defined chains.
> iptables -P INPUT DROP
> iptables -P OUTPUT DROP
> iptables -P FORWARD DROP
>
>
> # User defined Chains ...
> # [ ... delete non-relevant stuff ]
>
> iptables --new cRES_LDROP
> iptables -F cRES_LDROP
> iptables -A cRES_LDROP -j LOG --log-level info --log-prefix [FW Drop-Res]
> iptables -A cRES_LDROP -j DROP
<snip>
You are appending a logging rule and then appending a drop rule so the
order of processing would be log and then drop - John
--
John A. Sullivan III
Chief Technology Officer
Nexus Management
+1 207-985-7880
john.sullivan@nexusmgmt.com
---
If you are interested in helping to develop a GPL enterprise class
VPN/Firewall/Security device management console, please visit
http://iscs.sourceforge.net
next prev parent reply other threads:[~2004-07-19 10:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-18 20:50 subnet problem Mail Lists
2004-07-18 21:02 ` Antony Stone
2004-07-18 22:10 ` Mail Lists
2004-07-19 9:12 ` Antony Stone
2004-07-20 3:15 ` Mail Lists
2004-07-21 23:46 ` Mail Lists
2004-07-19 10:52 ` John A. Sullivan III [this message]
2004-07-20 3:17 ` Mail Lists
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=1090234347.27794.13.camel@localhost \
--to=john.sullivan@nexusmgmt.com \
--cc=lists@sapience.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 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.