When Microsoft started enforcing online accounts to use my computer. It was then that I fully jumped ship. I was using Linux way before that for my media server, HTPC, etc., but it was that and the Steam Deck that made me finally fully jump.
When Microsoft started enforcing online accounts to use my computer. It was then that I fully jumped ship. I was using Linux way before that for my media server, HTPC, etc., but it was that and the Steam Deck that made me finally fully jump.
pfSense = Firewall and router system based on FreeBSD. Has both open source and commercial versions. Built for SMB to Enterprise uses. Extremely powerful with all of the bells and whistles you’d expect from a professional firewall product.
OPNSense = Basically pfSense with a different UI. It’s a fork of pfSense. Much of the same capability, but is built by a smaller company.
OpenWRT = Replacement firmware for embedded devices (as well as x86). It’s open source WiFi router firmware that runs on tens of thousands of devices. Many vendors will even base their custom firmware on OpenWRT and put a different skin on it (GL.iNet, for example).
The GitHub repo of the maintainer shows that the project is archived and dead.
Does that offer any advantages over the kiosk mode functionality? Looks like that repo was abandoned in 2023 and marked as archived.
As long as your browser supports the DRM, it should stream 1080p and 4k fine. Chrome is best, unfortunately, specifically for Netflix.
It loads the web page in full screen kiosk mode in Chrome.
I run an HTPC that works fully with my AirMouse Remote I bought for it for ~$15USD. It uses Flex Launcher running on Debian.
Basically, I use it for Plex, some Netflix, retrogaming, and Steam.
I was in a similar boat to you were I looked at Plasma Big Screen, LibreElec, etc. Plasma BigScreen was too buggy or unmaintained. LibreElec is great if you want to play local stuff, but terrible for streaming things like Netflix. In the end I said “screw it. I’ll make my own”. Now it’s the center of my living room.
If you’re getting a /64 from your ISP via DHCPv6, you likely need to send a prefix hint. I’d guess /60. Then you’ll have multiple /64s to work with on your inside interfaces.
Who is the ISP?
If you’re allocated DHCPv6-PD with a subnet, you don’t use a relay.
Prefix ID of 0x1 means “Use the first prefix available in the block as a /64 for the LAN”. Essentially your ISP probably gave you a /48, /56, or /60. The firewall is giving prefix IDs to all of the /64s you can fit inside of one of these and allocating them numbers 1 through whatever. Each LAN you have can have its own prefix ID. A /60 has 16 /64 networks that you can subnet it into.
I’m not against AI. I’m against the hoards of privacy-disrespecting data collection, the fact that everybody is irresponsibility rushing to slap AI into everything even when it doesn’t make sense because line go up, and the fact nobody is taking the limitations of things like Large Language Models seriously.
The current AI craze is like the NFTs craze in a lot of ways, but more useful and not going to just disappear. In a year or three the crazed C-level idiots chasing the next magic dragon will settle down, the technology will settle into the places where it’s actually useful, and investors will stop throwing all the cash at any mention of AI with zero skepticism.
It’s not Luddite to be skeptical of the hot new craze. It’s prudent as long as you don’t let yourself slip into regressive thinking.
Debian ticks all of these boxes.
Stable release
Wayland or X Server
It’s Debian, so literally everything is built for it, except maybe some obscure arch packages
Has options for any DE you want
Steam can be installed via Flatpak
Only thing I’m not sure about is your air print stuff. I’m sure there is a package that a quick apt install would get, though.
It uses pamac/pacman for packages like Arch. I believe pamac has automatic updates, if turned on.
I’d argue chain loading coreboot/libreboot from u-boot isn’t really “supporting it” as much as it’s just extending it, but fair enough. In the end it’s still using u-boot with extra steps.
Coreboot is for x86-64. ARM usually uses U-Boot.
Flex Launcher.
How, exactly, is Wayland a mess? It has a good legacy window compatibility layer and is solving a lot of problems X11 had. Seems perfectly alright to me.
I work for a company in Texas, USA. We actively discourage Windows being used in our organization and push people to use macOS or Linux.