topic Re: fw monitor not filtering in General Topics

fw monitor not filtering

Johannes_Schoen — Thu, 11 Apr 2019 11:13:11 GMT

Hi community,

I have some problems with monitoring devices through an vpn tunnel.
I used

fw monitor -e "accept( host(<ip>));"
fw monitor e ‘(accept src=<ip>);'

but I got the whole traffic - the filter is not working.

Is that maybe one of the nice bugs of R80.20?
Currently I'm on JHF73 because Check Point shredded my IA.

Looking forward to your suggestions

Best Regards
Johannes

Re: fw monitor not filtering

Maarten_Sjouw — Thu, 11 Apr 2019 11:25:38 GMT

Maybe you can try without the extra ( ) like:
fw monitor -e "accept host(10.10.10.10);" -m iO

Re: fw monitor not filtering

NickGriffiths — Thu, 11 Apr 2019 11:37:59 GMT

I've just highlighted this in here too: https://community.checkpoint.com/t5/Product-Announcements/R80-20-Jumbo-Hotfix-Accumulator-New-Ongoing-Take-73/bc-p/50391#M96

Regardless of SecureXL status, T73 appears to have broken the filters.

fw monitor not filtering

G_W_Albrecht — Thu, 11 Apr 2019 11:44:11 GMT

I am sorry, but i really do not understand what you want to achieve here. Check Point's FW Monitor is a powerful built-in tool for capturing network traffic at the packet level. For monitoring devices for health, traffic rate a.o. most customers use SMNP !

fw monitor filters are using a subset of CheckPoints old INSPECT syntax to specify the packets to be captured. Details concerning functionality, syntax a.o. can be found in How to use FW Monitor and in How to use FW Monitor.

Re: fw monitor not filtering

Nick_Doropoulos — Thu, 11 Apr 2019 12:02:31 GMT

Hi Johannes,

Specifying just the host/source ip address is still bound to overwhelm you with a great deal of output, depending on the services that the host in question uses and the traffic it generates in general.

I think the best way forward would be for you to tell us the following:

What is it exactly you are trying to achieve?
Is the host in question on your site or on the remote site?
What is exactly the traffic you are really interested in?
What interface did you run the fw monitor command on?
Did you turn securexl off before running the command? Remember that you don't have to do that on R80.20.

Many thanks.

Re: fw monitor not filtering

NickGriffiths — Thu, 11 Apr 2019 12:09:41 GMT

The post that I made regarding the fw monitor filter being broken by JHFA T73 appears to have disappeared from the 'official' ongoing T73 thread. (The thread itself has been deleted).

I assume this means that a retraction of T73 is about to be made, functionality of fw monitor has been broken, and it will soon be replaced by a new ongoing take.

The symptoms of the OP match my findings, e.g. filters not being applied correctly/at all post upgrade to T73; but fine in T47.

Re: fw monitor not filtering

Johannes_Schoen — Thu, 11 Apr 2019 14:50:41 GMT

Hi @opal, didn't work, it's the same.

Re: fw monitor not filtering

Johannes_Schoen — Thu, 11 Apr 2019 14:51:13 GMT

@Nick thanks for your reply, another wonderful bug in the CP world.
I guess it can only get better from now on

Re: fw monitor not filtering

Johannes_Schoen — Thu, 11 Apr 2019 14:52:42 GMT

@G_W_Albrecht: sry, I didn't explian myself from the beginning on.
Monitoring the cluster nodes with SNMP stopped working and I wanted to make sure, that the SNMP packets are passing the firewall.
Unfortunately the filters are broken (T-73) - maybe my monitoring problem is based on similar hotfix issues....

Re: fw monitor not filtering

Johannes_Schoen — Thu, 11 Apr 2019 14:53:39 GMT

Dear Nico, I think it's a bug with JHF-73 - filtering the traffic with the stated expression should work as expected.

Re: fw monitor not filtering

PhoneBoy — Fri, 12 Apr 2019 01:09:30 GMT

Did you open a TAC ticket on this?

Re: fw monitor not filtering

Johannes_Schoen — Fri, 12 Apr 2019 13:22:56 GMT

No, I haven't opened up a TAC case.

The expression-thing seems to be known and is one of many recently experienced bugs.

Regarding the strange SNMP behavior: I first need more time to exclude other issues.

Re: fw monitor not filtering

Martin_Schagerl — Wed, 17 Apr 2019 13:46:28 GMT

take74 still shows the issue

Re: fw monitor not filtering

Matt_Killeen — Mon, 15 Jul 2019 15:42:45 GMT

FROM sk30583

fw monitor -F "{src IP}, {src port}, {dst IP}, {dst port}, {protocol num}"

Filtering the packets based on IP/port/protocol.
Notes:

Value 0 is used as "any".
Up to 5 filters are supported. Multiple filters are applied on packets in OR logical manner.

Note: Relevant for R80.20 from Jumbo Hotfix Accumulator for R80.20 (Take 73)

examples using fw monitor -F "{src IP}, {src port}, {dst IP}, {dst port}, {protocol num}":

fw monitor -F "0, 0, 0, 443, 0"

fw monitor -F "0, 0, 2.2.2.2, 0, 0"

fw monitor -F "1.1.1.1, 0, 2.2.2.2, 443, 0"

example for all DNS traffic which also captures all return traffic from DNS

fw monitor -F "0, 0, 0, 53, 0" -F "0, 53, 0, 0, 0" -w

I believe you need -w for full packet length capture and can still use -o to output files.

There is also a fw monitor -U to set fw monitor back to defaults. It appears to unload the monitor but not really sure what that does - I'm still testing the syntax and searching for more detailed documentation.

Re: fw monitor not filtering

Johannes_Schoen — Mon, 15 Jul 2019 14:58:15 GMT

Thanks @Matt_Killeen for the update.
The old fw monitor was so hard to use, this new syntax is so innovative and ease to use.
Why use -e 'accept src(1.2.3.4)', when it's so much easier to use -F "1.2.3.4, 0, 0, 0, 0"
I want to get the pills or the stuff to smoke, the product management obviously got....

I mean we can be glad, the we are allowed to use IPs and no hex-stuff

Re: fw monitor not filtering

Scott_Paisley — Thu, 25 Jul 2019 08:03:07 GMT

Take 87 also seems to have the same issue

Re: fw monitor not filtering

ChammiK — Tue, 27 Aug 2019 02:55:29 GMT

Does this show you all the inspection points? I tried this with -p all but it only shows me a single position in the inbound chain. What I need to see is the interface that the traffic is going out of.

Re: fw monitor not filtering

Danny — Tue, 27 Aug 2019 20:45:11 GMT

@Johannes_Schoen ,

I'm working to make using FW Monitor to be the easiest experience ever. Just follow my work progress @ FW Monitor SuperTool.

Re: fw monitor not filtering

ChammiK — Tue, 27 Aug 2019 22:49:48 GMT

This seems to be a really nice tool to use. I am a bit skeptical about SecureXL getting disabled though. The gateway is under a bit of load at the moment.

However, this doesn't help me with my problem at hand. I have the filters and syntax correct but I'm only seeing a single inspection point in the firewall chain no matter what I do. Got a TAC case opened for this. Was just wondering if anyone successfully used fw monitor to capture all inspection points in R80.20 JHF take 87+

Re: fw monitor not filtering

Danny — Wed, 28 Aug 2019 01:18:57 GMT

If you're at R80.20 JHF take 87+ SecureXL won't be disabled by FW Monitor SuperTool. Also if your gateway is under load and you are using an older version you should disable SecureXL only for the IP addresses to be monitored. This has to be done on the management though.