From owner-freebsd-hackers Thu Jan 22 03:01:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA03614 for hackers-outgoing; Thu, 22 Jan 1998 03:01:18 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from abattoir.com (resort.bigbook.com [204.17.233.67]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA03605 for ; Thu, 22 Jan 1998 03:01:15 -0800 (PST) (envelope-from banshee@abattoir.com) Received: (from banshee@localhost) by abattoir.com (8.8.8/8.7.3) id DAA16635 for hackers@freebsd.org; Thu, 22 Jan 1998 03:01:15 -0800 (PST) Date: Thu, 22 Jan 1998 03:01:15 -0800 (PST) From: John M Vinopal Message-Id: <199801221101.DAA16635@abattoir.com> To: hackers@FreeBSD.ORG Subject: routing by protocol Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk I live in CA outside of someplace where I can obtain centrex ISDN. Therefore I must watch my metering minutes. As my telnet sessions are often longlived, they get passed over a permanent v.34 line; ISDN is used in the evenings and simply set as a default route for those hours and then dropped. What I'd like to do is redirect all outgoing requests to WWW servers to go out the isdn line. Ie: rdr 0.0.0.0:80 -> tun1. I've thought of a number of ways to do this; all are horrible hacks. * use ipfw to divert packets to :80, use custom hack (or nc) at the divert port to readdress and source route out. * hack my proxy server to source route. * have an external proxy server with a static route through the proper interface. * build a custom route for each www access through the proper interface. * dedicate a seperate machine as a proxy server internally with a default route out. It appears that my isp's disallow source routing however. Building routes one way or another appears the only viable method. Or is it? Have I missed something? -j