SmartConnect/BSD error messages

[nagyimre1980]

Send a message to Asus asking them to add a switch for it. In the meantime, if you're using Merlin's firmware set System Log - General Log > Log only messages more urgent than = alert.

It’s set up like this, and yet messages keep coming: e.g., Smart Connect

 

[ColinTaylor]

It’s set up like this, and yet messages keep coming: e.g., Smart Connect

That's interesting. I don't use Smart Connect so can you post a dozen or so lines from the log so that I know what you're seeing?

 

[nagyimre1980]

That's interesting. I don't use Smart Connect so can you post a dozen or so lines from the log so that I know what you're seeing?

Jul 29 18:38:51 bsd: bsd: Sending act Frame to 0a:******* with transition target eth10 ssid c8:*******
Jul 29 18:38:52 bsd: bsd: STA:0a******** no response
Jul 29 18:38:52 bsd: bsd: Sending act Frame to 0a:******** with transition target eth10 ssid c8:********
Jul 29 18:38:54 bsd: bsd: STA:0a:****** no response
Jul 29 18:39:59 bsd: bsd: Sending act Frame to 0a:******* with transition target eth10 ssid c8:*******
Jul 29 18:40:00 bsd: bsd: STA:0a:******* no response
Jul 29 18:40:00 bsd: bsd: Sending act Frame to 0a:******** with transition target eth10 ssid c8:*******
Jul 29 18:40:01 bsd: bsd: STA:0a:****** no response
Jul 29 18:40:26 bsd: bsd: Sending act Frame to 0a:******* with transition target eth10 ssid c8:******
Jul 29 18:40:27 bsd: bsd: STA:0a:******** no response
Jul 29 18:40:27 bsd: bsd: Sending act Frame to 0a:********* with transition target eth10 ssid c8:*********
Jul 29 18:40:28 bsd: bsd: STA:0a:****** no response

 

[nagyimre1980]

I deleted MAC addresses. I have a lot of these entries! I live in a big house, and I get these entries after every major movement. Hundreds per hour! This is not normal!

 

[ColinTaylor]

I deleted MAC addresses. I have a lot of these entries! I live in a big house, and I get these entries after every major movement. Hundreds per hour! This is not normal!

I turned on Smart Connect on my router and see the problem you have. For some reason bsd is logging its messages with a severity level of emergency. This sounds like a bug as I can't think why it should be logging at anything above notice level. I can't see any way for the user to change the bsd severity level, and unfortunately this is a closed source binary supplied by Asus. So again, this is something that Asus will have to fix.

Jul 29 18:07:56 RT-AX86U user.emerg bsd: bsd: Sending act Frame to 16:12:40:db:76:ab with transition target eth6 ssid f0:2f:74:92:37:d8
Jul 29 18:07:56 RT-AX86U user.emerg bsd: bsd: BSS Transit Response: ifname=eth7, event=156, token=1, status=1, mac=00:00:00:00:00:00
Jul 29 18:07:56 RT-AX86U user.emerg bsd: bsd: BSS Transit Response: STA reject
Jul 29 18:07:56 RT-AX86U user.emerg bsd: bsd: Skip STA:16:12:40:db:76:ab reject BSSID
Jul 29 18:19:43 RT-AX86U user.emerg bsd: bsd: Sending act Frame to 64:6e:69:2b:c8:0d with transition target eth7 ssid f0:2f:74:92:37:dc
Jul 29 18:19:44 RT-AX86U user.emerg bsd: bsd: STA:64:6e:69:2b:c8:0d no response
Jul 29 18:19:44 RT-AX86U user.emerg bsd: bsd: Sending act Frame to 64:6e:69:2b:c8:0d with transition target eth7 ssid f0:2f:74:92:37:dc
Jul 29 18:19:45 RT-AX86U user.emerg bsd: bsd: STA:64:6e:69:2b:c8:0d no response
Jul 29 18:34:02 RT-AX86U user.emerg bsd: bsd: Sending act Frame to c0:35:32:16:dd:7f with transition target eth7 ssid f0:2f:74:92:37:dc
Jul 29 18:34:02 RT-AX86U user.emerg bsd: bsd: BSS Transit Response: ifname=eth6, event=156, token=4, status=0, mac=f0:2f:74:92:37:dc
Jul 29 18:34:02 RT-AX86U user.emerg bsd: bsd: BSS Transit Response: STA accept
Jul 29 18:39:03 RT-AX86U user.emerg bsd: bsd: Sending act Frame to c0:35:32:16:dd:7f with transition target eth7 ssid f0:2f:74:92:37:dc
Jul 29 18:39:03 RT-AX86U user.emerg bsd: bsd: BSS Transit Response: ifname=eth6, event=156, token=4, status=0, mac=f0:2f:74:92:37:dc
Jul 29 18:39:03 RT-AX86U user.emerg bsd: bsd: BSS Transit Response: not for token 5
Jul 29 18:39:03 RT-AX86U user.emerg bsd: bsd: Sending act Frame to c0:35:32:16:dd:7f with transition target eth7 ssid f0:2f:74:92:37:dc
Jul 29 18:39:03 RT-AX86U user.emerg bsd: bsd: BSS Transit Response: ifname=eth6, event=156, token=5, status=0, mac=f0:2f:74:92:37:dc
Jul 29 18:39:03 RT-AX86U user.emerg bsd: bsd: BSS Transit Response: not for token 6

 

[dave14305]

I can't see any way for the user to change the bsd severity level,

If you look at the bsd -H help, there seems to be a bitmask available for DEBUG messages, and I see some bsd nvram variables have a hex value in them. But there are many bit values in the help output, so not sure which might influence the logging, if any.

 

[ColinTaylor]

If you look at the bsd -H help, there seems to be a bitmask available for DEBUG messages, and I see some bsd nvram variables have a hex value in them. But there are many bit values in the help output, so not sure which might influence the logging, if any.

Yeah, I saw those messages but couldn't see any way of using them. Nothing in nvram looked like an obvious candidate to me.

 

[nagyimre1980]

I turned on Smart Connect on my router and see the problem you have. For some reason bsd is logging its messages with a severity level of emergency. This sounds like a bug as I can't think why it should be logging at anything above notice level. I can't see any way for the user to change the bsd severity level, and unfortunately this is a closed source binary supplied by Asus. So again, this is something that Asus will have to fix.

Jul 29 18:07:56 RT-AX86U user.emerg bsd: bsd: Sending act Frame to 16:12:40:db:76:ab with transition target eth6 ssid f0:2f:74:92:37:d8
Jul 29 18:07:56 RT-AX86U user.emerg bsd: bsd: BSS Transit Response: ifname=eth7, event=156, token=1, status=1, mac=00:00:00:00:00:00
Jul 29 18:07:56 RT-AX86U user.emerg bsd: bsd: BSS Transit Response: STA reject
Jul 29 18:07:56 RT-AX86U user.emerg bsd: bsd: Skip STA:16:12:40:db:76:ab reject BSSID
Jul 29 18:19:43 RT-AX86U user.emerg bsd: bsd: Sending act Frame to 64:6e:69:2b:c8:0d with transition target eth7 ssid f0:2f:74:92:37:dc
Jul 29 18:19:44 RT-AX86U user.emerg bsd: bsd: STA:64:6e:69:2b:c8:0d no response
Jul 29 18:19:44 RT-AX86U user.emerg bsd: bsd: Sending act Frame to 64:6e:69:2b:c8:0d with transition target eth7 ssid f0:2f:74:92:37:dc
Jul 29 18:19:45 RT-AX86U user.emerg bsd: bsd: STA:64:6e:69:2b:c8:0d no response
Jul 29 18:34:02 RT-AX86U user.emerg bsd: bsd: Sending act Frame to c0:35:32:16:dd:7f with transition target eth7 ssid f0:2f:74:92:37:dc
Jul 29 18:34:02 RT-AX86U user.emerg bsd: bsd: BSS Transit Response: ifname=eth6, event=156, token=4, status=0, mac=f0:2f:74:92:37:dc
Jul 29 18:34:02 RT-AX86U user.emerg bsd: bsd: BSS Transit Response: STA accept
Jul 29 18:39:03 RT-AX86U user.emerg bsd: bsd: Sending act Frame to c0:35:32:16:dd:7f with transition target eth7 ssid f0:2f:74:92:37:dc
Jul 29 18:39:03 RT-AX86U user.emerg bsd: bsd: BSS Transit Response: ifname=eth6, event=156, token=4, status=0, mac=f0:2f:74:92:37:dc
Jul 29 18:39:03 RT-AX86U user.emerg bsd: bsd: BSS Transit Response: not for token 5
Jul 29 18:39:03 RT-AX86U user.emerg bsd: bsd: Sending act Frame to c0:35:32:16:dd:7f with transition target eth7 ssid f0:2f:74:92:37:dc
Jul 29 18:39:03 RT-AX86U user.emerg bsd: bsd: BSS Transit Response: ifname=eth6, event=156, token=5, status=0, mac=f0:2f:74:92:37:dc
Jul 29 18:39:03 RT-AX86U user.emerg bsd: bsd: BSS Transit Response: not for token 6

@RMerlin

Can you help? I’ve already written to ASUS, and they didn’t help! Maybe if you write, they will! Thank you!

 

[dave14305]

Yeah, I saw those messages but couldn't see any way of using them. Nothing in nvram looked like an obvious candidate to me.

Oh, there’s bsd_msglevel and bsd_dbg variables that are disabled in defaults.c but still exist in the binary. Worth a try.

https://github.com/RMerl/asuswrt-merlin.ng/blob/5896a9016856bcc4b5387be0125ad8bdf345ffee/release/src/router/shared/defaults.c#L1465

 

[ColinTaylor]

@nagyimre1980 Perhaps you could try this and see if it makes a difference:

nvram set bsd_msglevel="0"
service restart_bsd

 

[dave14305]

@nagyimre1980 Perhaps you could try this and see if it makes a difference:

nvram set bsd_msglevel="0"
service restart_bsd

I tried it and it didn’t seem to work for me. Never used Smart Connect until today’s test.

nvram set bsd_msglevel=0x000001
nvram set bsd_dbg=0
service restart_bsd

 

[RMerlin]

bsd_msglevel should be a mask to determine which event types are getting logged. If setting it to "0" does not prevent logging, then Asus/Broadcom might have changed something or hardcoded logging in recent builds, in which case it is what it is.

 

[nagyimre1980]

bsd_msglevel should be a mask to determine which event types are getting logged. If setting it to "0" does not prevent logging, then Asus/Broadcom might have changed something or hardcoded logging in recent builds, in which case it is what it is.

I’d be grateful if you could write to ASUS about this. I’ve contacted customer service multiple times with no results. Thank you!