Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 2 replies
  • Subscribers 2 subscribers
  • Views 498 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Routing

drbrown305
My External interface is 00.00.00.41/29 to 00.00.00.45/29
What I want to do is route HTTP to a different machine on my internal interface.
Ex: http://00.00.00.44/29 to http://192.168.1.49/28
     http://00.00.00.45/29 to http://192.168.1.48/28

I haven't figured out how to do so.

Any Ideas?


This thread was automatically locked due to age.
Parents
  • 0
    You need to configure the upper IPs as additional addresses on your WAN interface. Always use /32 as subnet mask, e.g. 00.00.00.45/32.

    Then you can use these definitions for a DNAT.

    ----------
    Sophos user, admin and reseller.
    Private Setup:

    • XG: HPE DL20 Gen9 (Core i3-7300, 8GB RAM, 120GB SSD) | XG 18.0 (Home License) with: Web Protection, Site-to-Site-VPN (IPSec, RED-Tunnel), Remote Access (SSL, HTML5)
    • UTM: 2 vCPUs, 2GB RAM, 50GB vHDD, 2 vNICs on vServer (KVM) | UTM 9.7 (Home License) with: Email Protection, Webserver Protection, RED-Tunnel (server)
Reply
  • 0
    You need to configure the upper IPs as additional addresses on your WAN interface. Always use /32 as subnet mask, e.g. 00.00.00.45/32.

    Then you can use these definitions for a DNAT.

    ----------
    Sophos user, admin and reseller.
    Private Setup:

    • XG: HPE DL20 Gen9 (Core i3-7300, 8GB RAM, 120GB SSD) | XG 18.0 (Home License) with: Web Protection, Site-to-Site-VPN (IPSec, RED-Tunnel), Remote Access (SSL, HTML5)
    • UTM: 2 vCPUs, 2GB RAM, 50GB vHDD, 2 vNICs on vServer (KVM) | UTM 9.7 (Home License) with: Email Protection, Webserver Protection, RED-Tunnel (server)
Children
No Data
Cookie Information Banner