From: Miernik <miernik@ctnet.pl>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] how to log pacets which hit routing rules?
Date: Thu, 29 Aug 2002 22:04:14 +0000 [thread overview]
Message-ID: <marc-lartc-103071431313834@msgid-missing> (raw)
In-Reply-To: <marc-lartc-103028073323267@msgid-missing>
On Thu, 29 Aug 2002, Wojtek wrote:
> > Is there some way to make iproute2 log to syslog or to a file selected
> > packets?
> >
> > I have a problem, that my packets dissapear somewhere, and I want to be
> > sure if they get to the routing stage or not, and where do they get
> > routed.
>
> use the iptables or ipchains with --log switch
I know that, but I did not mean that.
I want to log packets _at_the_roting_stage_, not at the filtering or NAT
stage.
--
Miernik _____________________________________
/ /
tel.: +48603070983 / / mailto:miernik@ctnet.pl
__________________/___/ ICQ UIN: 4004001
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2002-08-29 22:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-25 13:04 [LARTC] how to log pacets which hit routing rules? Jan Macek
2002-08-29 13:17 ` Wojtek
2002-08-29 20:39 ` James Sneeringer
2002-08-29 22:04 ` Miernik [this message]
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=marc-lartc-103071431313834@msgid-missing \
--to=miernik@ctnet.pl \
--cc=lartc@vger.kernel.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.