Asus WL-500g Deluxe bricked
Hi folks!
It seems like i bricked my brand new Asus WL-500g deluxe while playing with OpenWRT WhiteRussian RC1.
I messed up the firewall rules and locked my self out.
I did "iptables -F", but the default policy for INPUT is DROP... sad
Unfortunately, rebooting the router did not make it accessible again.
I tried to reflash the firmware but tftp says Timeout.
The ASUS firmware utility doesn't help either.
Any ideas are welcome!
Edit: The router responds to arp request, but not to ping.
Dead wl-500gP, restore button not working
Hi there,
I recently flashed my wl-500gP with Olegs pre4 and it worked for a few minutes. I was just transfering data via samba onto the external harddisk when it passed out and did not respond anymore. I cannot enter the restoration mode, when I press the restore button and plug in AC it reacts just as if I not push the restore button at all. I read similar effects on other routers of the wl-500 series and also read something about pin 10. Is there a similar workaround for the 500gP?
Any help would be appreciated!
Thanx in advance
sMiLe
WL500g Premium, brick & wl500g-recover.trx
Hi,
I have just bought a WL500g Premium router.
And on the 1st day I have lost control over it: flashing with OpenWRT (worked), then trying some network settings ... and it stopped responding.
Before I broke it (even after flashing with openWRT) I could see it's wireless interface (appeared on my Windows box, I could recognize it by MAC), I could also work with SSH over one of 4 LAN ports.
Then after changing some nvram parameter is ttopped responding.
No ping, no wireless interface.
Blind.
But hapily it still accepts tftp upload using the WAN port (lan port do not work although the port lights seem to flash as expected).
Using WAN i could upload some firmwares, but I found that only after using
wl500g-recover.trx (as described here http://wl500g.info/showthread.php?t=515 )
it constantly responds for pings to 192.168.1.1 on WAN (LAN ports are quiet).
But I cannot access it using telnet or ssh. These ports do not respond.
I have also tried the wl500g-clear-nvram.trx but with no success - after uploading it, and then some other firmware (eg. the wl500g-recover.trx firmware) - I still did not go any further.
Does telnetd start only on LAN interfaces (not responding for me) that I cannot access it?
How to enable telnetd on WAN using 192.168.1.1 ?
Any other firmware?
Now only ping works, but I cannot reset any settings, nothing ...
Any help?
Darek
No new posts wl-500g premium bricked -> no power LED at all
Hello all,
I know this may be slightly off topic, because I was using dd-wrt rather than Oleg's firmware but:
Last night I got v23 SP2 ASUS VPN version running on my wl-500. I initially set the clockfreq to 300 (by doing nvram set clkfreq=300, then nvram commit, the reboot).
Box came back up fine, reported 300mhz (cpuinfo).
I then proceeded to enable jffs, usb support, knockd, etc.
For jffs, the original command line commands didn't seem to work, so i grep'd nvram show for all jffs variables, and set the following to 1 (it worked then for a while after this... and through other reboots.. so I modified the wiki's for the subject)
nvram set jffs_mounted=1
nvram set enable_jffs2=1
nvram set sys_enable_jffs2=1
nvram set clean_jffs2=1
nvram set sys_clean_jffs2=1
nvram commit
reboot
So, a couple of hours later after getting things figured out a bit with knockd, etc, I noticed that the wireless 'signal quality' was quite poor for the laptop right next to the router (30-55 %, cycling, sometimes dropping).
I decided this was possibly because of the oveclocking or the increase in txpower to 70, so:
1. i decreased the txpower to 30, still no change, so
2. Changed clkfreq to 266.
On reboot, the router never came back- the power LED would stay on. That is not the problem at this point, story continues---
So, the router would still go into recovery mode (by pressing the reset button during reboot), so I knew it was saveable. It would not reply to ping requests.
Then I shorted the solder connection by pin 9 (as listed in the sticky at the top of the forums) for 15 seconds. The power LED went out, and i could again ping the unit YAY! Smile ... WELLLL... Went about my way resetting things. This time I set the JFFS in the web GUI (as well as 'clean jffs'), and the router never came back from reboot.
So, now the power led on the router never lights up, not even if trying to go into 'recovery mode'.
The router does appear to work as a switch still. And with the case off, you can see that the wlan led lights dimly at boot (and stays lit), as do all of the eth connections if a single device is conected (the one led for the connected port is full brightness)
I see on http://www.dd-wrt.com/wiki/index.php/User_talk:Oxo that someone is working on console connectivity to the unit, but the specifics are not listed. It looks like it requires building an external rs232 circuit.
Comments/suggestions anyone?
WL-500gP ... probably really dead!?
Hey guys!
I got myself a bricked router (don't know how it was bricked exactly because I received it in this state from its former user)... still I wonder if someone has an idea as to what course of action to take when the following serial console output is the only thing that the router will output:
----------------------------------------------------------------------
CFE version 1.0.37 for BCM947XX (32bit,SP,LE)
Build Date: ¤@ 6¤ë 12 16:31:07 CST 2006 (root@localhost.localdomain)
Copyright (C) 2000,2001,2002,2003 Broadcom Corporation.
Initializing Arena
Initializing Devices.
rndis0: Broadcom USB RNDIS Network Adapter (P-t-P)
CPU type 0x29006: 264MHz
Total memory: 33554432 KBytes
Total memory used by CFE: 0x80800000 - 0x8089B670 (636528)
Initialized Data: 0x808317E0 - 0x80833EC0 (9952)
BSS Area: 0x80833EC0 - 0x80835670 (6064)
Local Heap: 0x80835670 - 0x80899670 (409600)
Stack Area: 0x80899670 - 0x8089B670 (8192)
Text (code) segment: 0x80800000 - 0x808317E0 (202720)
Boot area (physical): 0x0089C000 - 0x008DC000
Relocation Factor: I:00000000 - D:00000000
Device eth0: hwaddr 00-XX-XX-XX-XX-XX, ipaddr 192.168.1.1, mask 255.255.255.0
gateway not set, nameserver not set
Null Rescue Flag.
Boot program checksum is invalid
Hello!! Enter Rescue Mode: (Check error)
Reading :: TFTP Server.
Failed.: Timeout occured
Reading :: TFTP Server.
Failed.: Timeout occured
[this continues forever]
----------------------------------------------------------------------
Additional notes:
1) Although it seems that an IP address is assigned to eth0 I can not ping the router (of course I have set a static IP in the same subnet on the computer I'm trying to connect from)!
2) The MAC address in the console output above has been altered for this posting, in real life looks like it should.
2) Recovery mode: same output except that it says "Hello!! Enter Rescue Mode: (Forced!)"
3) Pin shorting has not changed anything (Pin 9)
4) Neither TFTP or the ASUS Utility can connect to the router, not even in forced recovery mode.... probably because the router can not even be pinged (cp. point 1).
... sombeody got an idea how I can get some life back into the device?
Warning 2 bricked routers
Hello all,
I managed to brick two brand new wl500gp routers, just call me dum and dumer :). If anyone wants them just drop me a email and i will give you the address so you can arrange pickup (Brisbane).
I strongly recommend anyone considering using the wl500gp with alternative firmware, DD-WRT, OLEG, or OpenWRT to stick with the linksys hardware. These WL500's are technically better but the units are bugger, in that hardware reset and update process do not work very well at all.
I have tried all the methods suggested, reset, Firmware restoration, etc, with the expection of adding a serial port, which is just not worth my time!
I said i was dum not stupid
I do not think i will use the wl500 again, they just are not up to the job. As for giving them away i am not sure how much your time is worth but mine is worth a lot more than the cost of these things.
Lets just say in regard to wl500 I Have the tshiet, i live and learn and now move on!