From owner-freebsd-ipfw Sat Oct 12 10:16:38 2002 Delivered-To: freebsd-ipfw@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6A42937B401 for ; Sat, 12 Oct 2002 10:16:37 -0700 (PDT) Received: from carp.icir.org (carp.icir.org [192.150.187.71]) by mx1.FreeBSD.org (Postfix) with ESMTP id 17E7B43E97 for ; Sat, 12 Oct 2002 10:16:37 -0700 (PDT) (envelope-from rizzo@carp.icir.org) Received: from carp.icir.org (localhost [127.0.0.1]) by carp.icir.org (8.12.3/8.12.3) with ESMTP id g9CHGUpJ090299; Sat, 12 Oct 2002 10:16:30 -0700 (PDT) (envelope-from rizzo@carp.icir.org) Received: (from rizzo@localhost) by carp.icir.org (8.12.3/8.12.3/Submit) id g9CHGSUY090298; Sat, 12 Oct 2002 10:16:28 -0700 (PDT) (envelope-from rizzo) Date: Sat, 12 Oct 2002 10:16:28 -0700 From: Luigi Rizzo To: Andrey Degtyaryov Cc: freebsd-ipfw@FreeBSD.ORG Subject: Re: TOS matching in ipfw2 Message-ID: <20021012101628.A90230@carp.icir.org> References: <20021011142125.GH32697@astral-on.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20021011142125.GH32697@astral-on.net>; from ad@astral-on.net on Fri, Oct 11, 2002 at 05:21:26PM +0300 Sender: owner-freebsd-ipfw@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, Oct 11, 2002 at 05:21:26PM +0300, Andrey Degtyaryov wrote: > Hello! > Why iptos takes only the limited set of "spec" values in ipfw2? It would > be much more convenient, if "spec" could be any number. Why was it neccessary > to apply such restriction? i think i just copied whatever ipfw1 did. I believe there are no problems extending the tos to match any number (or ranges, for what matters). Many are asking me if i intend to implement ipfw2 actions which actually modify the packet being processed. The answer is yes, but i would like first to come up with a good syntax for those actions, e.g.: ipfw add 100 accept "ip.dst = 1.2.3.4, ip.tos=25" ip from a to b Of course one would want the syntax for packet modifications to be as general as possible, but i'd rather not need a full blown compiler to compile such actions... Suggestions welcome cheers luigi > In This way it would be possible to implement flexible traffic > shaping models according to the values of TOS. > I've implemented netgraph node which changes packets' TOS values > passed throw the interface (mark a traffic groups/clients) and ALTQ allocates > a bandwidtch in compliance with ones. I know about traffic conditioners and > use it on the routers which are running ALTQ. But i cannot / don't want install > ALTQ on all routers upon many reasons. > It would be much better to migrate from ALTQ to DUMMYNET (because of > higher accuracy of DUMMYNET)... > > -- > Andrew Degtiariov > AD5898-RIPE | AD5-UANIC > ad@astral-on.net > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-ipfw" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ipfw" in the body of the message