Hi all, first time poster so go easy!
We're running into an issue where a rule that is meant to catch ether-ip traffic on port 20033 is slipping through and being caught by a lower rule which allows any application and service. Rules as follows:
When running the "show session all filter rule X" command in cli, we can see that sessions are only established for the lower one, and not the higher one.
I suppose I'm wondering if the rules have been configured incorrectly caused by me missing something, or if it's configured fine and this appears to be a bug.
Many thanks!
Hello @ChickenTenderer
IP Protocol number of etherip (97) is not as same as TCP. I think that is the reason why it is not hitting the above rule when you defined TCP ports there. Traffic which is having destination port 20033 and with IP protocol number 6 or 17 will only hit this rule. Can you change it to applicationd deafult and see if it is working?
Hello @ChickenTenderer
IP Protocol number of etherip (97) is not as same as TCP. I think that is the reason why it is not hitting the above rule when you defined TCP ports there. Traffic which is having destination port 20033 and with IP protocol number 6 or 17 will only hit this rule. Can you change it to applicationd deafult and see if it is working?
