this post was submitted on 10 Nov 2023
2 points (100.0% liked)
Homelab
380 readers
9 users here now
Rules
- Be Civil.
- Post about your homelab, discussion of your homelab, questions you may have, or general discussion about transition your skill from the homelab to the workplace.
- No memes or potato images.
- We love detailed homelab builds, especially network diagrams!
- Report any posts that you feel should be brought to our attention.
- Please no shitposting or blogspam.
- No Referral Linking.
- Keep piracy discussion off of this community
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Whenever people ask for router OS (VM or physical) I'd always recommend OpenWrt. Come with WebUI by default (unlike Vyos) and you can do advanced CLI configuration with familiar Linux utils (unlike *sense), and for most users you really just want to do some VLAN so it is perfectly suitable. A bonus is that you could use the same UI for your router and AP, so even easier
Generally you will know when your demand is beyond OpenWrt's capability (usually when you can't find the required package in opkg), and by then you probably know the answer to this question better.
I second this. Openwrt is so fast, I can route 10gbit with half the resources of opnsense/pfsense. It has a nice GUI and has all the features I need.
Do you know if OpnSense allows you to have the same UI for the router and AP? I’m leaning towards either OpenWrt or OpnSense but still looking into the pros/cons between the two.
What this person means by "using the same UI for your router and AP" is that by installing OpenWRT on both your virtualized wired router and your Wi-fi access points, you don't have to learn two different web UIs to configure networking. If you have an existing wireless setup that you don't really want to screw with that doesn't have OpenWRT already, then that doesn't really apply.