MQTT streaming username and password not sent from MR

braham2019
Here to help

MQTT streaming username and password not sent from MR

Hi,

 

I have succesfully used MQTT for presence detection with a MQTT broker without username/password. 

However, when I reconfigure the MQTT server to require username and password, they are not being sent from the MR to my broker. They are, of course, configured in the Dashboard correctly. And they are working because I have other subscribers and publishers that use these credentials.

 

This is the message I receive in the Mosquitto log:

 

2022-11-23 21:47:13: New connection from 192.168.0.74:41098 on port 1883.
error: received null username or password for unpwd check

 

4 REPLIES 4
alemabrahao
Kind of a big deal
Kind of a big deal

Have you performed a packet capture? It's supposed to be simple to configure, maybe It's a bug.

I am not a Cisco Meraki employee. My suggestions are based on documentation of Meraki best practices and day-to-day experience.

Please, if this post was useful, leave your kudos and mark it as solved.

It's a bit more complicated it appears. I have 4 MR AP. One MR18 doesn't check in (old firmware). The two MR33 work just fine (running firmware MR 29.4.1)

 

The MR76 (MR 29.4.1) on the other hand doesn't seem able to login.

 

2022-11-24 07:10:16: New connection from 192.168.0.74:45932 on port 1883.
error: received null username or password for unpwd check
2022-11-24 07:10:16: Client <unknown> disconnected, not authorised.

  I can do a packet capture, but I'm not sure what to look for.

alemabrahao
Kind of a big deal
Kind of a big deal

Have you checked it:

 

  • MQTT is supported on Wi-Fi 5 wave 2 APs as well as Wi-Fi 6 APs and later. Access Points that do not support the feature will not forward any MQTT message. If your network has APs which support MQTT, you will be able to navigate to Wireless > IoT radio settings in the dashboard, and find the new tab "MQTT" right next to Bluetooth.
  • MQTT is only supported on MR 28.X firmware and later.
  • Cisco Meraki MR devices only support MQTT version 3.1.1

I don't know if it makes sense, but is a good idea to check it.

I am not a Cisco Meraki employee. My suggestions are based on documentation of Meraki best practices and day-to-day experience.

Please, if this post was useful, leave your kudos and mark it as solved.
braham2019
Here to help

Well, now it does seem to work (but not for all AP's) after I entered credentials for the eleventh time (it always does that every time I log a support ticket 🙄).

 

I have 4 AP's: one MR18, two MR33 and one MR76. It appears indeed the MR18 doesn't show up in the Mosquitto logs (fine with me). All are on MR 29.4.1 except the MR18 (on MR 26.8.3)

 

2022-11-23 22:20:19: New connection from 192.168.0.73:48044 on port 1883.
2022-11-23 22:20:19: New client connected from 192.168.0.73:48044 as Q2PD-87Z4-EM6V:1911709132 (p2, c1, k60, u'mqtt').
2022-11-23 22:20:25: New connection from 192.168.0.72:35869 on port 1883.
2022-11-23 22:20:25: New client connected from 192.168.0.72:35869 as Q2PD-87NW-4884:477406211 (p2, c1, k60, u'mqtt').
2022-11-23 22:20:45: New connection from 192.168.0.74:41422 on port 1883.
error: received null username or password for unpwd check
2022-11-23 22:20:45: Client <unknown> disconnected, not authorised.

 

So both the MR33 now work correctly (I see theire login in Mosquitto), but the MR76 (192.168.0.74) has issues

Get notified when there are additional replies to this discussion.
Welcome to the Meraki Community!
To start contributing, simply sign in with your Cisco account. If you don't yet have a Cisco account, you can sign up.
Labels