![]() I even tried deleting the WAN Failover app and then re-installing it with no luck. I tried completely deleting all the settings and setting them up again with no luck. ![]() Without this working I can't get my 4G backup connection to automatically take over connection if my VDSL connection drops off. I've tried just ignoring the test run and setting up the test in a few different ways and then saving it but that just leads to WAN Failover then believing each WAN is disconnected. I also get an error message if I click on the "generate suggestions" button, suggesting that for whatever reason the WAN Failover feature has absolutely zero internet connectivity. (I tested local IP's and loopback and that does result in successful test) If you are unable to ping the local loopback adapter, TCP/IP might need to be reloaded or reconfigured on the machine you are using. 0.1, and pinging this address will always return a reply unless the firewall prevents it. It's ONLY the WAN Failover app that is unable to ping any external IP at all. In a TCP/IP network, the loopback IP address is 127.0. If I use the Troubleshooting tools under the Network configuration I can ping it just fine. Ask Question Asked 8 years, 5 months ago. Ping the Loopback Address - Type Ping 127.0.0.1 Successfully pinging the loopback address verifies that TCP/IP is both installed and configured correctly on the local client. Fail to ping other ports in the loopback connection. My ultimate goal is to ping lo0:192.20.11.1 on router 'Good'. I advertise the respective networks Lo0 and Lo1 via OSPF, so I am not sure if I can understand whats going on. I've used 8.8.8.8 as a failover test for years now without issue and all of a sudden a couple of nights ago it magically stopped working with no configuration changes at all. When i ping 127.0.0.1 and any address of 127 series (except 127.0.0.0 and 127.255.255.255),i am not finding any difference. The following steps elaborate on how to use the Ping utility to perform progressively more distant tests on network connectivity. From WG4R3 I cant ping Lo0 and Lo1 on WG4R2 and vice and versa. I've also tried 1.1.1.1 which also fails. Many programs requires this to function correctly, such as debuggers, so I do not understand how it was disabled in my setup. When I try to run the test in the configuration. It appears that Debian 8 iptables denied loopback access on localhost in my installation. I've tested on both my VDSL and 4G connections and both of them just pop up an error message: ![]() In addition, after the issue is resolved, I turned the firewall off, the loopback IP is still pingable. Now the loopback IP 127.0.0.1 can be pinged. To confirm this, try running arp -a on your machine, and youll see a list of all the IP addresses that could be found on your LAN. Ok, for a few days now I've got this really weird issue where WAN Failover is unable to ping. I turned off the Firewall, and chose 'Use Windows Recommended Settings', then the Firewall is turned on again. It just means that the arp failed, i.e., the IP address couldnt be located on the LAN.
0 Comments
Leave a Reply. |