Hi all,
My CPE610 just got delivered this morning, i downloaded the factory file to flash to the node, the web interface of the tp link rejected it, so did it via the PXE server route, now the node looks like it is just in a reboot loop after taking the renamed "recovery.bin' file.
Ideas?
Wade
VK1MIC
Is it likely v 2 of the 610 will be supported?
Are you able to recover back to the standard TP-Link software?
If so a copy of the boot/dmesg information would help in creating a version for th TP-Link CPE610 V2
Please post a photo of the version sticker with the serial number blanked out.
happy to provide.
Start by providing the same information that was given in this thread https://github.com/aredn/aredn_ar71xx/issues/219
Enable ssh on the device and then connect to it using ssh.
Thank you
Once more item. What is the output of
cat /dev/mtdblock2 | grep CPE610
CPE610(TP-LINK|UN|N300-5|00000000):2.0
So I have what I would assume would be a cpe610 v1 since I have been using it for a while. I upgraded to Arden mesh v 3.20.3 a few months ago. After upgrading I could not access my node. I assumed some thing went wrong and would have to look into it later since I was busy. I picked it back up today and ended going clear back to factory tp-link software via tftp boot. I think tried to put the 3.20.3 on again and I am also have what seems like a reboot loop. I can see the node come up I get a link and then the link goes right back down. I am not sure if the node is in a reboot loop or if the Ethernet is just bouncing. I see the same behavior if it is plugged in to a switch or direct to pc.
Any thoughts on how to debug? i also looked for some nightly builds but did not see any for this model.
Scott
This bug was resolved in the Nightly builds
The Image can be downloaded here
http://downloads.arednmesh.org/snapshots/trunk/targets/ath79/generic/