- CheckMates
- :
- Products
- :
- Quantum
- :
- Management
- :
- fw monitor - traffic dropped after i
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Are you a member of CheckMates?
×- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
fw monitor - traffic dropped after i
I have ike (udp/500) traffic coming, and it's getting dropped after i in fw monitor.
Log show that it was being dropped due to CPearlydrop.. changed early drop optimization to 0 so I can see it in the logs, and it's just bypassing my rule and hitting the default drop any.
[vs_0][fw_33] eth1-01:i[492]: x.x.x.x -> y.y.y.y (UDP) len=492 id=30892
UDP: 500 -> 500
[vs_0][fw_3] eth1-01:i[492]: x.x.x.x -> y.y.y.y (UDP) len=492 id=31502
UDP: 500 -> 500
my rule, i'm allowing x.x.x.x to y.y.y.y (which is static NAT), with IKE, gIKE, udp/500, udp/4500 all allowed.
Can't figure out what I'm missing here.
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Unified Policy may contain filter criteria that cannot be resolved on a connection's first packet, such as Application or Data. Therefore, on some connections the final rule match decision is reached only on the following data packets.
However, the Rule Base may decide to block the connection at an early stage without a final rule decision, if all potential rules of the layer for a specific connection have a Drop or Reject action. This drop will issue a log with Rule Name "CP_Early_Drop" and hits will be counted for all the potential rules.
The purpose of this optimization is to improve security by dropping the connection as soon as possible.
However, if you want to get full visibility on the exact rules that dropped the connection, you can turn off the optimization.
Do the following to change the global parameter permanently:
-
Connect to the command line on the Security Gateway.
-
Login to the Expert mode.
-
Set the value of the kernel parameter up_early_drop_optimization to 0 permanently:
-
Create the $FWDIR/boot/modules/fwkern.conf file (if it does not already exit):
[Expert@HostName]# touch $FWDIR/boot/modules/fwkern.conf -
Edit the $FWDIR/boot/modules/fwkern.conf file in Vi editor:
[Expert@HostName]# vi $FWDIR/boot/modules/fwkern.conf -
Add the following line (spaces and comments are not allowed):
up_early_drop_optimization=0 -
Save the changes and exit from Vi editor.
-
Check the content of the $FWDIR/boot/modules/fwkern.conf file:
[Expert@HostName]# cat $FWDIR/boot/modules/fwkern.conf -
Reboot the Security Gateway.
-
-
In SmartConsole, install the policy.
-
Make sure that the new value was set:
[Expert@HostName]# fw ctl get int up_early_drop_optimization
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Unified Policy may contain filter criteria that cannot be resolved on a connection's first packet, such as Application or Data. Therefore, on some connections the final rule match decision is reached only on the following data packets.
However, the Rule Base may decide to block the connection at an early stage without a final rule decision, if all potential rules of the layer for a specific connection have a Drop or Reject action. This drop will issue a log with Rule Name "CP_Early_Drop" and hits will be counted for all the potential rules.
The purpose of this optimization is to improve security by dropping the connection as soon as possible.
However, if you want to get full visibility on the exact rules that dropped the connection, you can turn off the optimization.
Do the following to change the global parameter permanently:
-
Connect to the command line on the Security Gateway.
-
Login to the Expert mode.
-
Set the value of the kernel parameter up_early_drop_optimization to 0 permanently:
-
Create the $FWDIR/boot/modules/fwkern.conf file (if it does not already exit):
[Expert@HostName]# touch $FWDIR/boot/modules/fwkern.conf -
Edit the $FWDIR/boot/modules/fwkern.conf file in Vi editor:
[Expert@HostName]# vi $FWDIR/boot/modules/fwkern.conf -
Add the following line (spaces and comments are not allowed):
up_early_drop_optimization=0 -
Save the changes and exit from Vi editor.
-
Check the content of the $FWDIR/boot/modules/fwkern.conf file:
[Expert@HostName]# cat $FWDIR/boot/modules/fwkern.conf -
Reboot the Security Gateway.
-
-
In SmartConsole, install the policy.
-
Make sure that the new value was set:
[Expert@HostName]# fw ctl get int up_early_drop_optimization
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
More read here:
Early drop of a connection before the final rule match
