Portmaster 1.6.13 causes connection failures in games

[Marc05]

Since updating from 1.6.10 to 1.6.13, I've not been able to play Multiversus multiplayer. Shutting down Portmaster allows the connections to succeed. I don't see any relevant blocked connections and the game app is allowed.

I imagine whatever is happening is the same cause as: #1601

Potentially relevant/Unexpected logs:

240630 12:30:59.045 t2/handler:152 > WARN 965 kext: src/packet_callouts.rs:143 failed to get key from nbl: failed to get net_buffer data
240630 12:31:49.050 t2/handler:152 > WARN 967 kext: src/packet_callouts.rs:143 failed to get key from nbl: failed to get net_buffer data
240630 12:32:41.040 t2/handler:152 > WARN 969 kext: src/packet_callouts.rs:143 failed to get key from nbl: failed to get net_buffer data
240630 12:32:41.572 v/location:303 > WARN 971 netenv: failed to get IPv4 device location from traceroute: did not receive any actionable ICMP reply
240630 12:32:42.054 t2/handler:152 > WARN 973 kext: src/packet_callouts.rs:143 failed to get key from nbl: failed to get net_buffer data
240630 12:33:50.042 t2/handler:152 > WARN 975 kext: src/packet_callouts.rs:143 failed to get key from nbl: failed to get net_buffer data
240630 12:33:51.053 t2/handler:152 > WARN 977 kext: src/packet_callouts.rs:143 failed to get key from nbl: failed to get net_buffer data
240630 12:33:51.053 t2/handler:152 > WARN 979 kext: src/packet_callouts.rs:143 failed to get key from nbl: failed to get net_buffer data
240630 12:33:54.041 t2/handler:152 > WARN 981 kext: src/packet_callouts.rs:143 failed to get key from nbl: failed to get net_buffer data
240630 12:33:58.048 t2/handler:152 > WARN 983 kext: src/packet_callouts.rs:143 failed to get key from nbl: failed to get net_buffer data
240630 12:34:28.175 CURRENT TIME

[github-actions]

This issue has been automatically marked as inactive because it has not had activity in the past two months.

If no further activity occurs, this issue will be automatically closed in one week in order to increase our focus on active topics.

[github-actions]

This issue has been automatically closed because it has not had recent activity. Thank you for your contributions.

If the issue has not been resolved, you can find more information in our Wiki or continue the conversation on our Discord.