Port Forwarding Rule not working

Follow

Zorro

• February 02, 2026 18:36

Service RDP
Protocol TCP
Interface All WANs
External Port 12568 (actually using a different port this is an example) 
Device PC1 (Also has reserved IP) 
Internal Port 3389
Allow Selected Source My current public IP. (Also tried All Sources) 
Plan to add time window later or only turn on when needed but can't get it to work at all. 

Firewalla Gold SE in Router mode, no double NAT, still blocks the traffic.  Block Type IP Filtering
Device Active Protect is currently Off

0

• 

  Zorro

  • February 02, 2026 22:39

  Found the issue, I have a Block rule on all my LANs to block traffic from the Internet.  I thought we had to have that for security but it appears it is redundant and firing before the port forward rule?

  0

  Comment actions Permalink
• 

  FirewallaSupportDesk

  • February 03, 2026 00:20

  By default, Firewalla has Ingress Firewall, so you don't need to manually create a rule to stop Internet inbound traffic. The reason why port forwarding didn't override the rule you created can be found in Rules Logic: 

  Exceptions:

  • Except for the Ingress Firewall rule, all BLOCK rules on inbound traffic (e.g., region blocks) always have priority over inbound ALLOW rules (e.g., port forwarding). For example, if you have a Region block, it will prevent a connection from the blocked region even though port forwarding is enabled. 

  0

  Comment actions Permalink

Please sign in to leave a comment.