- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
01-30-2014 01:49 AM
Hi everybody,
we got a lot of syn-packets which were dropped by the rule any-allow. But we haven't this rule, so is it a inbuilt rule and
why do i need a DoS-Rule to be protected against Syn-Floods if there is a builtin rule.
Cheers klaus
01-31-2014 06:33 AM
So it should be a bug.
Maybe restarting some services will solve this but I can't say you'll not see same behaviour then, or not.
Best; I advice an upgrade to 5.0.11
01-30-2014 08:06 AM
Hello Sir,
Do you have a DOS protection profile configured on your PAN firewall..? As per my knowledge, PAN is not having such inbuilt rule on it. Could you please expand the session details as mentioned below and update here.
Thanks
01-30-2014 08:13 AM
did you check zone protection ?
if no zone protection or dos protection is used then better to open a case.
01-30-2014 08:14 AM
Maybe you have flood protection turned on in a network profile? That might do it.
Mike
01-30-2014 08:38 AM
Hello kdd,
From the description we see that the inbuilt rule has taken charge. What we will have to look is at the time of issue did we see any DOS or zone protection profile counters triggered.(If they are configured )
This can be seen by " less dp0-log dp-monitor.log" Also we can check the commands to see the triggers for the syn flood
show dos-protection rule <rule name>
show zone-protection zone <zone name>
Example for Dos counters:
01-31-2014 03:05 AM
Thx for your comments.
to make it more visible and comprehensible what the zero point is:
- log entry
- DoS rule
- DoS protection profil
- DoS global counters
what i understood so far is that there seems to be a inbuilt rule which was taken in advance because the limitation of our own DoS-protection rule isn't as narrow as the default
where can i get information about the settings of the any-allow rule ? it sounds also strange to me to call a rule any-allow and then drop the packets. anywhere,
but there should be a clue to the inbuilt rule
01-31-2014 05:43 AM
Since it says "Session limit event" and your rule name is different, this is not normal.
What os version you are using ?
01-31-2014 06:17 AM
I am not sure if this is an unlisted bug but if you have time to upgrade it will be better.
There are some Dos related issues (49337—Traffic was blocked even though the DoS Protection policy was configured to allow it. - but written that fixed with 5.0.5)
Have you ever used "any_allow" name for a rule ?
01-31-2014 06:28 AM
yes, as we started with new zones there was a "any-allow" rule but not yet
01-31-2014 06:33 AM
So it should be a bug.
Maybe restarting some services will solve this but I can't say you'll not see same behaviour then, or not.
Best; I advice an upgrade to 5.0.11
01-31-2014 06:49 AM
thx for your assistance unfortunately there is still another problem with this version
02-10-2014 12:06 AM
after upgrade to 5.0.10 this behavior is completely disappeared. Thanks to all for your support
Regards Klaus
02-10-2014 05:53 AM
kdd if you're running HA you might want to move to 5.0.11 ASAP.... there are some huge HA bugs (dataplane restarts....) in 5.0.10
02-10-2014 07:36 AM
we wanna upgrade to 5.0.11. it is also an advice of panos but thank you too and is also done fast
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!