ubject: [FW1] Inbound, Outbound, Eitherbound
>
> I am looking for some real world experience to help me answer this
question.
> We are currently having licensing issues (this is due to the way that we
set
> up our BigIP boxes behind our FW, long story) But what is happening is
that
>
und to the
gateway and outbound from the gateway.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of
Tim Parker
Sent: Monday, April 09, 2001 4:26 AM
To: '[EMAIL PROTECTED]'
Subject: [FW1] Inbound, Outbound, Eitherbound
I am looking for some real
[mailto:[EMAIL PROTECTED]]
Sent: Monday, April 09, 2001 3:22 PM
To: Tim Parker; [EMAIL PROTECTED]
Subject: RE: [FW1] Inbound, Outbound, Eitherbound
> What I am thinking of trying, but this is where I need the
> help!, is changing the setting from eitherbound (the default)
> to inboun
ps a brief
topology schema would be of more help.
Cheers
Keith McCammon
-Original Message-
From: Tim Parker [mailto:[EMAIL PROTECTED]]
Sent: Monday, April 09, 2001 5:26 AM
To: '[EMAIL PROTECTED]'
Subject: [FW1] Inbound, Outbound, Eitherbound
I am looking for some real world e
> What I am thinking of trying, but this is where I need the
> help!, is changing the setting from eitherbound (the default)
> to inbound for our rulebase. I am curious though, if there
> are any other ramifications, other than the fact that the
> firewall will let anything from "inside" the
To: '[EMAIL PROTECTED]'
> Subject: [FW1] Inbound, Outbound, Eitherbound
>
>
>
> I am looking for some real world experience to help me answer
> this question.
> We are currently having licensing issues (this is due to the
> way that we set
> up our BigIP boxes behin
I am looking for some real world experience to help me answer this question.
We are currently having licensing issues (this is due to the way that we set
up our BigIP boxes behind our FW, long story) But what is happening is that
our FW is seeing external addresses on one of the internal interfac
