Turris OS 4.0 alpha2 is out!

SFP on Omnia in 4.0 is supported by kernel but problem is in device tree. Currently we “solved” support of SFP by providing you with two device trees (for phy and for sfp). You have to manually switch between those. In future we are thinking about u-boot glue code that would choose correct device tree or some kind of daemon that would overlay device tree in runtime (but for that we need new kernel).
Anyway, current support of sfp in hbk and hbd branches is in form of two device trees and you have to change link in /boot/dtb to sfp one if you want to use sfp.
(Note that on Omnia we have known issue in hbd and hbk that if was wan cable is plugged in then kernel panics)

In 4.0 DSA is used to configure switch (not switch-config as previously). If you try to configure switch with swich-config then it fails and weird stuff happens. Don’t do that.

DSA configures switch from netlink configuration. That means that to create vlan you have to just connect netlink interfaces to their own bridge. If you need tagged vlan then you have to use driver-level tagging ([OpenWrt Wiki] VLAN). DSA should correctly configure switch with such configuration. I wasn’t able to test this all in OpenWRT yet so I am not sure if it is going to go smooth but there seems to be no Luci way of tagging.

When we release new release it is going to be automatically installed according to updater configuration. You can also use switch-branch to move your router to different release cycle (hbs=stable, hbt=testing, hbk=openwrt stable, hbd=openwrt master)

Read README and ./compile_pkgs --help.

https://repo.turris.cz/hbs/medkit/omnia-medkit-latest.tar.gz
Do not use Mox or Turris 1.x medkit on Omnia!