All of lore.kernel.org
 help / color / mirror / Atom feed
From: "David Busby" <busby@pnts.com>
To: jmurlick@sicredi.com.br, netfilter@lists.netfilter.org
Subject: Re: Please ... how can i log all packets dropped ?
Date: Sat, 19 Jul 2003 12:49:39 -0700	[thread overview]
Message-ID: <007c01c34e2e$e42aacd0$1100000a@busbydev> (raw)
In-Reply-To: !~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAArnhC4pMfykCnPZlPMhHrI8KAAAAQAAAAyh7iEzTuckqggWRQr9qR0AEAAAAA@sicredi.com.br

At the end of the rules say -j LOG, any packet that makes it that far will
then be droped by the policy.




----- Original Message ----- 
From: "Juliano Murlick" <jmurlick@sicredi.com.br>
To: <netfilter@lists.netfilter.org>
Sent: Saturday, July 19, 2003 10:38
Subject: Please ... how can i log all packets dropped ?


> 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:
>
> 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
>
>
>



  reply	other threads:[~2003-07-19 19:49 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 [this message]
2003-07-19 21:01   ` Juliano Murlick
2003-07-19 22:05 ` Ramin Dousti
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='007c01c34e2e$e42aacd0$1100000a@busbydev' \
    --to=busby@pnts.com \
    --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.