From owner-freebsd-hackers  Mon Dec  2 11:42:11 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id LAA08151
          for hackers-outgoing; Mon, 2 Dec 1996 11:42:11 -0800 (PST)
Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA08146
          for <hackers@freebsd.org>; Mon, 2 Dec 1996 11:42:08 -0800 (PST)
Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id MAA29564; Mon, 2 Dec 1996 12:42:03 -0700 (MST)
Date: Mon, 2 Dec 1996 12:42:03 -0700 (MST)
Message-Id: <199612021942.MAA29564@rocky.mt.sri.com>
From: Nate Williams <nate@mt.sri.com>
To: Nate Williams <nate@mt.sri.com>
Cc: hackers@freebsd.org
Subject: Solved!  (Was Re: Routing questions)
In-Reply-To: <199612021645.JAA28732@rocky.mt.sri.com>
References: <199612021645.JAA28732@rocky.mt.sri.com>
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Nate Williams writes:
> Background:
> I've got a block of 32 IP addresses assigned to me (a chunk out of a
> class C), and everything has been working wonderfully thanks to advice
> from folks on hackers when I set this up.
> 
> Howevever, my boss now wants his own little dedicated network at home.
...

Based on feedback from Joe Greco and such, he suggested contacting my
ISP and having them assign us another block of addresses for out home
networks.  I didn't think it was a 'kosher' thing to ask for, but based
on his prodding I did and I'm now the proud owner of another 32 IP
addresses, which I'll break into 4 chunks and assign to each of the
employees for their home.

It's by *far* the easiest solution, and given that we're not using
anymore bandwidth than we were paying for already the ISP was more than
willing to give us more addresses.  It'll work out really well for us,
and saves on the nightmare of trying to hack around routes and such (and
I still don't have to learn about NAT).


Nate