Recent content by JohnSmith

  1. JohnSmith

    Release Asuswrt-Merlin 3006.102.7 is now available

    All my connection for firmware updates for all my routers are ethernet only. Since your RT-BE58 Go is an AiMesh Node and NOT setup as the main AiMesh router, I thought maybe that might have something to do with the firmware update failing for me, but I found out that is incorrect. I tested the...
  2. JohnSmith

    Release Asuswrt-Merlin 3006.102.7 is now available

    ASUS just released new firmware today "ASUS RT-BE58 GO Firmware Version 3.0.0.6.102_39125",, so I downloaded their new firmware, extracted their files from the zip, hashed the files, and tried to firmware upgrade the new file, same error as Merlin firmware "It started to "Applying Settings" and...
  3. JohnSmith

    Release Asuswrt-Merlin 3006.102.7 is now available

    Purchased an ASUS RT-BE58 Go for vacations/backup and decided to upgrade its original firmware to Merlin V3006_102.7_2 FW. After setting it up in basic Wireless Router mode, and being able to login to to the GUI, I went to Advanced Settings | Administration | Firmware Upgrade | AiMesh router...
  4. JohnSmith

    WANFailover Dual WAN Failover ***v2 Release***

    I deleted them via SSH, but then I had to go into the "wan-failover.conf" file and blank out the IP address I gave for WAN0. Was looking for an automatic way as part of the script to re-disable it again, which would remove the route created by it. No worries, all back to the way it was...
  5. JohnSmith

    WANFailover Dual WAN Failover ***v2 Release***

    1. If you add a WAN0 or WAN1 Web GUI IP address, and it doesn't allow you to get to the devices portal, are there any troubleshooting steps to try? 2. If you add a WAN0 or WAN1 Web GUI IP address, and then you want those to be "Disabled" again, how do you revert those back, as the logic only...
  6. JohnSmith

    WANFailover Dual WAN Failover ***v2 Release***

    On my AX88U, you go under WAN | Internet Connection | WAN Type (My choices are WAN(WAN0) or Ethernet LAN(WAN1), then under "WAN DNS Setting", click the "Assign" button, which gives you options of a "DNS List", which at the bottom is "Manual Setting", which you can assign IP addresses for DNS...
  7. JohnSmith

    Release Asuswrt-Merlin 386.12 is now available for AC models

    Upgraded RT-AC3100 from V386.11 Final to V386.12 Final via dirty firmware upgrade with no issues.
  8. JohnSmith

    WANFailover Dual WAN Failover ***v2 Release***

    Update from V2.0.5-beta3 to V2.0.5-Final, appears to be working.
  9. JohnSmith

    WANFailover Dual WAN Failover ***v2 Release***

    Update from V2.0.3-Final to V2.0.4-beta1, appears to be working.
  10. JohnSmith

    Release Asuswrt-Merlin 386.11 is now available for AC models

    Upgraded RT-AC3100 from V386.10 Final to V386.11 Final via dirty firmware upgrade with no issues.
  11. JohnSmith

    WANFailover Dual WAN Failover ***v2 Release***

    Are you sure you have an RT-AX88U as per your signature? There is no V386.10 ASUS Merlin firmware for this product, only V386.8 (which I am on), V388.1 and V388.2. My RT-AC3100 uses V386.10. Are you using an AC68U instead as per "gateway wan1 : 192.168.1.1 (DSL-AC68U-8298)"?
  12. JohnSmith

    WANFailover Dual WAN Failover ***v2 Release***

    Had my WAN1 go down over night, and since it was not my primary internet, everything continued along no problem. Saw this error in the debug logs, that may just be a typo in the script that a variable is not being added to the text Mar 31 03:54:19 wan-failover: Debug - HTTP Web Access: 0 [[...
  13. JohnSmith

    WANFailover Dual WAN Failover ***v2 Release***

    More interesting info @Ranger802004 So I hard powered down my ASUS AX88U router (both ISP modems were still powered up), and then powered it back up, and my ISP02 (Secondary WAN) took over as the "Connected" connection, and my ISP01 (Primary WAN) was in "Hot-Standby", but after a minute or so...
  14. JohnSmith

    WANFailover Dual WAN Failover ***v2 Release***

    Had to add the following command: ip rule add from all iif lo to 8.8.8.8 lookup wan0 priority 100 which once added at SSH command line, it allowed the following ping to occur: ping -I eth0 8.8.8.8 which then the FAILOVER occurred. Once FAILOVER occurred, ran command: ip rule del from all...
Back
Top