From owner-freebsd-current Thu Oct 15 11:08:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA02106 for freebsd-current-outgoing; Thu, 15 Oct 1998 11:08:41 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA02059 for ; Thu, 15 Oct 1998 11:08:32 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from woof.lan.awfulhak.org (brian@woof.lan.awfulhak.org [172.16.0.7]) by awfulhak.org (8.8.8/8.8.8) with ESMTP id TAA03739; Thu, 15 Oct 1998 19:08:00 +0100 (BST) (envelope-from brian@Awfulhak.org) Received: from woof.lan.awfulhak.org (brian@localhost [127.0.0.1]) by woof.lan.awfulhak.org (8.9.1/8.9.1) with ESMTP id LAA00689; Thu, 15 Oct 1998 11:30:32 +0100 (BST) (envelope-from brian@woof.lan.awfulhak.org) Message-Id: <199810151030.LAA00689@woof.lan.awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: Terry Lambert cc: brian@Awfulhak.org (Brian Somers), mike@smith.net.au, rkw@Dataplex.NET, fjaccard@urbanet.ch, current@FreeBSD.ORG Subject: Re: [GIMPS] /proc/net/route needed In-reply-to: Your message of "Thu, 15 Oct 1998 01:33:18 -0000." <199810150133.SAA14949@usr04.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 15 Oct 1998 11:30:32 +0100 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > And doesn't work as dial-on-demand apps will have created the > > necessary routing entries and UPd the interface already. > > This is absolutely the wrong level at which this should be implemented. You're assuming a one-to-one mapping from interface to transport. As things currently stand, ppp decides when which transports are used based on the contents of ppp.conf. There's no way any other program can ask it ``what would happen if I gave you this packet'', as the decision is partially based on the current packet load. To implement things as a firewall management daemon, the daemon would need to be smart enough to not only start ppp, but to instruct it on which link[s] to use as a transport. The daemon would also need to have the facility to be told when a transport is no longer available, and it would have to interrogate ppp as to how much traffic has been sent down a given link. Any program can configure a tun interface and multiplex the data in whatever way it chooses. The best that could be done to control this would be to have a central ``transport policy'' file and some API for reading/writing how many packets have been sent over which transports. So, for the moment, I suspect things will remain the same; the public interface layer will be brought up despite the lower layers not yet being available. When something arrives at the higher layer, the dialup is performed. [.....] > Terry Lambert > terry@lambert.org > --- > Any opinions in this posting are my own and not those of my present > or previous employers. > -- Brian , , Don't _EVER_ lose your sense of humour.... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message