>
> Application firewall behavior.
> Does anyone know how the application firewalls use addresses. Do all users
> look like they are coming from the address of the application firewall ? I had
> heard that some firewalls
> ( Interlock ) can pass the addresses through or change them as they go through.
> I'm particularly interested in what the Raptor Eagle does with TCP services on
> ports 20,21,23, 25, 53,70, and 80. Does it pass them through with the same
> address or does it make them all appear like they are coming from the address
> of the Eagle ?
The Eagle's address is the one that remote systems see. Internal addresses
are completely hidden since both sides are talking to application
level processes that act as a server and client at the same time.
I don't think there is anything that fakes routes transparently and I
don't know of any application level firewall that passes on packets
with original addresses router style. Anyone?
There are a number of scenarios where it would be nice for the
application/network level of the gateway to emulate ip addresses.
For instance: Using only one ip address for the firewall and
transparent application level proxies, allow internal machines to use
direct ip addresses to Internet machines. The internal machines could
use bogus ip addresses which are translated by the firewall gateway.
(Of course that has it's own complications.)
Only one address/port for each incoming standard connection could be
supported (telnet, ftp, smtp,...), but other than that, outgoing
connections would be made as if the machines were on Internet.
> Brett
>
sdw
--
Stephen D. Williams Local Internet Gateway Co.; SDW Systems 513 496-5223APager
LIG dev./sales Internet: sdw @
lig .
net
OO R&D Source Dist. By Horse: 2464 Rosina Dr., Miamisburg, OH 45342-6430
Comm. Consulting ICBM: 39 34N 85 15W I love it when a plan comes together
Newbie Notice: (Surfer's know the score...)
I speak for LIGCo., CCI, myself, and no one else, regardless of
where it is convenient to post from or thru.
References:
|
|
