[Bug] Protocol 4 is mislabeled as "IPv4"

[ghost]

Checklist

• [X] I have used the search function to see if someone else has already submitted the same bug report.
• [X] I will describe the problem with as much detail as possible.

App version

3.8.0

Windows version

Windows 11 19045

Steps to reproduce

1. Start adding a new rule
2. Look at Protocols
3. Notice Protocol 4 is labeled as "IPv4"

Expected behavior

No response

Actual behavior

Protocol 4 is mislabeled as "IPv4" in SimpleWall, but Protocol 4 is actually "IP-in-IP" encapsulation https://en.wikipedia.org/wiki/List_of_IP_protocol_numbers . It does not filter any IPv4 TCP and/or IPv4 UDP packets. Protocol should simply renamed from "IPv4" to "IP-in-IP".

Logs

No response

[henrypp]

dont understand ur language and where is a problem

[ghost]

That's Microsoft's labeling for internal code, but it is misleading to label it simply as "IPv4". Protocol 4 is a defined network protocol and the correct label for it is "IP-in-IP" or "IPIP" - https://www.rfc-editor.org/rfc/rfc1853 .