From what I understand the border router implementation in the RIOT tree is in need of some work. That got me wondering. What border router implementation is everyone using and on what hardware?
I'm working with Bluetooth and HC-05 modules and hoping to get a RIOT interface for those someday- because they are readily available and inexpensive.
A while back I stumbled upon some Python source code that did MQTT <-> Serial-translation and I've been working to integrate that into my project.
Here was the code : https://github.com/clixx-io/clixx.io/blob/master/tools/serial_router.py
I'm just testing and refining it. It does seem to work but I need to add a few things like reconnecting to the MQTT server if the connection drops. But if anybody wanted to pull it into RIOT as something to get started with MQTT I wouldn't object at all.
Regards
David
Hi Adam!
From what I understand the border router implementation in the RIOT tree is in need of some work. That got me wondering. What border router implementation is everyone using and on what hardware?
Sorry, I missed that one. You're right, border router implementation in RIOT is rather hard coded to use the serial port as a backbone interface, what's definitely a bad idea. (But it was the only option we had these days, when it's got originally implemented due to a lack of other hardware.)
Now, we're working on a more generic solution with real support of multiple interfaces of various types.
So far, for demos and stuff like this, we were using some kind of a scripted Linux based border router.
Cheers, Oleg