Services: Difference between revisions
From Edge Threat Management Wiki - Arista
Jump to navigationJump to search
No edit summary |
No edit summary |
||
| Line 14: | Line 14: | ||
** TCP Traffic from non-WANs to the primary address of each non-WAN interface on the HTTP Port will be forwarded to the local web service to provide services. In the rare event that those ports are required for port forwarding the default HTTP Port can be changed to another port, like 8080. | ** TCP Traffic from non-WANs to the primary address of each non-WAN interface on the HTTP Port will be forwarded to the local web service to provide services. In the rare event that those ports are required for port forwarding the default HTTP Port can be changed to another port, like 8080. | ||
''Note:'' The configured HTTPS port will be forwarded to the local apache process listening on port 443. The configured HTTP port will be forwarded to the local apache process listening on port 80. The '' | ''Note:'' The configured HTTPS port will be forwarded to the local apache process listening on port 443. The configured HTTP port will be forwarded to the local apache process listening on port 80. The ''Access Rules'' will evaluate these sessions post-redirection where destination port has already been altered. | ||
Latest revision as of 17:10, 4 February 2018
Services
The Services tab configures the local services available on the Untangle Server. The Untangle Server hosts an HTTPS and HTTP server (apache) that hosts services like administration, spam quarantine, reports, blockpages, etc.
- HTTPS Port
- TCP Traffic to the primary address of each interface on the HTTPS Port will be forwarded to the local web server to provide services. Often if you only have one public IP (1.2.3.4) and wish to port forward the HTTPS port to an internal service like webmail to an internal machine you will need to move the HTTPS Port to another port, like 4343, so that port can be forwarded to your internal machine. In this case the administration and other HTTPS services will be accessible at "https://1.2.3.4:4343/" and 443 can be forwarded.
- HTTP Port
- TCP Traffic from non-WANs to the primary address of each non-WAN interface on the HTTP Port will be forwarded to the local web service to provide services. In the rare event that those ports are required for port forwarding the default HTTP Port can be changed to another port, like 8080.
Note: The configured HTTPS port will be forwarded to the local apache process listening on port 443. The configured HTTP port will be forwarded to the local apache process listening on port 80. The Access Rules will evaluate these sessions post-redirection where destination port has already been altered.
