CPUG

The Check Point User Group

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

1. CCSA/CCSE One-Week Dual-Certification Training Course with CPUG in San Francisco!
    Courses Starting 12/8, (2009) 1/19, 2/9, 3/9, 4/6, 5/4, 6/8, 7/6, 8/3.
2. 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 > VPN's (Virtual Private Networks)
Register FAQ Members List Calendar Search Today's Posts Mark Forums Read

Reply
 
LinkBack Thread Tools Display Modes
  #1 (permalink)  
Old 2006-04-10
Junior Member
 
Join Date: 2005-10-28
Posts: 1
Rep Power: 0
gbib1dde has an average reputation (10+)
Default fw_getfwifnum: no interface name

Hi there

We have recently deployed a fault tollerant cluster running on IPSO 3.9, with NGX HFA2. Prior to this, we had 2 firewalls running VRRP, with subtely different rule bases. On the old rule bases, we had Site to Site and Remote Access VPN's working without any problems.

Since changing the configuration to have a CP Express Cluster, consisting of 2 gateways, we have been unable to establish any VPNs.

We have run vpn debug on and vpn debug ikeon, and collected traces. In addition, we have run debugs on a remote tunnel end point, and we have run local tcpdumps. All information suggests that we are sending out Phase 1 IKE packets, but do not respond to the replies. The replies are received, (shown by tcpdump) however they do not appear to be processed by VPN-1.

Looking through vpnd.elg, we see a constant message - fw_getfwifnum: no interface name. Does anyone know what this means? We have logical interfaces defined in IPSO - and logical interface names defined within Checkpoint Topology.

If anyone can provide any pointers to what fw_getfwifnum: no interface name means - and whether this could cause a VPNDaemon problem, I would love to hear.

Thanks in anticipation.

Rowland

https://www.nettitude.com
Reply With Quote
  #2 (permalink)  
Old 2006-05-18
Junior Member
 
Join Date: 2005-10-12
Posts: 6
Rep Power: 0
jcamillo has an average reputation (10+)
Default Re: fw_getfwifnum: no interface name

I also have the same issue - in my vpnd.elg log I am getting the same message: fw_getfwifnum: no interface name

So far I have a case open with Nokia support and they are working with Checkpoint.

Do you notice any Drops due to antispoofing in you tracker logs?
Reply With Quote
  #3 (permalink)  
Old 2006-06-15
Junior Member
 
Join Date: 2006-04-12
Posts: 9
Rep Power: 0
JOBAR has an average reputation (10+)
Default Re: fw_getfwifnum: no interface name

Did you allready try with a reboot of the firewall module ? I had the same problem after an upgrade, allways received the error : no interface name, and it seems to be resolved after an reboot.
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 23:54.


Powered by vBulletin® Version 3.7.4
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO 3.2.0