TP-Link TL-WR710Nv1
DD-WRT v3.0-r48810 std (05/06/22)
GUI install over r40189 on wired connection
Soft bricked
uptime ---> 0
Wireless connection update fails. The device restarts but is still on 40189. Wired connection appears to have soft-bricked the device. I get a short feint green LED flash followed by long bright green LED flash every 5 seconds upon plugging in the router.
Holding reset button for 10 seconds is unresponsive. 30/30/30 reset does nothing. _________________ Delivering pure fact does not mean you are rude. Ignoring social contract in the delivery of pure fact does make you rude.
Now that I have had this running on my router for a couple days and through a couple reboots I'm having an issue with " Start Up Commands" not getting the results expected.
The unit is a TP-Link ARCHER-C7 v5.
I'm trying to populate the hosts file with the static ip's of all the clients. The startup command is a simple
echo "list of ip / hostname pairs" >> /tmp/hosts. I thought it was working because after the first reboot after saving it I was getting the the list of active client names and ip in the status / lan page. But today I noticed that the hostnames were not showing up, this after a reboot last night. I ssh'd into the router and disovered that no host / ip pairs were present other than the router's own. When I tried to run the echo command directly in the "Command" field it had no effect yet other commands like "less /tmp/hosts" produced output.
While still ssh'd into the router I was able to populate the "/tmp/hosts" file using the same command and format as recorded in the "Start Up" command field. Not sure what to do at this point.
TP-Link ARCHER-C7 v5 Daul Band Wifi / Router
DD-WRT v3.0-r48810 std (05/06/22
Linux 3.18.140-d6 #141654 Fri May 6 07:24:51 +07 2022 mips
New DD-WRT install uploaded via WebUI.
Mode: Gateway
Uptime: Day and a half since last reboot. _________________ ARCHER-C7v5 | v3.0-r55460 std | AP Gateway
WNDR4000|v24-52189_NEWD-2_K3.x_mega|Inactive Spare
Well this is a you can't reboot enough after an install. This morning I rebooted the router and the "Startup Command" did run and populate my hosts file. In fact the latency I was initially experiencing seems to have cleared. I think the latency may have been caused by having two MAC addresses for the same client on record. One for when I was wired directly to router and then later the same client was connected via wifi.
jbkt23 wrote:
The unit is a TP-Link ARCHER-C7 v5.
I'm trying to populate the hosts file with the static ip's of all the clients. The startup command is a simple
echo "list of ip / hostname pairs" >> /tmp/hosts. I thought it was working because after the first reboot after saving it I was getting the the list of active client names and ip in the status / lan page. But today I noticed that the hostnames were not showing up, this after a reboot last night. I ssh'd into the router and disovered that no host / ip pairs were present other than the router's own. When I tried to run the echo command directly in the "Command" field it had no effect yet other commands like "less /tmp/hosts" produced output.
TP-Link ARCHER-C7 v5 Daul Band Wifi / Router
DD-WRT v3.0-r48810 std (05/06/22
Linux 3.18.140-d6 #141654 Fri May 6 07:24:51 +07 2022 mips
New DD-WRT install uploaded via WebUI.
Mode: Gateway
Uptime: Day and a half since last reboot.
_________________ ARCHER-C7v5 | v3.0-r55460 std | AP Gateway
WNDR4000|v24-52189_NEWD-2_K3.x_mega|Inactive Spare
I had to retire my ArcherC7v5 today. After a month of tinkering with wifi settings to reduce episodes of extreme latency the router began to drop connections between wired clients on the local lan. Pings with packet loss rates of 40% to 75% between clients both wired and wifi. Fortunately I had my Broadcom WNDR 4000 updated and ready in reserve. I reconnected that router and I'm up and running without issue now.
@the-Joker
Eth0 and wlan0 have different MAC's. So no strangeness in that regards. Sorry if my statement was ambiguous.
When I'm ready to troubleshoot the ArcherC7 I'll start a new thread. I don't think it is the build. _________________ ARCHER-C7v5 | v3.0-r55460 std | AP Gateway
WNDR4000|v24-52189_NEWD-2_K3.x_mega|Inactive Spare
Yes, I guess the rule of thumb is to see if the build comments go beyond 3 pages before it gets pulled.
I did get some helpful debugging scripts out of b49028 if I'm capable of implementing them. _________________ ARCHER-C7v5 | v3.0-r55460 std | AP Gateway
WNDR4000|v24-52189_NEWD-2_K3.x_mega|Inactive Spare
