lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:	Wed, 03 Jun 2009 09:18:55 +0200
From:	Patrick McHardy <kaber@...sh.net>
To:	Chris Friesen <cfriesen@...tel.com>
CC:	netdev@...r.kernel.org
Subject: Re: relationship between ingress policer and netfilter hooks?

Chris Friesen wrote:
> Patrick McHardy wrote:
>> Chris Friesen wrote:
>>
>>> Hi all,
>>>
>>> Can someone tell me where the hook is for incoming packets to be sent
>>> through the ingress policer?
>>>
>>> In particular, I'm trying to find out how the ingress traffic shaping
>>> hook relates to the various netfilter hooks so that I can set them up to
>>> behave nicely together.
> 
>> They're not related at all. The ingress qdisc is hooked at
>> net/dev/core.c:handle_ing().
> 
> Thanks.  Based on that the shaping is done before any of the netfilter
> hooks, which is what I was trying to figure out.

Correct.

> On a related note...the deliver_skb() call right before the call to
> handle_ing()--is that to allow packet sockets to receive everything that
> arrives on the wire even if some of it may be dropped later?

Yes, its the final delivery for ptype_all handlers.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ