Thread Info
  • State Suggested Answer
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 27 subscribers
  • Views 9179 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

Create loopback rule for XG itself

Daniel Bingham

Hi,

A very long time ago, I upgraded from V17 to V18.

Today, I decided to hit the magic button about cleaning up unused NAT Rules under Rules and Policies --> NAT Rules.

Since doing that, my loopback to the XG itself has stopped, meaning I can't use my DNS address to get to the XG when internal, I must use the LAN IP. Can somebody please hold my hand on setting up the loopback for the XG itself, please?

Thanks



This thread was automatically locked due to age.
Parents
  • FormerMember
    0 FormerMember

    Hi ,

    Thank you for reaching out to the Community! 

    Loopback rules

    You can create loopback rules from destination NAT rules to allow internal hosts to communicate with other internal hosts over the external IP address or the domain name. For example, create a destination NAT rule to translate incoming traffic to your servers and create a loopback rule.

    To create a loopback rule, specify the following destination NAT rule criteria:

    • Original source: Any
    • Translated source: Original
    • Translated destination: Don’t set to original.

    Reference: NAT rules.

    Thanks,

  • 0 in reply to FormerMember

    Thanks, Harsh.

    I created the rule, but I don't understand the KB article where it says

    Unknown said:
    Translated destination: Don’t set to original.

    What should it be set as? If I create a host to say the gateway, it then blocks all outbound traffic.

Reply Children