ciarmcom
commented
7 years ago ARM Internal Ref: IOTCLT-1275
Closed rdoume closed 7 years ago
ciarmcom
commented
7 years ago ARM Internal Ref: IOTCLT-1275
JanneKiiskila
commented
7 years ago Hei,
It's using UDP mode - which network interface are you using? There are many firewalls that have issues with UDP and they close the UDP "hole" after certain time. It is possible you're hitting this issue. If you can, could you try with TCP? Please see section "Changing socket type" in the README.md.
rdoume
commented
7 years ago The interface would be an eth interface between my 6lowpan border router (https://github.com/ARMmbed/k64f-border-router) and my computer. My client is a node in the 6lowpan network, and therefore uses the AT86RF233, and is connected to the border router and the backhaul.
The TCP mode does not change a thing. I do not think it's due to my firewall, as, like I said, I can send regular UDP packet that I create using the UDPsockets and its fonction sendto(); I am able to see in Wireshark those packets going in my interface and use them. However, while using this example, I cannot even see the packets going through the interface on wireshark. And this is probably caused by the socket error that you can see in the trace. But I can't explain why this error is happening.
teetak01
commented
7 years ago @rdoume which version of mbed-client.lib and mbed-os.lib are you using? We recently fixed one issue in client related to WIFI + mbed-os also had some regression with mesh which has been fixed already.
rdoume
commented
7 years ago My mbed-os.lib is https://github.com/ARMmbed/mbed-os/#d5de476f74dd4de27012eb74ede078f6330dfc3f and my mbed-client.lib is : https://github.com/ARMmbed/mbed-client/#1c03b36ac944532688a39d9a6bd7f8a42aecf8f3
teetak01
commented
7 years ago @SeppoTakalo can you check this? It would seem to failing in DNS-handler.
SeppoTakalo
commented
7 years ago I tested client on top of LwIP using IPv6 and results are the same:
DBG ][mClt]: resolve_server_address()
[DBG ][mClt]: M2MInterfaceImpl::register_object - OUT
[DBG ][mClt]: M2MInterfaceImpl::socket_error: (4), retry (1), reconnecting (0)
[DBG ][mClt]: M2MInterfaceImpl::internal_event : new state 0
[DBG ][mClt]: M2MInterfaceImpl::state_engine
[DBG ][mClt]: M2MInterfaceImpl::state_idle
[DBG ][mClt]: M2MNsdlInterface::stop_timers()
[DBG ][mClt]: stop_listening()
[DBG ][mClt]: M2MInterfaceImpl::socket_error - reconnecting in 15(s), count 1/3
[DBG ][mClt]: M2MInterfaceImpl::timer_expired()
[DBG ][mClt]: M2MInterfaceImpl::internal_event : new state 5
[DBG ][mClt]: M2MInterfaceImpl::state_engine
[DBG ][mClt]: M2MInterfaceImpl::state_register
[DBG ][mClt]: stop_listening()
[DBG ][mClt]: M2MInterfaceImpl::state_register() - new port: 64339
[DBG ][mClt]: resolve_server_address()Using mbed-OS-5.3-RC1.
So this on not 6LoWPAN related.
JanneKiiskila
commented
7 years ago Hi, would be interesting to get the same results from mbed-OS 5.2.0 (#e435a07d9252f133ea3d9f6c95dfb176f32ab9b6).
JanneKiiskila
commented
7 years ago Hi,
we have been struggling witha bit of a similar case here. The image you compiled for the client (not the border router), what is the mbed_app.json for it like? Seems having too many features turned on there can yield issues like this.
JanneKiiskila
commented
7 years ago Hi @rdoume,
with ethernet on IPv6 I was able to easily create a similar situation, though I'm not 100% sure if this will apply to you. Please check the mbed_app.json you used for creating the client (not the border router), does it include both "LWIP" and "NANOSTACK"? If it does, please remove the "LWIP".
JanneKiiskila
commented
7 years ago Hi, @rdoume - any updates on this case?
rdoume
commented
7 years ago Hi, I'm on leave until beginning January and cannot answer your questions. However I managed to make it work somehow, without knowing how. But what you posted about too many features in the mbed_app.json might be it. I'll test is first week of January
JanneKiiskila
commented
7 years ago Thank you @rdoume, excellent to hear you got it working, with your permission I'd like to close this ticket.
JanneKiiskila
commented
7 years ago Closing this out.
Hey there, I currently have an issue with the example client, and after trying all i could think, i thought you might have an idea. My client is one board K64f with the firefly shield in 6lowpan_nd mode, one other K64f in border router mode connected to my pc by ETH, and my LWM2M server being a local leshan server. I am able to send regular UDP packet from my client board to my computer, and i'm able to see them through Wireshark, so I know the routing process is correct. I'm able to connect to the leshan server through the OMA-LWM2M addon for firefox, to see the server. Here is the trace of my client:
I can see that there is a socket error, number 4, although could not find properly what it means. However, I don't get why there is this error. Maybe you understand? Sincerely,