From owner-freebsd-current Fri Apr 24 13:46:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA25936 for freebsd-current-outgoing; Fri, 24 Apr 1998 13:46:26 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id NAA25922 for ; Fri, 24 Apr 1998 13:46:21 -0700 (PDT) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id VAA21907; Fri, 24 Apr 1998 21:08:52 +0200 From: Luigi Rizzo Message-Id: <199804241908.VAA21907@labinfo.iet.unipi.it> Subject: Re: Bandwidth throttling etc. To: julian@whistle.com (Julian Elischer) Date: Fri, 24 Apr 1998 21:08:52 +0200 (MET DST) Cc: kjc@csl.sony.co.jp, current@FreeBSD.ORG In-Reply-To: <3540D3AE.52BFA1D7@whistle.com> from "Julian Elischer" at Apr 24, 98 11:02:03 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Luigi Rizzo wrote: ... > I notice that teh mpath module released the other day what is this module and who released it ? > works for him so I guess it should work for us.. :-) it's not much that it works or not, it is being useful or not. > Also, on the topic of BPF for ip filter descriptions. ... > Having spent a while looking at it yesterday, I think that our > knowledge that the filter is working with an IP packet can be used > to produce a much more efficient filter than BPF. As a 'language', > ipfilter or ipfw would each be a better place to start. right... and in any case, for initial experiments probably ipfw can be enough. A simple optimization could be to split the inbound and outbound rules since this is tested on each rule. I have already added the flow_id field to the mbuf header and things seem to work (this is on a diskless machine so you bet the code is exercised). I am also working on extending the ipfw interface to add more actions. I have added one: ipfw add [number] pipe X ...filtering option... which passes traffic through a "pipe" module with given delay, bw and buffers. Another command will be necessary to configure a "pipe": ipfw pipe {add|get|configure|delete} bw XX delay YY buffers ZZ and this way you should be able to do class-based throttling. If everything goes well, the bandwidth limiting code (dummynet) should be working under ipfw control in a week or so. cheers luigi -----------------------------+-------------------------------------- Luigi Rizzo | Dip. di Ingegneria dell'Informazione email: luigi@iet.unipi.it | Universita' di Pisa tel: +39-50-568533 | via Diotisalvi 2, 56126 PISA (Italy) fax: +39-50-568522 | http://www.iet.unipi.it/~luigi/ _____________________________|______________________________________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message