Re: [mosquitto-dev] user experience report trying to configure a bridge

[Greg Troxel <gdt@xxxxxxxxxx>]

Some updates -- I really hope this is helpful!

I now realize that I cannot figure out from the man page whether one has
to give the local IP address and port and how one specifies that the
local system is running TLS, or if one has to worry about this at all.
(In my case, there is no listener on 1883, and the only listener
configured is TLS.)

A lot of my problem was giving a bad port number on the remote (where
there was a TLS listener, but not mosquitto!).  That made things work
much bettter, but I still don't understand the error messages I got
earlier.

With this fixed, I realize that dns names do work, and the expected cert
name matching is ok.

I also realize that the local connection is logical and one doesn't have
to worry about TLS.

I didn't get from the description about topic that it was the same form
as acl, rather than being a prefix, and that one probably wants
something like "stuff/#".

The man page sort of hints about loops, and try_private talks about loop
detection.  It seems that bridging "foo/# both" between two mosquitto
instances (wtih try_private left default) reliably does the right thing,
and I wonder if the man page intends to caution against that, or if
that's a reasonable thing to do.

If it helps, my use case is a bunch of sensors in multiple places, and a
main broker at a stable IP address.  Some of those places should have
local brokers, so that sensors/monitors/etc. can communicate locally
when the internet is down, but also that normally local monitors can see
remote sensors, and other monitors can see the local sensors.  This
feels normal to me, but maybe it isn't.