2,4GHz Wifi unstable

[Michl]

I think this is a bug in stock firmware and even merlin. I installed now DD-WRT again and this works.

As you can see in logs, client (eg. 192.168.2.51 - smartphone) will not be registered in network. Router acceppts no more incomming requests at 2,4GHz network after some minutes.

DHCP-Nutzungen:
Hostname IP Address MAC Address Expires
DELL 192.168.2.2 e8:2a:ea:90:f5:42 23:59:01 DELL Precision M3800
Michaels-iPad 192.168.2.37 40:30:04:24:31:62 23:58:38 iPad2
OPWL20001E3687446 192.168.2.4 00:01:e3:68:74:46 23:58:29 VoIP-DECT
android-b4403e2f96d35731 192.168.2.51 90:18:7c:d2:6a:85 23:58:11 Galaxy S3 mit Stock-Firmware

Verbindungen:

Android: - WLAN aus -

Proto NATed Address Destination Address State
tcp 192.168.2.37:61895 17.130.254.34:5223 ESTABLISHED
tcp 192.168.2.37:61896 193.149.80.67:443 ESTABLISHED
udp 192.168.2.4:5060 217.10.79.9:5060 ASSURED
udp 192.168.2.2:51944 192.168.1.16:161 UNREPLIED
udp 192.168.2.2:51944 192.168.1.10:161 UNREPLIED

Android: - WLAN ein -
tcp 192.168.2.37:61895 17.130.254.34:5223 ESTABLISHED
tcp 192.168.2.2:65119 173.194.39.1:443 ESTABLISHED
tcp 192.168.2.37:61896 193.149.80.67:443 ESTABLISHED
tcp 192.168.2.37:61903 213.199.179.157:40033 ESTABLISHED
tcp 192.168.2.2:65120 173.194.39.5:443 ESTABLISHED
tcp 192.168.2.37:61904 91.190.216.81:80 TIME_WAIT
udp 192.168.2.4:5060 217.10.79.9:5060 ASSURED
udp 192.168.2.2:51944 192.168.1.10:161 UNREPLIED
udp 192.168.2.2:51944 192.168.1.16:161 UNREPLIED

Android: - IP wird abgerufen -
tcp 192.168.2.37:61895 17.130.254.34:5223 ESTABLISHED
tcp 192.168.2.37:61896 193.149.80.67:443 ESTABLISHED
tcp 192.168.2.37:61903 213.199.179.157:40033 ESTABLISHED
tcp 192.168.2.37:61904 91.190.216.81:80 TIME_WAIT
udp 192.168.2.4:5060 217.10.79.9:5060 ASSURED
udp 192.168.2.2:51944 192.168.1.16:161 UNREPLIED
udp 192.168.2.2:51944 192.168.1.10:161 UNREPLIED

Android: - Verbinden -
tcp 192.168.2.37:61895 17.130.254.34:5223 ESTABLISHED
tcp 192.168.2.37:61896 193.149.80.67:443 ESTABLISHED
tcp 192.168.2.37:61903 213.199.179.157:40033 ESTABLISHED
udp 192.168.2.4:5060 217.10.79.9:5060 ASSURED

Android: - Verbindung mit 5G -
tcp 192.168.2.51:56647 173.194.65.188:5228 CLOSE
tcp 192.168.2.51:40565 173.194.65.188:443 ESTABLISHED
tcp 192.168.2.37:61895 17.130.254.34:5223 ESTABLISHED
tcp 192.168.2.51:41406 54.195.251.62:5223 ESTABLISHED
tcp 192.168.2.51:34734 31.13.100.11:443 ESTABLISHED
tcp 192.168.2.51:39717 173.194.39.6:443 ESTABLISHED
tcp 192.168.2.51:49200 31.13.100.11:443 ESTABLISHED
tcp 192.168.2.37:61896 193.149.80.67:443 ESTABLISHED
tcp 192.168.2.51:53714 31.13.93.5:443 ESTABLISHED
tcp 192.168.2.37:61903 213.199.179.157:40033 ESTABLISHED
tcp 192.168.2.51:54578 173.194.39.6:80 ESTABLISHED
tcp 192.168.2.51:40730 173.194.39.6:80 ESTABLISHED
tcp 192.168.2.51:38293 173.194.39.1:80 TIME_WAIT
tcp 192.168.2.51:38382 173.194.39.6:443 TIME_WAIT
udp 192.168.2.4:5060 217.10.79.9:5060 ASSURED


Wireless-Protokoll:
SSID: "Michl24"
RSSI: 0 dBm SNR: 0 dB noise: -92 dBm Channel: 1
BSSID: 38:2C:4A:4B8:F0 Capability: ESS ShortSlot
Supported Rates: [ 1(b) 2(b) 5.5(b) 6 9 11(b) 12 18 24 36 48 54 ]
VHT Capable:
Chanspec: 2.4GHz channel 1 20MHz (0x1001)
Primary channel: 1
HT Capabilities:
Supported MCS : [ 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21
22 23 ]
VHT Capabilities:
Supported VHT (tx) Rates:
NSS: 1 MCS: 0-9
NSS: 2 MCS: 0-9
NSS: 3 MCS: 0-9
Supported VHT (rx) Rates:
NSS: 1 MCS: 0-9
NSS: 2 MCS: 0-9
NSS: 3 MCS: 0-9

Mode : AP Only

Stations List
MAC Associated Authorized RSSI PSM SGI STBC Tx rate Rx rate Connect
Time
00:01:E3:68:74:46 Yes Yes -32dBm Yes No No 1M 54M 00:21:11

SSID: "Michl5"
RSSI: 0 dBm SNR: 0 dB noise: -92 dBm Channel: 36/80
BSSID: 38:2C:4A:4B8:F4 Capability: ESS
Supported Rates: [ 6(b) 9 12(b) 18 24(b) 36 48 54 ]
VHT Capable:
Chanspec: 5GHz channel 42 80MHz (0xe02a)
Primary channel: 36
HT Capabilities:
Supported MCS : [ 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21
22 23 ]
VHT Capabilities:
Supported VHT (tx) Rates:
NSS: 1 MCS: 0-9
NSS: 2 MCS: 0-9
NSS: 3 MCS: 0-9
Supported VHT (rx) Rates:
NSS: 1 MCS: 0-9
NSS: 2 MCS: 0-9
NSS: 3 MCS: 0-9

Mode : AP Only

Stations List
MAC Associated Authorized RSSI PSM SGI STBC Tx rate Rx rate Connect
Time
90:18:7C2:6A:85 Yes Yes -45dBm No Yes No 108M 150M 00:02:27
E8:2A:EA:90:F5:42 Yes Yes -52dBm No Yes Yes 526.5M 866.7M 00:20:42
40:30:04:24:31:62 Yes Yes -62dBm Yes No No 65M 65M 00:21:01


But I'm annoyed about the ASUS support. There only people who question catalog/basic questions. Typical first level support.
I have suggested that a technician or programmer looks at the problem in a remote maintenance, but apparently there is no third level support at ASUS.
Perhaps Merlin is more interessted to improve Merlin firmware.

 

[RMerlin]

I don't understand what you are trying to say here, sorry. Your client does get a DHCP lease, it also shows under the list of associated wifi clients, so to me it looks like it's working perfectly normally - I don't see anything wrong in what you pasted.

 

[Michl]

Hello RMerlin
Sorry. My english is a little bad

I think, I should tell you the story at beginning.

I have bought a new router ( ASUS RT-AC68U).
I applied my old settings from my old Linksys WRT54G with DD-WRT.
All seems to work.
But after a few hours (usually next morning), all my devices which are connected to 2,4GHz Wifi has loose there connections and a reconnect fails.
5 GHz network seems to work better. But also not perfectly.

I had contact ASUS support. At the end, I should replace the device. It could be defect.
But my second device shows same behaviour.
I tried ASUSWRT-Merlin and DD-WRT.
At DD-WRT all my client devices works perfectly, so I am happy. But stock or merlin firmware looks more modern. and my intension is to improve firmware for users which uses stock or merlin firmware.

I think, the reason isn't the client or driver, because 4 different client devices can't connect to wifi.
- Windows computer (DELL M3800)
- Android smartphone (Galaxy S3)
- Apple iPad 2
- Old VoIP DECT (Siemens Gigaset SL75WLAN)

If you interested for this strange behaviour, I would be cooperative to find the problem.

 

[octopus]

Have you tried to let your client "forget" remove wifi network and reconnect again?

 

[RMerlin]

Also, make sure you use a fixed channel number (ideally 1, 6 or 11), in case your router might be switching to a channel that's not supported by your clients.

 

[Michl]

Also, make sure you use a fixed channel number (ideally 1, 6 or 11), in case your router might be switching to a channel that's not supported by your clients.

Of course.
I tried the suggestions of "staticfree" and "chris.at" in my first post (http://www.snbforums.com/threads/wifi-on-rt-ac68u-unuseable-mad.23054/)

Is there (on router) any logs available which are helpful?

 

[Michl]

Have you tried to let your client "forget" remove wifi network and reconnect again?

That seems to me at most a workaround, not a fix

My try of a reconnection shows my log above.
But I tried only to disable wifi on my smartphone and reactivate again.
I have not removed all the wifi profile, so I did not have to re-enter my security key.
The first 4 blocks shows different states of reconnection.
1) disable wifi on smartphone
2) enable wifi on smartphone
3) smartphone tries to get a dynamic IP
4) smartphone tries a logon to network

But this steps ends never in a succesful connection.

As you can see, the router never knows about the device in his list.

After that, I changed to my 5G wifi profile on android and the device logged on in in a few seconds (section 5 - "Verbindung mit 5G"). Now, the device appears in list "station list".

 

[RMerlin]

Is there (on router) any logs available which are helpful?

Not really. There's very little logged by the wireless driver, and chances are you'd get more information by the client's log as to the reason for the failure to reconnect.

 

[Michl]

Is driver not open source?

Do you believe, you can't improve anything?
Do you have interest for a remote maintenance like team viewer?

 

[RMerlin]

Is driver not open source?

No, it's a proprietary driver from Broadcom.

 

[Michl]

No, it's a proprietary driver from Broadcom.

Okay. But why does it work in DD-WRT??

 

[RMerlin]

Okay. But why does it work in DD-WRT??

Could be a number of reasons. Different driver, kernel, default settings, etc...

Sent from my Nexus 4 using Tapatalk

 

[Michl]

It's really strange.

Yesterday, I received an ASUS RT-AC56U and I checked whether this device shows same behaviour.
Router runs in factory settings except own SSID and password for wifi.
I powered off all my wifi devices except my Galaxy S3.

In the morning (after 7 hours) the same behaviour/result. S3 has no more wifi connection and can't reconnect to wifi.

I wonder why other users do not have these problems.

 

[Michl]

No, it's a proprietary driver from Broadcom.

But perhaps other services are terminated unexpected!?
Do you have contact to broadcom as programer if reason is wifi driver?

 

[ecnav]

You might want to pay closer attention as to when it is losing the connection. I have had this problem before for a while and realized that my next door neighbor comes home at a certain time, and puts their baby to sleep and turns on the wireless baby monitor camera.

As for you claiming it is working with DD-WRT, you might want to validate that some more. It may just be coincidence.