Yeah I find it more interesting to see how it's built from scratch, then I can decide if it's worth doing myself or just using X. I think this is a good software principle in general.
replyBasically any computer is a router if you're brave enough.
replyWindows PCs had (have?) that Internet connection sharing feature for a long time. It was really just a checkbox to enable NAT too.
Sometimes I think combining a firewall/router/switch/AP/file server/etc into a device called a "router" really confuses people. Even people who should know better.
the naming is part of the confusion. consumer "routers" are really NAT gateway + DHCP server + DNS cache + WiFi AP + maybe a firewall, all in one box. separating them makes each piece clearer.
replyIt is much, much easier than it used to be. The documentation and videos alone available make something like this a very welcoming learning experience that anyone can complete step by step by pausing a video and replaying it.
replyLike most things, really. I used to build routers from old PCs, but eventually those tiny appliances caught up with the performance/functionality I need.
replyYou can do a lot of routing on a $70 Mikrotik, although they might not be "easy".
I really want to end up with one of these for at least a few months: https://mikrotik.com/product/rds2216
replyAt $2k out the door that's way more reasonable than I thought it'd be.
replyToo bad I can't fill it with old spinning rust.
For sure, it's a path and passage towards devices like that.
replyEveryone has a starting point, starting with soemone has lying around is one thing.. the quicker they can get going the more they can get to leveraging the real power in most devices.