Padden,
Eitherbound makes the packets to be inspected when the
arrive to the interface and when they're leaving the
gateway.
Inbound makes the inspection when the packet arrives to
the interface, no matter if it is coming from internal network to an external
one.
CCSA
material for v4.1 rev. A has a terrific example, in which Eitherbound could be
used if you have 'an untrusted administrator' that may rely on the firewall
machine itself to browse the internet, but I think it sucks! Would you have an
untrusted admin with physical and logical access to the FW machine? I don't
think so! :)
-----Mensagem original-----
De: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]Em nome de Padden, Greg
Enviada em: Monday, August 14, 2000 1:17 PM
Para: '[EMAIL PROTECTED]'
Assunto: [FW1] Inbound, outbound, or eitherbound?So what are other people using for this Property for applying the ruleset to the firewall's interfaces?
I was using Eitherbound, but was told that changing this to Inbound would gain me some performance.
Does anybody know any drawback to changing to Inbound?
Network Engineer, MSCE, CCNA
Information and Telecommunications Services
King County
700 5th Ave, Suite 1800
Seattle, WA 98104
(206)263-4804 Fax (206)263-4834
<<Padden, Greg.vcf>>
