Thread Info
  • State Verified Answer
  • Replies 10 replies
  • Subscribers 5 subscribers
  • Views 3227 views
  • Users 0 members are here
Options
Suggested

[NC-50136] WAN link manager: BACKUP status RED

twister5800

 Hi,

I have seen it before with v17, but I installed a XG 210 yesterday at home, with v18 EAP1, I keep seeing this:

 

 

 

I can ping 192.168.8.1 when I connect my computer to the 4G router.

 

dgd.log shows this:

DEBUG Oct 27 07:01:48 [8705]: Failed, Retrying(1) Ping : 128.0.0.1
DEBUG Oct 27 07:01:48 [8705]: GW (WAN%5f4G,PortE5) : Waiting for reply
DEBUG Oct 27 07:01:48 [8705]: Current Status : Dead

DEBUG Oct 27 07:01:50 [8705]: Failed, Retrying(2) Ping : 128.0.0.1
DEBUG Oct 27 07:01:50 [8705]: GW (WAN%5f4G,PortE5) : Waiting for reply
DEBUG Oct 27 07:01:50 [8705]: Current Status : Dead

 

Look at the IP, it shows 128.0.0.1 ?!

Should be 192.168.8.1 as it the one that is typed in the rule:

When I change from active/active to active/ backup, dgd.log shows this:

WARNING Oct 27 06:59:56 [7844]: Pingtest, ipv4 bind ipaddress error:1678289088 : Cannot assign requested address
DEBUG Oct 27 06:59:58 [7844]: Failed, Retrying(1) Ping
WARNING Oct 27 06:59:58 [7844]: Pingtest, ipv4 bind ipaddress error:1678289088 : Cannot assign requested address

 

Anyone knows why? :-)

Parents
  • 0

    Hey Martin

     

    Your E5 interface is configured as DHCP,

    Try configuring it to a static IP of 192.168.8.100 and use the 8.1 which I assume is the router as the gateway.

     

    I have seen some strange issues when having a modem infront of an XG if that modem is doing NAT.

    Regards

    Gavin

    Regards,

    Gavin Daniels. DipIT(Networking)

     

     
  • 0 in reply to GavinDaniels

    GavinDaniels said:

     

    Your E5 interface is configured as DHCP,

    Try configuring it to a static IP of 192.168.8.100 and use the 8.1 which I assume is the router as the gateway.

     

    I have seen some strange issues when having a modem infront of an XG if that modem is doing NAT.

    Hi Gavin,

    Thanks for the feedback! - I can confirm this does actually work!!

     

    Thanks :-)

    -----

    Best regards
    Martin

    Sophos XGS 2100 @ Home | Sophos v20 Technician

  • 0 in reply to twister5800

    Hey,

    Glad to help.

    I believe that it is something to do with the underlying IP address tables when the system starts, the interface comes up, not having a static address uses 128.0.0.1 until DHCP completes, but the gateway address does not reset for the Wan Link manager after DHCP init.

     

    Pretty sure that was what I partly debugged in the V16 firmware where I encountered the issue, so always used external interfaces with static address'.

     

    Regards,

    Gavin Daniels. DipIT(Networking)

     

     
Reply
  • 0 in reply to twister5800

    Hey,

    Glad to help.

    I believe that it is something to do with the underlying IP address tables when the system starts, the interface comes up, not having a static address uses 128.0.0.1 until DHCP completes, but the gateway address does not reset for the Wan Link manager after DHCP init.

     

    Pretty sure that was what I partly debugged in the V16 firmware where I encountered the issue, so always used external interfaces with static address'.

     

    Regards,

    Gavin Daniels. DipIT(Networking)

     

     
Children
Unfiltered HTML