Firmware v1.9.2.7 CR7 now 7g [Oleg]

Printable View

Show 40 post(s) from this thread on one page

16-05-2006, 08:15
wl500grocks

WPA-PSK is broken in wireless client mode (1.9.2.7-7c)
Thanks for the great firmware.

I'm using 1.9.2.7-7c and I've set up my ASUS wl500g in wireless client mode. Everything works if wireless security is not used. The moment I set WPA-PSK the PCs connected to ASUS cannot ping the main router or its PCs. On the wireless->status page, it says it is connected to main router.
Quote:
Originally Posted by Oleg

New firmware is now available for download. Changes since 1.9.2.7-6b:

Fixed issues with samba writes using large buffers
pppoe ac name and service name are now in effect
Add a workaround for default gateway with non-local address
Updated to busybox-1.1.0-pre1 (new applets, including nice nohup stty ether-wake)
Updated to dropbear-0.47
Added flashfs backup (done by engy)
Fixed firewall internal 80 wan accept (done by engy)
PPPoE connections are now forced to be nomppe nomppc
Proper NAT handling for different netmasks (techno report)
Poweroff is working now
Hidden page enter key fix (engy)
Added System Setup | Services Page
Added support for samba cp1251
Url filter page is removed, as it was not functional
kernel-syn-recv.patch (ported by oleo)
New firewall rules layout (done by unaiur)
WL300g is now working in Home Gateway mode too (reset to defaults is required after upgrading)
Apply button is now does not jump to next page
Added L2TP WAN connection type support (demand dialing/idle timeouts are not supported)

Update in the -7a: fixed a tar bug

Updates in the -7b: rolled back to busybox-1.01. Added http_lanport patch (credits to Leon Kos), SoundBlaster Audigy 2 NX soundcard support (credits to Daniel Pustka) and enabled serial ports IRQ sharing.

Updates in the -7c release:

All Save/Finish buttons are functional again
Small lease time should not cause problems with dhcp client anymore
PPTP peer address could now be the same as PtP address

Download using this link.
18-05-2006, 03:06
wl500grocks

Any ideas? Without WPA-PSK support the client mode is practically useless. Please help.

Quote:

Originally Posted by wl500grocks

Thanks for the great firmware.

I'm using 1.9.2.7-7c and I've set up my ASUS wl500g in wireless client mode. Everything works if wireless security is not used. The moment I set WPA-PSK the PCs connected to ASUS cannot ping the main router or its PCs. On the wireless->status page, it says it is connected to main router.
18-05-2006, 09:57
Oleg

Switch Extended Mode to Ethernet Bridge. It would start working for sure.
18-05-2006, 12:15
alien433

how long until release 1.9.2.7 cr7d
18-05-2006, 19:30
Oleg

Quote:

Originally Posted by alien433

how long until release 1.9.2.7 cr7d

Still in development. Latest -pre is here
18-05-2006, 21:33
spunki

asus wl-500g premium

Hello!

I ned some firmware to upgrade radio power on asus wl-500g premium access point for bridge! Can someone help me?
20-05-2006, 09:14
alien433

Oleg wat are the changes in the latest development?
23-05-2006, 15:30
0x00F6

Oleg, will wchar support be included in new release ?
it seems that oleo already did it for 1.9.2.7-7c
I'm currently on 1.9.2.7-7d-pre4 and to my great inconvenience cannot use most of standard c++ libraries
23-05-2006, 15:35
Oleg

Quote:

Originally Posted by alien433

Oleg wat are the changes in the latest development?

updated wi-fi stuff, wl550ge support, dhcp+pptp support, pwc 9.0.2
25-05-2006, 11:41
0x00F6

so it gives us precious <iostream> ???
gollum! gollum!

( i mean what about wchar anyway ? ) :D
25-05-2006, 14:16
oleo

I am running wchar enabled 7c for three months now in AP WDS mode without any problems. And would like to see wchar support in the upcoming release. With my custom firmware I am able to compile most defunc c++ optware programs. Enabling is trivial and I don't see any reason why not to enable wchar support. It gives less than 4KB to firmware.

Since I do not have time to upgrade to latest uclibc myself, I am thinking of separate uclibc for system and optware. Built with latest toolchain.

My hopes are also on kernel upgrade to 2.4.32. But anyway Don Oleg firmware has been proven stable and I can say: We do not need another version as the old one is working perfectly.

The only thing to consider when upgrading to wchar is that uClibc is not binary compatible and that whole optware repository must be rebuilded/reinstalled. That's why I am running my own ipkg wvhar enabled site.

What about sources to pre-releases? Only trx?
25-05-2006, 14:56
andre@home

i had some stability issues with 1.7.5 firmware so i updated to WL500g-1.9.2.7-7c.trx
Done by the rules... ;) first to the default settings and than... flash.
It works immediately. However some remarks:
WEP encryption ok
WPA-PSK: lan cards get connected, but no traffic possible. (*)
printer: my Kyocera FS-1010 is recognized, printing nearly ok as I get an extra page with the text:
E="Microsoft Word - Document 2"
@PJL RDYMSG DISPLAY="
seems a ready message but i knew aleady it was printed... ;)

System:
wl500-g as bridge fixed own ip number.
wireless and/or fixed connection with L3800C laptop, WL-100g card.
*= as soon encryption is activated I loose my connection on the fixed cable wl-500g-laptop If I do the same with WEP both (wireless and UTP) stay connnected and i get traffic.

I've searched the forum/web.
Suggestions welcome.

** and I loose my wireless connection too (I forgot to mention).
When I run a ping it gets lots when the WPA-PSK becomes active. The wireless connection seems still present according the signal bar in the Asus tool.
25-05-2006, 15:17
Oleg

Quote:

Originally Posted by oleo

I am running wchar enabled 7c for three months now in AP WDS mode without any problems. And would like to see wchar support in the upcoming release. With my custom firmware I am able to compile most defunc c++ optware programs. Enabling is trivial and I don't see any reason why not to enable wchar support. It gives less than 4KB to firmware.

Since I do not have time to upgrade to latest uclibc myself, I am thinking of separate uclibc for system and optware. Built with latest toolchain.

My hopes are also on kernel upgrade to 2.4.32. But anyway Don Oleg firmware has been proven stable and I can say: We do not need another version as the old one is working perfectly.

The only thing to consider when upgrading to wchar is that uClibc is not binary compatible and that whole optware repository must be rebuilded/reinstalled. That's why I am running my own ipkg wvhar enabled site.

What about sources to pre-releases? Only trx?

I'm now working on uclibc-0.9.27 support, including wchar_t. These way it would be openwrt whiterussian compatible.
This is not just a plug and play... Still working with toolchain.

Building uclibc 0.9.19+wchar looks terrible to me.
25-05-2006, 17:16
SurJector

Problem to "wl join" with -7c

Hi,

I don't manage to join an existing wi-fi network with my WL-HDD using 1.9.2.7 CR7c.
I've a WL500g (running 7c as well), configured as Home Gateway, with wi-fi enabled, ssid "Random". My laptop connects without any problem to the WL500g. I would like my WL-HDD to be a client on the wi-fi network, as well as a client on the separate wired network. I've used "Home Gateway" mode (so that the eth[012] are not bridged together), set WAN as automatic (and it works fine), and tried the following (with Wi-Fi set to open mode):

$ wl ap 0
$ wl join "Random" imode bss amode open
$ wl assoc
eth2: Invalid argument
Not associated. Last associated with SSID: "Random"

I've also tried the WPA-PSK mode to no avail.

What do I have wrong ? Please ? Pretty please ?

Thanks.
25-05-2006, 17:29
Oleg

Quote:

Originally Posted by SurJector

Hi,

I don't manage to join an existing wi-fi network with my WL-HDD using 1.9.2.7 CR7c.
I've a WL500g (running 7c as well), configured as Home Gateway, with wi-fi enabled, ssid "Random". My laptop connects without any problem to the WL500g. I would like my WL-HDD to be a client on the wi-fi network, as well as a client on the separate wired network. I've used "Home Gateway" mode (so that the eth[012] are not bridged together), set WAN as automatic (and it works fine), and tried the following (with Wi-Fi set to open mode):

$ wl ap 0
$ wl join "Random" imode bss amode open
$ wl assoc
eth2: Invalid argument
Not associated. Last associated with SSID: "Random"

I've also tried the WPA-PSK mode to no avail.

What do I have wrong ? Please ? Pretty please ?

Thanks.

No comments. I'm wonder, why everyone invents it's own wheel?
Everything is available via web interface, no manual intervention required. Just switch Wireless | Advanced | Extended mode to Ethernet Bridge. RTFM from ASUS.

Show 40 post(s) from this thread on one page