ARTICLE: VyOS for Home Use

I wrote this series for people that are new to networking (or maybe just new to VyOS), but like the idea of a feature rich router like VyOS. Maybe they’re learning enterprise networking, and want to ensure that their home router helps reinforce everything that they’re learning at the time.

Part 1 - Initial Setup:

Part 2 - Internet Access:

Part 3 - LAN Connections:

Part 4 - DNS filtering using AdGuard Home:

Part 5 - Traffic Monitoring with ntopng:

14 Likes

Part 6 - Hardening :slight_smile:

2 Likes

Part 4 - DNS filtering using AdGuard Home:

6 Likes

Part 5 - Traffic Monitoring with ntopng

5 Likes

I tried your steps firewall rules breaks internet ,also disabling ntp server gave issues like some clients didnt get dhcp address

Internet shouldn’t be lost when doing part 2 of the series. If you already had LAN connections, then doing part 2 will kill internet access to clients until you add the part 3 firewall portion.

Can you provide these from Op Mode (obfuscate anything you don’t want to include):
show ntp
show interfaces
show firewall

And provide these from Conf Mode:
show firewall | commands
show service ntp | commands
show nat | commands

1 Like

yes it now works thanks again can you check out this post and guide me

Hi L0crian, thank you so much for this blog series and the accompanying videos! It encouraged and guided me setting up my first custom-built home router/firewall, which has replaced my old off-the-shelf device and has been running flawlessly for more than a month now :slight_smile:

May I make a request? Can you please write a blog article/do a video on how to configure a podman container on VyOS not running in host-networking mode (but rather in its own network with classic podman port mapping)? All examples I could find online (including your container examples) use “allow-host-networks”, and I got those to work just fine.

However, for special use cases (like a full-blown kasmweb “OS in a container”, e.g. https://hub.docker.com/r/kasmweb/ubuntu-noble-desktop) I would need the container to run in an isolated network to avoid port collisions with the host. And I can’t - for the life of me - get port mapping to work :frowning:
I suspect either my firewall rules or my NAT configuration to interfere with container networking - no packets seem to come through in either direction. Or perhaps I’m completely missing a step required for port mapping, like adding extra NAT rules?
(For basic setup, I followed the “VyOS 1.5.x Quick Start Guide”, so my firewall/NAT rules more or less match those examples.)

If you consider writing a blog post on this, I suggest you create an example based on a very simple container image like https://hub.docker.com/r/nginxdemos/hello which only listens on port 80

Thanks again, and please keep up the good work!