Take the 2-minute tour ×
Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

I think I had a bad idea this night.

I flashed ftp://dd-wrt.com/others/eko/BrainSlayer-V24-preSP2/2013/01-01-2013-r20453/tplink_tl-wa901ndv2/factory-to-ddwrt.bin into a brand new tplink-wa901nd v2, and now it doesn't look very good. The power led is on, and also on is the LAN led when I attach the cable to my computer but the WLAN and SYSTEM are now always off.

When I attach the cable to my computer, I cannot access http://192.168.1.1. I haven't much experience on bricks, but this looks like one.

doing a netscan on my network I see:

network router  Router  192.168.1.1 MAC-ADDRESS 
network router  Router  224.0.0.1   MAC-ADDRESS 
unidentified device hidden  224.0.0.251 MAC-ADDRESS 

I tried to telnet and ssh 192.168.1.1 with no luck.

Any advice?

UPDATE

I tried to do the 30/30/30 reset, and nothing changed.

I tried the tftp transfer using the original firmware from tp-link; this is the output:

tftp> connect 192.168.1.1 
tftp> binary
tftp> rexmt 1
tftp> timeout 60
tftp> put wa901nv2_en_3_12_16_up(120224).bin
Transfer timed out.

basically, it's not answering to tftp (and timing out).

I tried also immediately after a reset, during boot time. no luck.

share|improve this question
    
You can't brick these routers without overwriting the CFE. If you just flashed the firmware, it's recoverable. You have to push a new firmware at it using tftp right as it's booting up. The process is explained here. –  David Schwartz Jan 5 '13 at 2:36
    
the router doesn't even respond to ping. port 21 is not open. I did a port scan and nothing is open between port 1 and 1000. –  Luigi R. Viggiano Jan 5 '13 at 3:17
    
It won't respond to pings and it won't respond to a port scan. The only thing you can do is push a tftp to it. It will, however, respond to ARP requests, so you can confirm that it's working that way. –  David Schwartz Jan 5 '13 at 3:18
    
first of all, thank you for the help. I tried the tftp, it tells me "Tranfer timed out". –  Luigi R. Viggiano Jan 5 '13 at 3:24
    
That's normal. You have a narrow window to get the tftp started in. Keep trying around reboot time. If you got an ARP reply, it will work. –  David Schwartz Jan 5 '13 at 3:35
show 1 more comment

2 Answers

The post is a bit old and muy english is not the best, but i got the same problem and solved it by forcing to resolve the ip to the rigth mac address.

In windows xp command line, type arp -a and you gonna see that the ip 192.168.1.1 is resolved to a mac address that its no the same the router got on its label. Type arp -d 192.168.1.1 to remove the entry and then arp -s 192.168.1.1 xx-xx-xx-xx-xx where xx... is the mac address signaled on your router label.

Then try to get up to the router configuration typing 192.168.1.1 in your browser and it should work.

Just note that it only work for me using WiFi connection.

share|improve this answer
add comment

It seems the DD-WRT firmware for the TP-Link WA901ND disables the LAN port. Refer to posts here: http://www.dd-wrt.com/phpBB2/viewtopic.php?t=71721&postdays=0&postorder=asc&start=180

My experience with this device is the same.

The good news is that you should be able to connect to the wireless interface. The default wireless SSID is dd-wrt, no security (no passphrase) and uses an IP Address of 192.168.1.1.

I was successfully able to connect to the access point this way and see the DD-WRT firmware had installed. I tried playing with it to enable the LAN port again, but it seems the firmware is no yet ready for production. Without a LAN port, it is fairly useless!

You can also re-flash it back to stock TP-Link firmware through the web interface over wireless. Just download the webrevert firmware from DD-WRT and you should be able to access it again on the default settings (192.168.1.254) over the LAN port.

share|improve this answer
    
Thanks, I didn't notice the SSID was available. I have the dd-wrt wifi SSID but after connected the IP 192.168.1.1 doesn't respond to any port (ssh, http, telnet, ping). I see the IP 192.168.1.1 is assigned to the router, but I can't connect in any way. I tried to port scan it, but no results. –  Luigi R. Viggiano May 18 '13 at 14:24
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.