- Products
- Learn
- Local User Groups
- Partners
- More
Firewall Uptime, Reimagined
How AIOps Simplifies Operations and Prevents Outages
Introduction to Lakera:
Securing the AI Frontier!
Check Point Named Leader
2025 Gartner® Magic Quadrant™ for Hybrid Mesh Firewall
HTTPS Inspection
Help us to understand your needs better
CheckMates Go:
SharePoint CVEs and More!
How can we create a service for Any tcp and UDP ports.
Port should be- Any
And protocol should be - TCP and UDP ??
Hi @Chauhanrht8
Creat two new services with a port range from 1 to 65535 for udp service and tcp service.
Set no protocol in protocol field and don't use ‚match for any‘.
Now add this two new services to your rule.
TCP_ANY:
Port: 1-65535
Match for any: no
Protocol: none
UDP_ANY:
Port: 1-65535
Match for any: no
Protocol: none
Not sure why you would want to do this, but create a group and insert a tcp and udp object.
Each object respectively contains the port range of 1-65535 or just "any" and you are good to go.
* Any also matches for applications and not just TCP/UDP ports as requested.
Therefore just create a new tcp_any and udp_any object >0, uncheck Match for Any and use these in your rule.
Example:
How To Describe "Any Application"
Matching unknown traffic
Hey,
I was not writing about "any" in the typical way of "any" in the service column. With any I meant to write "any" in the TCP or UDP objects itself. "Any" or 1-65535 should end up with the same functionality, doesn't it?
You may want to be sure to uncheck the 'match for any' in the service properties. I expect you will receive the warning that service objects may inherit that change.
See sk150553 for an example.
The idea sort of negates having a firewall though. I assume you likely have a good reason.
Hi @Chauhanrht8
Creat two new services with a port range from 1 to 65535 for udp service and tcp service.
Set no protocol in protocol field and don't use ‚match for any‘.
Now add this two new services to your rule.
TCP_ANY:
Port: 1-65535
Match for any: no
Protocol: none
UDP_ANY:
Port: 1-65535
Match for any: no
Protocol: none
Hi,
What is the use case to have Protocol = NONE ?
Why 2 separate services are proposed (TCP_ANY and UDP_ANY) though the meaning is same as we are not using any protocol ? Is it only for more readability ?
What will be behavior of checkpoint firewalls if do not choose Protocol = None ? Because Source IP will choose either TCP or UDP for communication.
Regards,
Sajjad
Thanks.
So it means any protocol (like TCP, UDP , GRE, IPSec, etc.) under IP-Protocol will be considered, it is like everything.
Leaderboard
Epsum factorial non deposit quid pro quo hic escorol.
User | Count |
---|---|
15 | |
12 | |
8 | |
6 | |
6 | |
6 | |
5 | |
5 | |
4 | |
3 |
Tue 07 Oct 2025 @ 10:00 AM (CEST)
Cloud Architect Series: AI-Powered API Security with CloudGuard WAFThu 09 Oct 2025 @ 10:00 AM (CEST)
CheckMates Live BeLux: Discover How to Stop Data Leaks in GenAI Tools: Live Demo You Can’t Miss!Thu 09 Oct 2025 @ 10:00 AM (CEST)
CheckMates Live BeLux: Discover How to Stop Data Leaks in GenAI Tools: Live Demo You Can’t Miss!Wed 22 Oct 2025 @ 11:00 AM (EDT)
Firewall Uptime, Reimagined: How AIOps Simplifies Operations and Prevents OutagesAbout CheckMates
Learn Check Point
Advanced Learning
YOU DESERVE THE BEST SECURITY