From owner-freebsd-isp Mon Sep 15 03:05:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id DAA18793 for isp-outgoing; Mon, 15 Sep 1997 03:05:07 -0700 (PDT) Received: from panda.hilink.com.au (panda.hilink.com.au [203.8.15.25]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id DAA18784 for ; Mon, 15 Sep 1997 03:05:01 -0700 (PDT) Received: (from danny@localhost) by panda.hilink.com.au (8.8.5/8.8.5) id UAA23960; Mon, 15 Sep 1997 20:04:48 +1000 (EST) Date: Mon, 15 Sep 1997 20:04:47 +1000 (EST) From: "Daniel O'Callaghan" To: Ernie Elu cc: freebsd-isp@FreeBSD.ORG Subject: Re: Different routes for each protocol In-Reply-To: <199709150836.SAA02016@spooky.eis.net.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, 15 Sep 1997, Ernie Elu wrote: > I am curious if it is at all possbile to route indiviual protocols via > different default routes or interfaces. Sure, but only if you control the sending routers. Since you don't control what Connect's and TIS's routers do, you need to find other ways. > For example say I have FreeBSD box and two different Internet providers > that I connected to one with a much faster link than the other eg. T1 and > a 64k ISDN each off their own router or interface. The slower link offers > a monthly flat rate ans the T1 charges per megabyte so I want to load up the T1? Don't you mean E1? > One idea I had was to give each protocol it's own IP address via an alias. > > eg. smtp.your.domain.com aaa.bbb.ccc.001 > pop.your.domain.com aaa.bbb.ccc.002 You are on the right track. Ask TIS for a new netblock, and put your slow services onto that set of network numbers. > But that only takes care of inbound traffic, outbound will still go via > the default route. What do you care if the outbound takes a different path? You don't pay for data sent to CCA or to Telstra. Danny