Firmware v1.9.2.7 CR3 - Now CR3b [Oleg]
New firmware and sources are available for download. This firmware was not carefully tested, so consider it as beta.
- Fixed problems with 1.9.2.7 radius authentication
- Fully functional client mode support, just like 1.7.5.9-5 had (i.e. WAN and WLAN interfaces roles are exchanged)
- Workaround for broken ISP DHCP servers configurations (solves problem with renewing IP addresses)
- Added checks to mount code to not mount the same partitions twice (so, you could now manually mount whatever you want in the post-boot script, and these partitions will not be mounted twice by firmware itself)
- Updated dropbear to latest 0.44test4, which includes client ssh now
- Replaced default ppp/pppoe stuff with ppp-2.4.3 (includes mschap/mschap v2 authentication support, should work with PPTP servers configured for mschap only)
- Various pptp/pppoe related fixes, Tx only option is now functional
- Added Idle timeout support, broken in the ASUS firmwares. For now, for this to work you need to manually specify DNS server addresses! To make connection permanent either specify idle timeout of 0 or use auto DNS (this way idle is ignored)
- Added support for invocation of ppp custom ip-up, ip-down scripts (should be placed to the /usr/local/sbin/
- Fixed problems with "PRINTER: bla-bla-bla" printed to the printer attached to the parallel port
- Added simple samba configuration from the web (remember to set LAN hostname, otherwise samba will not work!)
Update: whole zoo is updated to 1.9.2.7-3a, use it if you've problems with PPPoE/PPTP connections or FTP users problems.
Latest news: updated to 3b: 1.9.2.7-3b
- Fixed minor problem with Samba: setting Hostname in the Special Requiremnt from ISP is no longer affecting hostname used for Samba
- Fixed PPPoE connection issues - moved to ppp-2.4.2. Added experimental support for MPPE over PPTP connections
- Fixed kbps/kbits thing in the ASUS Bandwidth Management (thanks to yato for figuring this out)
- Manual DHCP assignment list is now limited to 32 entries (vs 8 in stock)
Problems with internal ftp server
Seems to me that there are some problems with the user account list:
I've tried to set private accounts and also an anonymous access whith read only rights (user: anonymous / pass: * / rights: read only) but all these access are dinied!
With previous firmware: when these accounts are correctly setted and when I plug an usb key freshly formatted in fat32, wl500g creates two directories (ftp_pub and ftp_pvt) and subdirectories in ftp_pvt according to private user account setted before... but with fw 1.9.2.7 CR3, nothing happends!
Anyone who experiment the same things?
Misc 1.9 and 1.8 firmware issues
Quote:
Originally Posted by Oleg
New firmware and sources are available for
download. This firmware was not carefully tested, so consider it as beta.
Unfortunately, I still have problems with latest firmware [1.9.2.7-3] as with the whole 1.9.2.7 series. I have Asus WL500g, working as home router [SPI, MASQ, AP]. I have two issues:
1) Random reboots [I could to a remote syslogging to see if it has any issues, but if it OOPSes, than it probably won't do a thing] after a while, whenever listening to shoutcast streams. I'm not using any URL filter [ie. string netfilter match], not any special Netfilter rules except standard ones generated by router sw itself [NAT, MASQ, SPI].
2) Random problems with WPA connecting clients. In 1.9.2.7-1 version WPA client couldn't connect at all, in -2 and -3 they can connect but randomly they seem to be connected [radio link active, but no IP packets from AP to client] but no communication appears to be ongoing [ie. as the encryption is wrong]. WEP64/128 on the other hand work perfectly.
If I flash the router back to 1.8 series, all the problems dissapear [and router is being stable]. However, 1.8 series seem to lose connection to USB printers from time to time. Especially if printer was left in some other state then poweroff [ie. if WL500g gets any error from printer saying there were no paper and then printer gets poweroff-ed] such, connection cannot be reactivated [no matter printer state is] except by rebooting the router.
I hope it helps, let me know if you need any specific detail.