Date: Tue, 21 Jul 1998 14:16:25 -0700 (PDT) From: Doug White <dwhite@resnet.uoregon.edu> To: Eric Hake <eric@clean.net> Cc: questions@FreeBSD.ORG Subject: Re: NATd questions Message-ID: <Pine.BSF.4.00.9807211406180.8360-100000@resnet.uoregon.edu> In-Reply-To: <3.0.5.32.19980721001331.007c0ea0@clean.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 21 Jul 1998, Eric Hake wrote:
> I originally wanted to write privately so I wouldn't sound like an idiot in
> a public forum, but oh well :)
This is actually quite intelligent for the usual fare on this list. :-)
> Here's the deal -- I am wrestling with my upstream provider over an address
> plan I sent in -- it seems that they feel my request is too large -- I am
> wiring 90 offices now and up to 180 - 190 by the end of the year...
Yow! How big are these offices? How many addresses each?
> They want me to consider NAT, and had no idea that FreeBSD had natd
> capability -- I sent him the URL of the man page, and he said "hey! I
> didn't know the free BSD community had come so far!"...
Thanks for turning him on to us :)
> At any rate -- I have checked a few of my O'Reilly books, and they say that
> nat has it's advantages and disadvantages as well... ("Managing IP Networks
> with Cisco Routers", pages 237-239) -- most notably a speed hit.
There is some, but fast CPUs can fix that. Your main latency will be
elsewhere though.
> Here's how they want me to use it -- Router->NAT Address Pool->NAT
> box->Private IP space...
More or less. You'll want to set up one machine (or more, depending on
your anticipated load) and route all the traffic through it. Then route
the internal network using your own IP addresses. I'd suggest using the
10.x.x.x block (which is reserved for unconnected networks) so you have
plenty of space.
> I am wondering if the nat dameon in FreeBSD is as capable as some
> commercial solutions my upstream is favoring? Will it be more trouble than
> it's worth? Will it crap out on me with my network? How reliable is it?
The commercial solutions (that are FreeBSD based, like the InterJet)
probably use natd internally :)
For the record, our nat-enabled PPP link from my house to the University
has these stats:
Connect time: 3089622 secs # that's 35.7 days
894648205 octets in, 242018768 octets out
Works great, haven't had to touch it in any way, except to log in and
check the statistics. :-) Have to run cvsup in multiplexed mode, but
that's the only thing we have that complains.
> I have these and a few other questions, but again, I didn't want to sound
> like a dwaddle, but it's too late for that now... :)
Go for it. I mean, the name of this list _is_ ``questions,'' after all.
Doug White | University of Oregon
Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant
http://gladstone.uoregon.edu/~dwhite | Computer Science Major
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.00.9807211406180.8360-100000>