From owner-freebsd-questions Wed Jan 25 08:59:02 1995 Return-Path: questions-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id IAA00578 for questions-outgoing; Wed, 25 Jan 1995 08:59:02 -0800 Received: from hutcs.cs.hut.fi (root@hutcs.cs.hut.fi [130.233.192.2]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id IAA00569 for ; Wed, 25 Jan 1995 08:58:49 -0800 Received: from shadows.cs.hut.fi by hutcs.cs.hut.fi with SMTP id AA22521 (5.65c8/HUTCS-S 1.4 for ); Wed, 25 Jan 1995 15:09:54 +0200 Received: by shadows.cs.hut.fi (5.0/SMI-SVR4) id AA11237; Wed, 25 Jan 1995 15:10:01 --200 Date: Wed, 25 Jan 1995 15:10:01 --200 From: hsu@cs.hut.fi (Heikki Suonsivu) Message-Id: <9501251310.AA11237@shadows.cs.hut.fi> To: freebsd-questions@freefall.cdrom.com Cc: ohtroute@niksula.hut.fi Subject: What interface to use for configurable routing priorities? Organization: Helsinki University of Technology, Otaniemi, Finland Content-Length: 734 Sender: questions-owner@FreeBSD.org Precedence: bulk We have got a project to design configureable priorities into routing code for BSD kernel. For configuration, we need an interface to kernel. What would be the recommended way to do this? procfs seems to be a good idea, other solutions are extending the current route interface or doing another but similar interface for this? We need various information passed to and from kernel, - priority of a network (source & destination), - priority of a protocol, - tuning the effect of various other parameters, like length of packets, - bandwidth limits (for interfaces or routes), - getting statistics. - Heikki Suonsivu, T{ysikuu 10 C 83/02210 Espoo/FINLAND, hsu@cs.hut.fi home +358-0-8031121 work -4513377 fax -4555276 riippu SN