Not going to speak on what the DOC says as I don't have time to go look at it. But NAT is not that sophisticated. It is actually quite standard now. Most every ISP will deliver or recommend a router solution for home internet access. These routers typically own one public IP address and serve out DHCP private address into your network. These private IP addresses access the internet via network address translation through the router. Basically what NAT does is generates a new port for the request and passes the request as if it came from the public address. When the result comes back, nat knows which internal private IP to route it to based on the port. NAT is wonderful in that it doesn't matter what ports you need access to on the net, ie; instant messengers, pop3's, or whatever.. NAT handles it and changes the originating port on the fly to handle it. Most people cannot afford a real routing software like Winroute Pro but ICS clearly handles NAT well. You just don't get the extra bells and whistles. Persona lly never used ICS for a large network but I can tell you one of our customers is running 100+ workstations behind Winroute PRO and NAT and have not had a glitch.
Having a full featured router / software router will enable you to do much more than the basic internet stuff. With NAT and PAT (port address translation) you can take inbound request for example :81 and route them to a private internal systems port 80.. Hence, having multiple web servers. For this matter you can get as creative as I do and have 15 machines behind your router machine and build different ports to lots of internal boxes for different services. So if your serious about having fun at your house, heres a little sample (example) using NAT / PAT with a few port maps. PUBLIC IP address: 24.1.1.1 Private IP addresses: 192.168.1.2 - whatever 24.1.1.1:80 takes you to your default web server on router server 24.1.1.1:21 takes you to your default ftp server on router server 24.1.1.1:82 takes you to the webserver on 192.168.1.2 24.1.1.1:22 takes you to your FTP file server on 192.168.1.2 etc. etc. etc. NAT is fun, not sophisticated. Danny On 02/Nov/2001 10:30:30, Jeff Adams wrote: > The Sambar documentation is correct. Each device behind the router that has > a public IP address can have traffic routed to the Internet via a router. > Any device that has a private address (e.g. 10.0.0.0 - 10.255.255.255, > 172.16.0.0 - 172.31.255.255, or 192.168.0.0 - 192.168.255.255 (covered in > RFC 1918)) will not have traffic routed to the Internet via a router. Every > router should support and be configured as such because these ranges are > recognized world wide as non-routable. > > To enable devices with private IP address access to the Internet, > alternative access must be setup - namely a proxy (basic) or Network Address > Translation (NAT) (sophisticated). > > -Jeff > > -----Original Message----- > From: [EMAIL PROTECTED] [<A >HREF="mailto:[EMAIL PROTECTED]";>mailto:[EMAIL PROTECTED]</A>]On Behalf Of > Rodney > Sent: Friday, November 02, 2001 09:42 AM > To: sambar > Subject: [sambar] router? > > This is from the sambar docs. I don't think it's true. Comments? > ************************************************************* > Why would I use a proxy server rather than a router ? > Routers can only be used when every machine on the network has a public IP > address. The costs associated with maintaining your own class C network are > significantly higher than having single dial-up or ISDN connection. > > Highest Regards, > Rodney Richison > > -------------------------------------------------------------------------------- > For unsubscription of this list send an email to [EMAIL PROTECTED] with email > data containing unsubscribe emailadd sambar > > -------------------------------------------------------------------------------- For unsubscription of this list send an email to [EMAIL PROTECTED] with email data containing unsubscribe emailadd sambar
