@ google "disable firewall >your linux dist<"
since the FW reports the router activity, is looks like it's doing what's it's supposed to.
1 Like
new things, first time I see the firmware in the system log
Mar 04 09:54:29 e6530 systemd[1]: Starting Network Manager Script Dispatcher Service...
Mar 04 09:54:29 e6530 dbus-daemon[672]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Mar 04 09:54:29 e6530 systemd[1]: Started Network Manager Script Dispatcher Service.
Mar 04 09:54:29 e6530 nm-dispatcher[14918]: req:1 'up' [eno1]: new request (1 scripts)
Mar 04 09:54:29 e6530 nm-dispatcher[14918]: req:1 'up' [eno1]: start running ordered scripts...
Mar 04 09:54:29 e6530 nm-dispatcher[14918]: req:2 'connectivity-change': new request (1 scripts)
Mar 04 09:54:30 e6530 in.tftpd[14944]: RRQ from 192.168.0.1 filename ArcherC2600_1.0_tp_recovery.bin
Mar 04 09:54:36 e6530 kernel: e1000e 0000:00:19.0 eno1: NIC Link is Down
Mar 04 09:54:37 e6530 dhclient[14958]: Internet Systems Consortium DHCP Client 4.4.1
Mar 04 09:54:37 e6530 wicd[669]: Internet Systems Consortium DHCP Client 4.4.1
Mar 04 09:54:37 e6530 wicd[669]: Copyright 2004-2018 Internet Systems Consortium.
Looks like the flash might have worked, if you actually had the file there.
nope, cause the connection stops..
r 04 10:14:26 e6530 in.tftpd[2885]: RRQ from 192.168.0.1 filename ArcherC2600_1.0_tp_recovery.bin
Mar 04 10:14:33 e6530 kernel: e1000e 0000:00:19.0 eno1: NIC Link is Down
Mar 04 10:14:33 e6530 dhclient[2902]: Internet Systems Consortium DHCP Client 4.4.1
But that would happen if the UL is successful, and the router reboots.
no no, all that is about 2 sec..... and still the same for the router
maybe I dont have the good timing to hold and release the reset button
:26 request for file, :33 reboot, looks pretty normal to me.
If you can see the request for the file coming in, then you've done the right thing.
Note, you will not be able to access the c2600 afterwards, unless you switch back to DHCP, or set a static IP in the 192.168 1 subnet, instead of 192.168.0
When I hold reset, and see the firmware loaded in journal , i release, and the LEDs on router close, and restart.
After that, loose connection, and even after 5 minutes the router is still on the same state, all LEDs are there
How do you know its in the same state, if the connection is lost?
on that router, the 6 or 7 leds on top are not supposed to be all there.....no blinks, all opens.
and there is nothing if I do 192.168.1.1 or 0.1, and yes the DHCP is auto now tom test it
They won't blink, if there's no traffic.
I know but usualy, on my router I only have power, wifi and one more, not 6 o7 lights, never seen that in 6 months.....
also, the tftp is not working all the time, I got that errors pretty often
sudo systemctl restart tftpd-hpa.service
Job for tftpd-hpa.service failed because the control process exited with error code.
See "systemctl status tftpd-hpa.service" and "journalctl -xe" for details.
Apples and bananas, you can't compare the led function between stock and openwrt.
Then run the tftpd in foreground, to be able to clearly see what happens.
Maybe I could see the log now?
Which log, where?
About ftpd
well,
man tftpd, apply the parameters and run it in foreground.
The next step would be listening in with (e.g.) wireshark, to check that the whole file was indeed transferred. But from the outside (in.tftpd[2885]: RRQ from 192.168.0.1 filename ArcherC2600_1.0_tp_recovery.bin) it appears as if it would be working, make sure that you're serving the correct file (OpenWrt factory) as ArcherC2600_1.0_tp_recovery.bin.
If this doesn't succeed, the next escalation step would be attaching a 3.3V based USB2serial adapter, to see what's happening on the router.
1 Like
I was trying with the TP link oem firmware
Thank you all.
I got it.
I took 15 minutes to flash.
I mean, before that, I waited 5 minutes and nothing happened, so I started from scratch. But this time I let go for 15 minutes and the router restarted and it was flashed.
Thank you very much.
1 Like