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

Using and Configuring DUAL WAN connection with XG 135

Hi All,

We already have one Internet Connection from an ISP having a static IP address , Some time this internet connection is down  due to which whole online services are down. For Safety and high availability we want to get additional Internet Connection from a second ISP with a separate Static IP.

I want to Use only one  WAN connection at a time i.e. Primary and Secondary.

I know that i can use WAN Link Manager for Failover etc. 

my question is about NAT as shown below i.e. SourceNAT as selected under outbound Address has only one IP  and our domain name which is associated with the primary WAN IP address  under go daddy. do i have to change/update it manually each time we move to secondary WAN connection, Please share your experiences. thanks. 

 



This thread was automatically locked due to age.
Parents
  • Hi Vicky,

    I would recommend enabling the gateway soecific nat policy or just masq if you are using the primary address on each interface.

    External DNS can geberally only point at 1 IP, yes so you will have to manually change. There are DNS services out there that can do health checking and dynamically change.

    Emile

  • You want me to do some thing like  the below? 

     

  • Hello Vicky,

    Yes, because that SourceNAT definition is one you have made so unless that IP in the Masq policy can be accessed from both interfaces it will fail on the other interface.

    There is actually a definition called "MASQ" which just uses the primary address of the interface when it routes out, that is what I intended for you to use or if you needed to change the primary IP of the interfaces separately you would use the gateway-specific default NAT policy and configure the NAT policy in the WAN link manager.

    Emile

Reply
  • Hello Vicky,

    Yes, because that SourceNAT definition is one you have made so unless that IP in the Masq policy can be accessed from both interfaces it will fail on the other interface.

    There is actually a definition called "MASQ" which just uses the primary address of the interface when it routes out, that is what I intended for you to use or if you needed to change the primary IP of the interfaces separately you would use the gateway-specific default NAT policy and configure the NAT policy in the WAN link manager.

    Emile

Children