If not would anyone be willing to put some money into this. By my calculations we only need about 10 people paying $7-10 or even less if we get more people. Biggest problem is going to be the shipping.
Is the DD-WRT team willing to receive the money into PayPal and then go out and buy one in Germany? As this would cut the cost down. It would also give some security to the investment.
Posted: Fri Aug 31, 2012 19:56 Post subject: Now: the chance to make a donation!
Hello guys I just stumbled upon this thread and by coincidence found an auction on ebay-Germany that sells an TL-WA901ND Ver. 2.2!
So if anybody of you who owns a V.2 and wants to get it supported by donating one to the developers, this is your chance. Since the seller is located in Germany, postage is only 4,90 € to the Germany-based developers.
Didnt work correctly for me. Updated firmware using factory-to-ddwrt.bin, says it updated successfully then on restart I am unable to log in. Ive tried 192.168.1.254 and 192.168.1.1 but nothing.
I'm having the same problem like the others...I installed the fw and after restart just DHCP seems to work. No reply to ping, no web administration GUI, no telnel....
Please can somebody tell me how restore it?
Posted: Fri Oct 12, 2012 23:26 Post subject: Thank goodness for ymodem and a serial cable! Recovery info.
Well, I installed it as well... It's been an adventure. There is hope after flashing this, but it takes some technical skill and soldering skills. Since I'm so shaky, I asked my father to solder the cable on and it's worked properly.
I've setup a serial cable to help troubleshoot it.
The pins use a standard TP-Link pin out. I have a serial convertor that accepts 3-5v DC to power the MAX232, so I just stole some power from the TP-Link to power it.
TFTP via uBoot wouldn't work. It seemed to not bring eth0 properly, hence my requiring the use of a serial cable.
The device DOES boot up, it seems that it doesn't handle the networking setup properly. I don't feel like troubleshooting it at this point in time
After I login via serial, I find that the network devices are configured. However, there's no default route setup.
If I do a "ifconfig eth0 192.168.16.1" it sets up the network connection.
I believe this to be a firewall or routing issue that's causing this problem.
The bridge appears configured properly, but then it doesn't accept incoming connections.
So, going via eth0, I'm able to reach the web interface and ssh after manually configuring the network.
Since I didn't want to troubleshoot too much (aka: get my room back online), I've recovered the original firmware.
The web interface wouldn't allow me to load the firmware obtained from TP-Link via the Upgrade section... I kept getting a "Bad trx header" error.
There was no way for me to get the firmware to the device other than ymodem over serial.
Steps I took to recover:
THIS REQUIRED A SERIAL CABLE
