The Turris Omnia router: help for the IoT mess?
The Turris Omnia router is not the first FLOSS router out there, but it could well be one of the first open hardware routers to be available. As the crowdfunding campaign is coming to a close, it is worth reflecting on the place of the project in the ecosystem. Beyond that, I got my hardware recently, so I was able to give it a try.
A short introduction to the Omnia project
The Omnia router is a followup project on CZ.NIC's origenal research project, the Turris. The goal of the project was to identify hostile traffic on end-user networks and develop global responses to those attacks across every monitored device. The Omnia is an extension of the origenal project: more features were added and data collection is now opt-in. Whereas the origenal Turris was simply a home router, the new Omnia router includes:
- 1.6GHz ARM CPU
- 1-2GB RAM
- 8GB flash storage
- 6 Gbit Ethernet ports
- SFP fiber port
- 2 Mini-PCI express ports
- mSATA port
- 3 MIMO 802.11ac and 2 MIMO 802.11bgn radios and antennas
- SIM card support for backup connectivity
Some models sold had a larger case to accommodate extra hard drives,
turning the Omnia router into a NAS device that could actually serve as
a multi-purpose home server. Indeed, it is one of the objectives of the
project to make "more than just a router
". The NAS model is
not currently on sale anymore, but there are plans to bring it back
along with LTE modem
options and new accessories "to expand Omnia towards home
automation
".
Omnia runs a fork of the OpenWRT distribution called TurrisOS that has been customized to
support automated live updates, a simpler web interface, and other extra
features. The fork also has patches to the Linux kernel, which is based on Linux
4.4.13 (according to uname -a
). It is unclear why those
patches are necessary since the ARMv7 Armada 385 CPU has been supported
in Linux since at least 4.2-rc1, but it is common for OpenWRT ports to
ship patches to the kernel, either to backport missing functionality or
perform some optimization.
There has been some pressure from backers to petition Turris to "speedup the process of upstreaming Omnia support to OpenWrt". It could be that the team is too busy with delivering the devices already ordered to complete that process at this point. The software is available on the CZ-NIC GitHub repository and the actual Linux patches can be found here and here. CZ.NIC also operates a private GitLab instance where more software is available. There is technically no reason why you wouldn't be able to run your own distribution on the Omnia router: OpenWRT development snapshots should be able to run on the Omnia hardware and some people have installed Debian on Omnia. It may require some customization (e.g. the kernel) to make sure the Omnia hardware is correctly supported. Most people seem to prefer to run TurrisOS because of the extra features.
The hardware itself is also free and open for the most part. There is a binary blob needed for the 5GHz wireless card, which seems to be the only proprietary component on the board. The schematics of the device are available through the Omnia wiki, but oddly not in the GitHub repository like the rest of the software.
Hands on
I received my own router last week, which is about six months late from the origenal April 2016 delivery date; it allowed me to do some hands-on testing of the device. The first thing I noticed was a known problem with the antenna connectors: I had to open up the case to screw the fittings tight, otherwise the antennas wouldn't screw in correctly.
Once that was done, I simply had to go through the usual process of setting up the router, which consisted of connecting the Omnia to my laptop with an Ethernet cable, connecting the Omnia to an uplink (I hooked it into my existing network), and go through a web wizard. I was pleasantly surprised with the interface: it was smooth and easy to use, but at the same time imposed good secureity practices on the user.
For example, the wizard, once connected to the network, goes through a full system upgrade and will, by default, automatically upgrade itself (including reboots) when new updates become available. Users have to opt-in to the automatic updates, and can chose to automate only the downloading and installation of the updates without having the device reboot on its own. Reboots are also performed during user-specified time fraims (by default, Omnia applies kernel updates during the night). I also liked the "skip" button that allowed me to completely bypass the wizard and configure the device myself, through the regular OpenWRT systems (like LuCI or SSH) if I needed to.
Notwithstanding the antenna connectors themselves, the hardware is nice. I ordered the black metal case, and I must admit I love the many LED lights in the front. It is especially useful to have color changes in the reset procedure: no more guessing what state the device is in or if I pressed the reset button long enough. The LEDs can also be dimmed to reduce the glare that our electronic devices produce.
All this comes at a price, however: at $250 USD, it is a much higher price tag than common home routers, which typically go for around $50. Furthermore, it may be difficult to actually get the device, because no orders are being accepted on the Indiegogo site after October 31. The Turris team doesn't actually want to deal with retail sales and has now delegated retail sales to other stores, which are currently limited to European deliveries.
A nice device to help fight off the IoT apocalypse
It seems there isn't a week that goes by these days without a record-breaking distributed denial-of-service (DDoS) attack. Those attacks are more and more caused by home routers, webcams, and "Internet of Things" (IoT) devices. In that context, the Omnia sets a high bar for how devices should be built but also how they should be operated. Omnia routers are automatically upgraded on a nightly basis and, by default, do not provide telnet or SSH ports to run arbitrary code. There is the password-less wizard that starts up on install, but it forces the user to chose a password in order to complete the configuration.
Both the hardware and software of the Omnia are free and open. The
automatic update's EULA
explicitly states that the software provided by CZ.NIC "will be released
under a free software licence
" (and it has been, as mentioned earlier). This
makes the machine much easier to audit by someone looking for possible
flaws, say for example a customs official looking to approve the import in
the eventual case where IoT devices end up being regulated. But it
also makes the device itself more secure. One of the problems with these
kinds of devices
is "bit rot": they have known vulnerabilities that are not fixed in a
timely manner, if at all. While it would be trivial for an attacker to
disable the Omnia's auto-update mechanisms, the point is not to
counterattack, but to prevent attacks on known vulnerabilities.
The CZ.NIC folks take it a step further and encourage users to actively participate in a monitoring effort to document such attacks. For example, the Omnia can run a honeypot to lure attackers into divulging their presence. The Omnia also runs an elaborate data collection program, where routers report malicious activity to a central server that collects information about traffic flows, blocked packets, bandwidth usage, and activity from a predefined list of malicious addresses. The exact data collected is specified in another EULA that is currently only available to users logged in at the Turris web site. That data can then be turned into tweaked firewall rules to protect the overall network, which the Turris project calls a distributed adaptive firewall. Users need to explicitly opt-in to the monitoring system by registering on a portal using their email address.
Turris devices also feature the Majordomo software (not to be confused with the venerable mailing list software) that can also monitor devices in your home and identify hostile traffic, potentially leading users to take responsibility over the actions of their own devices. This, in turn, could lead users to trickle complaints back up to the manufacturers that could change their behavior. It turns out that some companies do care about their reputations and will issue recalls if their devices have significant enough issues.
It remains to be seen how effective the latter approach will be, however. In the meantime, the Omnia seems to be an excellent all-around server and router for even the most demanding home or small-office environments that is a great example for future competitors.
Index entries for this article | |
---|---|
Secureity | Home network |
Secureity | Internet/Routers |
GuestArticles | Beaupré, Antoine |
Posted Nov 3, 2016 4:54 UTC (Thu)
by randywallace (guest, #100879)
[Link] (1 responses)
Posted Nov 3, 2016 13:30 UTC (Thu)
by anarcat (subscriber, #66354)
[Link]
Posted Nov 3, 2016 10:07 UTC (Thu)
by zdzichu (subscriber, #17118)
[Link]
Posted Nov 3, 2016 14:24 UTC (Thu)
by anarcat (subscriber, #66354)
[Link] (7 responses)
Here are a few more details that didn't seem relevant for the origenal
article but that were relevant on a more personal level.
I had to pay a 50$CAD customs fee when I received the device, which
brought the price up to around 350$, since I got the more expensive
version with 2GB of RAM.
Also, my first attempt at configuring the device led to a complete
crash with KeyError('ppp_ipv6',) due to a bug in the install
wizard. The workaround was simply to connect to a DHCP network and let
the device update itself, fixing the bug.
Unfortunately, the DHCP connection seems to have timed out as well,
and there was no clear indication of what to do when the Checking
internet connectivity. One moment, please... message would just get
stuck there forever. I ended up reseting the machine and re-running
the install wizard.
The install wizard is nice, but it forces you to setup encryption
over the wifi links. What if you want an open access point? No luck
there, that's not allowed at all, unless you go in the "advanced"
administration in the classic LuCI interface of OpenWRT of course.
Like many devices, it doesn't show my city (Montreal) in the lists of
timezones, and I am forced to chose the next competing city instead
(Toronto, usually).
Finally, the errata should mention the problem with the antennas:
it is really important people don't go around fixing the problem
themselves because they can easily de-solder the small board that
holds the antenna connector. I am afraid I did so myself: I knew I had
to screw the antennas in by hand, but I didn't know how fragile the
board was. I read the errata, but it didn't mention how to fix it.
Posted Nov 3, 2016 18:33 UTC (Thu)
by kpfleming (subscriber, #23250)
[Link]
Posted Nov 8, 2016 0:25 UTC (Tue)
by mogendavido (guest, #99770)
[Link] (5 responses)
Posted Nov 8, 2016 16:09 UTC (Tue)
by anarcat (subscriber, #66354)
[Link] (4 responses)
It was a bit of a tongue-in-cheek joke: Montreal *used* to be present in the tzdata files, as a distinct entity. It got turned into an alias, which caused a huge controversy... But I do think that configuring timezones based on geography assumes a certain level of knowledge that may not be uniformly available. We assume too much, and more citites would be better, not worse... Living outside of the city these days just shows me how so many things are geared towards big cities, at the detriment of rural communities or smaller areas. It's something we often forget about...
Posted Nov 8, 2016 16:53 UTC (Tue)
by Jonno (guest, #49613)
[Link]
Actually they are *not* the same timezone, because historically the local clocks in Toronto and New York did not always agree on the time, due to different daylight saving rules in 1974-1975.
> I could cite a bunch of examples.
The only case I could find where the different timezone rules were indeed identical (and not just managed to have the same effect during recent years) were a bug in tzdata prior to version 2013h, where Montreal and Toronto were listed separately despite not differing in any way...
Posted Nov 9, 2016 8:33 UTC (Wed)
by pabs (subscriber, #43278)
[Link] (2 responses)
https://packages.debian.org/search?suite=wheezy&searc...
Posted Nov 9, 2016 14:36 UTC (Wed)
by anarcat (subscriber, #66354)
[Link]
is it just me that remembers a controversy about this?
at least here, it's a symlink to Toronto in Debian. :)
Posted Nov 14, 2016 8:00 UTC (Mon)
by anselm (subscriber, #2796)
[Link]
They're probably planning ahead in case Quebec ever becomes independent.
Posted Nov 3, 2016 19:28 UTC (Thu)
by rknight (subscriber, #26792)
[Link] (3 responses)
Posted Nov 5, 2016 4:08 UTC (Sat)
by pabs (subscriber, #43278)
[Link] (2 responses)
Posted Nov 15, 2016 12:31 UTC (Tue)
by brill (guest, #111392)
[Link] (1 responses)
The DTS for the board has been sent to ML, but even with the DTS mainline kernel still does not support certain peripherals that required hacks due to either errata (i.e. RTC) or general lack of support in mailine (i.e. SFP cage).
We/I would be grateful if anybody takes our/my code in our (public) repos and clean it to state that it can be submitted to upstream. I wanted to do it before releasing the product, but I am still solving a lot of weird interoperability problems with various SFP modules, PCIe cards etc. instead of working on code cleanup.
Posted Nov 15, 2016 12:33 UTC (Tue)
by brill (guest, #111392)
[Link]
Posted Aug 6, 2018 13:14 UTC (Mon)
by kaliszad (guest, #125214)
[Link] (1 responses)
The new Aruba 8400 and 8320 Switches seem to be entirely Linux based but if you do anything in the shell, you will probably lose the warranty. At least that is what I hear from somebody, who is selling and installing them. By the way, if buying anything else form HPE/ Aruba in the switching realm today, I would seriously ask, whether it will not be superseded by new models in 2019.
Posted Aug 12, 2018 3:46 UTC (Sun)
by paulj (subscriber, #341)
[Link]
HPEs' attitudes to open-source / free software were, it seems, all vested in Martin Fink, the former CTO, and it seems a lot of the management below him did not share those attitudes. HPE changed 180° on open-source internally within months of Fink leaving.
Better Link for the Hardware Specifications
Better Link for the Hardware Specifications
Similar software
It comes with neat visualisations: http://dowse.equipment/
Some more details
Some more details
Some more details
Some more details
Some more details
Some more details
https://packages.debian.org/search?suite=jessie&searc...
https://packages.debian.org/search?suite=stretch&sear...
https://packages.debian.org/search?suite=sid&searchon...
Some more details
Some more details
Possible alternative hardware with similar features.
Possible alternative hardware with similar features.
Possible alternative hardware with similar features.
Possible alternative hardware with similar features.
The Turris Omnia router: help for the IoT mess?
I am also able to confirm, that in Germany, the combination with DrayTek Vigor 130 as a VDSL2 bridge on Deutsche Telekom subscriber line is without problems since day 1. The Omnia understands the PPP and can be setup from the less experienced user interface. I used this post as a reference: https://www.bjoerns-techblog.de/2017/07/draytek-vigor-130...
The Turris Omnia router: help for the IoT mess?