was trying enabling the extra 16 mb of ram think I mist typed something, my falt for not double checking things.
a little knowledge is very dangeros
thanks
Printable View
was trying enabling the extra 16 mb of ram think I mist typed something, my falt for not double checking things.
a little knowledge is very dangeros
thanks
Well yesterdat i had no powerlight too, but after an hour , i put the power-connector in the router and it suddenly got powered, but i think u already tried that
@Oleg
Yesterday I bought an ASUS 500g deluxe. Because the serial number starts with 4c I decided to upgrade unit bootloader. I followed your instructions on this forum step by step and it everything went ok. The process goes exactly as you describe ending with resetting the unit to defaults. After that I upgraded the firmware to 1.9.3.5 beta.
When I was ready with these procedures I putted the unit in AP-mode; my ADSL-modem is acting as DHCP-server. Unfortunately I had now a problem which there was not before. In AP-mode the WAN port is dead (however the LED is burning). It doesn't matter if I instruct the unit to get an IP-address from the DHCP-server or if I give the unit an appropriate static IP-address. Downgrading the unit to firmware 1.8.2.1 doesn't help; the problem persists.
In Home Gateway mode the WAN port not dead. The WAN port is than working normally.
What should I do now. If I put the cable of my ADSL-modem in an LAN port everything is working fine. But when doing that I loses one LAN port which I need for another PC; in that case I have one LAN-port to short.
Oleg, can you help me out?
Added this to Known Bugs Section.
I believe this should be fixed by ASUS in the firmware.
I will also try to fix this in the custom firmware.
have just taken 3 hrs to read thru this forum, and now my head feels just like my WL-500g: DEAD.
upgraded from 1.8.1.9 to 1.9.2.7, worked fine but WLAN a bit slow. dealer said to upgrade to 1.9.3.6 (beta but from ASUS website), and that apperently killed the unit. no access the normal way, and even the recovery tool (firmware restoration) comes back with either no unit found, or starts to update for a second or two, then FAILED, CHECK CONNECTION (wired !).
i think i have tried all i could find, but there are so many ifs and buts in the mssgs here in the forum that at the end i know less than intitially. all versions of pressing reset and turning on, trying the CLEAR-NVRAM version, the IP adresses given (where in XP to enter anyhow?), and whatever.
does anybody here have some kind of summary, some kind of steps a simple user like me can follow, step by step, without going thru a million websites that to me seem to make it only more confusing, most of then telling different stories anyhow?
i have used the SEARCH function, i have read thru everything i could, but ... the blasted thing still plays dead.
and i am supposed to have it installed by monday ...
greetings - heinz -
Network Connections > Local Area Connection > Right-click > Properties > Internet Protocol > Properties
have been trying this now 5 times:
>> 1. pull power cable and wait 20 seconds
>> 2. keep button pressed and connect power cable: power led should flash
>> 3. ping 192.168.1.1 should reply else redo steps 1 and 2
no chance: pinging comes back HOST NOT REACHABLE.
so also no further steps possible. any ideas?
greetings - heinz -
tomilius, thats where i thought it was, and where i had entered it, but no difference in the results: none.
on the ping i now get TIME LIMIT EXEEDED
greetings - heinz -
Come to think of it, I had this same problem. Leave your router unplugged for an extended period of time for it to cool off. Try... an hour. If that doesn't help, leave it unplugged overnight.
I put my router in the freezer once for about 3 minutes. Couldn't hurt, I suppose.
Just to also mention it here...
You did try leaving the router off for a while, right?
10-20 minutes at a time, should be enough, no?
i have now become something like an acrobat, pressing an almost non-existing button in the back, at the same time plugging in the powercable, and all the time watching the LED in the front. while with my third hand selecting files on the computer and pressing ENTER. forget the mouse ...
greetings - heinz -
PS: one thing that i cant quite figure out: does not occasionally somebody of ASUS (sales/service) check this most competent board? they MUST have a foolproof method to reset a dead unit, they would not have the time to try 32 systems how to get back to recovery mode and to flash a new system.
i was not trying to be ironic when i said 'competent' to the members of this board, but it just seems that too many opinions sometimes overshadow the real (and often simple) way.
The truth is, most people don't have as much trouble as you do. I didn't have your EXACT problem, but my router was doing something to the effect of sending out 1 packet per second (really). I unplugged it and plugged it back in but that didn't help. I had to leave it unplugged--all night. Sure, 10 or 20 minutes sounds reasonable... but it was 2 AM or so when I was doing this anyway, and I had thought it was broken so I just left it unplugged all night and it worked normally in the morning.
It's not that there's a single, simple, working way to solve these problems. It's situation-dependent, I'd expect.
But here's the guide that should get it working or your router is toast (probably overheated and melted something):
1. Leave the router completely unplugged for 12 hours at room temperature or below.
2. Boot the router with the button on the back held down.
3. Notice the blinking LEDs.
4. Now, set a wired computer's IP address to anything in the 192.168.1.0 subnet (probably other than 192.168.1.1--192.168.1.10 works).
5. Run the ASUS Firmware Restoration utility.
6. Use it to upload some firmware--some good firmware, not corrupted or such.
That stuff should work under any circumstances... or your router is toast.
tom, did just that. night in the cooler DID make a difference, at least it was found and recognized.
the update with the 1.8.1.9 version the also started, also a new feeling. it went for about 15-20 seconds, then broke of with the usual FAILED error and asking me to check the connection.
then unplugged it, held RESET for 10 seconds, turned it on again, and now it
is recognized in DISCOVER, but when i check the version, it shows 1.9.2.7,
which is the one i had tried to flash on saturday, and which broke the whole thing.
what do i have now? half a 1819, half a 1927? a corrupted one? setup and all
screens show up normally, but i will only have a chance to check operation late this afternoon. and as a newcomer in this field i will probably not find out any hidden mistakes of inconsistencies for quite a while, or untill it is too late.
any suggestions? try the whole thing over again?
greetings - heinz -
The WL-500g really is a great router--probably has more features, or at least more feature potential, than any other. You can try leaving it in the cooler even LONGER as that seems logical... or you can exchange it. Or you can return it. I, myself, haven't even had the best of luck with this router when it comes to stability or reliability, and if it keeps it up, I may return mine myself.
But I doubt it. I just got a VPN on this thing!
Stand it up, too. That seems to help it not overheat.
overheating or overuse cannot really be the issue on mine: was brandnew out of the box on friday, only worked that day for about 30 minutes (with 1819), then software was upgraded to 1836, which slowed it down a bit (trying for less than an hour), and friday into saturday night the disaster with 1927 happened.
so alltogether it might have been turned one one hour+!
how do you explain this putting it in the cooler, and the long waiting times in-between? never heard this on anything non-mechanical. have unfrozen stuck HDDs this way, but this was 15 years ago.
and yes, from all i hear it is a great router, and compared to many others it is even more reliable. but ...
now for an update: my mixture of 1819 and 1927 firmware (as shown) really does not work, found this out even before i can get to a DSL modem this afternoon. the unit is found when using DISCOVER, and i can even get into the menus.
when trying to acces it from the IE (using my.router or 192....), no connection can be made at all. it shows NO CABLE CONNECTED (which is not true anyhow).
returning it to the dealer might be the best option. but there i might get into a loop: it was the dealer who suggested to update to 1927!
any idea if i stick to 1819, as the unit comes out of the box, how bad that one is and where the main deficiencies or problems are? can i live with it?
greetings - heinz -
Well it's obviously broken.. Why not return it and get a new one from the store?
S.
that is naturally an option, as it is only 3 days old. but: officially all guarantees are invalid if one tries to flash anything BETA, and 1927 is marked as such even on ASUSs website. so i am not sure where i stand.
but it still leaves the main question: WHY did this happen? following all instructions to the point, and having enough experience form the past? how did it happen? will it happen on the next unit too? shall i just stay with 1819?
what am i then missing, what problems will come up and will remain unsolved?
greetings - heinz -
so, i am back, a day later than planned i managed to test this strange WL-500g.
seems to work fine, both the router part, as well as the WLAN and the connection to the DSL modem. now i am not a power user, so i cannot yet identify any small problems, but standard things seem ok.
the AIR light seems to blink/flicker about every two seconds, traffic or no traffic. any idea if this is normal?
why i call it a strange machine: though i uploded (see earlier mssgs) version 1819 into it, it still shows 1927 when checking it.
does that mean i could have a corrupt system? or just that the indication did not update properly? is there any way (please: short of flashing it again and again) of testing, maybe with some command line commands, to test which version is r e a l l y in there?
so far all testing, wired LAN and WLAN, was with WIN XP systems. the next problem will be to test WIN98se, later tonight. any WINDOWS 98 users out there that have any specific suggestions? ASUS says it will work fine, my dealer (!) says it will not at all. very encouraging, no?
greetings - heinz -
if it is showing another firmware version you have done something somewhere wrong..Quote:
Originally Posted by heinz57g
the air led flickers often, yes this is normal as your network generates traffic even if all pc's are turned off (your network does not know those pc's are turned off..)
try to flash to a custom firmware, and see if it responds when you are trying to telnet to the unit, PLEASE CONSULT MANUAL on how to use Firmware restoration util as this is one of the best ways!
>> if it is showing another firmware version you have done something
>> somewhere wrong..
thats what i thought, but how to find out?
>> the air led flickers often
clear. in this case, with everything switched off, every two seconds to the dot, almost like it was searching.
>> try to flash to a custom firmware
WOW, thats what i was trying to avoid. pls take a minute and have a look at the posts below, between me and tom mostly, and see how much headache the flashing already caused.
so you understand why i am more than reluctant to ty flashing again. but if need be, which of the versions here is the most stable one for very standard operations? just solid router access, and WLAN as it should be.
>> telnet the unit ...
can you explain what this means, and/or where i could get simple info on it?
>> PLEASE CONSULT MANUAL
surely done 100times over.
>> use Firmware restoration
thats what was done: originally with 1927. when it left a non-working non-responding machine, it was flushed (after a night in the cooler) with 1819. that flashed for 20+ seconds, then broke off with an error, but strangely enough the set works now. but still shows 1927 as the firmware version. go figure. i can't.
greetings - heinz -
the firmware restoration tool at your windows machine will show if there are errors occured, and if flashing was a succes or notQuote:
Originally Posted by heinz57g
either your wl500g unit is a brick (from factory) or something else is wrong.
don't take this personally:
Ofcourse I personally do not have much problems with those units as expected so sometimes it's hard to believe others do have problems although mostly the same problems stay after they got a replacement from asus or the shop(and thus the error was between the monitor and the chair)
flashing 1.9.2.7-4 (custom one) would do fine
antiloppp, dont worry, i take all things technical with a lot of humor, i would have long given up (in the 1980s with my ALTAIR) if not humor would have kept me alive. never take anything personal, ever, specially not on a forum like this one where info and opinions are usually so well founded.
- >> the firmware restoration tool at your windows machine will show if
- >> there are errors occured, and if flashing was a succes or not
it showed an error after 20 seconds of flashing v1819. but the unit DID work after that, and shows it is running v1927 (the BETA from the ASUS page)!
and it seems to run normally (2 days only, but nothing to compare with).
- >> either your wl500g unit is a brick (from factory) or something else
- >> is wrong
THAT needs again humor. i will see after the weekend if the dealer wants
to exchange it.
- >> don't take this personally
see above, never do.
- >> it's hard to believe others do have problems
well, if it tell you that i have been thru some 100+ computers, still some 20 of them running, from a SINCLAIR spectrum that runs my heating system, to a P-M735 laptop that tries to run my life and business, and that i usally do NOT have much problems setting up any equipment, would that help a bit?
- >> thus the error was between the monitor and the chair
i sure know what you mean. and sometimes the most obvious mistakes are the most difficult to find, because one does not look in the simple corners. never happend to you?
- >> flashing 1.9.2.7-4 (custom one) would do fine
you mean -CR4? will do that, weekend. any special remarks before i go to the mad-house, then?
many greetings - heinz -
PS: hey, i just notice YOU are running -3c. now it know, you want me to test -4 just to make me sweat ... and my wife angry for a totally spoiled weekend.
Just my two cents. I've discovered totally upredictable router behaviour when plug/unplug Ethernet cables in it. In other words when 500g is switched on it's highly undesirable to change cable connection.Quote:
Originally Posted by heinz57g
To my mind the reasons are quite simple:
- I have outdated electric wiring with unstable ground connection. Therefore ISP hardware, router and my desktop have slightly different electric potential of ground terminal, enough to shock router's electronics.
- I have quite a dry air in my apartment and very often meet with static electricity. Moreover I've read reports of guys who are living in area with very strong thunderstorms, and they have fried up two LAN ports during last 2 years.
To avoid problems with mains and static I finish all cabling before switching router on and do it only after all peripherial devices (from router's point of view :) ) switched on.
Good luck in wiring and routing ;)
every two cents are welcome! actually i consider these hints at least 50 cents worth. really, every bit helps. see below, some 4-5 mssgs down, the way routers stay overnight in a refridgerator ... and it helped!
greetings - heinz -
well mostly i'm running pre-CR versions meaning newer than the current ones, so no I do not want you to test CR4. I have a stronge believe in Oleg that his latest custom release works fine and better than the 3C I'm currently running :D
I do update so now and then all my devices at the same time..
so, tonight is the night when i will try the flashing again, the unit is already in the fridge. so to all who read this, do me the favor and keep your fingers crossed for me. i hate to feel like an idiot.
and to all who helped or commented, it is a free beer on me if everything works out well. not blackmail, just a thankyou. and dont worry, it will not be cyberspace-beer! it WILL be there.
a few questions came up while reading and reading posts and manuals:
- a - the webinterface is factory set to admin / admin. to change the password, there is a page, easy.
but how and where/how to change the login name (which is highly recommened to be done wherever i
read about it)?
- b - after flashing the new firmware, the reset button is to be pressed for 5++ seconds. WHEN is this supposed to be done? (1) right after the interface confirmed the update, you log off it, but the unit is still turned on? or (2) after and while the unit is turned off? or (3) after the unit was off, then is again fully turned on, then the RESET, then off and on again?
- c - and once i have everything set and done, and am mainly interested in a stable working unit, with good range, but not interested in speed (11Mbps will do just fine in this case), is there a point of setting speed limited to 11? i keep reading that speed at AUTO balances speed against range, which to me means if it tries high speed, it would automatically lower the range, which is the opposite of what i need.
greetings, and already sweating - heinz -
PS: my wife has already moved out for the weekend ...
Make sure you've read this post before you start upgrading: http://wl500g.info/showthread.php?t=1329
Now that I've made my contribution to this topic and your firmware upgrade, I would like to remind you to not forget the free beer when the upgrade went successfully.
:D
Ok, now seriously:
The custom firmware has page for that too.Quote:
Originally Posted by heinz57g
When the webinterface has come back (=upgrading has finished and the router has rebooted) you can start pushing the reset button.Quote:
Originally Posted by heinz57g
As you practivally explained yourself: The router and client itself are trying to connect at the highest speed possible for the range that is between them. However if you are really far away, I can imagine that when the speed on the router is set to e.g. 1Mb you might get a connection earlier. But, auto should suffice just fine.Quote:
Originally Posted by heinz57g
Hmm, are you sure thats not just the summer coming closer and closer? ;)Quote:
Originally Posted by heinz57g
hey, just for those who think i am joking: i meant it about the beer. and for those who dont drink beer, i'll throw in a bottle of wine from a country that claims to have excellent wine, but nobody has ever heard of. so ... that is also the reason why i'm so over-careful: i am sitting in this country right now, and being 2000km away from the nearest real computershop, and a local dealer that is most unhelpful (not true: he just doesnt know), and that makes me dead serious about my promises. just watch it. it might take some time, but it will be there.
greetings - heinz -
i am back. not on the original system, but at least in the office where i can write emails and get into the forum.
the firmware update of the WL-500g worked. cooling it down well before doing anything, and giving it time between actions really helped, or so it feels.
1927-4 seems stable. i cannot see much difference to the earlier version, but the extra entry for login name. is there anything i should know? or just let it do its job? are the real improvements hidden way? fine with me.
what didnt work, and what contributed technically to my silence, was the second part: getting it to hook up with 3x WL-167g USB sticks in WIN98 computers. install was difficult but fine (it asked for several well hidden files, in WINDOWS/SYSTEMS/HELP/RASPPPOE and wherever).
but the various mssg in the control software shows it receiving and sending fine, with signal 90++% all the time, but i cannot address anything with the browser. IE6.0 (latest updates) just plays dead. it says something like 'looking for proxy', then gets the standard error page. internet or the WL-500g pages, same effect: none.
i dont know how many settings of IP adresses in network i have tried, or how often i have set it from automatic to static IP. till 4:00h in the morning when my head refused to distinguish between a light switch and the computer.
IE6.0 works fine when connected to the DSL modem directly, but that is in a room (normally) unaccessible to me, one floor down. but nothing reacts on WLAN, which is what i need desperately.
any suggestions whatsoever?
greetings - heinz -
Before my vacation I flashed my 500g to v1.9.2.7 CR6b and everything worked without any problems...
I went on vacation for two weeks and I got home yesterday hopin to pop in my laptop and do some catching up... but that was a nono...
My entire router was deadish... Wan dead, Wireless dead... Only thing that was working was dhcp.
I've hard reset it and re-entered all my settings. Everything on the router is working again except my wireless. I've tried everything I’ve learned about this piece of equipment in the last six months but nothing's working.
Tried changing channels, multiple hard resets and re-entering the settings. Hell, at the moment I’m trying the basic, standard settings that come with wireless after a reboot but that won't work either... I'm running out of idea's fast and I can use all the help I can get.
HI!
I tried to flash my WL500g with tftp, but I think I did not wait long enough before I powercycled it.
When I put the power plug in, all leds light up for a moment, then all leds except power go off. The power led stays on for ca. 3, then starts to blink in 1s intervals.
The router does not respond to pings, pushing the reset button has no effect.
Did I brick my router?
Any ideas are welcome!
Greets,
Daniel
It's in the firmware restoration mode and should answer pings. You've to check your network config.
Thanks for your answer! You were right.
I did not connect directly to it, but through a hub, i think that was the problem.
I was already looking for a cheap place to buy a new one ;)
Hi!
I have two WL500gx. The one in the summer house 500 km away is almost dead. I can still make an SSH shell to it and SCP to or from it, but no webserver reacts any more.
The big problem is that it will not reboot when the command is entered. Neither does the kill or killall commands work any more, most other seem to work.
Any ideas how to make it reboot whithout travelling 500 km? :(
try to start the webserver manually.
Code:/opt/etc/init.d/S80thttpd start
Yeah, I have done that, but I still need to reboot. God knows what it lets through right now...
at first try to do:Quote:
Originally Posted by Pjotrek
ps -ef | grep httpd
kill -9 <httpd-pid>
then again
ps -ef | grep httpd
a) are both httpd still alive now ??
b) take a look at your /tmp/syslog.log ...
Thanks, but I did try all that. Kill -9 just does not have any effect, just as the reboot and halt commands.
please show us your (remote) listing of:Quote:
Originally Posted by Pjotrek
Code:ps -ef
cat /tmp/syslog.log
iptables -L -vn
iptables -L -vn -t nat
netstat -an
ifconfig