I'm about to install my Mikrotek router and I'm not planning to create a high availability cluster just yet. My main goal is to run the core components of my network directly on the router, including DHCP, DNS management, firewall, and general network administration.
With RouterOS 7 supporting Docker, I'd like to host all my homelab Docker containers there or on a fast flash drive. I'm new to networking, and while this seems intuitive to me, I've noticed that most people host their network management on their PC's Docker setups. Is there a specific reason for that? Would it be better to keep these services on a separate machine?
Here's what I hope to accomplish:
1. Get a public IP from my ISP.
2. Set my Plusnet hub to bridge mode.
3. Install all necessary network management apps directly on the router.
4. Utilize RouterOS's Docker support to run Portainer/Rancher, Keycloak, HeadScale, Home Assistant, and Traefik.
This approach seems logical to me because I could manage my network regardless of what OS or hardware I use for media or other activities. However, I see that most people prefer to have their network management on a separate machine. What are some reasons against keeping everything on the Router/Firewall? Also, I want to have all my Docker apps accessible on the local network.
1 Answer
It can definitely be tempting to run everything on your router, especially since it simplifies the setup. However, one reason many folks prefer using a separate machine for network management is performance. Routers, even advanced ones, often have limited resources compared to a dedicated PC, which can manage Docker containers more efficiently. This can lead to faster response times and better reliability, especially if your network management tasks become demanding.
Totally agree! Plus, if something goes wrong on the router, you might lose access to everything at once. It's safer to separate the critical management tasks.