mbed client on ethernet with LWIP

Dependencies:   mbed Socket lwip-eth lwip-sys lwip

Fork of mbed-client-classic-example-lwip by sandbox

Committer:
mbedAustin
Date:
Thu Jun 09 17:08:36 2016 +0000
Revision:
11:cada08fc8a70
Commit for public Consumption

Who changed what in which revision?

UserRevisionLine numberNew contents of line
mbedAustin 11:cada08fc8a70 1 # Known Issues
mbedAustin 11:cada08fc8a70 2
mbedAustin 11:cada08fc8a70 3 ## About this document
mbedAustin 11:cada08fc8a70 4
mbedAustin 11:cada08fc8a70 5 This is the list of known issues for the 15.11 release of [mbed Client](https://github.com/ARMmbed/mbed-client). We publish mbed-client as module in GitHub, and track open issues as tickets in the repository. That makes for an easy development flow, but doesn’t make it very easy for you to get a single view of all the issues that affect the whole release.
mbedAustin 11:cada08fc8a70 6
mbedAustin 11:cada08fc8a70 7 The purpose of this document is to provide that single view of all the key issues we are aware of. It isn’t a complete list; it’s a filtered and reviewed list, focusing on the issues we thought you’d want to be aware of. Each item explains the problem, as well as workarounds if those are possible. For items filed through GitHub, we’ve included a link to the issue so that you can follow the discussion and code - or even suggest a solution.
mbedAustin 11:cada08fc8a70 8
mbedAustin 11:cada08fc8a70 9 For more information about an issue, contact us on the [mbed forums](http://forums.mbed.com).
mbedAustin 11:cada08fc8a70 10
mbedAustin 11:cada08fc8a70 11 ### Other information not in this document
mbedAustin 11:cada08fc8a70 12
mbedAustin 11:cada08fc8a70 13 We’re still very actively building mbed Client and the 15.11 release is a technology preview. As such there are some other limitations of the release that you can find described in the [release note](https://www.mbed.com/en/development/software/mbed-client/releases/mbed-client1511).
mbedAustin 11:cada08fc8a70 14
mbedAustin 11:cada08fc8a70 15 #### Important Note for Windows Users
mbedAustin 11:cada08fc8a70 16
mbedAustin 11:cada08fc8a70 17 If you are using this release on Microsoft Windows, please be advised that
mbedAustin 11:cada08fc8a70 18 because of the way Windows handles filename and paths, you may have problems
mbedAustin 11:cada08fc8a70 19 if you attempt to use this in a deep directory hierarchy with a long
mbedAustin 11:cada08fc8a70 20 path name (e.g. `c:\some\very\long\path`). If you experience problems
mbedAustin 11:cada08fc8a70 21 unpacking or building this release, please try it in a location with a
mbedAustin 11:cada08fc8a70 22 shorter path before filing a bug. Thanks.
mbedAustin 11:cada08fc8a70 23
mbedAustin 11:cada08fc8a70 24 ***
mbedAustin 11:cada08fc8a70 25 ### mbed Client API may not be fully interoperable with other LWM2M servers.
mbedAustin 11:cada08fc8a70 26
mbedAustin 11:cada08fc8a70 27 *Description*: mbed Client API is OMA LWM2M compatible. However, some features may not be fully interoperable against other open source LWM2M servers. This is the first release version and more features will be made interoperable over coming releases.
mbedAustin 11:cada08fc8a70 28
mbedAustin 11:cada08fc8a70 29 *Workaround*: mbed Client is compatible with mbed Device Connector Service, which can be tested at [https://connector.mbed.com](https://connector.mbed.com).
mbedAustin 11:cada08fc8a70 30
mbedAustin 11:cada08fc8a70 31 *Reported Issue*: ARM internal reference IOTCLT-366
mbedAustin 11:cada08fc8a70 32
mbedAustin 11:cada08fc8a70 33 *Priority*: Major
mbedAustin 11:cada08fc8a70 34
mbedAustin 11:cada08fc8a70 35 ### mbed Client for Linux doesn't support IPv6 connectivity
mbedAustin 11:cada08fc8a70 36
mbedAustin 11:cada08fc8a70 37 *Description*: mbed Client for Linux platform currently works only for IPv4-enabled LWM2M server addresses. IPv6 address support is currently broken.
mbedAustin 11:cada08fc8a70 38
mbedAustin 11:cada08fc8a70 39 *Workaround*: mbed Client is compatible with mbed Device Connector Service which can be tested from [https://connector.mbed.com](https://connector.mbed.com) over IPv4 Address.
mbedAustin 11:cada08fc8a70 40
mbedAustin 11:cada08fc8a70 41 *Reported Issue*: https://github.com/ARMmbed/mbed-client-linux/issues/19
mbedAustin 11:cada08fc8a70 42
mbedAustin 11:cada08fc8a70 43 *Priority*: Major
mbedAustin 11:cada08fc8a70 44
mbedAustin 11:cada08fc8a70 45 ### mbed Client will occasionally disconnect from LWM2M Server because of network errors
mbedAustin 11:cada08fc8a70 46
mbedAustin 11:cada08fc8a70 47 *Description*: If mbed Client is kept running for long durations (over 24 hours) with long lifetime values, it occasionally goes offline due to unstable network conditions - and doesn't send periodic updates to LWM2M server.
mbedAustin 11:cada08fc8a70 48
mbedAustin 11:cada08fc8a70 49 *Workaround*: Set the periodic lifetime value to less than 15 minutes if you want to run stability tests. Also, implement a network error handling mechanism on the application side, to handle `error()` callbacks received from the mbed-client library.
mbedAustin 11:cada08fc8a70 50
mbedAustin 11:cada08fc8a70 51 *Reported Issue*: ARM internal reference IOTCLT-206
mbedAustin 11:cada08fc8a70 52
mbedAustin 11:cada08fc8a70 53 *Priority*: Major
mbedAustin 11:cada08fc8a70 54
mbedAustin 11:cada08fc8a70 55 ### mbed Client might experience a memory leak when running for long durations
mbedAustin 11:cada08fc8a70 56
mbedAustin 11:cada08fc8a70 57 *Description*: mbed Client might have memory leak issues when left running for longer than 12 hours.
mbedAustin 11:cada08fc8a70 58
mbedAustin 11:cada08fc8a70 59 *Workaround*: None
mbedAustin 11:cada08fc8a70 60
mbedAustin 11:cada08fc8a70 61 *Reported Issue*: ARM internal reference IOTCLT-290
mbedAustin 11:cada08fc8a70 62
mbedAustin 11:cada08fc8a70 63 *Priority*: Major
mbedAustin 11:cada08fc8a70 64