Replies: 1 comment 1 reply
-
Multiple endpoints are not yet supported. Only one default (without TLS) and one encrypted endpoint can be used. But there are already branches which add support for a feature called "Endpoints" which are basically a list of endpoints like TCP, WebSocket etc. which can have different settings. But I cannot tell when this is ready to be released. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello.
I'm a bit new to MQTTnet. We have a use case where we need to support multiple devices, each having a unique endpoint. Each device will communicate using the same IP address but on different ports. We need to support connections to each device over TLS, and we must also support default connection (non-TLS). Also, we only support one connection at a time. Our requirements are basically as follows. These aren’t the actual values but just added for the example.
Device A: 127.0.0.1:50005 (TLS 1.2 / TLS 1.3)
Device B: 127.0.0.1:50006 (TLS 1.2 / TLS 1.3)
Default endpoint: 127.0.0.1:50003
We would like to do this using a single Server / Broker, something like the following. However, this doesn’t seem to work. The broker starts successfully, but when trying to connect the client, only the device 2 client connection is successful. It seems to make some sense that this wouldn’t work, because device 2 endpoint options aren’t appending, but instead overwriting device 1.
Ideally, we would like to create / start our server broker once (e.g. app start or when user clicks connect) so that when changing from device 1 to device 2, or vice-versa, we won’t have to stop the broker, reconfigure it to use the endpoint options associated with the new selected device and then restart it.
Is this possible?
Thanks!
Beta Was this translation helpful? Give feedback.
All reactions