RE: [FW1] Estblished connection!!!

["McCammon, Keith" <Keith.McCammon@FW1-NOSPAMeadvancemed.com>]

I had heard the same about VPN connections.  However, we've been testing extensively with ours, and we haven't had anyone get "knocked off" yet.  There is a bit of a pause if you're in the middle of an operation, but nothing that has caused us to have to reauthenticate.

 

Just thought I'd throw that in...

-----Original Message-----
From: Tim Holman [mailto:tholman@uk.didata.com]
Sent: Wednesday, July 11, 2001 5:12 AM
To: Konstantinos Bilalis; fw-1-mailinglist@beethoven.us.checkpoint.com
Cc: owner-fw-1-mailinglist@beethoven.us.checkpoint.com
Subject: Re: [FW1] Estblished connection!!!

It's advisable to knock the undesirable connection ASAP.  Use the 'active' log viewer to do this.

Installing the policy.

As for installing the policy, it seems to throw out existing VPN connections, and a few other things, but I've never found a reliable resource that says what stays and what goes, so assume everything stays from a security perspective, and that everything goes from an uptime perspective.

Policy installs in real-time environments should definitely be done out of hours....

 

Tim

----- Original Message -----

From: Konstantinos Bilalis

To: fw-1-mailinglist@beethoven.us.checkpoint.com

Cc: owner-fw-1-mailinglist@beethoven.us.checkpoint.com

Sent: Wednesday, July 04, 2001 11:57 AM

Subject: [FW1] Estblished connection!!!

 

Dear all.

 

When a undesirable connection has already been established and afterwards I install the relevant policy, what about this connection???

Will it stop to operate or what???

 

Thanks in advance,

Kostas

***

The information in this e-mail is confidential and intended solely for the individual or entity to whom it is addressed. If you have received this e-mail in error please notify the sender by return e-mail, delete this e-mail, and refrain from any disclosure or action based on the information.

****