All of lore.kernel.org
 help / color / mirror / Atom feed
From: "dais" <dais00@mails.tsinghua.edu.cn>
To: "'Joakim Axelsson'" <gozem@aaricia.hemmet.chalmers.se>,
	<netfilter-devel@lists.netfilter.org>
Subject: RE: hi,anyone know where ippool v2.0 goes.
Date: Thu, 3 Oct 2002 17:24:56 +0800	[thread overview]
Message-ID: <000a01c26abe$bd10a3b0$0f966fa6@dais> (raw)
In-Reply-To: <20021003074643.GD9998@aaricia.hemmet.chalmers.se>

got it.
thank you very much:-)

> -----Original Message-----
> From: netfilter-devel-admin@lists.netfilter.org 
> [mailto:netfilter-devel-admin@lists.netfilter.org] On Behalf 
> Of Joakim Axelsson
> Sent: Thursday, October 03, 2002 3:47 PM
> To: dais; netfilter-devel@lists.netfilter.org
> Subject: Re: hi,anyone know where ippool v2.0 goes.
> 
> 
> 2002-10-03 08:53:26+0200, Joakim Axelsson 
> <gozem@aaricia.hemmet.chalmers.se> ->
> > 2002-10-03 13:57:22+0800, dais <dais@ccert.edu.cn> ->
> > > hi,
> > > 
> > >     i searched the list and find somebody rewrite ippool
> > > and aimed to add hash mode that is very useful in my opinion.
> > > but i can't find anything more.If nobody continues,i'll consider 
> > > to do that.any advices?
> > >     thx
> > >     Pluto.Dai
> > > 
> > 
> > Code is almost finished. Havn't had time to put the last things 
> > togther though.
> > 
> 
> You can find the code so far at: 
> http://aaricia.hemmet.chalmers.se/~gozem/ippool/
> 
> Please 
> understand that this code is HIGHLY under development. 
> However this code seams stable, but not finished on all 
> parts. Its NOT a patch so you have to have good knowlage 
> about how to install additional files and get them to work 
> with Makefiles etc. in kernel. Please do not ask me how to 
> install it. If you don't know you shouldn't be using this code (yet).
> 
> Also, the API between ippool mainframe and the ippool 
> pool-types are subject to change. So don't put in too much 
> work into writing your own pool-types unless preperad to 
> convert them fiting a new API.
> 
> Unfinished parts:
> * ippool -R and -S (restore and save) is not yet implemented.
> * Will move the looks from mainfram to each pooltype to 
> handle instead.
> * Add a few more pooltype: hash, timehash, nettree, 
> portbitmap, accounting,
>   limitbitmaps.
> * Also convert it more to not only handle IP, but handle skbs instead,
>   meaning a pool can contain anything matching a skb. eg. ipv4, ipv6,
>   tcp-ports. This is almost finished.
> 
> A side note. This is ippool 0.3, the ippool in netfilter cvs 
> is 0.1. When stable it will go 1.0
> 
> Have fun! :-)
> 
> -- 
> /Joakim Axelsson A.K.A Gozem@EFnet
> 

      reply	other threads:[~2002-10-03  9:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-03  5:57 hi,anyone know where ippool v2.0 goes dais
2002-10-03  6:53 ` Joakim Axelsson
2002-10-03  7:46   ` Joakim Axelsson
2002-10-03  9:24     ` dais [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='000a01c26abe$bd10a3b0$0f966fa6@dais' \
    --to=dais00@mails.tsinghua.edu.cn \
    --cc=gozem@aaricia.hemmet.chalmers.se \
    --cc=netfilter-devel@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.