IoT UDP client can not communicate with server by using global IPv6

RE: IoT UDP client can not communicate with server by using global IPv6

Petter Myhre — Tue, 26 May 2015 15:47:35 GMT

You can also try to install Wireshark on the PC and sniff your Local Area Connection. To see if the IPv6 packets are getting there.

RE: IoT UDP client can not communicate with server by using global IPv6

Rick Zhong — Tue, 26 May 2015 15:38:45 GMT

Hi Petter,

Thanks for your reply,

By using the tshark to trace the packets flow, seems nrf51-DK trying to send the packet to the correct globla address of the PC eth0, but it does not receive any response. I will continue examine every step I made and keep updating : )

RE: IoT UDP client can not communicate with server by using global IPv6

Rick Zhong — Tue, 26 May 2015 15:35:25 GMT

Hi Jun Qing,

Thanks for your kindly reply,

I also found that whether add icmp6_rs_send() or not,

PC can ping the nrf51-DK using global ipv6(2005:XX...)after the add the ipv6 prefix through ifconfig.

When setting the nrf51-DK UDP server ip address to Pi, the netcat can show the correct UDP message.

But when I setting the server ip address to the PC with global ipv6 address, the netcat doesn't show up anything.

The UDP socket communication between the Pi and PC seems correct, the firewall setting shutdown for the testing.

I will keep update the debug processing.

Really appreciate for your kindly advice : )

RE: IoT UDP client can not communicate with server by using global IPv6

Petter Myhre — Tue, 26 May 2015 09:18:09 GMT

Are you able to ping the IPv6 address of the PC? Have you tried to sniff the different interfaces on the RPi? I'm using tshark. Try doing a "tshark -I bt0" and see if the IPv6 packet is sent with the correct addresses.

RE: IoT UDP client can not communicate with server by using global IPv6

Jun Qing ZOU — Tue, 26 May 2015 01:22:08 GMT

Hi Rick!

This example is designed to use link-local addresses only so there is no call of icmp6_rs_send() in the code. If you have updated the code to send Router Solicition and thus get global address allocated (it seems so as your ping OK), you may try the "netcat" command on Raspberry Pi first. Example of usage,

nc -6 -l 5911 -u -v

You might need to update the code to tell the client what's your R.Pi's global address.

For PC, you'll have to make Windows to allow the incoming UDP connection in firewall setting (inbound rules).