RIOT-OS/RIOT
RIOT-OS/RIOT
1
0
Fork 0
mirror of https://github.com/RIOT-OS/RIOT.git synced 2025-01-17 05:32:45 +01:00
Code Releases Activity

emcute example: Added more FAQ entries to readme (#12611)

Browse Source 
* examples/emcute_mqttsn: add more FAQ entries

Co-authored-by: Alexandre Abadie <alexandre.abadie@inria.fr>
This commit is contained in:
Chamaeleon- 2020-07-10 14:21:47 +02:00 committed by GitHub
parent 6b9edb76bd
commit 547a880fa6
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 15 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
examples/emcute_mqttsn/README.md
View File

@ -105,3 +105,18 @@ default, this example sets this statically ID to `gertrud`. If you want to
connect more than one node to the broker, you need to set a custom ID for each
node during compile time. Simply use the `EMCUTE_ID` environment variable for
this, e.g. build with `EMCUTE_ID=horst make all`.
### I see incoming messages in RSMB, but no outgoing message seems to arrive?
The UDP socket handling for IPv6 based endpoints in the `Mosquitto.rsmb`
implementation is buggy when it comes to handling link local addresses,
as the implementation does not remember the interface on which data comes in,
hindering it from sending out any responses.
Workaround: either use global IPv6 addresses or [ULAs](https://tools.ietf.org/html/rfc4193).
### I have a problem with reusing topics, what could it be?
It also seems that the `Mosquitto.rsmb` implementation has a bug when it comes
to subscribing to topics: if a topic name was formerly registered and the same
topic name is later used for issuing a subscription request, the gateway will
assign a new topic ID to the same topic name, so publish messages to the
initially assigned topic ID will not be seen by that subscription.