| CPUG | |
| The Check Point User Group | |
| A Resource For The Check Point Community. Fast. Useful. Independent. | |
|
| |||||||
![]() |
| | LinkBack | Thread Tools | Display Modes |
| |||
| Hi All, Jus wanna find out more on excatly how anti-spoofing works... this is my gut feel from my experience.. correct me if i'm wronng... here goes... On internal designated interfaces, this will ensure that if x,y networks are behind the interfaces, only x,y networks will be allowed, the rest will be dropped.. On External designated interfaces, this will ensure that anything that is not designated internal will be dropped... lets say internal has x,y,z networks... anything designated external will drop the above mentioned, the rest are allowed... This correct?? |
| |||
| also wanted to add that Checkpoint calls it "anti-spoofing" while cisco refers to as "Unicast Reversed-Path Forwarding" uRPF. The other thing worth mentioning is that if you have an environment where asymetric routing exists such as dual-ISP connection for your Internet connection upstream. In that case you may want to use "loose" mode instead of "strict" mode. |
| |||
| Quote:
Another note... on Asymmetric routing.. isnt this so called not supported by Checkpoint?? This is so called a security breach isn't it?? On the HA cluster type... theres this "Support non-sticky connections."... isnt this the one that will allow Asymmectric to work when in so called HA environment?? |
| |||
| Quote:
The commands are reverse path forwarding, the feature is anti-spoofing. Quote:
For a truly statefull firewall, you cannot "support" asymmetric routing, because it breaks state. Quote:
|
![]() |
| Thread Tools | |
| Display Modes | |
| |