RE: IEWB v2 : 8.1- TCP intercept watch-timeout

From: Wang, Ting \(Taylor\) (wangting@avaya.com)
Date: Wed May 03 2006 - 09:47:09 ART

• Next message: Radioactive Frog: "Re: interesting article of certifications"
• Previous message: Eric.Stuhl@ferguson.com: "RE: Argument over Logos and Usage"
• Maybe in reply to: Wang, Ting \(Taylor\): "IEWB v2 : 8.1- TCP intercept watch-timeout"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]

Hi Group,
Thanks for your confirmation.
A further question on this topic. If the requirement is for a different
case that connection time for legitimate users is 60 s. I should use
the following command. Is that command only work for intercept mode not
for watch mode?

ip tcp intercept connection-timeout 60.
Taylor

  _____

From: Sidalo [mailto:sidalo@gmail.com]
Sent: Wednesday, May 03, 2006 3:15 AM
To: Wang, Ting (Taylor)
Subject: Re: IEWB v2 : 8.1- TCP intercept watch-timeout

Your thinking is correct. Intercept is default mode, and you will have
to change the mode to watch

On 5/2/06, Wang, Ting (Taylor) < wangting@avaya.com
<mailto:wangting@avaya.com> > wrote:

        Hi Group,
        The solution need 30s of watch-timeout.
        ip tcp intercept watch-timeout 30
        As I had understood, the watch mode is needed for "
watch-timeout" to work, but the default mode is intercept mode. I think
the mode should be changed to watch mode. Could anyone correct me if I'm
wrong?

        Thanks,
        Taylor

• Next message: Radioactive Frog: "Re: interesting article of certifications"
• Previous message: Eric.Stuhl@ferguson.com: "RE: Argument over Logos and Usage"
• Maybe in reply to: Wang, Ting \(Taylor\): "IEWB v2 : 8.1- TCP intercept watch-timeout"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]

This archive was generated by hypermail 2.1.4 : Thu Jun 01 2006 - 06:33:20 ART