[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Doing nat only with <ONE> nic
- To: misc_(_at_)_openbsd_(_dot_)_org
- Subject: Re: Doing nat only with <ONE> nic
- From: Chuck Yerkes <chuck+obsd_(_at_)_2002_(_dot_)_snew_(_dot_)_com>
- Date: Thu, 21 Nov 2002 10:42:30 -0800
- Mail-followup-to: Chuck Yerkes <chuck+obsd_(_at_)_2002_(_dot_)_snew_(_dot_)_com>, misc_(_at_)_openbsd_(_dot_)_org
- Reply-to: misc_(_at_)_openbsd_(_dot_)_org
The 2 simple things that jump to my mind:
1) get another NIC - a decent one, not a US$15 special.
2) for simple home use for a person who doesn't really "do" Unix,
get a dedicated NAT box/DSL router instead. Quiet, simple to
configure, unlikely to die like an old machine, and YOU don't
have to maintain it. You get a reasonable protection via
NAT if you keep it from mapping new connections back.
If/when that "old machine" dies and he has no internet access
for weeks, he will dislike Unix more.
Quoting David Rio (is04607_(_at_)_salleURL_(_dot_)_edu):
> A friend of mine has bought a new internet access. The ISP gave him a
> "modem-bridge" that has one ethernet port. Clients has to use dhcp to get
> ip addresses. This Ip addresses are public ones and only two computers can
> be using the internet access at the same time. Dirty? sure.
> My friend has four computers and wanted that all of them would have
> internet access. I tell him: Hey!! Now it is time to get openbsd in your
> So I got an old machine that he had at home and use it to configure the
> almost typical NAT-setup. What I say almost? Well, I say that because the
> machine that will do NAT has only ONE NIC.
Visit your host, monkey.org