From owner-freebsd-isp  Sat Mar 15 17:10:23 1997
Return-Path: <owner-isp>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id RAA16399
          for isp-outgoing; Sat, 15 Mar 1997 17:10:23 -0800 (PST)
Received: from panda.hilink.com.au (panda.hilink.com.au [203.2.144.5])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA16350;
          Sat, 15 Mar 1997 17:10:11 -0800 (PST)
Received: (from danny@localhost) by panda.hilink.com.au (8.8.5/8.7.3) id MAA23187; Sun, 16 Mar 1997 12:17:12 +1100 (EST)
Date: Sun, 16 Mar 1997 12:17:11 +1100 (EST)
From: "Daniel O'Callaghan" <danny@panda.hilink.com.au>
To: Cliff Addy <fbsdlist@revelstone.jvm.com>
cc: freebsd-questions@FreeBSD.ORG, freebsd-isp@FreeBSD.ORG
Subject: Re: Multiple Class Cs on one network
In-Reply-To: <Pine.BSF.3.91.970315125527.1098B-100000@revelstone.jvm.com>
Message-ID: <Pine.BSF.3.91.970316121042.17824j-100000@panda.hilink.com.au>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-isp@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk


I'm not sure if I understand how you have done what you have done so far, 
but my guess is that you have aliased your original class C onto your 
ethernet interface.  What I have done for my WWW servers is put an entire 
class C onto lo0 and route to the box as a gateway for the network.

e.g


203.29.224.16/28
-------------------------------.30
|      |       |       |
.17   .18     .20     .19
                       {lo0=203.8.13.*}

.17, .18, .20, .30 all have a route to 203.8.13.0 via 203.29.224.19

You can do this with a static route in FreeBSD via the command
"route add 203.8.13.0 203.29.224.19" or in the static routes section of
/etc/sysconfig.

Alternatively you can use gated if you want dynamic routing.

Cheers,

Danny