But if you allow port forward rules to intercept the traffic when Untangle is considering it part of its own functionality, you create a situation where a block page returns another resource. That's bad... real bad.
But if you allow port forward rules to intercept the traffic when Untangle is considering it part of its own functionality, you create a situation where a block page returns another resource. That's bad... real bad.
Rob Sandling, BS:SWE, MCP
NexgenAppliances.com
Phone: 866-794-8879 x201
Email: support@nexgenappliances.com
Just got this from Untangle, WEEKS after everyone has already been screwed:
Dear Valued Untangle Partners and Customers,
We have an important update regarding your NG Firewall configuration, which may require your attention regarding your port forwarding rules.
Ports 80 and 443 are now reserved on all IP Addresses, including aliases in NG Firewall 16. This means that port forwarding on TCP ports 80 and 443 are not functional unless the services are moved to alternate ports. Additional considerations regarding service ports are described in the Untangle knowledge base article What happens when I change my service ports?.
The Untangle Team
Untangle, Inc.
25 Metro Drive
Suite 210
San Jose, CA 95110
Last edited by johnsonx42; 11-12-2020 at 12:52 PM.