[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [mosquitto-dev] Use of mesh type of bridge MQTT broker
|
Yes, that's correct. The best you could do here is make a custom bridge that encodes provenance in messages as user properties and use that to decide whether a message is delivered or not.
Thank you.
Create a mesh with MQTT brokers as shown in the attached image and bridge messages to each of them.
Device A publishes message A to MQTT broker A. Then MQTT broker A will forward it to MQTT brokers B, C, and D.
Then, MQTT broker B forwards it to MQTT brokers C and D.
MQTT broker C does not know that message A forwarded from MQTT broker B was forwarded from MQTT broker A, so it forwards it to MQTT broker A.
I am using MQTT broker as a bridge. So I want to make the bridge like a mesh
type.
But, when I make it a mesh type, it keeps repeating the bridge forever.
Is it possible to use mosquitto to stop the bridge from repeating?
Can you help me? Thnak you.
Can you describe your scenario in a bit more detail? I wrote a separate multi-way bridge for connecting brokers and all it does is subscribe with "no local", then deliver any matching messages. Of course, if there is more than one of these bridges running, "no local" wouldn't work, so there'd be no way to track which messages should and shouldn't be forwarded. "mesh" sounds a bit like you're trying that, but I'm only guessing at your topology.
_______________________________________________
mosquitto-dev mailing list
mosquitto-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/mosquitto-dev