Absolutely great.
A working SSH client, and the darn client mode fixed again.
Great work 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)
Last edited by Antiloop; 14-01-2005 at 14:08.
Absolutely great.
A working SSH client, and the darn client mode fixed again.
Great work Oleg!
WAP are working?
Home Page
Marco Sousa from PORTUGAL
[ WL-500g - fw: 1.9.2.7-7e [Oleg] | WL-500gP - fw: 1.9.2.7-7f-USB-1.63 [Oleg&koppel.cz] ]
Yes! With the ppp new version, I might be able to use a ppp connection using bluetooth without loosing connectivity with internet on client side. I'm going to test this right now. Thanks Oleg
I upgrade fw to 1.9.2.7.2-3
I have hardware reset..
I'm has make configuration from zero!
My router continue to restart with this fw, I have tried everthing.
And now the wl do not connect automaticly...
full log in attach
...
Jan 1 00:00:06 kernel: USB Mass Storage support registered.
Jan 1 00:00:06 pppd[80]: Plugin rp-pppoe.so loaded.
Jan 1 00:00:06 pppd[80]: RP-PPPoE plugin version 3.3 compiled against pppd 2.4.3
Jan 1 00:00:06 pppd[81]: pppd 2.4.3 started by admin, uid 0
Jan 1 00:00:06 kernel: lp driver: get device ID
Jan 1 00:00:06 kernel: neg fail
Jan 1 00:00:12 kernel: lp driver: get device ID
Jan 1 00:00:12 kernel: neg fail
Jan 1 00:00:12 kernel: neg fail
Jan 1 00:00:21 dnsmasq[51]: DHCPINFORM(br0) 192.168.1.126 00:04:e2:aa:b4:d0
Jan 1 00:00:21 dnsmasq[51]: DHCPACK(br0) 192.168.1.126 00:04:e2:aa:b4:d0 INT
Jan 1 00:00:24 dnsmasq[51]: DHCPINFORM(br0) 192.168.1.126 00:04:e2:aa:b4:d0
Jan 1 00:00:24 dnsmasq[51]: DHCPACK(br0) 192.168.1.126 00:04:e2:aa:b4:d0 INT
Jan 1 00:00:46 pppd[81]: Timeout waiting for PADS packets
Jan 1 00:00:46 pppd[81]: Fatal signal 11
Jan 1 00:00:46 pppd[81]: Exit.
Jan 1 00:02:48 wan: connected manually
Jan 1 00:03:49 wan: disconnected manually
Jan 1 00:03:51 dnsmasq[51]: read /etc/hosts - 4 addresses
Jan 1 00:03:51 dnsmasq[51]: reading /tmp/resolv.conf
Jan 1 00:03:52 wan: connected manually
Jan 1 00:03:54 pppd[162]: Plugin rp-pppoe.so loaded.
Jan 1 00:03:54 pppd[162]: RP-PPPoE plugin version 3.3 compiled against pppd 2.4.3
Jan 1 00:03:54 pppd[163]: pppd 2.4.3 started by admin, uid 0
Jan 1 00:03:59 pppd[163]: PPP session is 100
Jan 1 00:03:59 pppd[163]: Using interface ppp0
Jan 1 00:03:59 pppd[163]: Connect: ppp0 <--> eth1
Jan 1 00:04:00 pppd[163]: PAP authentication succeeded
Jan 1 00:04:00 pppd[163]: peer from calling number 00:90:1A:10:11:CB authorized
Jan 1 00:04:00 pppd[163]: local IP address 213.13.239.138
Jan 1 00:04:00 pppd[163]: remote IP address 213.13.72.1
Jan 1 00:04:00 pppd[163]: primary DNS address 194.65.100.117
Jan 1 00:04:00 dnsmasq[51]: read /etc/hosts - 4 addresses
Jan 1 00:04:00 dnsmasq[51]: reading /tmp/resolv.conf
Jan 1 00:04:00 dnsmasq[51]: using nameserver 194.65.100.117#53
Jan 1 00:04:01 PPPoE: connect to ISP
Last edited by int; 09-01-2005 at 00:05.
Home Page
Marco Sousa from PORTUGAL
[ WL-500g - fw: 1.9.2.7-7e [Oleg] | WL-500gP - fw: 1.9.2.7-7f-USB-1.63 [Oleg&koppel.cz] ]
I suspect problems with your ISP, but I will check on how to increase timeouts/discovery.Originally Posted by int
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?
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:Originally Posted by Oleg
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.
After I upgraded my router to CR3, i can't connect to my ISP. Tried hard reset + upload settings form file, but it didn't work.
I put back CR2, did a hard restet, and now its working again with CR2.
Do you have any idea what could be the problem?
I attach my syslog.
Thanks in advance!
The problems is not with my ISP, this issue only appen in 1.9.2.7-3 fw then the WL reboot (I dont know why, I suspect that are another issue).Originally Posted by Oleg
I this that the problem that not auto-connect ISP are about WL reboot random,
like kreator
If i shutdown the power of my WL and power-up the WL connect auto to ISP
Last edited by int; 09-01-2005 at 12:23.
Home Page
Marco Sousa from PORTUGAL
[ WL-500g - fw: 1.9.2.7-7e [Oleg] | WL-500gP - fw: 1.9.2.7-7f-USB-1.63 [Oleg&koppel.cz] ]
yes, this is a bug.Originally Posted by Spot
Which connection type are you using?Originally Posted by Csali
I can't fix this - I've no idea why this happens. Also, it does not happens to me.Originally Posted by int
My mistakeOriginally Posted by Int
My issues:
1.9.2.7-1 reboot random
1.9.2.7-2 reboot random
1.9.2.7-3 reboot random, and do not autoconnect(only happens after reboot issue)
Last edited by int; 09-01-2005 at 12:34.
Home Page
Marco Sousa from PORTUGAL
[ WL-500g - fw: 1.9.2.7-7e [Oleg] | WL-500gP - fw: 1.9.2.7-7f-USB-1.63 [Oleg&koppel.cz] ]
The range has decreased sinths firmware 1.9.2.7Originally Posted by Changelog ASUS 1.9.2.7
Because I use the follow setup http://wl500g.info/showpost.php?p=3516&postcount=2
I have to use the full range. I Changed the output power but this hasn't any effect
Maybe you can correct in in the firmware?
KEEP FORUMS @ WL500G.INFO UP!!! - DONATE NOW, CLICK HERE!!!