CC1312R: Does Wi-SUN ns_coap_node example use those certificates in wisun_certificates.h?

Hi YiKai,

They are defined in mbed_config_app.h. If you want to use a different certificates file you can change the defines in this file:

#define MBED_CONF_MBED_MESH_APP_CERTIFICATE_HEADER                            "wisun_certificates.h"
#define MBED_CONF_MBED_MESH_APP_OWN_CERTIFICATE                               WISUN_CLIENT_CERTIFICATE
#define MBED_CONF_MBED_MESH_APP_OWN_CERTIFICATE_KEY                           WISUN_CLIENT_KEY
#define MBED_CONF_MBED_MESH_APP_ROOT_CERTIFICATE                              WISUN_ROOT_CERTIFICATE

(There is some more documentation about the certificates in the User's Guide: 

https://dev.ti.com/tirex/explore/content/simplelink_cc13x2_26x2_sdk_5_20_00_52/docs/ti_wisunfan/html/wisun-stack/networklayer.html#certificates-for-certification )

Cheers,

Marie H.

I try to define those with none-existing header file but I still can build the project successfully. It is obvious that current  stack doesn't use those defines. Please provide correct way to do this.

Hi YiKai,

Did you implement the code for adding the certificates (arm_network_trusted_certificate_add etc?) You can find an example implementation in borderrouter_ws.c.

Cheers,

Marie H.

Yes. I implement the code for adding the certificates but it seems not work out for my issue which is ns_coap_node cannot join other vendor's border router. I think there is still something wrong with my setup. Need to find any clue to see how to make it work.

Hi Yikai,

That's interesting.

Can you capture a sniffer log and see if there is any hint? (This will require both devices to just run on one channel. I would also recommend to use fixed GTKs.)

https://dev.ti.com/tirex/explore/content/simplelink_cc13x2_26x2_sdk_5_20_00_52/docs/ti_wisunfan/html/wisun-guide/debugging-index.html#packet-sniffer

Cheers,

Marie H.

Sorry, I cannot set other vendor's border router to run on single channel for now. I attach console log for your reference and maybe you can have some hint about this.

01> [INFO][wsks]: KeyS get array (not alloc): 0 i: 0 free: 0 eui64: 00:12:4b:00:14:f7:d1:1a
01> [INFO][wsbs]: Active supplicant limit, active: 0 max: 1 summed averageQ: 1 adapt averageQ: 0 LLC averageQ: 1 LLC EAPOL averageQ: 0 drop: F
01> [INFO][ksep]: Initial-key init
01> [INFO][ksep]: Initial EAPOL-Key recv, eui-64: 00:12:4b:00:14:f7:d1:1a
01> [INFO][ksep]: PMK not live PTK not live GTKL 0
01> [INFO][wspa]: PAE: start EAP-TLS, eui-64: 00:12:4b:00:14:f7:d1:1a
01> [INFO][eapa]: EAP-TLS init
01> [DBG ][tlsp]: TLS: init
01> [INFO][eapa]: EAP-TLS start, eui-64: 00:12:4b:00:14:f7:d1:1a
01> [INFO][eapa]: EAP-TLS: send REQ type IDENTITY id 1 flags ff len 9, eui-64: 00:12:4b:00:14:f7:d1:1a
01>
01> [DBG ][secl]: prot timeout, state: 5
01> [INFO][ksep]: Initial-key finished, eui-64: 00:12:4b:00:14:f7:d1:1a
01> [INFO][eapa]: EAP-TLS: recv RESPONSE type IDENTITY id 1 flags 41 len 14, eui-64 00:12:4b:00:14:f7:d1:1a
01>
01> [INFO][eapa]: EAP-TLS: send REQ type TLS id 2 flags 20 len 10, eui-64: 00:12:4b:00:14:f7:d1:1a
01>
01> [INFO][eapa]: EAP-TLS: recv RESPONSE type TLS id 2 flags 0 len 86, eui-64 00:12:4b:00:14:f7:d1:1a
01> [DBG ][tlsp]: TLS: start, eui-64: 00:12:4b:00:14:f7:d1:1a
01>
01> [INFO][eapa]: EAP-TLS: send REQ type TLS id 3 flags c0 len 614, eui-64: 00:12:4b:00:14:f7:d1:1a
01>
01> [INFO][eapa]: EAP-TLS: recv RESPONSE type TLS id 3 flags 0 len 6, eui-64 00:12:4b:00:14:f7:d1:1a
01> [INFO][eapa]: EAP-TLS: send REQ type TLS id 4 flags 0 len 200, eui-64: 00:12:4b:00:14:f7:d1:1a
01>
01> [INFO][eapa]: EAP-TLS: recv RESPONSE type TLS id 4 flags 0 len 13, eui-64 00:12:4b:00:14:f7:d1:1a
01> [ERR ][tlsl]: TLS error: -30592
01> [ERR ][tlsp]: TLS: error, eui-64: 00:12:4b:00:14:f7:d1:1a
01> [DBG ][tlsp]: TLS: finish, eui-64: 00:12:4b:00:14:f7:d1:1a
01> [ERR ][eapa]: EAP-TLS: handshake failed
01> [INFO][eapa]: EAP-TLS: send FAILURE type TLS id 4 flags ff len 8, eui-64: 00:12:4b:00:14:f7:d1:1a
01> [INFO][eapa]: EAP-TLS finish, eui-64: 00:12:4b:00:14:f7:d1:1a
01>
01> [INFO][rplc]: transmit dio, rank: c4
01>
01> [DBG ][secl]: prot timeout, state: 5
01> [DBG ][tlsp]: TLS: finished, eui-64: 00:12:4b:00:14:f7:d1:1a free F
01> [DBG ][secl]: prot timeout, state: 5
01> [INFO][eapa]: EAP-TLS finished, eui-64: 00:12:4b:00:14:f7:d1:1a
01>
01> [INFO][wsbs]: Send PAN configuration

Hi Yikai,

I will pass it on to the Software developers.

What kind of BR device is this?

Cheers,

Marie H

It's Silicon Labs' Wi-SUN BR.

Marie H It seems there is something wrong with certificate exchange, which you can refer to the wireshark log with GAK: df:2b:5f:54:9b:28:7f:73:1b:bc:a9:9e:0d:e8:e6:40 .

wisun.zip

Hi Yikai,

Can you try replacing the certificates in "wisun_certificates.h" instead of adding your own file?

Please also double check the format. They need to have the PEM format (not binary format).

Cheers,

Marie H.

Yes, I had replaced the certificates in "wisun_certificates.h" and see the same issue. What do you mean I have to use PEM format? I just copy the certificates into "wisun_certificates.h". Is that correct step?

Marie H I get replied from SL:

The preamble size changes with the Operating Mode selected:

• Operating Mode 1a/1b/2a: 8 bytes
• Operating Mode 3: 12 bytes
• Operating Mode 5: 24 bytes

However, preamble is set as 4 bytes in sysconf when operation mode 1b is selected. Please check if this is bug of TI sysconf.

Hi YiKai,

Good to hear it works now!

I will correct the documentation in the next release.

And I will forward the comment on preamble bytes to the SW team.

Cheers,

Marie H.

Marie HIf you hear anything about preamble bytes from your SW team, please update here to let me know. Thanks.

Hi Yikai,

I'm sorry, the information showed in the PHY Properties section of SysConfig is not actually used. 

As you say, the preamble bytes change with the operating mode selected.

Cheers,

Marie.

Marie H Do you mean this is actually a bug in wisun stack/sysconf and we should change preamble as I mentioned before?

Hi Yikai,

It's a bug only in SysConfig. We'll remove the PHY Properies view. Please ignore this tab and don't make any changes inside.

Cheers,

Marie H.

Marie H But if I ignore PHY Properies view and don't change Preamble Count in it, I cannot join TI wisun device into SL wisun border router.

Marie H Thanks for confirming this.