Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 4 replies
  • Subscribers 28 subscribers
  • Views 8659 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

Gateway not working when configure as backup

Speatech

Hi,

Our WAN Link Manager configuration was working fine until today. If I disconnect the main ISP network cable, the second ISP link takes over. Wan Link Manager shows the backup gateway as activated. Windows 10 is showing that I am connected to the internet even if I am not. I can ping the modem but not the 8.8.8.8 .

If I set this second gateway as Active rather than Backup, it will work.

What could be the issue? 

Here are our configurations:



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

    Not sure if its related but it looks like in your failover rules you have the gateway set to ping its own address as a test.  I'd recommend pinging something else, like the default gateway or a reliable DNS service like Google.  

  • 0 in reply to Bill Roland

    That is not its own address (192.168.2.1) but the next gateway(192.168.0.1). And the ping to this address works fine from the router. Yeah if the firewall is used as a gateway to the WAN, it is better to ping to the outside since a modem (next gateway) could work fine but the link to the ISP could be down.

    In my case, the cable is disconnect from the main ISP (port 2). The log mention that there is no connection at all. 

    I though it could be a firewall rule issue. But I can surf the internet if I set the backup ISP gateway as active or force the weight at 1. Obviously something to do with the WAN link manager.

  • 0 in reply to Speatech

    What definately can be a problem is the double NAT over the backup connection. You do MASQ/SNAT to its interface IP in the 192.168.0.0/24 network and the router on 192.168.0.1 will do it, too to it‘s public IP.

    I would try to not use MASQ on this connection and set the failover condition to any, not gateway x on port y. Maybe you have to set up a static routes to your internal networks ( to the XG’s IP in the 192.168.0/24 network) on the 192.168.0.1 gateway.

Reply
  • 0 in reply to Speatech

    What definately can be a problem is the double NAT over the backup connection. You do MASQ/SNAT to its interface IP in the 192.168.0.0/24 network and the router on 192.168.0.1 will do it, too to it‘s public IP.

    I would try to not use MASQ on this connection and set the failover condition to any, not gateway x on port y. Maybe you have to set up a static routes to your internal networks ( to the XG’s IP in the 192.168.0/24 network) on the 192.168.0.1 gateway.

Children
No Data