Packets not matching with firewall rule, hitting default deny / rule violation

Started by user12314, Today at 04:20:39 PM

Previous topic - Next topic
Hi everyone.

I got a rule that should be very simple, but it just won't work.
I got an IP on a vlan, that should be able to send back and forth data with TCP and UDP to another IP on the same vlan. It's for gamestreaming using Steam Link (not the physical device, just the software any steam client comes with).

UDP packets arrive fine, but TCP packets never match with the rule and thus get hit with the default deny rule.

I've tried:
- ipv4, protocol TCP/UDP, in, pass, source: <ip of PC>, port any, destination: <ip of handheld device>, port any
- ipv4, protocol any, in, pass, source: <ip of PC>, port any, destination: <ip of handheld device>, port any

I've found online it has to do with the TCP flags, but the tcp packets that won't match for me have the flags 'A' or 'PA', i understand it's not such a case then.

I'm at a loss why this won't work, everything else works like this on the firewall??

Some help would be greatly appreciated, thank you

If both devices are in the same vlan they can discover each others IPs directly via ARP and communicate directly between each other. The firewall is not responsible in this case.

If its different vlans and it must be routed over the firewall, or when you configured a bridge, thats a different story.
Hardware:
DEC740

Fixed: It seems to have been a steam link bug where it won't work outside of big picture mode