Public IPv6 addresses on nodes with servers on an IPv4 connected private network.
|Number of nodes involved||Around 10|
|Time of platforms usage||Hours|
|External documentation||In the git repository in ‘user_contributions’ folder|
I gave an IPv6 access from the internet to a sensor network. Where the virtual machine, acting as router between internet and the sensor network has only an IPv4 connectivity.
On the senslab platform, a network was built with RPL routing and a border router making the link between the wireless network and the virtual machine using SLIP.
To get public IPv6 addresses, I used a IPv6 over IPv4 tunnel offered by http://www.gogo6.com/freenet6/tunnelbroker.
I got a /56 tunnel, that allowed me to give a /64 prefix for the sensor network and use another /64 prefix for the configuration.
So each node on the network was accessible from the outside with public IPv6 addresses.
I could ping all the nodes on the platform from the internet using their IPv6 addresses, and I could access the webserver that was running on the border router node.
It also work when setting up one virtual machine from another senslab site as an IPv6 router, and route the packets for the sensor network to the VM where the experiment is running.
It is a scenario that may be what the IPv6 deployment on senslab will be: One IPv6 router that gives prefixes to running experiments and routes the packets.