how to setup network enviornment for IoT

RE: how to setup network enviornment for IoT

samchang — Sun, 15 May 2016 14:01:03 GMT

hey ! I'm also meet this issue, is control device from outside world works for you now ?
There are refrences may help for you, wiki.debian.org/BridgeNetworkConnections

RE: how to setup network enviornment for IoT

Petter Myhre — Wed, 10 Jun 2015 07:11:52 GMT

@Arnaud Nelissen. Please add a new question and link to this one if it is relevant.

RE: how to setup network enviornment for IoT

Arnaud Nelissen — Thu, 04 Jun 2015 12:47:33 GMT

I have a problem using this technique... From another computers in the network, I can successfully ping BLE devices that I am connected to (I had to add the prefixes as stated).

But when I try connecting another BLE device, all connected devices get disconnected. If I reconnect them, a new bluetooth interface is created (bt1), and it seems that the devices are then connected to this interface...

What do you think I am doing wrong ?

Thanks in advance...

RE: how to setup network enviornment for IoT

Petter Myhre — Mon, 25 May 2015 12:58:51 GMT

@Rick Chung. Please add a new question and link to this one if it is relevant.

RE: how to setup network enviornment for IoT

Rick Zhong — Mon, 25 May 2015 07:18:35 GMT

Hi All,

Because I am doing the same experiment, so I followed this thread.

I am using the nrf_udp_client project in IoT SDK as the code base for testing the udp communication.

The network topology is the same as the first user.

I followed all the upon steps to configure the radvd.conf and ipv6 prefix.

It's work, now I can ping the nrf51-DK both from PC and raspberry Pi by using the global address.

But the PC can not receive any packet from nrf51, there's no respond when I executed the "Python Server Example"

(I have update the SERVER_IPV6_ADDRESS to the global ipv6 address of the PC)

Is there any possible way to narrow down the issue : )

RE: how to setup network enviornment for IoT

Petter Myhre — Tue, 19 May 2015 11:07:28 GMT

Thank you.

RE: how to setup network enviornment for IoT

Fab1223 — Tue, 19 May 2015 11:06:53 GMT

Ok i will go with my thread itself.

RE: how to setup network enviornment for IoT

Petter Myhre — Tue, 19 May 2015 11:00:21 GMT

@Punith. This is not okey. This question is about simulating a global network, do not hijack it with your questions.

RE: how to setup network enviornment for IoT

Fab1223 — Tue, 19 May 2015 10:55:44 GMT

This we can do from tunnelling but after did 6to4 tunnelling in router my router config is as fallows.
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)

But my router is not pinging ipv6.google.com. Kindly tell me what is an issue?.

Regards Punith

RE: how to setup network enviornment for IoT

FormerMember — Tue, 19 May 2015 07:28:29 GMT

What you first can try is to make sure that you can have bi-directional communication, meaning that you can ping the router/PC/DK from some IPv6 test site.

RE: how to setup network enviornment for IoT

Fab1223 — Tue, 19 May 2015 07:13:34 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: how to setup network enviornment for IoT

chao — Wed, 28 Jan 2015 01:34:04 GMT

thanks. I can pin the DK_board ,when I add the prefixes to eth0 and bt0.

RE: how to setup network enviornment for IoT

FormerMember — Mon, 26 Jan 2015 10:36:23 GMT

The reason for this is that fe80 is the prefix for the local IPv6 address in the network nRF51 DK <-> Raspberry Pi. If you want to ping the nRF51 DK from your PC, you have to use a global IPv6 address. The only difference between a local and a global IPv6 address, is the prefix.

There are two steps for adding the prefix ( "2005" is used as example prefix):

Add bt0 and eth0 interface into the file /etc/radvd.conf:

    interface eth0

    {

        AdvSendAdvert on;
        prefix 2004:abc::/64
        { 
            AdvOnLink on;
            AdvAutonomous on;
            AdvRouterAddr on;
        };
        route ::/0
        {
        };

    };

    interface bt0
    {
        AdvSendAdvert on;
        prefix 2005::2/64
        {
            AdvOnLink off;
            AdvAutonomous on;
           AdvRouterAddr on; 
        };
    };

If you you are testing the MQTT example, the eth0 interface and with a prefix "2004:abc" is the address of the eth0 interface used by the broker. This prefix has to match the broker "address" set in the publisher/subscriber code:

static const ip6_addr_t                     m_broker_addr =
{
    .addr =
    {HTONL(0x20040abc),
    0x00000000,
    0x00000000,
    HTONL(0x00000003)} 
};

Add the prefixes to eth0 and bt0 in the terminal:

ifconfig bt0 add 2005::1/128
ifconfig bt0 add 2005::/64
ifconfig eth0 add 2004:abc::1/128
ifconfig eth0 add 2004:abc::/64
(service radvd restart)

When running the CoAP example, it's possible that the command "service radvd restart" not should be run.

After "2." you should be able to ping your BLE device with its global address (prefix 2005) both from the Raspberry Pi and from the PC: (Windows) ping 2005::028F:31FF:FE65:78FB