Hi Peter,
it was some “years ago”, so it may be deprecated.
The WebUI offers you a “very basic” variant to enter the bootstrap config for a client.
If you want to change such a configuration, you’re intended to use the REST API, see
https://dev.eclipse.org/mhonarc/lists/leshan-dev/msg00803.html
Mit freundlichen Grüßen / Best regards
Achim Kraus
(INST/ECS4)
Bosch Software Innovations GmbH | Stuttgarter Straße 130 | 71332 Waiblingen |
GERMANY | www.bosch-si.com
Sitz: Berlin, Registergericht: Amtsgericht Charlottenburg; HRB 148411 B
Aufsichtsratsvorsitzender: Dr.-Ing. Thorsten Lücke; Geschäftsführung: Dr.-Ing. Rainer Kallenbach, Michael Hahn
From: leshan-dev-bounces@xxxxxxxxxxx [mailto:leshan-dev-bounces@xxxxxxxxxxx]
On Behalf Of Peter Waher
Sent: Montag, 28. August 2017 09:41
To: leshan-dev@xxxxxxxxxxx
Subject: [leshan-dev] Incorrect Bootstrap server Uri configured
Hello
I have a question regarding the test bootstrap server at leshan.eclipse.org/bs (coap:leshan.eclipse.org:5783 or :5784):
If I explicitly ask my client to connect to the non-default CoAP port, bootstrap is initiated and the security and server objects are written to my device. However, the URI to the bootstrap server
is not correct. The URI includes the default port numbers (5683/5684), and not the actual ones (5783/5784). This results in an error, when I want to request a new bootstrap initiation, but from the programmed bootstrap URI as defined by the corresponding security
object configured the first time).
This is also reflected in the Leshan GUI:
![cid:image001.png@01D31FE6.ED4A1230](pnghPi5eSqam5.png)
But I find no way to update the bootstrap URI, when I register a configuration: (I can only explicitly write the URL of one LWM2M Server.)
![cid:image002.png@01D31FE6.ED4A1230](pngnnfHVK6K61.png)
Is the bootstrap URI not supposed to point to the 5783/5784 port numbers used by the bootstrap server instead of the CoAP default 5683?
Best regards,
Peter Waher