Builds 3.0.0.4.220.18 are out!

[erwinquek]

Which page crashed it? I just went through every pages, and the http service never stopped working.

See if the http process is still running when that happens. Also make sure you aren't changing the https port to 443 (which would conflict with AiCloud). Default https port is 8443.

U mean the default port 8443 is for aicloud or the web interface of the router?

 

[uncle.f]

U mean the default port 8443 is for aicloud or the web interface of the router?

Hmm.. I have my SSH running on port 443. Does it mean that I have problems with httpd because of that? I do not use and do not want to use https with the web interface. Neither I want to use aicloud.

 

[RMerlin]

I upgraded to 220.18 from 220.17. I clicked on 'System Log' and then 'Wireless Log' and it locked up. I then power cycled the router,and try to select 'Wireless Log' again and it locked up. Power cycled, reloaded 220.18, cleared NVRAM, rebooted, power cycled, input settings, and then tried to select 'Wireless Log' and it locked up. Power cycled and reloaded 220.17, and can now select any tab on web GUI without it locking up.

Did you have any wireless device connected at the same time? What happens if you turn them off, can you isolate one particular device causing it?

 

[RMerlin]

Hmm.. I have my SSH running on port 443. Does it mean that I have problems with httpd because of that? I do not use and do not want to use https with the web interface. Neither I want to use aicloud.

Having ssh on port 443 will conflict with AiCloud. You will have to change it.

 

[RMerlin]

U mean the default port 8443 is for aicloud or the web interface of the router?

8443 is the default for the web interface. AiCloud uses 443.

 

[Gingernut]

Did you have any wireless device connected at the same time? What happens if you turn them off, can you isolate one particular device causing it?

The same thing more or less while accessing the system log tabs, precisely the wireless log one. The web server process was still running, checked with the top command. After fighting and trying to restart only that service, didn't find out how to, I gave up and rebooted.

It happens when you access the wireless log tab but not always, I've got the same wireless clients as always.

 

[erwinquek]

8443 is the default for the web interface. AiCloud uses 443.

I have an application running off 8443 and its port forwarded. For 8443 on the web interface, its meant for https right? If i do not enable https for the web interface, it should be ok right?

 

[Ramon]

Merlin i have tried your latest release .220.18 and i had the same problems with connecting to the router UI like a few others. This happend after i turned on port forwarding. After that i cant connect to the UI anymore. I powered cycled the router and then it is oke again, but after 10 min i cant connect.. I have switched back to version .220.17

 

[RMerlin]

I have an application running off 8443 and its port forwarded. For 8443 on the web interface, its meant for https right? If i do not enable https for the web interface, it should be ok right?

That's correct. So long you don't enable HTTPS support, you can use port 8443 for port forwarding.

 

[RMerlin]

The same thing more or less while accessing the system log tabs, precisely the wireless log one. The web server process was still running, checked with the top command. After fighting and trying to restart only that service, didn't find out how to, I gave up and rebooted.

It happens when you access the wireless log tab but not always, I've got the same wireless clients as always.

The wireless tab can take a few seconds to complete processing, during which time httpd might be unresponsive. It can take up to 3 secs per connected wifi client the first time you access that page, so if you have 5 wireless clients, the web server might stop responding for up to 15 secs.

I'll revert that back in the next release. It will mean however that the first time the page gets loaded, wireless clients will be unable to report their RSSI, until you manually refresh that page.

 

[mikeg]

Wireless clients does not vonnect or drop connection

I have the same issue with wireless clients , a laptop with built wireless and
a stationary with an Asus USB-N53. I am logged in to the web-gui and when I want to switch to another page from for example the syslog to the wireless
nothing happen and after a time I get a disconnect from the router.
No respons from the Asus if I try to ping or telnet to it.
Another thing : in the wireless log on the 2.4 GHz band I got this

192.168.2.34 Mike-laptopPC 4294967 Mbps -10 dBm assoc auth
192.168.2.19 android_9610fd5 11 Mbps -40 dBm assoc auth


I usually have 270 Mbps or 135 Mbps spped on my laptop. Seems yo
be a bug .....

 

[RMerlin]

I have the same issue with wireless clients , a laptop with built wireless and
a stationary with an Asus USB-N53. I am logged in to the web-gui and when I want to switch to another page from for example the syslog to the wireless
nothing happen and after a time I get a disconnect from the router.
No respons from the Asus if I try to ping or telnet to it.
Another thing : in the wireless log on the 2.4 GHz band I got this

192.168.2.34 Mike-laptopPC 4294967 Mbps -10 dBm assoc auth
192.168.2.19 android_9610fd5 11 Mbps -40 dBm assoc auth


I usually have 270 Mbps or 135 Mbps spped on my laptop. Seems yo
be a bug .....

There seems to be an uninitialized buffer in the code that didn't get caught at compile time. I'll take a closer look when I get home tonight.

 

[RMerlin]

Gingernut, mikeg: Check your PMs.

 

[RMerlin]

I will be releasing 3.0.0.4.220.18b on Github during the evening. This release will fix various issues and quirks related to the Wireless Log page:

• Invalid RX rate will be reported as "??" instead of a random value (seems to be an issue with the wireless driver not always returning a valid RX rate)
• Added the display of the TX rate
• Rewrote the RSSI retrieval code. No longer makes multiple attempts at obtaining a valid value (you will have to manually refresh the page if the RSSI gets reported as ??), and uses the wireless IO interface to retrieve the value.
• Fixed a few other potential issues in the wireless info retrieval

RT-AC66U build is up, other builds are slowly compiling and will be uploaded later tonight. Let me know if they resolve any issues you might have encountered related to the Wireless Log page or the httpd server stopping responding.

 

[RogerSC]

Firmware 220.18b looks good, except for one thing...you can't tell if you have 18 or 18b installed, since the version is 18 for 18b.

Did the number of character positions for the firmware version string run out?

 

[RMerlin]

Firmware 220.18b looks good, except for one thing...you can't tell if you have 18 or 18b installed, since the version is 18 for 18b.

Did the number of character positions for the firmware version string run out?

The version string doesn't accept letters, that's why it's kept at 220.18.

 

[mikeg]

Gingernut, mikeg: Check your PMs.

Ok, thanks RMerlin - I have updated to fw .18B and it loks good on the wireless
log. Just an issue left : the unexpected disconnects when I am in the web-gui
of the router : The connection has timed out
The server at 192.168.2.1 is taking too long to respond.
After this message I can not reach anything on internet and no respons on
ping or telnet from the unit. The status on the wireless in Windows is connected
on internet and the speed is 270 Mbps - as before the disconnect.
When I leave it like that after a period of time the connection is reestablished.
Then I can reach the web-gui and the internet too.

 

[mikeg]

Firmware 220.18b looks good, except for one thing...you can't tell if you have 18 or 18b installed, since the version is 18 for 18b.

Did the number of character positions for the firmware version string run out?

I used Tools - System Information and got the info about when the fw. was built. RT-AC66U
Firmware Build: Tue Sep 25 02:42:17 UTC 2012 root@99b4845

 

[RogerSC]

The version string doesn't accept letters, that's why it's kept at 220.18.

Anyways, 18b is working well for me. And it is nice to see the wireless client transmit speed.

Thanks.

 

[AnthonyArmato]

Anyways, 18b is working well for me. And it is nice to see the wireless client transmit speed.

Thanks.

Where do you see that ?