Nrf51 IOT TCP Client testing

RE: Nrf51 IOT TCP Client testing

Petter Myhre — Thu, 21 May 2015 14:18:38 GMT

It could be that your router doesn't support protocol 41. Have you tried to sniff? I would try to use wireshark and sniff the et0 interface. Then you should see packets with destination address 192.88.99.1 when you ping ipv6.google.com.

RE: Nrf51 IOT TCP Client testing

Fab1223 — Wed, 20 May 2015 13:02:10 GMT

sudo tcpdump -ns 0 -i eth0 proto 41 -vv

i issued this command to check protocol 41. but only displayed on terminal is
"tcpdump: listening on eth0, link-type EN10MB (Ethernet), capture size 65535 bytes"

So i think my router does not support protocol 41. What need to do know?.

RE: Nrf51 IOT TCP Client testing

Fab1223 — Wed, 20 May 2015 12:51:54 GMT

How to check my router support protocol 41 and it is not blocked?.
I tired by removing tunnel completely also but not works. No i install complete Ubuntu 14.04 LTS version with kernel 3.17.

RE: Nrf51 IOT TCP Client testing

Petter Myhre — Wed, 20 May 2015 12:23:14 GMT

Did you try tshark? Can you check if your router supports protocol 41, and that it is not blocked? Protocol 41 is generally used for tunneling. Could it be that you are behind some NAT? If your IP is not globally unique tun6to4 may not work. You could also try to remove the tunnel completely and try again. Are you using VMWare? If you are you need to use Brdiged and not NAT under Network connection in Virutal Machine Settings.

RE: Nrf51 IOT TCP Client testing

Fab1223 — Wed, 20 May 2015 05:10:27 GMT

I am not getting any error while i run the script , it just throughs my ipv4 and ipv6 address. But still i am not able to ping ipv6.google.com. Kindly tell me how to solve this.

RE: Nrf51 IOT TCP Client testing

Petter Myhre — Tue, 19 May 2015 12:01:13 GMT

117.218.56.124 is your public IPv4 address which you get with ipv4_cur=$(dig @ns1.google.com -t txt o-o.myaddr.l.google.com +short | tr -d "\"") 192.168.1.102 is your local IPv4 address which you get from eth0 interface.

RE: Nrf51 IOT TCP Client testing

Fab1223 — Tue, 19 May 2015 11:32:49 GMT

One thing i notice is my inet addr is 117.218.56.124 even i passed 192.168.1.102 in my script. Why is it so(compared to document is SDK)?.

RE: Nrf51 IOT TCP Client testing

Fab1223 — Tue, 19 May 2015 11:30:47 GMT

Yes i did "ip link set dev tun6to4 up"

I am able to ping 192.88.99.1 but ipv6.google.com is not pinging.

Yes first i need to solve the tunnelling issue. then i will go with bt0.

RE: Nrf51 IOT TCP Client testing

Petter Myhre — Tue, 19 May 2015 11:25:54 GMT

The setup can be a bit unstable, please do "ip link set dev tun6to4 up" before you do the ipv6 ping. The prefix of the bt0 interface should be 2002:75da:387c::1/64, but I think you should focus on getting the tunnel up first. Are you able to ping 192.88.99.1? It is difficult to know what the problem is, if you haven't got any errors and have followed the setup. You could try to sniff the interface, and see what is happening. You can try tshark, you sniff an interface with "tshark -I bt0"

Edit 21.05.2015: Corrected IPv6 address/prefix of bt0 interface

RE: Nrf51 IOT TCP Client testing

Fab1223 — Tue, 19 May 2015 11:10:20 GMT

Now if in case , i am able to ping ipv6.google.com from router then i can ping my router and DK from internet right?.

Regards Punith

RE: Nrf51 IOT TCP Client testing

Fab1223 — Tue, 19 May 2015 10:27:24 GMT

Yes with teredo , it gives unicast ipv6 address so it is pinging ipv6.google.com.

Now i remover teredo , added tun6to4 by modifying the script which is now giving the prefix. Here it is tun6to4

tun6to4
Link encap:IPv6-in-IPv4
inet addr:117.218.56.124 Mask:255.255.255.255
inet6 addr: ::192.168.1.102/96 Scope:Compat
inet6 addr: 2002:75da:387c::1/48 Scope:Global
UP RUNNING NOARP MTU:1480 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:904 errors:3 dropped:0 overruns:0 carrier:3
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:83519 (83.5 KB)

Now i changed same prefix in /etc/radvd.conf

interface bt0
{
AdvSendAdvert on;
prefix 2002:75da:387c::1/48
{
AdvOnLink off;
AdvAutonomous on;
AdvRouterAddr on;
};
};

But i am not able to ping ipv6.google.com from by router. Kindly tell me what is problem?

RE: Nrf51 IOT TCP Client testing

Petter Myhre — Tue, 19 May 2015 10:18:12 GMT

In the link you are just simulating a global network. This can't be used on the Internet. Are you sure you need a tunnel? You said you were able to ping ipv6.google.com, which requires IPv6 connectivity. Anyways, Teredo gives your router an IPv6 address that doesn't have a prefix, it is a unicast address. Please see this for more information.

RE: Nrf51 IOT TCP Client testing

Fab1223 — Tue, 19 May 2015 09:58:13 GMT

i installed the package

sudo apt-get install miredo

for tunnelling and not fallowed the script.

Now teredo ipv6 address (which is of router) is pinging from internet . but DK is not pinging.

Regards Punith

RE: Nrf51 IOT TCP Client testing

Fab1223 — Tue, 19 May 2015 09:47:03 GMT

i fallow this link

devzone.nordicsemi.com/.../

my router is also not pinging from internet.

Which ipv6 address i need to ping whether bt0 or eth0?.

Regards Punith

RE: Nrf51 IOT TCP Client testing

Petter Myhre — Tue, 19 May 2015 09:37:54 GMT

You shouldn't send router advertisments on the eth0 interface. You should get router advertisments from the network on the eth0 interface. The router advertisments are used to assign a IPv6 address and prefix to the eth0 interface. Check what they are by in ifconfig. Before you try to ping the nRF51 DK you need to be able to ping the router from the internet.

RE: Nrf51 IOT TCP Client testing

Fab1223 — Tue, 19 May 2015 09:29:13 GMT

yes i added prefix and started radvd service also but device is not pinging from internet.

Here is my configuration

interface eth0
{
AdvSendAdvert on;
prefix 2005:abc::/64 {
AdvOnLink on;
AdvAutonomous on; AdvRouterAddr on;
};
route ::/0
{
};
};

interface bt0
{
AdvSendAdvert on;
prefix 2001:db8::/64
{
AdvOnLink off;
AdvAutonomous on;
AdvRouterAddr on;
};
};

And also i added these from command line

ifconfig bt0 add 2001:db8
ifconfig eth0 add 2004:abc::1/64::1/64
service radvd restart

Now able to ping device from my pc and by router but not by internet.

Kindly suggest me , where i am missing.

Regards Punith

RE: Nrf51 IOT TCP Client testing

Petter Myhre — Tue, 19 May 2015 07:26:52 GMT

Hi,

It seems you have native IPv6 connectivity. What ipv6 address and prefix is your router getting?

Have you set up RADVD so that the nRF51 DK gets the correct prefix? It should be something like:

interface bt0
{
	AdvSendAdvert on;
	prefix 2002:c213:5692::1/64
    {
	    AdvOnLink off;
    };
};

(This is from my 6to4 tunneling setup)

You also need to add the prefix to the bt0 interface and restart radvd:

ifconfig bt0 add 2002:c213:5692::1/64
service radvd restart

You can try to ping the nRF51 DK from the internet here.

Edit 21.05.2015: Corrected IPv6 address/prefix of bt0 interface

RE: Nrf51 IOT TCP Client testing

Fab1223 — Tue, 19 May 2015 07:12:18 GMT

Hi All,

I able to control device (DK) from my router and my PC (both are connected to LAN). Now i want to control device from outside world ?. How to do it?.

My router is pinging both google.com and ipv6.google.com. And also both device and router has global ipv6 address.

Kindly suggest me.

Regards Punith

RE: Nrf51 IOT TCP Client testing

Fab1223 — Mon, 18 May 2015 10:00:40 GMT

Hi Petter,

I am doing in My ubuntu PC 14.04 linux 3.17. Now tcp client is working fine with my PC and problem is , i did not change the client code with proper server ip.Once i change it works fine.

Right now my server code is running on router itself , so i can control device. But if i want to control the device from outside world , how to do it. Give any example code for that , i am good at linux also , kindly suggest any solution. I assigned global ip for both device and router.

Regards Punith

RE: Nrf51 IOT TCP Client testing

Petter Myhre — Wed, 13 May 2015 11:15:15 GMT

Could you please explain a bit more about your setup? How are you routing this? Are you using a RPi? Have you performed any other ping tests than PC to nRF51 DK?