![](/media/cache/profiles/aa7fd480bd75d86948e7f7aac11d2704.jpg.50x50_q85.jpg)
Not working
Fork of U_Blox_DeviceConnector by
Diff: README.md
- Revision:
- 6:8fff223f3f84
- Parent:
- 5:b7d7ca715fdb
- Child:
- 7:9a1ee269650b
--- a/README.md Mon Aug 01 18:15:14 2016 +0100 +++ b/README.md Tue Aug 02 10:00:21 2016 +0100 @@ -71,6 +71,22 @@ 6LoWPAN ND and Thread use IPv6 for connectivity. Therefore, you need to verify first that you have a working IPv6 connection. To do that, ping the Connector IPv6 address `2607:f0d0:2601:52::20` from your network. +**NOTE:** If you are using [k64f-border-router](https://github.com/ARMmbed/k64f-border-router) (which can be used only as a 6LoWPAN BR and only with FRDM-K64F), you need to enable another security feature. By default, k64f-border-router uses `PSK` as security. You can either enable security here on your mbed-os-example-client application, e.g., + +```json + "target_overrides": { + "*": { + "mbed-mesh-api.6lowpan-nd-security-mode": "PSK", + } + } +``` +or you can remove link layer security from k64f-border-router. For doing that, change the [mbed_app.json](https://github.com/ARMmbed/k64f-border-router/blob/master/mbed_app.json) fetched from k64f-border-router repository, e.g., + +```json + "config": { + "security-mode": "NONE", + } +``` #### mbed gateway To connect the example application in 6LoWPAN ND or Thread mode to Connector, you need to set up an mbed 6LoWPAN gateway router as follows: