Inclusion of Docker Image for Debian 12 on Raspberry Pi

[Waz-Cpt]

Hello There,

Would be great to include an image for raspberry pi in your docker images.

[bunkeriot]

@Waz-Cpt Absolutely! I’ve added that to my to-do list and will keep you posted once it’s released.

[Waz-Cpt]

Obviously, if your Home Assistant Addon comes first I would not need this.

Is your MQTT broker able to run with password and username access for mqtt clients that support this and with ACL for devices that do not autentication simultanteously?

[bunkeriot]

@Waz-Cpt Yes, if you to "Broker Config" menu in BunkerM and you enable "Allow Anonymous Accesss" your MQTT clients will be able to access with and without password

[Waz-Cpt]

Would you be able to have a ACL in place to only allow specific ID Address to connect?

[bunkeriot]

@Waz-Cpt In the "Connected Clients" menu, you can choose which MQTT client to enable or disable based on their ID, even if they are part of your ACL.

[Waz-Cpt]

Is it possible to bridge brokers? I am thinking it is best to keep the devices that do not support username and password authentication to run on their own VLAN with no bridging across directly and then either have two brokers bridge across the VLANs.

Other option is to have the broker listening on two seperate VLANs.

Any of this possible? There are many older IIoT products that were design without thinking about a network having an internet connection.

[bunkeriot]

@Waz-Cpt Yes, bridging brokers will be a feature included in the upcoming BunkerM Pro version! For now, this functionality isn’t available in the community version.

Regarding the broker listening on two separate VLANs, this is something I offer as part of a customized BunkerM clustering development service. It’s absolutely possible and can be tailored to your specific needs, though it’s not part of the community version.

If you’d like to learn more, feel free to reach out at: support@bunkeriot.com.

[Waz-Cpt]

Is this normal?

Then removed clientid prefix and got the following:

[bunkeriot]

@Waz-Cpt You should not remove ID_prefix afterwards. The first message is normal and it's a Mosquitto error message telling you about the features that will be soon deprecated, but still working for now. So just keep the ID_prefix