Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 3 replies
  • Subscribers 2 subscribers
  • Views 2602 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

Adding a NULL route to DNAT

Mark_D_01
Hi all
As a temp measure at a customers site I want to add a NULL address ie 0.0.0.0 or 127.0.0.1
to a dnat rule until I can get the customer to supply me with IP address of incoming address's for a Terminal Server somebody else has used any with auto rules.

Why can I not add a Host 0.0.0.0 or 127.0.0.1

Thanks

Mark


This thread was automatically locked due to age.
Parents
  • 0
    Because these are reserved addresses which can't be used in a DNAT. Why don't you simply add a "fake" (non-existent) address?

    ----------
    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
    Because these are reserved addresses which can't be used in a DNAT. Why don't you simply add a "fake" (non-existent) address?

    ----------
    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