this post was submitted on 02 Aug 2023
358 points (98.1% liked)
Technology
60116 readers
2564 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Not silly at all for multi-gig connections. I'm running it on Pi 4 which does well for a 1Gbps connection with SQM. Sometimes it's cheaper to get old x86 hatdware to do the same. Or I've heard you could run it in a Docker container on a bigger machine.
You can definitely run it in a VM (which is how I handle it) but container support wouldn't surprise me.
The "silly" part was more that if you have x86 you can use opnsense/pfsense but I'm with you in that SQM is a big draw as well as less risk of compatibility issues as my APs are also flashed with openwrt. And the BSDs were well behind on wireguard support when I first switched to x86, although they have since caught up now I believe.
Exactly, standardization is a very significant pro. Hardware support being a dependency for standardization. I wrote a simple SaltStack module for OpenWrt and I'm using that to manage the config of multiple OpenWrt devices across multiple locations. That happens to live along with the rest of my Salt code which manages everything else.