Portmaster block only tcp and udp protocol and not blocking other protocols

[rajagopalan181]

Pre-Submit Checklist:

• Check applicable sources for existing issues:
  • Windows Known Issues
  • Linux Known Issues
  • Github Issues

What happened:

Portmaster block only tcp and udp protocol and not blocking other protocols as per this list ( https://www.iana.org/assignments/protocol-numbers/protocol-numbers.xhtml )

What did you expect to happen?:
All the protocol is this list - ( https://www.iana.org/assignments/protocol-numbers/protocol-numbers.xhtml ) must be blocked

How did you reproduce it?:

Debug Information:

[github-actions]

Greetings and welcome to our community! As this is the first issue you opened here, we wanted to share some useful infos with you:

• 🗣️ Our community on Discord is super helpful and active. We also have an AI-enabled support bot that knows Portmaster well and can give you immediate help.
• 📖 The Wiki answers all common questions and has many important details. If you can't find an answer there, let us know, so we can add anything that's missing.

[Daksani]

What specific protocol are you finding isn’t being blocked? The majority of the protocols you listed still rely on TCP or UDP for transport. Portmaster is a consumer-focused firewall, and like most firewalls, it primarily targets TCP and UDP traffic because these are the protocols most frequently exploited in attacks. Additionally, most routers are not configured to forward other types of protocols, and even if they did, the network stack on the destination device would typically discard such traffic, as it wouldn’t know how to process it. This effectively eliminates a significant attack vector for non-TCP/UDP protocols.

If you are using specialized application-layer protocols, you’re likely operating within a private network or managing some kind of backbone infrastructure, where such traffic is intentionally permitted rather than blocked by your firewall.

For cases where protection against non-standard or application-specific protocols is necessary, you’ll probably need to invest in enterprise-grade hardware, which offers more granular control over protocol-level filtering.

[rajagopalan181]

Only tcp and udp protocol blocked in portmaster And other protocols are not blocked  in portmaster as per this list in this link - ( https://www.iana.org/assignments/protocol-numbers/protocol-numbers.xhtml )[ windows firewall will block all 255 protocols ] ---- On Mon, 25 Nov 2024 10:18:03 +0530 ***@***.***> wrote ---- What specific protocol are you finding isn’t being blocked? The majority of the protocols you listed still rely on TCP or UDP for transport. Portmaster is a consumer-focused firewall, and like most firewalls, it primarily targets TCP and UDP traffic because these are the protocols most frequently exploited in attacks. Additionally, most routers are not configured to forward other types of protocols, and even if they did, the network stack on the destination device would typically discard such traffic, as it wouldn’t know how to process it. This effectively eliminates a significant attack vector for non-TCP/UDP protocols. If you are using specialized application-layer protocols, you’re likely operating within a private network or managing some kind of backbone infrastructure, where such traffic is intentionally permitted rather than blocked by your firewall. For cases where protection against non-standard or application-specific protocols is necessary, you’ll probably need to invest in enterprise-grade hardware, which offers more granular control over protocol-level filtering. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>

[rajagopalan181]

Windows firewall will block all 255 protocols If the attacker uses other protocols means their can bypass portmaster security  ---- On Mon, 25 Nov 2024 10:18:03 +0530 ***@***.***> wrote ---- What specific protocol are you finding isn’t being blocked? The majority of the protocols you listed still rely on TCP or UDP for transport. Portmaster is a consumer-focused firewall, and like most firewalls, it primarily targets TCP and UDP traffic because these are the protocols most frequently exploited in attacks. Additionally, most routers are not configured to forward other types of protocols, and even if they did, the network stack on the destination device would typically discard such traffic, as it wouldn’t know how to process it. This effectively eliminates a significant attack vector for non-TCP/UDP protocols. If you are using specialized application-layer protocols, you’re likely operating within a private network or managing some kind of backbone infrastructure, where such traffic is intentionally permitted rather than blocked by your firewall. For cases where protection against non-standard or application-specific protocols is necessary, you’ll probably need to invest in enterprise-grade hardware, which offers more granular control over protocol-level filtering. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>

[Raphty]

This is not correct! what do you base this wrong assumption on?

[vlabo]

If you are referring to ICMP like some of the other issues you opened try switching to the beta channel and see if this fixes the behavior you are experiencing.
https://wiki.safing.io/en/FAQ/SwitchReleaseChannel

If not please provide more details how you are doing the tests and what is not blocked.