Internet of Things – are you ready for IPv6?


Say Internet of Things and understanding is split into: “my refrigerator will order milk over the internet” or “hackers can take control of my car”, but mostly “yeah – already got that to control my central heating”. Techies (like me) just go misty-eyed over all of these new gadgets.

IoT is much bigger than all of this. Over the past three years, enterprises have had to learn how to manage employees own devices connecting to corporate WiFi. This has required a huge uplift in WiFi bandwidth requirements and the ability to recognise and control access for many more devices as employees look for corporate data (email, CRM, price lists, etc.) on their smartphones and tablets.

Now imagine the mulitple of devices if every room, corridor and stairway has lighting, heating, aircon, occupancy and door locks advise and control through IoT devices. Then consider IoT signalling maintenance requirements of drinks and snacks machines. Car parks using IoT to show empty spaces. The list goes on; how will enterprise IT admin connect these devices through corporate WiFi?

The data rate will be small (and hopefully each device will talk to an internal gateway server, not over the internet) but each device will have a unique physical address and a requirement for an IP address – there will be a need to consider IPv6. Is your enterprise network IPv6 capable? Does your DNS allow IPv6 mapping?

IPv6 was first described in 1998 (Internet Protocol, Version 6 (IPv6) Specification,S. Deering, R. Hinden (December 1998)) – but how many enterprise networks are capable of supporting this extended IP addressing scheme?

I access the internet via BT Business Broadband; testing my browser capability using shows that BT DNS supports only IPv4 name resolution. So I just have to wait for BT to enable IPv6 addressing – or should I consider DNS that is already IPv6 capable? As an enterprise, you have to do this now!

For a way forward with IPv6, take a look at:


Serious cloud presence for €2.99 /month


I am a bit of a geek and consequently end up trying new hardware, apps and frameworks all the time. One issue with this is maintaining a reliable OS image. I am currently fiddling about with IoT hardware that runs a trusted connection to a web server to avoid broad internet access. Evaluating each new framework inevitably results in library inconsistencies and unstable platforms with unexpected errors. One way forward is to run in containers and consensus is that Docker ( is the leading solution.

Recently, I was looking to run Docker on ARM platforms. Why ARM? – great return out of extremely lightweight, low-cost computing platforms. Earlier this year, hypriot ( showed more than 2,000 docker containers running static web servers on a single Raspberry Pi2. OK – an interesting exercise.

For a cloud server with dedicated hardware, take a look at Scaleway ( – they build their own hardware and each user gets their own 4 ARM cores, 2GB memory, 50GB SSD disk, 1 reserved public IPv4 and 200Mbit/s un-metered bandwidth ( for €2.99 /month – this is  good stuff!