Node is not entering in stage 5

[nikunjp26]

Dear Team,

We have ported the wsbrd demon sdk v1.8 on android platform of Allwinner h616 processor using the ndk-18 (API level 28). attached the patch in which we have done the minor changes as per the api difference. (FYI:we used the libnl library version 3.4.0.)

After compilation we are able to generate the wsbrd binary and able to run on our android device. We did the proper configuration as per attachment and trying to join the node but node is passing the stage 4 only and not entering into stage 5. here i attached the logs of both wsbrd process.

FYI: We are using can1.0 mode.

FYI : we are running the coap server example in node.

We are running the below steps in android device as run the demon process.

• mount -o rw,remount /

mkdir /dev/net
ln -s /dev/tun /dev/net/tun

ip rule add from all lookup main pref 1

./init-container.sh local

Attached files :
0001-Modify-as-per-android-board.patch

log-wsbrd-android-board.log

init-container.txt
wsbrd-conf.txt

Please hep us to solve this issue as soo as possible

[MathisMARION]

Hello and thank you for your report.

We will need more details to investigate the issue, the logs provided only contain the first second after boot. I suggest enabling traces icmp,rpl,dhcp,drop on wsbrd. Additional info about the other Wi-SUN node would be appreciated if possible. If you are using a Silicon Labs device, you can use J-Link RTT to get logs and Silicon Labs PTI to get packet captures.

[nikunjp26]

Dear Mathis Marion,

We are stuck in another points so will send you the logs soon.

best regards,
Nikunj Patel

[nikunjp26]

Dear Mathis Marion,

Please find the below RTT Log traces and wsbrd logs.

RTT_Logs 2.txt

wsbrd-log.txt

let us know if need more details.

best regards,
Nikunj Patel

[MathisMARION]

Hello,

The RTT traces for the node reveal that it fails in join state 4, when trying to retrieve an IPv6 address through DHCPv6.
I am noticing that an external DHCPv6 server is in use based on your wsbrd config file. Is the DHCPv6 server running on the same machine as wsbrd? If not, is a DHCPv6 relay program running on the Linux host?

[nikunjp26]

Dear Mathis Marion,

Please find the below RTT Log traces, wsbrd logs and wsbrd.conf file.

We changed the Internal_dhcp option to true in wsbrd.conf. we used the ethernet for internet and we are using the external radius server.neighbour_proxy is commented.

and we run service using below command
./init-container.sh local

206E_16_04_24_rtt.log
wsbrd_internal_dhcp_true_16042024.txt
wsbrd.conf.txt

Thanks & Best Regards,
Nikunj Patel

[nikunjp26]

Dear Mathis Marion,

Can you please guide us what may be the issue and what we can do the next items to overcome this issue? as we are stuck at this point to deploy this feature in product

best regards,
Nikunj Patel

[MathisMARION]

The wsbrd logs show that the DHCPv6 server fails to send its reply:

1713260841.741440: rx-dhcp sol       src:fe80::1a7a:3eff:fe1d:206e
1713260841.741749: tx-dhcp rply      dst:fe80::1a7a:3eff:fe1d:206e
warning: dhcp_send_reply: sendmsg: Network is unreachable

We are not sure what the reason is for this error is, but I am suspecting to some sort of kernel network configuration issue, maybe a missing route, or a parameter disabled. We will get back to you when we have something more specific.

[nikunjp26]

Dear Team,

you can guide us to check in details some of parameters of library or any configuration where you have any doubts which we can try from our side and update you.

best regards,

[silabs-AyoubA]

Hi Nikunj,

Can you please explain why you added this rule ip rule add from all lookup main pref 1?
What is the behavior if you remove this rule?

Best Regards,
Ayoub

[nikunjp26]

Dear Ayoub,

We checked without this rules but still the same issue we are facing.

best regards,
nikunj patel