[Solved] INACCESIBLE AFTER CHANGING IP ADDRESS: TP-Link Archer C-25

After correctly installing lede and luci for this router, I was able to access its configuration without any problem... And everything worked fine.

However, after changing the IP address from 192.168.1.1 to 192.168.111.1 to be able to repeat a network, the router has become inaccessible: neither directly with the new address, nor in failsafe mode, nor in bootloader recovery mode, nor resetting to defaults.

  • Router: TP-Link Archer C25 vers. 1
    Three Buttons: Power On/Off - Hole Reset - WPS / Wi-Fi On/Off

  • Lede: https://downloads.lede-project.org/snapshots/targets/ar71xx/generic/lede-ar71xx-generic-archer-c25-v1-squashfs-factory.bin, installed without problems from the firmware upgrade of tp-link.
    
  • Luci, installed without problems with internet from Linux terminal.
    
  • At that time the router was accessible through the ip address 192.168.1.1 and Luci.
    
  • The ip address was changed to 192.168.111.1 and it was accessible at that time.
    
  • The router is turned off.
    
  • The router is turned on and turns out to be inaccessible by any means.
    

    This is the sequence of leds that the router turns on when i powered it:

  1. Power On: fixed for 5 seconds
  2. All Leds On: 1 second
  3. Power On: fixed for 5 seconds
  4. All Leds On: 1 second
  5. Power On: 1 second
  6. Power On: 0.1 second blinking rhythm during 2 seconds
  7. Power On: a slow 0.2 second blinking rhythm during 7 seconds
  8. Power On: fixed.

This has happened with two different routers of this model... What can I do to solve it?

Start with the LEDE documentation...

https://lede-project.org/docs/start

In failsafe mode ( gear LED blinking rapidly) the address will go back to 192.168.1.1.

Failsafe mode documentation...

https://lede-project.org/docs/user-guide/failsafe_and_factory_reset

Thanks... but I did not see another similar problem...

yes... i know it... i can't connect in failsafe mode from 192.168.1.1

Try the steps here for doing a hard reset…

https://www.dd-wrt.com/wiki/index.php/Recover_from_a_Bad_Flash

Thank you ... now I will try this method ...

I've been working with Openwrt for years ... is there a recovery mode like 192.168.0.66/24?

this method does not work either...

any other idea?

Reflash using TFTP.

See this tutorial…

http://forum.tp-link.com/showthread.php?81462-How-to-recovery-the-router-when-you-bricked-it1

In your case, you would rename the LEDE firmware file archerc25v1_tp_recovery.bin

thank you for your attention ... now I have to work ... I will try it tomorrow and I will put the results here ...

There is no such thing as 30/30/30 reset in LEDE or OpenWrt.

https://lede-project.org/faq/303030_reset

Interesting...why is that?

Seems a lot more straight-forward than watching LED's...especially for newbies.

The 30/30/30 is more folklore than anything else. On any modern router, the reset button is merely a GPIO input to the CPU. Pressing it with no power applied to the router can't possibly do anything.

There are 3 things the reset can do:

Bootloader recovery mode. This has nothing to do with LEDE or any other firmware, it depends on the bootloader. Pressing the reset button while the bootloader is still running can do various things such as TFTP recovery or a CFE webpage recovery. When a bootloader recovery mode has been activated, the bootloader does not attempt to boot the firmware image. Instead it becomes a client or server to accept a new firmware which will then be flashed.

Failsafe mode. Pressing the reset button at a particular time early in the LEDE boot process will prevent the overlay partition from being mounted. This causes the default configuration files in the squashfs to be used, instead of the user's previous (mis)configuration. It is useful for advanced users who can ssh in and repair the damaged configuration rather than the final option of...

Reset to defaults. After LEDE has fully booted, pressing the reset button for more than 5 seconds then releasing it will cause a reboot and erase the overlay partition. Any user installed or configured settings are permanently removed and LEDE is ready to reconfigure as if it has just been installed.

1 Like

30/30/30 still seems to be alive and well...folklore or not.

Several router vendors still publish it as a troubleshooting technique.

I've used it to reset stock firmware on TP-Link routers (made within the last couple of years), and DD-WRT firmware.

Good info though...thanks.

is it a lease issue on your computer? you can assign a static ip address 192.168.111.9 whatever, see if that helps. how many devices have you tried it from?

No ... it's not a lease problem on the computer ... the assignment of a static IP address does not solve access to the router ...

For two, almost three, years we have worked with Openwrt and tp-link 841n and we never had a problem of this type to change an ip address ...

In fact, that same ip address with Openwrt, is used by about 100 devices ...

It's the first time we tested Lede and it's the first time we worked on TP-Link Archer C25 ... and we've already taken two bricked routers after changing their ip address ...

In this case this does not happen. It was a method I usually used when I installed an incorrect version of Openwrt for the TP-Link 841n. It does not work here...

This does not work either. Putty can not access from 192.168.1.1/24. Nor from a Linux terminal.

This does not work, either.

I'm going to try to give all the data that I can think of in this case to see if anyone else comes up with what else I could do ...

  1. Router: TP-Link Archer C25 vers. 1
    Three Buttons: Power On/Off - Hole Reset - WPS / Wi-Fi On/Off

  2. Lede: https://downloads.lede-project.org/snapshots/targets/ar71xx/generic/lede-ar71xx-generic-archer-c25-v1-squashfs-factory.bin, installed without problems from the firmware upgrade of tp-link.

  3. Luci, installed without problems with internet from Linux terminal.

  4. At that time the router was accessible through the ip address 192.168.1.1 and Luci.

  5. The ip address was changed to 192.168.111.1 and it was accessible at that time.

  6. The router is turned off.

  7. The router is turned on and turns out to be inaccessible by any means.

  8. This is the sequence of lights that the router has when it is turned on:
    · Power On Led: fixed for 5 seconds
    · All Leds On: 1 second
    · Power On Led: fixed for 5 seconds
    · All Leds On: 1 second
    · Power On Led: 1 second
    · Power On Led: 0.1 second blinking rhythm during 2 seconds
    · Power On Led: a slow 0.2 second blinking rhythm during 7 seconds
    · Power On Led Fix.

Try downloading and running Advanced IP Scanner and see if it finds the router...

http://www.advanced-ip-scanner.com/

In the IP range 192.168.0-254.0-254 can't find it... (grrrrr)

By the way ... this is an interesting program.