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 > Licensing
Register FAQ Members List Calendar Search Today's Posts Mark Forums Read

Reply
 
LinkBack Thread Tools Display Modes
  #1 (permalink)  
Old 2005-08-13
roadrunner roadrunner is offline
Senior Member
 
Join Date: 2005-08-12
Posts: 162
Rep Power: 3
roadrunner has an average reputation (10+)
Default What does fw putkey -n do ?

What does fw putkey -n do ?
(This FAQ is relevant to FireWall-1 4.1 and earlier) putkey -n is documented on Check Point's Partner Support page, but not very well.

Normally, when "putkeys" are done between systems and, say, a Management Console and a Firewall Module begin communicating with one another, the actual communication takes place between the nodename IP addresses of each box. To find out the nodename IP address of a Unix box, you take the value of "uname -n" and compare this against the system's local host file (or other name resolution mechanism). Whatever IP address that "name" resolves to is the "nodename IP" address for that box.

If for some reason the systems can not communicate via the nodename IP addresses (because the nodename IP on one box must be tied to a non-routable or non-reachable IP address), you can use putkey -n to "overrides" the nodename IP address of the local system. Sometimes you will also use putkey -n after you have changed the IP address of one or more systems to "reset" the authentication to the proper IP.

The syntax for putkey -n is:

fw putkey -n local-ip remote-ip

Where "local-ip" refers to the local IP used for communication (e.g. the value that will "override" the local nodename IP) and "remote-ip" is the remote system's IP address.

Warning about using 'putkey -n': If you must do 'putkey -n' for multiple sites, you may only use only one distinct IP address for the "local IP" for all sites. The minute you use a different IP for -n, all the other putkeys you did with '-n' will cease to work. I'm not sure if this is a "bug" or a "feature", but that's the way it appears to work.

-- GuyR - 11 Jan 2004


FAQForm
FAQs.Class: RemoteManagementFAQs
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 20:00.


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