Port forward not working

Hi Jacob,

Thank you for the feedback.

Please share the below information:

• Appliance model details
• WAN Interface IP configuration: Static/Dynamic

Regards,

Deepti

Hi Deepti,

1. I have Sophos installed on a Netgate 2440 (originally bought with PFsense https://www.netgate.com/products/sg-2440.html )

2. WAN interface ip configuration is Dynamic (static DHCP address assigned from my ISP provider)

Regards

Jacob

Hi Jacob,

We found , service has been misconfigured for Forwarding rule.

Service RDP and "Blue Iris" has been created with Source Port/Destination Port TCP (3389) / (3389), TCP (81) / (81) respectively

Those should be  TCP (1:65535) / (3389)  and TCP (1:65535) / (81). Please update that.

Other point, we have been already reported issue NC-22584, where with Dynamic WAN interface and Port dnat rule, after reboot of the appliance, it is not working on some environment.

That has been resolved in SFOSv17 RC-1. If you catch such kind of issue with Beta-2, you can disable/enable the rule, to be worked.

Hi Jacob,

We found , service has been misconfigured for Forwarding rule.

Service RDP and "Blue Iris" has been created with Source Port/Destination Port TCP (3389) / (3389), TCP (81) / (81) respectively

Those should be  TCP (1:65535) / (3389)  and TCP (1:65535) / (81). Please update that.

Other point, we have been already reported issue NC-22584, where with Dynamic WAN interface and Port dnat rule, after reboot of the appliance, it is not working on some environment.

That has been resolved in SFOSv17 RC-1. If you catch such kind of issue with Beta-2, you can disable/enable the rule, to be worked.

Thank you! That did it. Im just not sure i ever put in 1:65535 instead of just the actual port name. Is that something new in V17?

Also. I had to delete the whole firewall rule instead of just being able to edit the application rule (from 3389 and 81 to 1:65535) If i tried to edit those in the firewall rule but it gave an error saying that it was being used in a buisness application rule. 

Regards

Jacob

Hi Jacob,

The behavior is from the XG release. The source port should be any, if you don't want to filter from Source IP Address, else it will work only when  Source IP (Any), Source Port (3389), destination ip is your appliance IP  and destination port (3389).

Yes, for you service edit point, the JIRA id is already logged and tracking it via NC-22557

Regards,

Deepti