Hi,
I received the new Shield and I am wondering why there are neither the Advanced Settings nor the Package Manager Tabs visible?
How can I acces the old Foris GUI?
The same for the Luci GUI - the path cgib-bin/luci is not working, but from opkg it is already installed.
Regards
Evan
Ok - I tinkered a bit arround with that toy ;).
Disabling lighttpd and installing nginx-mod-luci-ssl does the trick.
Why is ist not possible to switch easily between the different GUIs?
Hi evan,
I have the same Problem, could you please give me a little more info on how to activate LuCI? Have been trying with the OpenWRT-howTo’s but haven’t had any luck 
Thanks
Peter
Hi Peter,
I did this as I was too lazy to edit the light lighttpd scripts/configs - maybee there is a better way ;):
opkg update
/etc/init.d/lighttpd stop
/etc/init.d/lighttpd disable
opkg install nginx-mod-luci-ssl
/etc/init.d/nginx start
/etc/init.d/nginx enable
and then enter https://host/cgi-bin/luci/
Or flash this - then you have both:
https://repo.turris.cz/hbs/medkit/mox-medkit-contract-shield-latest.tar.gz
Same problems with Luci here…
Since I find the Foris surface useless, I wanted to get more configuration options for the firewall with Luci webinterface. I tried the installation as well as a reset and the installation of the latest image (thanks to evan, I followed your steps exactly).
The IP Link https://xxx.xxx.xxx.xxx/cgi-bin/luci just showing me an 502 Bad Gateway and a nginx / 1.17.7
I have bad news for all of you. Turris Shield is intended for very unexpreienced users and that is also reflected in GUI. There are even some more advanced Foris configurations that were intentionally hidden. Absence of Luci is intentional and although it somehow slipped to image it is going to be removed with subsequent updates.
It is also not supported to use SSH. We appreaciate your interest but we do not ensure smooth update with changes done with SSH. SSH is there primarily for debugging purposes and not expected to be used by end user. You can do what ever you want with device you bought of course but support is going to be very limited in case of Shield with manual intervention.
In general you should buy Turris Mox to get Luci and more. Turris Shield is weaker hardware compared to Mox and is intended to serve as very simple router/firewall with Turris Sentinel and higher reliability.
Hi there @cynerd
I’m a little bit confused about turris shield. According to you:
Turris Shield is weaker hardware compared to Mox and is intended to serve as very simple router/firewall with Turris Sentinel and higher reliability.
But this contradicts the official documentation of turris shield which states that the hardware is exactly the same as MOX, modules A and C. (link to the official documentation).
So, is shield a rebranded MOX with different software or a completely new piece of hardware? If it is a rebranded MOX I guess that we can convert into a MOX (losing support & warranty) and have the full potential of the router.
I see the point of this router very basic users but I don’t understand why start now to limit the possibilities for power users, not having port forwarding is dealbreaker in my opinion (and also for some amazon customers).
To be exact it is the weaker variant of Mox A with Mox C. If you buy Mox Start it is going to have 1GB of memory while Mox A in Shield has only 512M of memory. There are also not all components on A board as they would be on Mox A (to make it cheaper of course). And documentation states that it is “based on” not “same”.
Turris shield tries to simplify experience for end users and to provide cheaper alternative to get to Turris routers. The limitations are partly needed to make it cheaper and thus Turris Shiled can’t be combined with Turris Mox expansions (at least not officially). But primary reason is still the user experience. It is based on feedback from distributors. The limitation to only reForis interface, removal of possibility to install additional software and additional default settings are there to reduce complexity and to present cleaner and targeted product. The missing port forwarding in this sense is honestly just an missing feature in reForis. We plan to add it but there is no ETA at the moment so our official statement is: if you need it you should by Mox. Honestly Turris shield is marketed and intended for users who do not host stuff at home, for users not able to articulate “port forwarding” in message, to users who mostly just consume stuff. As I already stated, you probably want to buy Turris Mox rather than Turris Shield.
Thank you for the explanation @cynerd
I see shield a capable enough router for some user scenarios with a much more attracting price than the MOX (99€ vs 160€) with the downsize of not being expandable and less dram memory (which is not a dealbreaker for many users).
I will consider if in the future there is vanilla openwrt support, which I guess that eventually will be.
Thank you!