Generally speaking I would avoid combining critical networking infrastructure with other services. Just from a reliability standpoint.
Let your router be just a router. Simple = reliable.
this post was submitted on 24 May 2025
11 points (82.4% liked)
Selfhosted
46676 readers
248 users here now
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
founded 2 years ago
MODERATORS
You can run a router VM but I run my opnsense on a thin client directly.
The R3 isn't really powerful enough for that.
On small x86 routers you can install Opnsense or IPfire which come with some non-router software to run a reverse-proxy or so. IP fire also allows to run full VMs, but the more advanced features are pretty limited.
Some people also do the reverse and run a full OS on them and then virtualize Opnsense and directly pass through a NIC to that VM.
@poVoq Yeah I was thinking that the overhead of a Hypervisor was a bit much hence something that is a bit more lightweight.
Why not OpenWrt?
@bizdelnick Oh I love Openwrt andnfor router functionality its great. But I am trying to have my cake and eat it by seeing what applications I could also selfhost on the box as well. e.g. anything such as email, file sharing, activitypub server or homeassistant
I'd run the lightest full OS that you can, and run containers for services.
If you really want to get fancy you could use something like the frrrouting package to make any Linux based operating system your router, but that's almost entirely configured through a cisco-like command interface
I'll be honest, I was writing while pooping and didn't really think it all the way through. A router in a container probably doesn't make sense. Maybe run the router on the OS, and then services in containers alongside. I'm not sure how janky the networking will be, if docker and the router will both be creating rules. Maybe one VM, so that it's just a plain bridge adapter, and containers in there.