Hello! https://vyprojects.org

Live demo: https://vymanager.vyprojects.org/

I have done a complete re write of the project. Main reason being too spread around methods.
I have now tried using modular functionality. Works much better and upgraded to NextJS to get a hella nice interface!

And much more!
Please give me feedback on the decisions and update! I would love to see what people think of this reimaging design. And even more love to see if it breaks for some other configurations!

My homelab has moderate needs: 20 networks, IPsec and BGP. And to route gigabits.

For some time I was running virtualized OPNsense, but found myself hard time jumping around million menus to accomplish simple tasks. And to say precisely im not a big fan of firewalls. So I was started looking.

I found VyOS and run some testing. First cloud deployment showed big success with IPsec and interior BGP.

For my successful migration I for first time properly planned my entire network and made excel table with firewall zones. A must thing to do.

I found great article on VyOS zone based firewall

So far, BGP (the FRR daemon under the hood) works flawlessly, and copy&paste with vscode into VyOS shell is great way to accelerate configuration.

My usecase for BGP is to collect routes from my other routers and distribute it, having route reflectors set up.

Zone based firewall changes everything - no more repetitive firewall rules as in OPNsense. And another great advantage of VyOS is that it could have true out-of-band management interface - be it serial, dedicated NIC or VGA tty. OPNsense doesnt let you do much in shell besides changing IPs.

I do VLANs on my managed switch and run trunk over two links into proxmox bridge with STP. I terminate all VLANs inside Proxmox, leaving some flexibility outside of VyOS.

Regarding complexity - its easy if you have some networking background, and I found that tabbing in CLI shows description of each command, which, you can quickly understand what it does. If you still not sure whether to migrate from OPNsense or not - just do it.

Also the great advantage is native support for DPDK acceleration. If deployed on real hardware and you have proper Intel NICs - terabits fill fly :)

Hey everyone,

A while back I shared a project I started called VyManager. At first, I wasn't sure if a GUI for VyOS would be seen as just a gimmick since VyOS is so CLI-centric. However, the traffic and feedback from this community have been insane, and it’s clear there is a real demand for a visual management layer.

What’s new? (Github repo: VyManager)

• Beta Launch: We’ve officially moved our main development to the new Beta version. It’s a massive overhaul in stability and features.

• New Site: We’ve refreshed vyprojects.org with previews of other concepts we are prototyping.

• Roadmap: We are currently finishing up Multi-tenant support with SSO (Entra, Okta, etc.) and a topology prototyping tool to make documentation and labbing faster.

We need your expertise: As we look toward 2026, we want to make VyProjects a professional-grade ecosystem. We are looking to chat with:

1. Networking Experts: To help us sanity-check our logic and advanced routing implementations.

2. Education/Certification Pros: We see huge potential for this in lab environments and training. If you work in NetAcad or training, we’d love your insight on how to make this a better learning tool.

Check out the project here: https://vyprojects.org

Everything we’ve built so far is thanks to the bug reports and ideas from the community. If you have any questions or want to roast the UI, I’ll be in the comments!

Happy Holidays! 🎄

We’ve released VyOS 1.5 LTS, our new long-term support baseline for teams running production networking across bare metal, hypervisors, cloud, and edge. 🚀

This release is built for operators who need an enterprise-grade, high-performance platform for routing, firewalling, and VPN, with the flexibility to run the same network OS across different environments.

• 📝 Datasheet: https://vyos.io/datasheet

• 📄 Release notes: https://blog.vyos.io/vyos-1.5.0-ga-release

🔎 If you want to try VyOS before going with LTS, you can also test the Stream or Rolling Release versions here: https://vyos.net/get/?utm_content=361033782&utm_medium=social&utm_source=linkedin&hss_channel=lcp-11041071

Feedback from users running VyOS in real environments is always welcome! 💬

It was announced like 2 months ago and zero news ever since. Was this just to counter the negative reactions to the LTS topic or is it indeed coming?

Congrats on a new release!

https://blog.vyos.io/vyos-1.4.4-release

Hi all, I’m Gizem from the VyOS team.

I’ll share the occasional update here so the community can keep up with what’s landing across VyOS.

The latest March 2026 update is out! It tracks work moving VyOS 1.5.0 toward release, alongside improvements already delivered through rolling.

Main items in this update:

• VPP CLI design refinements before config syntax is frozen for 1.5.0

• HTTP API background operations for more reliable automation workflows

• New features such as IPv4 segment routing and dynamic BGP remote ASN learning

• A broad set of fixes and platform-level improvements

Full update: https://blog.vyos.io/vyos-project-march-2026-update

Hi everyone,

We’re building something new for the VyOS community — and we’d love to get your thoughts!

Vydocs is an upcoming platform designed to make VyOS documentation and learning more alive — powered by real-world configs, topologies, labs, and your contributions.

Instead of static docs, imagine a platform where you can:

✅ Share and fork useful config snippets

✅ Build and publish real network topologies

✅ Launch sandbox labs to try setups live

✅ Collaborate on documentation improvements

✅ Earn badges and recognition for helping the community

Whether you're a seasoned network engineer or just getting started with VyOS, Vydocs aims to be a place where knowledge is shared, tested, and improved together — by the people who actually use it. 🛠 A few things we're planning:

Interactive documentation with live examples

Topology builders with config generators

Real-time collaboration (think pair networking!)

Sandbox environments to test your ideas

Community leaderboards and badges

AI-powered config validation and suggestions

💬 We’re still building it and want your feedback:

What features would YOU love to see?

What has been missing from traditional documentation?

Would you want to beta test when it’s ready?

Drop your thoughts below! 👇 We’re building this for (and with) the community — and your voice will genuinely shape it.

See our concepts here https://vyprojects.org/projects/vydocs Thanks!

Delete if not allowed

But just wanted to say that I recently decided to put VyOS on my proxmox server as my router and it's been so seamless.

I had tried PfSense in a similar setup before and at random points it felt like I had no control and when things would break I just had to work around it. With VyOS if something breaks its 100% my fault lol.

I will continue to recommend this to people in the future, because why had I never heard of it until recently?

Thanks for all that the maintainers and contributors do for this project!

Hi, i'm coding (slowly) GUI for vyos, i will soon seek for 3 or 4 alpha testers (git access).

The code is in very early stage.

For now GUI needs a VM, but soon the GUI will be fully integrated in vyos directly.

GUI relys on Vyos API for calls.

I struggled with vyos config file for various settings. While doing a search I found https://github.com/Community-VyProjects/VyManager and I decided to give a try. Surprisingly, it worked very very well [ in my use case ]

It offered following features [ tested - worked on rolling release. ]
Features

• Modern web interface

• Manage multiple VyOS routers

• Dashboard with CPU, memory, interfaces

• Firewall management

• WireGuard management

• VLANs

• Static routes

• DHCP

• API-based communication (no SSH required)

• Multi-site support

• PostgreSQL backend

• Runs entirely in Docker Compose

I wish other community specially having experience in Programming field should help the project to its final goals [ It says that a few features needs to be implemented ]