What's new

kernel: wl0: random key value: -

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

leerees

Senior Member
I'm seeing this in the logs every 10 seconds
kernel: wl0: random key value: -

Firmware Version:3.0.0.4.386_41712

Does anybody know what this means?
 
Last edited:
We can't see what you see.
 
Hello, the same thing happens to me too. She repeats herself continuously in the syslog. What can happen? I have both 2.4 and 5 Ghz bands configured with fixed channels and bandwidth.

My model router is RT-AC1200G+

Code:
Mar 25 21:52:40 rc_service: httpd 293:notify_rc restart_wireless
Mar 25 21:52:40 kernel: wl0: random key value: D3E3C38D200A50D45CE9B5496C99CDA7C1339E5FF48213F64DDDEF10F574A633
Mar 25 21:52:40 kernel: wl0: random key value: 2609B31EEC51773080129784DC91156739CAA8A4BC555027C7B00C339C0A56BC
Mar 25 21:52:41 kernel: wl1: random key value: 8614614BF5A4AD2796C649C8B1BA72286EB975CAAE51728F6B82A3ECE09AFB2C
Mar 25 21:52:41 kernel: wl1: random key value: F968A5DBD121890B485942CA1652B29794BEA5F3D064064C3261930E67883C40
Mar 25 21:59:37 kernel: wl1: random key value: 6A4FA4F2D86D3C96E4B7DA42D2156F577AB8151DA8EA47533A99D4CCA661330B

1616706596033.png

1616706716103.png
 
Last edited:
May be related to a client that needs a wifi driver update.
 
I see the same in my RT-AC1200G+, and it interrupts my phone WiFi at times. It appeared in some of the newer firmwares from ASUS. When it happens, an exclamation mark appears on the phone's WiFi icon, sometimes. Quite annoying. Happens on 2 phones from separate manufacturers.
 
Normal, happens when a device is switched off, or turns itself off, the random key generation is a security feature to prevent data getting in the hands of evil monsters during disasociation.
 
Last edited:
Normal, happens when a device is switched off, or turns itself off, the random key generation is a security feature to prevent data getting in the hands of evil monsters during dissociation.
That is all nice and dandy, as well true, but when it happens every few min and disconnects your clients what is the solution to this annoyance. I for example run AsusWrt Merlin 386.5_2 on RT-AX86U router and that thing is happening all the time. Drops connections while it negotiates new key etc...never stops. ideas?
 
Drops connections while it negotiates new key etc...never stops. ideas?
It doesn't "drop the connection while it negotiates new key". It will however have to negotiate new key if a connection is dropped and then reconnects. So your problem is not the key negotiation itself but a connection issue.
 
It doesn't "drop the connection while it negotiates new key". It will however have to negotiate new key if a connection is dropped and then reconnects. So your problem is not the key negotiation itself but a connection issue.
That is true, but what can cause the connection drop since the log itself is not registering any condition or the fact it dropped I get them all the time. Appears like every device in my home is dropping all the time and negotiating for new key(s).
 
That is true, but what can cause the connection drop since the log itself is not registering any condition or the fact it dropped I get them all the time. Appears like every device in my home is dropping all the time and negotiating for new key(s).
The message normally precedes another set of messages which indicates the reason, like those shown in this thread: https://www.snbforums.com/threads/what-does-reassoc-mean-in-the-logs.79090/

Typically this is caused by the client device being in sleep mode.
 
The message normally precedes another set of messages which indicates the reason, like those shown in this thread: https://www.snbforums.com/threads/what-does-reassoc-mean-in-the-logs.79090/

Typically this is caused by the client device being in sleep mode.
maybe in that person's router's log case, but not on mine. Just a constant flood of those keys being re-issued. Never had this before the last two firmware upgrades (I run AsusWrt-Merlin on mine) or maybe I didn't pay as much attention as I am recently but no I don't have it in my log, while it could make sense that it is to those devices that are "a sleep". However, I have another network in another property where I use a different Asus rt model and AiMesh with two of a kind rt's and few AP's and this is NOT present in any of the rt logs, just on this one and it could be also this asus router specific or few other models. The one I see it on is Asus RT-AX86U while none on Asus RT-AC68U with the exact same firmware version, which now is AsusWrt-Merlin 386.5_2....so I am still digging but so far didn't totally figure it out.
 
Hello, have you found the cause? I've started to see the same in my log a few days back without any obvious change to the network / device setup. I just noticed, while this happens, my guest networks goes down.
 
I just noticed this on mine.

I had 2 devices that have this behaviour.

1 device is a Chinese solar inverter which should be on the network. This loves to reconnect every 20 seconds apparently.
I have it on its own guest network with no intranet access. I don't know why it reconnects every 20 seconds but others have said similar about their inverters. So it continues to just do it's annoying thing.

The other device I have no idea what it is. I have decent records of every Mac address on my network. I disable random Mac on all the mobile phones connected. I don't know what this Mac is. And I don't believe it belongs on my network.
It doesn't get an IP on the network so doesn't appear to actually connect and perhaps doesn't have the correct password for the network.
My solution was to enable Mac filtering on the problem guest network. In particular I setup a reject list that rejected the problem mac.
Only other solution I found was to disable the guest network interface it was trying to connect to altogether.

Things I checked:
1)
System log
I needed to set "Log only messages more urgent than" to info. Notice filtered out the needed device mac info.
Note the Mac address of the device(s)

2)
Check the Mac address on an online Mac address lookup website.
It may assist to give you a brand name or an era for the device?

3)
System log -> wireless log
Can you find the Mac address?
Wait around for a few minutes to see if it pops up as if it isn't successful in connecting it might only show up very briefly sometimes.
Does the device have an IP address? This proves it did log into your network.
What wireless standard is it using eg 802.11n? This may help you estimate an age or type of the device.
It might help prove if this device should be on the network.

4)
Network Map -> view list -> interface
Basically the same as #3 but is a different system and may show up things slightly differently.
 
Last edited:

Latest threads

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top