Proxy doesn't necessarily solve the privateIP-to-publicIP problem. NAT does:

http://www.cablemodemhelp.com/proxy_vs_nat.htm

Proxy is application level. NAT is address translation.

HTH,

Christopher Hollow


JJB wrote:
Thanks for your reply, But I must be thick headed this morning,
because what you say below makes no sense to me.
I checked out the 2 referenced descriptions and they say
nothing about doing nat.

I have Lan with private ip address that send packets to
public internet. How does an proxy server solve the private ip
address versus my public ip address problem?

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of
[EMAIL PROTECTED]
Sent: Monday, February 02, 2004 11:28 AM
To: JJB
Cc: Jorn Argelo; [EMAIL PROTECTED]
Subject: Re: proxies and firewalls


Are you saying you know of an proxy server that does the nat
function?


Actually, the point of having  proxies is *not* having
to route. Your proxy machine should not be able to forward packets.

Roughly, there a two different sub-groups: Circuit layer and
application
layer proxies, names should be self explaining.

Example for an app layer gateway:

Port:   fwtk-2.1
Path:   /usr/ports/security/fwtk
Info:   A toolkit used for building firewalls based on proxy
services


Example for a circuit level proxy:


Port:   nylon-1.2
Path:   /usr/ports/net/nylon
Info:   A Unix SOCKS 4 and 5 proxy server


Socks5 is already app layer, too, IIRC.


Cheers, J.


_______________________________________________ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"

_______________________________________________
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"



_______________________________________________
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Reply via email to