From: "christophe barbé" <christophe.barbe.ml@online.fr>
To: netfilter@lists.samba.org
Subject: Re: simple rules and unexpected traffic
Date: Thu, 4 Jul 2002 19:47:09 -0400 [thread overview]
Message-ID: <20020704234709.GE909@localhost> (raw)
In-Reply-To: <200FAA488DE0D41194F10010B597610D2BA236@JUPITER>
[-- Attachment #1: Type: text/plain, Size: 2173 bytes --]
On Fri, Jul 05, 2002 at 09:44:36AM +1000, George Vieira wrote:
> Have you got any packet counts for the DROPped rules??
no.
> I'm still a bit stumped on the
>
> -A block -i ! eth0 -m state --state NEW -j ACCEPT
>
> as what other devices do you have???
I have only eth0 and lo.
Christophe
>
> thanks,
> George Vieira
> Systems Manager
> Citadel Computer Systems P/L
> http://www.citadelcomputer.com.au
>
>
>
> -----Original Message-----
> From: christophe barbé [mailto:christophe.barbe.ml@online.fr]
> Sent: Friday, 05 July 2002 8:57 AM
> To: netfilter@lists.samba.org
> Subject: Re: simple rules and unexpected traffic
>
>
> On Fri, Jul 05, 2002 at 12:54:36AM +0200, Jan Humme wrote:
> > On Friday 05 July 2002 00:45, christophe barbé wrote:
> > > On Fri, Jul 05, 2002 at 08:35:53AM +1000, George Vieira wrote:
> > > > Yes I've found that some user space programs can see stuff before
> > > > iptables.. tcpdump too I think...
> > >
> > > Yes it sounds logical for tcpdump or tools like that (which pass the
> > > interface in promiscuisious mode) to see everything. I was not expecting
> > > the same from a unprivileged app like gkrellm.
> > > It is stil unclear for me what is the data processing path.
> > >
> > > Has someone a clear picture of the packets path ?
> >
> > It is no problem to open a socket and receive a copy of all raw packets
> > before they get to the kernel iptables modules. See "man 7 packet" for
> > details.
> >
> > I believe this is how tcpdump does it too.
>
> Ok it sounds logical.
> Now the question is what is dropping these packets ? Apparently not
> rp_filter, and not netfilter because I see no log for it.
>
> Christophe
>
> >
> > Jan Humme.
>
> --
> Christophe Barbé <christophe.barbe@ufies.org>
> GnuPG FingerPrint: E0F6 FADF 2A5C F072 6AF8 F67A 8F45 2F1E D72C B41E
>
> Imagination is more important than knowledge.
> Albert Einstein, On Science
--
Christophe Barbé <christophe.barbe@ufies.org>
GnuPG FingerPrint: E0F6 FADF 2A5C F072 6AF8 F67A 8F45 2F1E D72C B41E
L'experience, c'est une connerie par jour mais jamais la même.
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2002-07-04 23:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-04 23:44 simple rules and unexpected traffic George Vieira
2002-07-04 23:47 ` christophe barbé [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-07-04 23:54 George Vieira
2002-07-05 0:34 ` christophe barbé
2002-07-04 22:35 George Vieira
2002-07-04 22:45 ` christophe barbé
2002-07-04 22:54 ` Jan Humme
2002-07-04 22:57 ` christophe barbé
2002-07-04 14:10 christophe barbé
2002-07-04 21:01 ` christophe barbé
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=20020704234709.GE909@localhost \
--to=christophe.barbe.ml@online.fr \
--cc=netfilter@lists.samba.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