Great Circle Associates Firewalls
(July 1997)
 

Indexed By Date: [Previous] [Next] Indexed By Thread: [Previous] [Next]

Subject: RE: Re: Stateful packet filtering
From: manuel . ricca @ pararede . pt
Date: 14 Jul 97 16:50:09 +0000
To: firewalls @ GreatCircle . COM (Non Receipt Notification Requested)
Alternate-recipient: Prohibited
Autoforwarded: FALSE
Conversion: Allowed
Conversion-with-loss: Allowed
Delivery-date: 14 Jul 97 16:50:16 +0000
Importance: normal
In-reply-to: <0714160957-Re: Stateful packet filtering* /@MHS>
Message-type: Multiple Part
Original-encoded-information-types: Teletex
X400-content-type: P2-1988
X400-mts-identifier: [/PRMD=pararede/ADMD=ip/C=pt;ISOCOR-33b5fada-Tubarao]
X400-originator: manuel . ricca @ pararede . pt
X400-received: by /PRMD=pararede/ADMD=ip/C=pt; Relayed; 14 Jul 97 16:50:09 +0000
X400-recipients: firewalls @ GreatCircle . com

You mean you can define proxies in Firewall-1?
Any 'transparent proxy' firewall must filter packets using all of the usual packet-filtering attributes
(check source and destination IP, check the inbound and outbound interface, disallow SYN's that are not
paired with ACK's, etc). However, it's much simpler to configure, since the packet filter rules are automatically
generated. Of course, performance will necessarily be affected, since reassembly must be done until
the application layer (although personally I think that you should put security and ease of configuration first - most
holes in firewalls are due to misconfigurations in access lists). I always thought that the 'power of Firewall-1' was
its throughput, and that this was because it's a packet-filter instead of application-level firewall.
>From what I've heard about stateful multi-layer inspection (SMLT), I had the impression that Firewall-1 would
actually have some kind of Finite State Automaton inside it, and would allow or disallow a packet given its state. From
the current state, it would only allow a packet if it knew it would transit to another valid state. This would eliminate
the need for complete reassembly of the packets. These are all my own suppositions, and I also suspect this is wrong or
unfeasible (then again maybe not, if it were made from the network level up), but it was the only way I could imagine for a firewall to analyse packets to the application layer without
having proxies defined (given the simplicity one gains with them), and without loosing too much performance.

TIA,
.M

------------
Manuel Ricca   (manuel .
 ricca @
 pararede .
 pt)
ParaRede - Tecnologias de Comunicação, S.A.
Tel: +351 1 3020451
Fax: +351 1 3020444

Indexed By Date Previous: Re: How secure is BGP? was Re: Two ISP's to one DMZ -
From: "R. Todd Truitt" <ttruitt @ cisco . com>
Next: Restricting access
From: Visionprof @ aol . com
Indexed By Thread Previous: Re: Stateful packet filtering
From: Paulo Fernandes <pjf @ star . sols . pt>
Next: Re: hi (high?)
From: Pete Davis <petedavis @ usa . net>

Google
 
Search Internet Search www.greatcircle.com