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 72 attendees signed up from 20 countries!
2. CCSA/CCSE One-Week Dual-Certification Training Course with CPUG in San Francisco!
    Courses Starting 10/6, 11/3, 12/8, (2009) 1/19, 2/9, 3/9, 4/6, 5/4, 6/8, 7/6, 8/3, 9/7.
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 > Dynamic Routing
Register FAQ Members List Calendar Search Today's Posts Mark Forums Read

Reply
 
LinkBack Thread Tools Display Modes
  #1 (permalink)  
Old 2008-02-28
hanren hanren is offline
Junior Member
 
Join Date: 2007-07-12
Posts: 4
Rep Power: 0
hanren has an average reputation (10+)
Default Add Anti-Spoofing Group and OSPF Neighbor broken

We've recently encountered an issue on OSPF. As briefed below:

FW Version:
[Expert@fw1]# fw ver
This is Check Point VPN-1(TM) & FireWall-1(R) NGX (R60) HFA_03, Hotfix 603 - Build 015

The OSPF setting is well configured and able to see and exchange the neighbor in database in the first time setup. Two days ago, my client have added a new corporate customer IP on EC router with IP as follows:

192.168.232.251 and 192.168.232.252

For the new APN Pools is 10.3.2.0/24 rule set has been added as:

Source : Besi_10.3.2.0_24
Destination: 192.168.232.251 and 192.168.232.252
Services: icmp_requests

1) When first time my client did a ping from 10.3.2.x to 192.168.232.251/252, the ping is dropped by FW due to 'Address Spoofing' on interface eth6 (this interface has been reserved for OSPF purpose).

2) So, I included and specified Besi_10.3.2.0_24 as 'Anti-Spoofing' group and push the topology again. The 'Anti-spoofing' message has gone and able to ping via FW to 192.168.232.252.

3) After a minute or so, the neighbor that were shown in the OSPF database was gone/broken. The core switch and other routers can't see the FW any longer in the OSPF database.

4) I then removed the anti-spoofing group from the topology, and it is strange that all the neighbor came back again.

Any ideas? How to resolve? thanks.
Reply With Quote
  #2 (permalink)  
Old 2008-03-03
hanren hanren is offline
Junior Member
 
Join Date: 2007-07-12
Posts: 4
Rep Power: 0
hanren has an average reputation (10+)
Default Re: Add Anti-Spoofing Group and OSPF Neighbor broken

Hi all,

I found the answer, just to add all the neighbor found (show ip ospf database) in the anti-spoofing group and push the policy again, then the neighbor will come back.
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:41.


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