Important changes to forums and questions
All forums and questions are now archived. To start a new conversation or read the latest updates go to forums.mbed.com.
5 years, 1 month ago.
Connected. IP of "mbed-os-example-mesh-minimal" WiSUN application
Hi ,
My mbed-os-example-mesh-minimal Wi-SUN application shows IP as:
Connected. IP = fd00:6172:6d00:0:68d7:4b42:e761:cdac
When I ping the IP, I cannot receive any response:
Pinging fd00:6172:6d00:0:68d7:4b42:e761:cdac with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out.
Ping statistics for fd00:6172:6d00:0:68d7:4b42:e761:cdac: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
Sincerely,
Mehdi
1 Answer
5 years, 1 month ago.
Hi Mehdi,
I recommended to test ping to WiSUN gateway first. When you start the gateway it should show it's own IP address. If it does not work then it is routing question. It depend from where you ping and what network the gateway and ping source are connected. When you get ping working to the gateway it should work to the connected WiSUN device.
Regards, Pekka
Hi
I can ping to my "border router" IP and get the response from it.
I can see my "router" added to "border router" neighbor table.
On "router" :
<ESC>[2K<ESC>[39m[INFO][WSND]: Wi-SUN bootstrap ready<ESC>[0m<CR><LF> Connected. IP = fd00:6172:6d00:0:1c50:1018:7618:12fb
On "border router":
IP Addr: fd00:6172:6d00:0:1c50:1018:7618:12fb<CR><LF> LL Addr: (STALE 0) 49:83:1e:50:10:18:76:18:12:fb<CR><LF> EUI-64: (REGISTERED 7047) 1e:50:10:18:76:18:12:fb<CR><LF> IP Addr: fe80::1c50:1018:7618:12fb<CR><LF> LL Addr: (STALE 0) 49:83:1e:50:10:18:76:18:12:fb<CR><LF> IP Addr: fe80::dc1f:8da3:c996:da48<CR><LF> LL Addr: (NEW 0) <CR><LF> IP Addr: fd00:6172:6d00:0:5c96:1eb9:d828:188e<CR><LF> LL Addr: (STALE 0) 49:83:5e:96:1e:b9:d8:28:18:8e<CR><LF> EUI-64: (REGISTERED 6108) 5e:96:1e:b9:d8:28:18:8e<CR><LF> IP Addr: fe80::5c96:1eb9:d828:188e<CR><LF> LL Addr: (STALE 0) 49:83:5e:96:1e:b9:d8:28:18:8e<CR><LF>
But still the router cannot response to ping from my computer.
On my router before joining I can see a prompt shows "invalid cert"
... <ESC>[2K<ESC>[31m[ERR ][tlsl]: invalid cert<ESC>[0m<CR><LF> <CR> <ESC>[2K<ESC>[39m[INFO][eaps]: EAP-TLS: send RESPONSE type TLS id 3 flags 0 len 599<ESC>[0m<CR><LF> <CR> <ESC>[2K<ESC>[39m[INFO][eaps]: EAP-TLS recv REQ type TLS id 4 flags 0 len 49<ESC>[0m<CR><LF> <CR> <ESC>[2K<ESC>[90m[DBG ][tlsp]: TLS: finish<ESC>[0m<CR><LF> <CR> <ESC>[2K<ESC>[39m[INFO][eaps]: EAP-TLS: handshake success<ESC>[0m<CR><LF> <CR> <ESC>[2K<ESC>[39m[INFO][eaps]: EAP-TLS: send RESPONSE type TLS id 4 flags 0 len 10<ESC>[0m<CR><LF> <CR> <ESC>[2K<ESC>[39m[INFO][eaps]: EAP-TLS finish<ESC>[0m<CR><LF> <CR> <ESC>[2K<ESC>[39m[INFO][sfwh]: 4WH: init<ESC>[0m<CR><LF> <CR> <ESC>[2K<ESC>[39m[INFO][sfwh]: 4WH: recv Message 1<ESC>[0m<CR><LF> <CR> <ESC>[2K<ESC>[39m[INFO][secl]: PMKID 51:84:8c:16:5a:57:96:66:0b:cc:cb:db:b1:b5:41:98 EUI-64 de:1f:8d:a3:c9:96:da:48 1e:50:10:18:76:18:12:fb<ESC>[0m<CR><LF> <CR> <ESC>[2K<ESC>[39m[INFO][sfwh]: 4WH: start<ESC>[0m<CR><LF> <CR> <ESC>[2K<ESC>[39m[INFO][sfwh]: 4WH: send Message 2<ESC>[0m<CR><LF> <CR> <ESC>[2K<ESC>[39m[INFO][sfwh]: 4WH: recv Message 3<ESC>[0m<CR><LF> <CR> <ESC>[2K<ESC>[39m[INFO][secl]: GTK recv index 0 lifetime 2590833<ESC>[0m<CR><LF> <CR> <ESC>[2K<ESC>[39m[INFO][sfwh]: 4WH: send Message 4<ESC>[0m<CR><LF> <CR> <ESC>[2K<ESC>[39m[INFO][sfwh]: 4WH: finish, wait Message 3 retry<ESC>[0m<CR><LF> <CR> <ESC>[2K<ESC>[39m[INFO][wspc]: NW key set: 0, hash: 00:c8:08:88:84:04:30:1a<ESC>[0m<CR><LF> <CR> <ESC>[2K<ESC>[90m[DBG ][mMIB]: Set key 0<ESC>[0m<CR><LF> <CR> <ESC>[2K<ESC>[90m[DBG ][wsbs]: authentication success<ESC>[0m<CR><LF> ...
Can it be the main issue?
Sincerely,
Mehdi
posted by 31 Oct 2019Assigned to 5 years, 1 month ago.
This means that the question has been accepted and is being worked on.