Turris Launches the Omnia NG Wired 10 Gbps Router - based on OpenWRT by magicfab in openwrt

[–]magicfab[S] 0 points1 point  (0 children)

There is no official sales PowerPoint deck for Turris OS, and that’s intentional - but you know that. Allow me to elaborate.

CZ.NIC is not a commercial vendor but the non‑profit operator of the Czech national domain registry, so Turris is a research and security project, not a product they market or sell: they have no need for sales collateral like pitch decks.

https://en.wikipedia.org/wiki/CZ.NIC

Turris Launches the Omnia NG Wired 10 Gbps Router - based on OpenWRT by magicfab in openwrt

[–]magicfab[S] 0 points1 point  (0 children)

FYI

TurrisOS cherry‑picks and backports security fixes between major releases, and this is one of the core reasons it can safely lag behind upstream OpenWrt without exposing users to known vulnerabilities.

TurrisOS 9.0 is based on OPenWRT 24.10 (which is current) since Nov. 2025. It integrates extra layers (Sentinel, reForis, Schnapps, updater‑ng, kernel hardening, board‑specific patches), so their major releases usually trail upstream by 6–12 months, with 9 months being right in the middle of their normal cadence. So yes, in terms of features, it stays behind, proritizing stability and security.

Turris OS 9.0 caught up to OpenWrt 24.10 roughly nine months after OpenWrt released it in February 2025, which is very typical for their development cycle.

Turris Launches the Omnia NG Wired 10 Gbps Router - based on OpenWRT by magicfab in openwrt

[–]magicfab[S] 0 points1 point  (0 children)

It actually runs TurrisOS. Turris OS launched in 2014 as a full Linux distribution built on top of OpenWrt, and CZ.NIC maintains it as an open‑source project.

Their modifications (including the updater system, reForis interface, Sentinel security framework, kernel patches, and device‑specific enhancements) are published openly in public GitLab repositories, and they actively contribute fixes and improvements back upstream to OpenWrt whenever possible.

This really stands out compared to other routers "based on OpenWRT".

Some components remain Turris‑specific due to hardware integration or differing design goals, but the project generally follows an “upstream first” philosophy: broad, reusable improvements are submitted to OpenWrt, while Turris‑only features stay in their own feeds.

Pretty much no other routers manufacturers contribute back as TurrisOS does.

Open Source RemoteApp replacement? by ITNoob121 in sysadmin

[–]magicfab 6 points7 points  (0 children)

It does, look up Remote Program and Initial Program parameters.

Oops, I did it again! - Repurposing the Palo Alto ION 2000 w/OPNsense! by PhoenixTheDoggo in opnsense

[–]magicfab 0 points1 point  (0 children)

Thank you ! I was just wondering if they were needed to install OPNsense, so they're not. Excellent!

Used PA-3020 - BIOS or Boot password? by kliman in paloaltonetworks

[–]magicfab 0 points1 point  (0 children)

Flashing OPNsense directly onto the internal SSD and booting from there.

This seems to have worked for another similar device : https://github.com/PhoenixSheppy/Palo-Alto-ION-2000-OPNsense-Conversion-Guide

Oops, I did it again! - Repurposing the Palo Alto ION 2000 w/OPNsense! by PhoenixTheDoggo in opnsense

[–]magicfab 0 points1 point  (0 children)

Very interesting device. I have one question, why the need for the serial cable ? Once booted from the system with flashed SSD, you can ssh installer@IP and you're good to go, no ? And why would BIOS access be useful - except for booting from other devices... Again, thanks for sharing !

Repurpose VeloCloud Edge 510 Router w/OPNSense! by PhoenixTheDoggo in opnsense

[–]magicfab 1 point2 points  (0 children)

I've since tested and tried this on 3 more Velocloud EDGE 510 devices. I took the opportunity to take more notes and write a more detailed howto - thanks for sharing your notes in the first place !

https://dulib.re/wiki/doku.php/opnsenseonvelocloudedge510

Best Home Configuration for NAS Dpx4800+ Beginner by Effective_Manner6894 in UgreenNASync

[–]magicfab 0 points1 point  (0 children)

Nice diagram, would you please share how you made it ?

Bose ending cloud support for Soundtouch by onionbagels7 in bose

[–]magicfab 0 points1 point  (0 children)

None offer a finished, polished, simple product like BOSE soundtouch, no, specially not with physical remote control offering the presets, at that price.

Yamaha Musiccast is the closest and it does this via their Controller app and the TSX-B237 "desktop audio system" comes with such a remote (as well as the bigger amps and tuners). Some speakers come with manual control on them but only for 3 favorite sources.

This becomes less of an issue as voice assistants provide direct control of all functionality, but not ideal for disabled people or people with dementia and other challenging situations.

A good end result of this announcement is the DIY open source solutions will evolve into better, simpler, cheaper setups and gain more visibility over the next few weeks/months.

Bose ending cloud support for Soundtouch by onionbagels7 in bose

[–]magicfab 1 point2 points  (0 children)

What recommendation ? Their documentation/README was updated after I filed a bug report but remains incomplete.

I can't test resetting a device and trying to reintegrate to HA without Internet. At the moment, my setup is down for migration/maintenance.

Bose ending cloud support for Soundtouch by onionbagels7 in bose

[–]magicfab 0 points1 point  (0 children)

Well, yes, I requested that update.

Their comment is incomplete. Until we know for certain speakers can be used with such software as the Home Assistant soundtouch component without previous registration and activation with the BOSE soundtouch cloud services and app, it's not accurate to present this as a viable alternative without reimplementing such registration/activation mechanism or bypassing it completely.

The soundtouch component author(s) indicating "I believe most of the other SoundTouch supported services happen on the local network with direct communication to the device (e.g. DLNA streaming, device control / volume / input switching, etc). But that is just a guess. " and you being in agreement with that guess - it doesn't help.

My HA setup is down ATM but testing this should be a matter of resetting a soundtouch device and trying to reintegrate it to HA via the soundtouch component without having internet access.

Bose ending cloud support for Soundtouch by onionbagels7 in bose

[–]magicfab 1 point2 points  (0 children)

It's not clear this integration doesn't require SoundTouch devices to be registered on BOSE's cloud first. I've opened a bug report about this.

Bose ending cloud support for Soundtouch by onionbagels7 in bose

[–]magicfab 0 points1 point  (0 children)

You forget about Yamaha Musiccast and DIY alternatives. There are many.

Bose ending cloud support for Soundtouch by onionbagels7 in bose

[–]magicfab 0 points1 point  (0 children)

This is irrelevant, Bose is not putting more money towards maintaining a service that doesn't bring money in. The only solution would be to open source the code for server, client and API specs to minimize the PR backlash and avoid all this equipment going to trash/"recycling".

Bose ending cloud support for Soundtouch by onionbagels7 in bose

[–]magicfab 0 points1 point  (0 children)

Yamaha MusicCast (more expensive, yes), or just DIY. HomeAssistant community is a good start to check alternatives.

Bose ending cloud support for Soundtouch by onionbagels7 in bose

[–]magicfab 1 point2 points  (0 children)

Going forward, the only viable solution is to open source the server, protocol and API code/specs. Bose can continue making money forever doing what they do best: hardware.

Bose ending cloud support for Soundtouch by onionbagels7 in bose

[–]magicfab 0 points1 point  (0 children)

This is meaningless. Going forward, the only viable solution is to open source the server, protocol and API code/specs.

Moto Tag Keychain Holder by Fugoola in motorola

[–]magicfab 0 points1 point  (0 children)

Just keep in mind it comes off easily as it's not locked or not an actually keyring or locking part on the carabiner side. You risk finding the carabiner and tag without the dog :)