http://www.dslreports.com/forum/r16493360 en Sun, 29 Nov 2009 15:13:40 EDT Sun, 29 Nov 2009 15:13:40 EDT http://www.dslreports.com/forum/remark,16514871 Diddy1 : Thankyou for your help!
Aaron]]> http://www.dslreports.com/forum/remark,16514871 Mon, 17 Jul 2006 04:15:58 EDT http://www.dslreports.com/forum/remark,16493599 gmcintire : The masquerading box acts as a firewall because it only accepts incoming connections that clients behind it have opened. A good explanation can be heard in episode #3 of Security Now: »www.grc.com/SecurityNow.htm (excellent podcast from Leo Laporte and Steve Gibson if nobody else is familiar with it). They can explain it more "user friendly" than I can, so I'll let you learn from them.

The biggest problems with NATs is any service that needs an incoming connection from the public Internet. Some of the most common programs to break are VPNs and peer-to-peer traffic (although it doesn't stop p2p, just slows down).

90% of your customers who just use the service for web browsing and email won't even notice if they're behind a NAT.]]> http://www.dslreports.com/forum/remark,16493599 Thu, 13 Jul 2006 15:54:30 EDT http://www.dslreports.com/forum/remark,16493520 Diddy1 : So what issues do you have? I'm thinking that for a provider, this isn't a good solution as there is the risk of alot of software that will not work? What can be done about this with Masq?
I was also told in another forum that Masq acts as a firewall as well? So could you just set it to forward the packets, ports, etc. that are having problems? I would imagine not because the problem would be in the translation itself?
I should have done more reading on this subject.
Aaron]]> http://www.dslreports.com/forum/remark,16493520 Thu, 13 Jul 2006 15:42:30 EDT http://www.dslreports.com/forum/remark,16493418 gmcintire : A proxy actually accepts the packet from the client, looks at it, then requesting the information directly from the server. After it gets the response from the remote server, it sends it back to the client. In this situation, the client is aware they're being proxied (unless you transparently proxy them, but that's a different issue).

Masquerading is the same thing as a NAT. You have 1 public IP address that can be used by many private IPs on your network. Think of it as just a layer 3 proxy... the client doesn't even have to be aware it's going through a NAT. We have a few hundred machines behind a single public IP address here (day job, not my WISP). It works well most of the time.]]> http://www.dslreports.com/forum/remark,16493418 Thu, 13 Jul 2006 15:22:52 EDT http://www.dslreports.com/forum/remark,16493360 Diddy1 : Can anyone provide some info. on the real differences between the two? I'm reading on the net now but perhaps a person explaining in their own words here would be better? I'm having a hard time finding info. on the true differences. I've got some books but limited info. as well.

Also, if you use 'masquerade' in Linux, how many client PCs can be used with one server?
Aaron]]> http://www.dslreports.com/forum/remark,16493360 Thu, 13 Jul 2006 15:14:15 EDT