From: Ramin Dousti <ramin@cannon.eng.us.uu.net>
To: Juliano Murlick <jmurlick@sicredi.com.br>
Cc: netfilter@lists.netfilter.org
Subject: Re: Please ... how can i log all packets dropped ?
Date: Sat, 19 Jul 2003 18:05:31 -0400 [thread overview]
Message-ID: <20030719220531.GA3868@cannon.eng.us.uu.net> (raw)
In-Reply-To: <!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAArnhC4pMfykCnPZlPMhHrI8KAAAAQAAAAyh7iEzTuckqggWRQr9qR0AEAAAAA@sicredi.com.br>
On Sat, Jul 19, 2003 at 02:38:01PM -0300, Juliano Murlick wrote:
> Hello ALL,
> I need log all packet dropped on my firewall, how can i get it ? I know how
> log all that i accept, like this:
If I understand your question correctly:
If you want to log the dropped packets only then you must allow the ones
you want in the beginning of your rule set and the very last rule (right
before the default DROP policy) must be LOG.
Ramin
>
> iptables -A FORWARD -p tcp -s $REDELOCAL --sport 1024:65535 -d $SSHSRV
> --sport 22 -j LOG
> iptables -A FORWARD -p tcp -s $REDELOCAL --sport 1024:65535 -d $SSHSRV
> --sport 22 -j ACCEPT
>
> i will LOG all packet from ssh connection, but i don't to log all packet
> dropped, my default policy is DROP:
>
> iptables -P FORWARD DROP
>
> please, if anyone knows it ? tell me ....
>
>
> Thanks in advance!
>
> Att,
> Juliano Murlick
>
>
>
>
> ---
> Outgoing mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.500 / Virus Database: 298 - Release Date: 10/7/2003
>
next prev parent reply other threads:[~2003-07-19 22:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-19 17:38 Please ... how can i log all packets dropped ? Juliano Murlick
2003-07-19 19:49 ` David Busby
2003-07-19 21:01 ` Juliano Murlick
2003-07-19 22:05 ` Ramin Dousti [this message]
2003-07-21 12:44 ` Juliano Murlick
2003-07-21 14:29 ` Ramin Dousti
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=20030719220531.GA3868@cannon.eng.us.uu.net \
--to=ramin@cannon.eng.us.uu.net \
--cc=jmurlick@sicredi.com.br \
--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.