running Firmware: DD-WRT v24-sp2 (03/25/13) std was resetted to defaults and upgraded via web to v3.0 [Beta] Build:36698 using Webupgrade wrt160nl-firmware.bin. After the upgrade was finished successfully the router rebooted but never came back. Tried 30/30/30 but without luck. I cannot get an IP via dhcp and with manual IPs (all I could think of) I cannot ping the router.
Current state is that the Power button is blinking on/off constantly.
Please, suggest what steps I can follow to recover if possible?
I am unable to ping the router if I connect directly. Tried almost any possible subnet the router could be in. DHCP also is failing...
You seem to be making this much more difficult than it really is.
Have you tried to TFTP a known good firmware to it?????
If you cannot TFTP firmware to the 160NL then perhaps you may need to use a serial connection......good news there is it should have serial pin header ---- but I doubt you will need that. I've only use serial on the 160NL few times and was always due to messing with some of BS builds ---- never a public released dd-wrt firmware
You seem to be making this much more difficult than it really is.
I cannot ping/reach the router if connected directly => I am unable to TFTP good firmware. I guess serial connection is my only option, correct? Can you point me to the correct guidline and how to do so?
You sound like I am not doing something right. Can you further explain if you can and have time.
sniffed what is received from the router but I am getting only ARP request from the router
Address Resolution Protocol (request)
Hardware type: Ethernet (1)
Protocol type: IPv4 (0x0800)
Hardware size: 6
Protocol size: 4
Opcode: request (1)
Sender MAC address: Cisco-Li_e8:19:59 (c0:c1:c0:e8:19:59)
Sender IP address: 192.168.1.1
Target MAC address: 00:00:00_00:00:00 (00:00:00:00:00:00)
Target IP address: 247.255.255.255
Strange that the linksys is arping for 247.255.255.255 but I was able to see its IP and have configured 192.168.1.2/24
Not able to ping 192.168.1.1 though and after I've set the .2 IP in the same subnet I see only ARP replies from the Cisco Linksys router.
Address Resolution Protocol (reply)
Hardware type: Ethernet (1)
Protocol type: IPv4 (0x0800)
Hardware size: 6
Protocol size: 4
Opcode: reply (2)
Sender MAC address: Cisco-Li_e8:19:59 (c0:c1:c0:e8:19:59)
Sender IP address: 192.168.1.1
Target MAC address: BelkinIn_14:48:42 (58:ef:68:14:48:42)
Target IP address: 192.168.1.2
I've tried to power on the router while holding the WPS key but could not see any TFTP requests or other type of traffic. Does this mean that the router is not trying to download the firmware and debrick itself?
Here is some nmap output
[23:43][~]$ nmap -v 192.168.1.1
Starting Nmap 7.40 ( https://nmap.org ) at 2018-10-16 23:44 EEST
Initiating Ping Scan at 23:44
Scanning 192.168.1.1 [2 ports]
Completed Ping Scan at 23:44, 0.00s elapsed (1 total hosts)
Nmap scan report for 192.168.1.1 [host down]
Read data files from: /usr/local/bin/../share/nmap
Note: Host seems down. If it is really up, but blocking our ping probes, try -Pn
Nmap done: 1 IP address (0 hosts up) scanned in 0.10 seconds
[23:44][~]$
[23:44][~]$ nmap -Pn 192.168.1.1
Starting Nmap 7.40 ( https://nmap.org ) at 2018-10-16 23:44 EEST
Nmap scan report for 192.168.1.1
Host is up (0.00017s latency).
All 1000 scanned ports on 192.168.1.1 are filtered
Nmap done: 1 IP address (1 host up) scanned in 0.23 seconds
Joined: 28 Jun 2011 Posts: 580 Location: Vilnius, Lithuania
Posted: Wed Oct 17, 2018 15:18 Post subject:
vmrv wrote:
I've tried to power on the router while holding the WPS key but could not see any TFTP requests or other type of traffic. Does this mean that the router is not trying to download the firmware and debrick itself?
yea I forgot to write type 'go' in the ReadMe.txt after it is flashed but tis in my serial-log.txt
Copy to Flash... write addr: bf040000
done
ar7100> go
lol, I'm gonna have to do it again to mine, had to do it last time because the firmware would not allow upgrading or downgrading, recovered it to one that would, waited for a new firmware and it did it again... ffs lol _________________ TPLINK TL-WR2543ND (5GHz)
WRT160NL (2.4GHz)