CPUG

The Check Point User Group

A Resource For The Check Point Community.  Fast.  Useful.  Independent.

1. Come to CPUG CON 2008 EUROPE in Switzerland on September 8th - 9th!
    Two days full of technical content for Check Point administrators in the beautiful Swiss Alps!
    We already have sign-ups from twelve different countries!
2. CCSA/CCSE One-Week Dual-Certification Training Course with CPUG in San Francisco!
    Courses Starting 7/14, 8/25, 10/6, 11/3, 12/8, (2009) 1/19, 2/9, 3/9, 4/6, 5/4, 6/8.
3. Corrent S3500 SecureXL Turbocards For Sale - Last Six Remaining - Get Your Spares!
4. Join Us On LinkedIn - We now have a CPUG group.


Go Back   CPUG: The Check Point User Group > Check Point Firewall-1/VPN-1 And Related Products > Services
Register FAQ Members List Calendar Search Today's Posts Mark Forums Read

Reply
 
LinkBack Thread Tools Display Modes
  #1 (permalink)  
Old 2005-08-13
BarryStiefel BarryStiefel is offline
Administrator
 
Join Date: 2005-08-11
Location: San Francisco, CA
Posts: 534
Rep Power: 10
BarryStiefel has disabled reputation
Default Increasing Global TCP Timeout

Increasing Global TCP Timeout



Some versions of the GUI do not allow you to set the TCP Timeout value past 2 hours. Check Point says TCP Timeout can be set up to 24 hours. In $FWDIR/lib/base.def there's a section that looks like this:

#define TCP_ESTABLISHED_RECORD(con,key,type) ( ((type & _TCP_ESTABLISHED) = 0, not_first, set type (type | _TCP_ESTABLISHED), record in connections ) or 1 )

You can multiply the TCP_TIMEOUT by some factor, which basically changes the units in the Policy Properties. So, if you put TCP_TIMEOUT*6, now the number you enter in Properties is multiplied by 6 seconds, not 1 second. Note that in no case is a timeout larger than 24 hours allowed. If you look at the output of 'fw tab -u table connections', the last column shows you the tcp connection timeout value. It's a way of checking that the change you make is really taking effect.

If you are also doing NAT in a version prior to 4.1, you will need to do the following. For Solaris, type:

echo "fwx_tcp_expiration?W 0x" | adb -w -k /dev/ksyms /dev/mem echo "fwx_udp_expiration?W 0x" | adb -w -k /dev/ksyms /dev/mem

where is the number of seconds you'd like to keep hidden connections, converted to hex. For example, to make the tcp timeout 14,000 seconds type:

echo "fwx_tcp_expiration?W 0x36B0" | adb -w -k /dev/ksyms /dev/mem

-- GuyR - 18 Jan 2004

FAQForm FAQs.Class: ServicesFAQs FAQs.OS: FAQs.Version:
Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are Off
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On



All times are GMT -7. The time now is 16:29.


Powered by vBulletin® Version 3.7.2
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.
LinkBacks Enabled by vBSEO 3.0.0