Bekijk de volledige versie : New firmware available

25-02-2004, 11:08
Guys, I've prepared the new firmware.
Changes: updated wl.o module with client mode support; busybox-1.0-pre7 with many tools compiled in (including telnetd, tftp, wget); PPTP DHCP support (experimental); nvram stored command execution. Also busybox is statically linked with uclibc, so resolver should work.

Firmware - http://jaffar.cs.msu.su/wl500g/wl500g-
Sources - http://jaffar.cs.msu.su/wl500g/wl500g-

Note for wl500b users. I've no much time to build wl500b versions, but you can flash the wl500g firmware to your boxes using firmware restoration and it should work, but do not touch anything related to the 11g operations.


P.S. Antiloop you can post these files on your site. :)


mirror @ http://files.wl500g.info/asus/wl500g/firmware/customized/wl500g-



25-02-2004, 17:08
Thanks, Oleg. I think ASUS should definitely pay some fee for your effort. :)
I will test to overburn my WL-500b tonight.

25-02-2004, 17:43
Originally posted by Technik
I will test to overburn my WL-500b tonight.
Anyway, you are doing this on your own risk. But we need the success story. :)

25-02-2004, 23:45
Oleg, I have successfully converted my WL-500b to WL-500g. :) Unfortunately it seems there's a problem with busybox - the route command does not work properly. When I run older busybox from usbfs, the route command works fine. Could you please check what's wrong?

26-02-2004, 09:32
Hmm, what happens exactly? At lease what you're trying to do and does it say something? Busybox does not have any special settings for the route...

26-02-2004, 09:56
Well, if you run route without parameters, it will display just part of the routing table and then hangs. If you try to add a default gateway, it does not change anything in the routing table... I did not test another busybox functions yet.
BTW, the resolver works perfectly now!

26-02-2004, 10:30
As for hangs - seems this is just resolver starts working - try using "route -n" amd let me know if it works for you. As for default routes - dhcpc uses route to add default gateway and if this works - route also works (and it works for me, but I'm unable to verify this right now). If you adding default gw manually - just recheck every step.

26-02-2004, 10:39
OK, Oleg, thanks for a tip, I will test it tonight.
I need to enter the default GW manually as there's usually no DHCP service running on our wireless networks.

Update - you were right, Oleg - the 'hang' problem is due to resolver so it may take long until the route command is completed.