|
|||||||||||
|
Re: Company Firewall's IP Address
From: Bill Hamel <billh(at)bugs.hamel.net>
Date: Tue Nov 19 2002 - 09:46:23 EST Ya know, if I didn't know any better I would think this thread is going in the direction of confusing the 'basic-security' reader.
The original user had a window pop up in a browser that showed him the IP address of the external interface of the firewall. This is absolutely normal if you "Extrapolate" what is going on. The user opens up his/her browser on their desk top. Their desktop has an internal IP address. The firewall translates this into and Externally routable IP address which lives on the external interface of the firewall. Once that packet is fired off to it's destination it typically goes through multiple hops (see "Traceroute") to get there. It needs a return path back to the external interface of the firewall hence the IP address MUST be available to the destination. IMHO a "Proxy" has nothing to do with this see "Basic Routing Principals" ;) -bh On Mon, 18 Nov 2002, Meritt James wrote: > The packets do not have to go directly to the source IP. They have to
This archive was generated by hypermail 2.1.8 : Wed Aug 23 2006 - 14:03:23 EDT |
||||||||||
|
|||||||||||