Firmware v1.9.3.5 BETA

Printable View

24-02-2005, 20:05
Antiloop

Firmware v1.9.3.5 BETA

WARNING: BETA VERSION
TRY AT YOUR OWN RISK!

DO NOT UPGRADE UNLESS YOU KNOW WHAT YOU ARE DOING
DOWNGRADE IS NOT EASILY POSSIBLE!!

Changelog:

Quote:

Fix 10 problems:
1. P2P networks causing lost of connectivity due to limited number of connections which firewall is keeps tracking (1024 by default)
2. Missing timezones at least for Australia, Azores Islands.
3. Radius authentication does not work.
4. Client mode does not work as expected: could not access internet in client mode.
5. Idle timeout and Tx only does not work with PPPoE.
6. Encryption WPA-PSK AES and WEP, WEP functions like it should but WPA-PSK AES does not function right.
7. WDS using WPA encryption does not function. No connection is established.
8. Bandwidth management page treat rate values as kilobytes, not kilobits.
9. WAN DHCP IP renewal does not work correctly with some ISP configurations, connections get dropped due to reacquiring of IP address.
10. Internal ftp server does not truncate files before overwriting, resulting in corrupted file if newer file is smaller than old one.

important!!

Quote:

When upgrading from 1.7.x.x based firmware: you MUST Reset your WL500g to defaults via the restore button at the back after upgrading to this firmware!

you do not have to do this when you upgrade from 1.8.x.x based firmware!
but we RECOMMEND you to do a restore to defaults.

Do not import saved settings from older/other firmwares! this can cause unstability to your device

find files here:

Mirror @ Chupa.nl
http://files.wl500g.info/asus/wl500g...1.9.3.5_EN.zip
25-02-2005, 17:14
int

Missing:

Timezones at least for (GMT) Portugal

Nice:
Status & Log - DHCP Leases show the manual ip
26-02-2005, 01:25
Stevio

I just installed the firmware 5 hours ago and i didnt noticed some strange things. I will post more results after a few days.
26-02-2005, 03:52
int

BUG
Reset Issue

I detected the same issue that i have in whole 1.9.X.X fw
26-02-2005, 03:54
int

Quote:

Originally Posted by Stevio

I just installed the firmware 5 hours ago and i didnt noticed some strange things. I will post more results after a few days.

You dont noticed this?

Bug
Sytem Time dont update to NTP Server
26-02-2005, 05:51
Wesleyrpg

How typical....bigpond support is broken, does its usual 'Network host unreachable' uslness manual IP specified for Heartbeat server
26-02-2005, 10:59
Stevio

Quote:

Originally Posted by int

You dont noticed this?

Bug
Sytem Time dont update to NTP Server

Well i dont have this message in the system log. Maybe u got this bug from another log tell me. For me it works :) Now i am trying to get the WDS working :)
26-02-2005, 16:25
hobbes

Feb 26 16:21:07 ntp client: time is synchronized to pool.ntp.org

seems to work ok for me

what I can't get to work and haven't yet is my webcam a trust 150 spacecam portable, i change to the correct driver OV* but as soon as i save it reverts to the other driver :(
26-02-2005, 23:55
tomilius

Anybody else has WPA-PSK: TKIP problems with 1.9.2.7 and up, including custom firmware? I know I did (/do). But I didn't seem to have any for close to 12 hours with this firmware (I stopped because of problems ASUS still hasn't solved that custom firmware has).
27-02-2005, 00:02
Stevio

Quote:

7. WDS using WPA encryption does not function. No connection is established

.

wont work, just as the other firmwares. Someone else tried this firmware and got it working. tell me how u did it :)
28-02-2005, 15:37
Spot

My first results...

Seems that not all process automatically start after each reboot (like pppoe connection to isp, ntp server, dyndns update or even dhcp-manual assignement...) or are executed with very long delays!

Problems occurs randomly, I think :rolleyes:

I also noticed that the asus gateway upnp icon (under win XP) does'nt appear immediately after 1st boot... and when It shows up, it does'nt desapear even when the router is unplugged :eek:

So... lot of strange behaviours that I never encounter with previous fw!
28-02-2005, 15:57
Styno

Quote:

Originally Posted by Spot

So... lot of strange behaviours that I never encounter with previous fw!

Did you reset to defaults properly?
28-02-2005, 23:45
Spot

Quote:

Originally Posted by Styno

Did you reset to defaults properly?

Everytime I upgrade (or downgrade :D ), I do a software restore, than I change fw with the restoration tool, than I do a hardware reset and finaly, I unplug my router for more than 10 minits... so I guess I take care enough :rolleyes: ...

But :D , yesterday, before doing this upgrage, I noticed that trying to change some params in my setup (fw 1.9.2.7 cr3), they didn't stay permanents after reboot!

Do you thing that has something to do with my results?
01-03-2005, 19:53
Twisterchen

Quote:

Idle timeout and Tx only does not work with PPPoE.

Hello

can any one say me for what Tx only stand

i think my router 500g dous not terminate the conecting to isp with idle time 300

what must i do

Thanks
Twisterchen
02-03-2005, 09:21
Styno

Quote:

Originally Posted by Twisterchen

can any one say me for what Tx only stand

Idle timer only resets on Tx (transmit = from you to your ISP).

Quote:

i think my router 500g dous not terminate the conecting to isp with idle time 300

There are other members like you having the same problem. Theoretically the Tx only option should be turned on for you, but it apparently doesn't work with most firmwares.

Search this forum for some of our Portugese members as they reported the same problem. http://wl500g.info/showthread.php?t=782
02-03-2005, 11:35
Spot

pppd starts on demand...

Well, after further testing, I've found that pppd doesn't "link" automaticaly on reboot. But only when I launch internet explorer... So I guess the pppd link when a client send request to the wan port?

And of course, ddns and ntp services do not start untill link is established... this is why I've thought (in my previous post) that all the starting process was erratic.

See above: pppd links after 2 minites... just when I run internet explorer.

Quote:

Jan 1 01:00:03 USB webcam: attached
Jan 1 01:00:03 USB webcam: attached
Jan 1 01:00:07 pppd[85]: pppd 2.4.1 started by (unknown), uid 0
Jan 1 01:00:07 pppd[85]: Using interface ppp0
Jan 1 01:00:07 pppd[85]: local IP address 10.64.64.64
Jan 1 01:00:07 pppd[85]: remote IP address 10.112.112.112
Jan 1 01:00:17 USB storage: vfat fs mounted to /tmp/harddisk
Jan 1 01:00:17 FTP server: daemon is started
Jan 1 01:02:28 pppd[85]: Starting link
Jan 1 01:02:28 pppd[85]: Serial connection established.
Jan 1 01:02:28 pppd[85]: Connect: ppp0 -> /dev/pts/0
Jan 1 01:02:28 pppd[85]: Warning - secret file /tmp/ppp/pap-secrets has world and/or group access
Jan 1 01:02:28 pppd[85]: Warning - secret file /tmp/ppp/chap-secrets has world and/or group access
Jan 1 01:02:29 pppd[85]: Remote message: CHAP authentication success, unit 10669
Jan 1 01:02:29 pppd[85]: Local IP address changed to 213.219.187.198
Jan 1 01:02:29 pppd[85]: Remote IP address changed to 213.219.187.1
Jan 1 01:02:30 ddns update: connected to members.dyndns.org (63.208.196.94) on port 80.
Jan 1 01:02:31 ddns update: request successful
Jan 1 01:02:33 ddns: ddns update ok
Mar 1 13:25:40 PPPoE: connect to ISP
Mar 1 13:25:49 ntp client: time is synchronized to time.windows.com
02-03-2005, 16:40
Twisterchen

ok
the idle timer not work right ?

ok no problem i have a flatrate but for people he doesn 't have a Flatrate it s a big problem

comes a Update from OLIG ?

i understand it when i check Tx than terminate the ISP the connecting, when Tx is not checked the terminate the Router the connecting
is that right ?

Twisterchen
02-03-2005, 16:45
Styno

Quote:

Originally Posted by Twisterchen

i understand it when i check Tx than terminate the ISP the connecting, when Tx is not checked the terminate the Router the connecting
is that right ?

Sorry Twisterchen, I totally do not understand your question....

Re-read my previous post in this thread, it explains Tx option (As it theoretically should work).
03-03-2005, 14:40
Twisterchen

ok my problem is
i have only set idle timer to 300 sec but my router does not disconnect after 300 sec
no Tx selected i dont understand it for what i need this

Quote:

Originally Posted by Antiloop

Fix 10 problems:
...
5. Idle timeout and Tx only does not work with PPPoE.
...

but my connecting does not disconnect

Twisterchen :cool:
03-03-2005, 17:42
Styno

The basics: An idle timer needs to reset in order to stop it from reaching the threshold on which it terminates the connection. This reset signal can be given on receiving (Rx) or transmitting (Tx) packets to and from the WAN.

With all those scriptkiddies and virusses wondering around in cyberspace, you will allways receive incoming connections (=packets) even while you are doing nothing. Therefore anyone who wants the disconnect timer working properly should enable the Tx option. This should terminate the connection after the time-out time when you (or the router) doesn't send any packets anymore.

The problem is that the Tx option was broken in previous firmwares and Asus tried to fix it in this one.

I hope you understand now.... :)
04-03-2005, 00:58
rprior

Bug report and DNS question

Hi.

I installed firmware 1.9.3.5 and found out that "Setting Management->Save As a File" is not working, I get a zero-length file every time.

Now a DNS question: is it possible to configure DNS entries for the local, privately addressed hosts of my home network?

Thanks.
Rui
05-03-2005, 01:23
rl2664

Hello,

for me, it´s impossible to connect ISP (T-Online/Germany) with FW 1.9.3.5. I don´t know where the problem is, any ideas?

Ronny

Jan 1 01:00:06 pppd[66]: pppd 2.4.1 started by (unknown), uid 0
Jan 1 01:00:06 pppd[66]: Using interface ppp0
Jan 1 01:00:06 pppd[66]: local IP address 10.64.64.64
Jan 1 01:00:06 pppd[66]: remote IP address 10.112.112.112
Jan 1 01:00:32 pppd[66]: Starting link
Jan 1 01:00:32 pppd[66]: Serial connection established.
Jan 1 01:00:32 pppd[66]: Connect: ppp0 -> /dev/pts/0
Jan 1 01:00:33 pppd[66]: Warning - secret file /tmp/ppp/pap-secrets has world and/or group access
Jan 1 01:01:03 pppd[66]: LCP: timeout sending Config-Requests
Jan 1 01:01:03 pppd[66]: Connection terminated.
Jan 1 01:01:34 pppd[66]: Starting link
Jan 1 01:01:34 pppd[66]: Serial connection established.
Jan 1 01:01:34 pppd[66]: Connect: ppp0 -> /dev/pts/0
Jan 1 01:01:35 pppd[66]: Warning - secret file /tmp/ppp/pap-secrets has world and/or group access
Jan 1 01:01:35 pppd[66]: LCP terminated by peer
Jan 1 01:01:35 pppd[66]: Modem hangup
Jan 1 01:01:35 pppd[66]: Connection terminated.
05-03-2005, 18:44
Twisterchen

i have no problem to connect do t-online / Germany
i connected
07-03-2005, 10:28
chris4335

useless version (at least for me)

Idel Timeout: Try to set "0", does not work in the web interface (same in the last release version)

PPP Connection to T-Online, connects and the disconnects

WLAN: IP Address assignment by DHCP does not work (same in the last release version)

I'm back to an 1.8.. Version, but these old version aren't Rockstable
either. This Router starts to become frustating.

Regards
chris
07-03-2005, 22:40
tomilius

It still seems one of the best routers feature-wise... At least, with custom firmware :)

I'm just waiting for the source code for something greater than 1.9.2.7 to be released, because everything so far has one problem or another. Heck, not a single ASUS firmware can serve DNS properly without adjustment.
09-03-2005, 21:19
Mark Laser

a couple of 1.9.3.5 beta probs

I was trying out my WL-500g deluxe (using the correct beta firmware - but there are no responses on that thread) and I found that I could not telnet into the router as I could with FW v1.9.2.7-cr3. So how can I do that?

Also, when setting up in client mode, I could never change from channel 1. I could set other channels, but they were ignored. <- apparently this is irrelevant. However, I never could get it to connect to my other router with this FW no matter what.

Great Forum and I have been learning alot.

Thanks,

Mark
11-03-2005, 19:23
marciton

can't change the router name ...

I can't change the default router name ... it's always my.router