[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[altq 836] Re: The future of ALTQ, IPsec & IPFILTER playing together ...
- To: snap-users@kame.net
- Subject: [altq 836] Re: The future of ALTQ, IPsec & IPFILTER playing together ...
- From: Jason R Thorpe <thorpej@zembu.com>
- Date: Wed, 2 May 2001 17:26:47 -0700
- Cc: gunther@aurora.regenstrief.org, darrenr@reed.wattle.id.au, julian@elischer.org, freebsd-net@freebsd.org, ipfilter@coombs.anu.edu.au, altq@csl.sony.co.jp
- In-Reply-To: <200105030001.KAA24308@avalon.reed.wattle.id.au>; from darrenr@reed.wattle.id.au on Thu, May 03, 2001 at 10:01:18AM +1000
- Mail-Followup-To: Jason R Thorpe <thorpej@zembu.com>,snap-users@kame.net, gunther@aurora.regenstrief.org,darrenr@reed.wattle.id.au, julian@elischer.org,freebsd-net@freebsd.org, ipfilter@coombs.anu.edu.au,altq@csl.sony.co.jp
- Organization: Zembu Labs, Inc.
- References: <20010502162327.Z21020@dr-evil.shagadelic.org> <200105030001.KAA24308@avalon.reed.wattle.id.au>
- Reply-To: thorpej@zembu.com
- Sender: owner-altq@csl.sony.co.jp
- User-Agent: Mutt/1.2.5i
On Thu, May 03, 2001 at 10:01:18AM +1000, Darren Reed wrote:
> > BPF "expressions" are literally BPF bytecodes.
>
> Well, one of the goals of IPFilter is it can parse (as rules) a textual
> representation of what's currently loaded into the kernel. At the moment
> that means collecting hex output, as the bytecode instructions are less
> suited to being displayed all on the one line.
For BPF bytecodes, that's problematic -- the optimizer often turns what
you originally had into something almost totally non-decompilable :-)
--
-- Jason R. Thorpe <thorpej@zembu.com>