[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [cobalt-users] Dual Internet Access (Balancing) using Qwest
- Subject: RE: [cobalt-users] Dual Internet Access (Balancing) using Qwest
- From: nobody <bs@xxxxxxxxxxx>
- Date: Sat Dec 30 23:51:01 2000
- List-id: Mailing list for users to share thoughts on Cobalt products. <cobalt-users.list.cobalt.com>
On Sat, 30 Dec 2000, John Cordeiro so wrote:
} Would SSL and other stuff still work using nat. I have the same situation
} except a diffrent provider and only need 1 interface. So if I get what your
} saying, install the router project, Use 1 ip for Priary DNS, 1 IP for
} Secondary DNS, 1 IP for RAQ Interface and that leaves 2 IPs. If you use nat
} on the RAQ you can host virtual sites via a Private (10. or 100. 0r 192.) Ip
} range right?
While the answer to your question is yes, NAT adds a
substantial amount of overhead as a result of the address mapping
that makes it work and, contrary to popular belief, that address
mapping results in a number of security issues that render it a poor
choice for use in a commercial hosting enviornment.
Sometimes we miss the basic simplicities of things. NAT
is attractive because it allows one to quickly, easily and cheaply
connect a whole lot of this and that to the Internet via one IP
address. If that is your goal than NAT is most certainly a viable
solution. But unless you're simply wanting to host your company's
web site and network internal workstations, then I'd suggest that
the quickest, easiest and cheapest solution is seldom suitable for
anything more than the most basic of needs.