New port forwarding issue?

Follow

Richard Poeling

• December 12, 2020 20:40

When I got my Firewalla gold a week ago, I set up port forwarding on a couple ports and everything was working.  Today I noticed that port forwarding has been moved to Network -> NAT and when I tried to set up a new port, I couldn't get Firewalla to allow external inbound traffic.  I even turned the firewall option off and back on, but no luck.  Only after I rebooted the device did it allow traffic outside to be routed to the server I had listening on the port.  Not a big deal, but I now can't get the Firewalla device to map an external port to a different internal port number.  For example if I set up external port 8100 to be mapped to internal port 80 on a web server, it accepts the entries but the connection from outside the network is refused.  When I reboot the Firewalla and it comes up, the NAT entry now shows that the 8100 external port is to be routed to 8100 internal port.  It's not remembering that I want 8100 to route to 80.  I can reproduce the problem by deleting the entry and repeating - even if I choose a different pair of ports.  Once I reboot the Firewalla device the internal port changes back to the external port.

1

• 

  Firewalla

  • December 12, 2020 21:07

  This sounds like a bug.  I just created a ticket for you and please if possible, let us know what version (ios or android) app you are using, and the version of the firewalla box.  in that ticket

  1

  Comment actions Permalink
• 

  Richard Poeling

  • December 12, 2020 21:59

  Thanks.  Oddly the two new entries I created earlier have disappeared.  I did not remove them.  Nor did I reboot the Firewalla since the last time when I observed the issues described in my post.  So now my new port forwards aren't even showing up and my server is no longer accessible from outside.  

   

  1

  Comment actions Permalink
• 

  IHaveABigNetwork

  • December 13, 2020 00:23

  I just went and checked and many of my rules have the same thing happening... when I set them up I would for example forward external port 9090 to internal port 80, and now the rules say 9090 is forwarded to 9090.

   

  No wonder some of my device's external access wasn't working!  Great catch Richard! 

  2

  Comment actions Permalink
• 

  Support

  • December 13, 2020 02:20

  @Richard. We've created a support ticket in our system to follow up. Meanwhile, can you please tell us your app version and platform?

  1

  Comment actions Permalink
• 

  Richard Poeling

  • December 13, 2020 14:30
  • Edited

  Firewalla Box Version 1.971 (52dcc669). The App Version g1.43.20 (3.6.20)

  0

  Comment actions Permalink
• 

  Firewalla

  • February 04, 2021 19:33

  @rob, are you in simple mode or router mode?

  0

  Comment actions Permalink
• 

  Rob Dennison

  • February 04, 2021 20:06

  Thanks for the quick response. I'm in router mode, but just deleted the comment because I found I WAS able to connect (iOS SSH app, turn off wifi, connect through cell network, all good).

  Sorry about that. It seems the problem I'm having isn't a result of Firewalla.

  More investigating ;)

  R.

  0

  Comment actions Permalink

Please sign in to leave a comment.