[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [wakaama-dev] Wakaama Client Test Object Issues with Leshan server Bootstrap Mode
|
Hi,
I'm glad your issues are resolved. I agree with Simon, Option B is the correct one for your issue #2. However this is possible to do with the wakaama bootstrap server ;) Just edit the examples/bootstrap_server/bootstrap_server.ini file and replace the "Delete=/" by several "Delete=/[Object ID]".
Regards,
David Navarro
-----Original Message-----
From: wakaama-dev-bounces@xxxxxxxxxxx [mailto:wakaama-dev-bounces@xxxxxxxxxxx] On Behalf Of Simon Bernard
Sent: Friday, 15 April, 2016 14:52
To: Wakaama developer discussions <wakaama-dev@xxxxxxxxxxx>
Subject: Re: [wakaama-dev] Wakaama Client Test Object Issues with Leshan server Bootstrap Mode
Hi,
Currently, the leshan bootstrap server start the bootstrap with a delete on /, then send write requests on /0 and /1 depending of the bootstrap configuration you define.
The spec say that delete on / must delete all the instances :
"Only in Bootstrap Interface, the Delete operation MAY targets "/" URI.
In that case, the operation MUST delete all the existing Object Instances - except LWM2M Bootstrap Server Account - in the LWM2M Client; this functionality could be used for initialization purpose before LWM2M Bootstrap Server sends Write operation(s) to the LWM2M Client."
Ideally, at leshan side, a bootstrap configuration should be a sequence of any bootstrap delete request and any bootstrap write request. In this case, users should do anything he want in a bootstrap session. (At mid term, I think this is something we should implement in
Leshan)
So, according to the spec, the right way is B)
But currently there is no easy way to do that with Leshan Bootstrap Server... A solution is to implement your own bootstrap server inspired by LwM2mBootstrapServerImpl and BootstrapResource.
Simon (from Leshan)
Le 14/04/2016 20:19, Kalley, Vibhor a écrit :
> Hi David,
>
> Thanks for your explanation.
>
> ISSUE#1 Is resolved. My enterprise team updated the server yesterday and JSON works fine with the example client.
>
> ISSUE#2 . Makes sense. I noticed Access_Control Object /2 and Test Object implements Delete, hence I don't see both of them after bootstrapping.
> So my question is: If we don't want those instances to be deleted, what is the correct way to do it according to the Spec ?
> Is it
> A) The Client should not implement a delete for those objects ?
> B) The Bootstrap server should only delete specific object like /0 ,
> /1 and not / (Is there a way to do this in Leshan-BS-server ?)
> C) The bootstrap should delete everything and the DM server should create them on registration ?
> D) Up to the developer to decide what to do
>
> Regards
> Vibhor
> -----Original Message-----
> From: wakaama-dev-bounces@xxxxxxxxxxx
> [mailto:wakaama-dev-bounces@xxxxxxxxxxx] On Behalf Of
> wakaama-dev-request@xxxxxxxxxxx
> Sent: Thursday, April 14, 2016 1:24 AM
> To: wakaama-dev@xxxxxxxxxxx
> Subject: wakaama-dev Digest, Vol 21, Issue 6
>
> Send wakaama-dev mailing list submissions to
> wakaama-dev@xxxxxxxxxxx
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://dev.eclipse.org/mailman/listinfo/wakaama-dev
> or, via email, send a message with subject or body 'help' to
> wakaama-dev-request@xxxxxxxxxxx
>
> You can reach the person managing the list at
> wakaama-dev-owner@xxxxxxxxxxx
>
> When replying, please edit your Subject line so it is more specific than "Re: Contents of wakaama-dev digest..."
>
>
> Today's Topics:
>
> 1. Re: Wakaama Client Test Object Issues with Leshan server
> Bootstrap Mode (Navarro, David)
> 2. Re: Wakaama Not Working for Raspbian & Fedora (Navarro, David)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Thu, 14 Apr 2016 08:10:14 +0000
> From: "Navarro, David" <david.navarro@xxxxxxxxx>
> To: Wakaama developer discussions <wakaama-dev@xxxxxxxxxxx>
> Subject: Re: [wakaama-dev] Wakaama Client Test Object Issues with
> Leshan server Bootstrap Mode
> Message-ID:
>
> <D4775DF50A67AE42A7B3D9F6517B87865D16B9ED@xxxxxxxxxxxxxxxxxxxxxxxxxxxx
> >
>
> Content-Type: text/plain; charset="us-ascii"
>
> Hi,
>
> Sorry the whole wakaama-dev list went to my spam folder.
>
> Regarding issue #1, are you using latest leshan ? There was an unsupported JSON feature in leshan parsing. It was fixed a month ago.
>
> For issue #2, this is the expected behavior: during the bootstrap process, the Bootstrap Server deletes all instances of objects. In the examples client, only the test object implements deletion. Thus the result you observe where the 1024 object has no instances.
>
> Regards,
> David Navarro
>
> From: wakaama-dev-bounces@xxxxxxxxxxx
> [mailto:wakaama-dev-bounces@xxxxxxxxxxx] On Behalf Of Kalley, Vibhor
> Sent: Tuesday, 12 April, 2016 18:39
> To: wakaama-dev@xxxxxxxxxxx
> Subject: Re: [wakaama-dev] Wakaama Client Test Object Issues with
> Leshan server Bootstrap Mode
>
> Hi,
>
> Any update on below ?
>
> From: Kalley, Vibhor
> Sent: Friday, April 08, 2016 9:12 PM
> To: wakaama-dev@xxxxxxxxxxx<mailto:wakaama-dev@xxxxxxxxxxx>
> Subject: Wakaama Client Test Object Issues with Leshan server
> Bootstrap Mode
>
> Hi,
>
> I am playing with the Wakaama client in bootstrap mode and I noticed a few issues. Will appreciate if you can help me understand the behavior:
>
> Issue1# If the wakaama client is compile with -D LWM2M_SUPPORT_JSON read the whole instance on one causes the server to throw exceptions. Though I can see the client is sending a response. I believe it's an issue with the leshan demo server. Is that true ?
>
> Issue2# Test Object /1024 and/or resources cannot be read/write after bootstrapping.
> Once the bootstrapping is done and the client tries to register to the leshan demo server, the register message does not contain instances to test object </1024>. Whereas in regular mode the wakaama client registers with instance ids also </1024/10>,</1024/11>,</1024/12> . Is this a bug in wakaama client ? Also the output of the >disp command doesn't print any instances unlike non-bootstrap mode.
>
> Wakaama Client registered after bootstrapping
>> Sending 125 bytes to [10.64.98.70]:5683
> 44 02 34 4D 4D 34 50 7D B2 72 64 11 28 3D 05 65 D.4MM4P}.rd.(=.e
> 70 3D 74 65 73 74 6C 77 6D 32 6D 63 6C 69 65 6E p=testlwm2mclien
> 74 03 62 3D 55 05 6C 74 3D 32 30 FF 3C 2F 3E 3B t.b=U.lt=20.</>;
> 72 74 3D 22 6F 6D 61 2E 6C 77 6D 32 6D 22 3B 63 rt="oma.lwm2m";c
> 74 3D 31 35 34 33 2C 3C 2F 31 2F 30 3E 2C 3C 2F t=1543,</1/0>,</
> 33 2F 30 3E 2C 3C 2F 35 2F 30 3E 2C 3C 2F 36 2F 3/0>,</5/0>,</6/
> 30 3E 2C 3C 2F 31 30 32 34 3E 2C 3C 2F 34 2F 30 0>,</1024>,</4/0
> 3E 2C 3C 2F 37 2F 30 3E 2C 3C 2F 32 3E >,</7/0>,</2>
>
>> disp
> /0: Security object, instances:
> /0/0: instanceId: 0, uri: coap://10.64.98.70:5683, isBootstrap: true, shortId: 111, clientHoldOffTime: 1
> /0/1: instanceId: 1, uri: coap://10.64.98.70:5683, isBootstrap: false, shortId: 123, clientHoldOffTime: 1
> /1: Server object, instances:
> /1/0: instanceId: 0, shortServerId: 123, lifetime: 20, storing: true, binding: U
> /3: Device object:
> time: 1367491215, time_offset: +01:00
> /5: Firmware object:
> state: 1, supported: false, result: 0
> /6: Location object:
> latitude: 27.986065, longitude: 86.922623, altitude: 8495.0000, uncertainty: 0.01, timestamp: 1460174150
> /1024: Test object, instances:
>
>
> Wakaama Client without bootstrapping
>> Sending 153 bytes to [10.64.98.70]:5683
> 44 02 E1 0B 0B E1 C1 7D B2 72 64 11 28 3D 05 65 D......}.rd.(=.e
> 70 3D 74 65 73 74 6C 77 6D 32 6D 63 6C 69 65 6E p=testlwm2mclien
> 74 03 62 3D 55 06 6C 74 3D 33 30 30 FF 3C 2F 3E t.b=U.lt=300.</>
> 3B 72 74 3D 22 6F 6D 61 2E 6C 77 6D 32 6D 22 3B ;rt="oma.lwm2m";
> 63 74 3D 31 35 34 33 2C 3C 2F 31 2F 30 3E 2C 3C ct=1543,</1/0>,<
> 2F 33 2F 30 3E 2C 3C 2F 35 2F 30 3E 2C 3C 2F 36 /3/0>,</5/0>,</6
> 2F 30 3E 2C 3C 2F 31 30 32 34 2F 31 30 3E 2C 3C /0>,</1024/10>,<
> 2F 31 30 32 34 2F 31 31 3E 2C 3C 2F 31 30 32 34 /1024/11>,</1024
> 2F 31 32 3E 2C 3C 2F 34 2F 30 3E 2C 3C 2F 37 2F /12>,</4/0>,</7/
> 30 3E 2C 3C 2F 32 2F 30 3E 0>,</2/0>
>
>> disp
> /0: Security object, instances:
> /0/0: instanceId: 0, uri: coap://10.64.98.70:5683, isBootstrap: false, shortId: 123, clientHoldOffTime: 10
> /1: Server object, instances:
> /1/0: instanceId: 0, shortServerId: 123, lifetime: 300, storing: false, binding: U
> /3: Device object:
> time: 1367491215, time_offset: +01:00
> /5: Firmware object:
> state: 1, supported: false, result: 0
> /6: Location object:
> latitude: 27.986065, longitude: 86.922623, altitude: 8495.0000, uncertainty: 0.01, timestamp: 1460174273
> /1024: Test object, instances:
> /1024/10: shortId: 10, test: 20
> /1024/11: shortId: 11, test: 21
> /1024/12: shortId: 12, test: 22
>
>
> I am using wakaama's lwm2m-client from last week, leshan-bs-server and leshan-demo-server from 2-3 weeks ago.
>
> Thanks
> Vibhor
> ________________________________
> NOTICE OF CONFIDENTIALITY:
> This message may contain information that is considered confidential and which may be prohibited from disclosure under applicable law or by contractual agreement. The information is intended solely for the use of the individual or entity named above. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or use of the information contained in or attached to this message is strictly prohibited. If you have received this email transmission in error, please notify the sender by replying to this email and then delete it from your system.
> ---------------------------------------------------------------------
> Intel Corporation SAS (French simplified joint stock company)
> Registered headquarters: "Les Montalets"- 2, rue de Paris,
> 92196 Meudon Cedex, France
> Registration Number: 302 456 199 R.C.S. NANTERRE
> Capital: 4,572,000 Euros
>
> This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies.
> -------------- next part -------------- An HTML attachment was
> scrubbed...
> URL:
> <https://dev.eclipse.org/mailman/private/wakaama-dev/attachments/20160
> 414/be41dc43/attachment.html>
>
> ------------------------------
>
> Message: 2
> Date: Thu, 14 Apr 2016 08:24:07 +0000
> From: "Navarro, David" <david.navarro@xxxxxxxxx>
> To: Wakaama developer discussions <wakaama-dev@xxxxxxxxxxx>
> Subject: Re: [wakaama-dev] Wakaama Not Working for Raspbian & Fedora
> Message-ID:
>
> <D4775DF50A67AE42A7B3D9F6517B87865D16BA0C@xxxxxxxxxxxxxxxxxxxxxxxxxxxx
> >
>
> Content-Type: text/plain; charset="utf-8"
>
> Hi,
>
> Sorry the whole wakaama-dev list went to my spam folder.
>
> If things work well on Galileo and not on ARM based board, there is probably an endianness issue. Are you defining LWM2M_SUPPORT_JSON ?
> Since the encoding code changed recently, could you retry using a more recent version of wakaama ?
>
> Regards,
> David Navarro
>
> From: wakaama-dev-bounces@xxxxxxxxxxx
> [mailto:wakaama-dev-bounces@xxxxxxxxxxx] On Behalf Of Ashish Yadav
> Sent: Monday, 11 April, 2016 07:59
> To: Wakaama developer discussions <wakaama-dev@xxxxxxxxxxx>
> Subject: Re: [wakaama-dev] Wakaama Not Working for Raspbian & Fedora
>
> Hi Team,
>
> Any solution on below?
>
> On 6 April 2016 at 14:52, Ashish Yadav <ashish.9433@xxxxxxxxx<mailto:ashish.9433@xxxxxxxxx>> wrote:
> Hi,
>
> I am using Wakaama Version downloaded from Github in the Month of Jan.
>
> It run pretty well when i compile and run it on Yocto Linux for my
> Intel Galileo Board, but i am facing below issues for Raspbian
> (Raspberry Pi Board), Fedora 22 (Samsung Artik Board)
>
> I get INTERNAL_SERVER_ERROR on reading some of the parameters, while some reads run pretty well as seen below.
>
> [Inline images 1]
>
>
> Could you please guide me as to whether there is any dependency for running it on Raspbian & Fedora?
>
>
> --
>
>
> Thanks & Regards,
>
> Ashish Yadav
>
>
>
> --
>
>
> Thanks & Regards,
>
> Ashish Yadav
> Phone: +91- 9867349433|
> ashish.9433@xxxxxxxxx<mailto:ashish.9433@xxxxxxxxx> | Skype:
> ashish.9433
> Website: http://heart-hackers.com<http://heart-hackers.com/> || Blog:
> http://tech.heart-hackers.com<http://tech.heart-hackers.com/>
> ---------------------------------------------------------------------
> Intel Corporation SAS (French simplified joint stock company)
> Registered headquarters: "Les Montalets"- 2, rue de Paris,
> 92196 Meudon Cedex, France
> Registration Number: 302 456 199 R.C.S. NANTERRE
> Capital: 4,572,000 Euros
>
> This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies.
> -------------- next part -------------- An HTML attachment was
> scrubbed...
> URL:
> <https://dev.eclipse.org/mailman/private/wakaama-dev/attachments/20160
> 414/09a4a204/attachment.html>
> -------------- next part -------------- A non-text attachment was
> scrubbed...
> Name: image002.jpg
> Type: image/jpeg
> Size: 27270 bytes
> Desc: image002.jpg
> URL:
> <https://dev.eclipse.org/mailman/private/wakaama-dev/attachments/20160
> 414/09a4a204/attachment.jpg>
>
> ------------------------------
>
> _______________________________________________
> wakaama-dev mailing list
> wakaama-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or
> unsubscribe from this list, visit
> https://dev.eclipse.org/mailman/listinfo/wakaama-dev
>
> End of wakaama-dev Digest, Vol 21, Issue 6
> ******************************************
> _______________________________________________
> wakaama-dev mailing list
> wakaama-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or
> unsubscribe from this list, visit
> https://dev.eclipse.org/mailman/listinfo/wakaama-dev
_______________________________________________
wakaama-dev mailing list
wakaama-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/wakaama-dev
---------------------------------------------------------------------
Intel Corporation SAS (French simplified joint stock company)
Registered headquarters: "Les Montalets"- 2, rue de Paris,
92196 Meudon Cedex, France
Registration Number: 302 456 199 R.C.S. NANTERRE
Capital: 4,572,000 Euros
This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.
