Using nginx ingress with istio service mesh So you started using Kubernetes (which is great). To get traffic into your cluster you need to choose an ingress implementation. Luckily several are available and there are a lot of good reasons to choose nginx as your ingress. After all nginx is a great web server and makes a great ingress for your kubernetes installation. But now you read about service meshes and want to have a service mesh.
If you want to use radius sooner or later you will probably discover freeradius. It is a handy little radius AAA (authentication, authorization, accounting) server with a lot flexibility and a small enough footprint most embedded devices (router etc.) probably are able to run it. freeradius also provides a lot of flexibility how to authorize your users provided by several modules. Currently you have three choices to create modules in freeradius, you can use rlm_python and use python or rlm_perl and use perl or write a new module from scratch in C.
Das WLAN ist frei… oder auch nicht Freies WLAN ist in. In vielen Branchen gehört das Anbieten von Gäste-WLANs auf möglichst einfache Weise mittlerweile zum guten Ton. Und auch viele Kommunen haben verstanden, dass freies WLAN in den Städten gut für den Tourismus und das Image der Stadt ist. Manchmal wird das freie WLAN-Projekt in einer Kommune aber auch komplett ad absurdum geführt. So z.B. in der Stadt Dortmund, wo die Stadttochter DOKOM21 ein angeblich freies WLAN aufbaut.
Go is currently all the hype. Unfortunately dependency management in Go is basicaly non existant. The most common pattern for managing dependencies is vendoring. There are several different approaches to vendoring, but some require you to rewrite your imports. While I think this is bad, other people seem to agree and there exists at least one build tool for Go which supports vendoring without import rewrites. Welcome to gb. Unfortunately gb doesn’t let you use your default commands any more.
The Container no one could find Docker is the new cool kid on the block when it comes to deploying applications. But as with every iteration in the IT this new kid does not only solves problems, it creates some new challenges. One these challenges is if you start moving to a docker based workflow for your services but have only very few containers (probably only one publicly available) to begin with.
Nowadays the Internet of Things is all the rage. Connected devices are popping up everywhere and tech people are feeling that something big is coming. Something as big as the internet itself. But is it really? The term “Internet of Things” implies that we have something very similar to the internet we know, but with devices talking to each other and sometimes to us. But what is currently created is far away from being just like “our” internet.
What is Contiki OS and why would you probably care? First Steps with Contiki OS: Why Contiki OS? Sometime ago I build an actor to replace my dumb Junkers room thermostat with something even dumber, but controllable so my smart home system can device how much should be generated. Long story, I created a prototype based on an Arduino and the prototyping shield and hooked it up via USB and it worked fine.