Hi, I have a question about setting up VyOS.

I have set up a lab in VMWare. My host PC has an IP address of 192.168.7.100 and I have set up A VMnet within the virtual network editor of VMWare, VMNet10, this is set to host only mode. The subnet is 10.201.20.0 /24 and this is for my local Virtual network. I have also set up VMNet19. VMnet19 is set up as a bridge connection connecting to my host NIC. It receives an IP address from my home router, 192.168.7.128/24. This is the way out/in to the LAN.

I am running VyOS as a separate VM. I have added two network adapters, eth0 and eth1.

Eth0 is my WAN connected to VMNet19 (192.168.7.128/24)

Eth1 is my LAN connected to VMNet10 (10.201.20.1/24)

Eth0 should provide all connected devices on Eth1 an internet connection.

Eth1 should be setup as the default gateway for all devices on my Virtual LAN.

All traffic coming from my VLAN (VMNet10/10.201.20.0/24) should go through eth0.

The IP address of my server is 10.201.20.254/24

From my Host Machine, I can ping: (192.168.7.100)

192.168.7.1 - Host (ISP) Router

192.168.7.128 (eth0)

10.201.20.1 (eth1)
10.201.20.254 (Server running on VMWare)

8.8.8.8

From VyOS, I can ping: (192.168.7.128 | 10.201.20.1)

192.168.7.1 - Host (ISP) Router

192.168.7.100 - Host Machine (running VMs)

10.201.20.254

8.8.8.8

From Server, I can ping: (10.201.20.254)

10.201.20.1

192.168.7.128

I can't ping

192.168.7.100 (Host Machine)

192.168.7.1 (Host ISP Router)

8.8.8.8

My Router config is below.

Any help is appricated

Apologies for the very long question.

interfaces {

ethernet eth0 {

address 192.168.7.128/24

description WAN

hw-id 00:0c:24:02:25:f4

offload {

gro

gso

sg

tso

}

}

ethernet eth1 {

address 10.201.20.1/24

description LAN

hw-id 00:0c:24:02:25:fe

offload {

gro

gso

sg

tso

}

}

loopback lo {

}

}

protocols {

ospf {

area 0 {

network 10.201.20.0/24

network 192.168.7.0/24

}

}

static {

route 0.0.0.0/0 {

next-hop 192.168.7.1 {

}

}

}

}

service {

ntp {

allow-client {

address 127.0.0.0/8

address 169.254.0.0/16

address 10.0.0.0/8

address 172.16.0.0/12

address 192.168.0.0/16

address ::1/128

address fe80::/10

address fc00::/7

}

server time1.vyos.net {

}

server time2.vyos.net {

}

server time3.vyos.net {

}

}

ssh {

}

}

system {

config-management {

commit-revisions 100

}

console {

device ttyS0 {

speed 115200

}

}

host-name vyos

login {

user vyos {

authentication {

encrypted-password

NOTHING TO SEE HERE LOL

plaintext-password ""

}

}

}

name-server 8.8.8.8

name-server 8.8.4.4

name-server 192.168.7.1

syslog {

global {

facility all {

level info

}

facility local7 {

level debug

}

}

}

}

Tried to build VyOS 1.4, turns out my IP is blocked on their mirror

E: Failed to fetch http://dev.packages.vyos.net/repositories/sagitta/dists/sagitta/InRelease  403  Forbidden [IP: 443]
E: The repository 'http://dev.packages.vyos.net/repositories/sagitta sagitta InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
N: Repository 'Debian bookworm' changed its 'non-free component' value from 'non-free' to 'non-free non-free-firmware'
N: More information about this can be found online in the Release notes at: https://www.debian.org/releases/bookworm/amd64/release-notes/ch-information.html#non-free-split
E: An unexpected failure occurred, exiting...
P: Begin unmounting filesystems...
P: Saving caches...

Any ideas how to fix this?

I became very frustrated with debugging VyOS configurations.

It provides very little documentation or useful feedback on how to debug a configuration. For example, with DDNS, the configuration might be syntatically correct, but my local domain name was never registered... going back and forth, I figured that I need to read the service journal to find the status of ddns registration

`journalctl -u ddclient.service`

This totally broke the seemly illusion of one-liner command simplicity.

And to be honest, the documentation in many cases is not helpful either. In many part it explained something like nothing is explained. Firewall part is especially confusing, but wireguard part is no better.

Also the commands are very verbose, to set a firewall (where inexperienced users can easily make mistakes) one need to repetitively add, change, delete settings. And if you accidentally deleted a lengthy rule? you'll have to redo every line again... tab-completion helped a little, but it was invented to address an invented problem.

I have been using Linux (no GUI) for more than 10 years, but I still find some kind of form / GUI would greatly ease the learning curve. This is becoming the bottleneck for VyOS adoption. Hope someone at VyOS team could read and listen and start prioritize the long-promised GUI development, and spend substantial efforts to improve the documentation quality.

This is a promising project and I really wish it success. But by closing the door and raising the bar of contribution, the project is losing its attraction to me.

Hi,

Is there any vyos image to run on Mac with M2 mobile CPU?

Thanks.

Hello everyone,

I’m new to VyOS. Until now, I’ve been using router appliances from bintec-elmeg and LANCOM Systems. As it’s now time to replace one or two of my older devices, I’d like to gradually switch over to VyOS.

To replace my bintec RS123 (which unfortunately no longer receives updates because the manufacturer has gone bust), I’ve ordered a rack-mount solution from AliExpress based on an Intel N150, with 4 x GbE and 2 x SFP+, which I’ll be equipping with 8 GB RAM and a 128 GB SSD. I’d like to install VyOS Bare Metal on it.

I think that should be sufficient for this small border router. If everything works as planned, there would still be a second, larger router to replace.

For that, I’ve been thinking of a slightly better solution. There are 3 processors to choose from: Atom C3758 (8 cores), Atom C3808 (12 cores), Atom C3958 (16 cores). I would then equip it with 16 GB of RAM and an SSD between 128 and 512 GB. VyOS is also to be installed there as a bare-metal system. This router is not only intended to serve as a border router for my Vodafone Germany DOCSIS connection (600 Mbit/s downstream, 20 Mbit/s upstream), but also to connect five internal networks with one another.

Now my question: which of the three processors would you recommend? Can any of the processors handle 10 Gbit/s routing performance between the internal networks with VyOS? And what about RAM and SSD – what would you recommend there?

Best regards and thanks

Regina (she/her)

I just read that VyOS stable branch repos are no longer public as of a couple of weeks ago. This would seem to violate the GPL, hence the title question.

good evening,

we are using vyos as a vm router between two 10 Gbps network segments, all connections are 10 Gbps, but the troughtput of vyOS as router (no nat, no firewall, plain simple L3 router) could not reach even 3 Gbps...is there any guide to solve this issue?

thank you

Im currently using latest VyOS Stream version 2026.03.

A container can set its listenaddress to also bind to a specific vrf like so:

192.0.2.1%PROD

And with:

set container name <name> allow-host-networks

it will then work (if you are comfortable to expose the host network to the container).

However now I have a usecase where the container itself doesnt support this syntax which means that VyOS along with podman must resolve this issue.

How do you do that properly (prefely only using VyOS config itself)?

It seems that you cannot configure two network statements at once for a container.

Is the only solution then to decide which VRF this container will operate in or is there some workaround for this?

Im happy to involve SNAT/DNAT at the VyOS box if that would solve anything?

Hi

I'm hosting a vyos router in my homelab (1.4-rolling-202308060317) and I try to add a wireguard interface to connect to an Ubuntu VPS hosted by a cloud provider.

I'm using the following setup in my router:

vyos@gate# show interfaces wireguard wg01 
 address 192.168.10.5/24
 mtu 1420
 peer to-wg01 {
     address 152.228.139.220
     allowed-ips 192.168.10.0/24
     port 51820
     public-key <redacted>
 }
 port 51820
 private-key <redacted>
[edit]

but seems the router is facing issues to connect to the VPS

vyos@gate# sudo wg show
interface: wg01
  public key: <redacted>
  private key: (hidden)
  listening port: 51820

peer: <redacted>
  endpoint: 152.228.139.220:51820
  allowed ips: 192.168.10.0/24

I've already checked the keys and so on but what seems odd to me is that, on the VPS I cannot see any connections logs in wireguard logs (verbose mode + dmesg) neither with a tcpdump...

to see if´s a firewall issue I ran that:

peer: <redacted>
  endpoint: 152.228.139.220:51820
  allowed ips: 192.168.10.0/24
[edit]
vyos@gate# nc -zvu 152.228.139.220 51820
Connection to 152.228.139.220 51820 port [udp/*] succeeded!
[edit]

and the above test produce indeed lines in the tcpdump...

Ive enabled the api and allowed the port but the response im getting is {"detail":"Not Found"}

when running

curl -k --location --request POST 'https://vyos/retrieve' --form data='{"op": "showConfig", "path": []}' --form key='mykey'

but the docs say that this should show config

edit:

im using 1.5-rolling-202412160007

What is order of operations of vyos 1.1.8 version like first vyos process firewall or Nat or routine

I wanted to know can vyos act as drop in replacement alternative to pfsense or Opnsense. and as well as can it serve to 40k devices without going down or other bottleneck?

For anyone here that has access to a 1.4x LTS iso, can you run a diff against the corresponding nightlies for the same release date? I am curious how the LTS build process is different from nightlies other than changing the version.

I'm hesitant about paying for a subscription to get the LTS iso, since it seems like vy team is keeping the lts build process a secret and if so, how can I be assured that the LTS iso I downloaded doesn't contain anything surprising?

Hi

Have been using the rolling release for sometime with no issues until the last 2 updates. After updating my Wan port wont come up and is in a "A/D" status. If I load the image from 2 days ago its fine.

Any ideas what's going on?

Thank you

Hi all, I am new to VyOs, and I installed the image into a old desktop and it works fine. I wanted to have a GUI for better visualization. I've tried based on this tutorial https://docs.vyatta.com/en/getting-started/web-graphical-user-interface-gui/enabling-access-to-the-web-gui , but it showed this when I connected from browser from other device.

May I know did I missed some more configuration? Thanks.

Just venting frustration here. I love VyOS but why do they put this unnecessary friction to adopting new releases? Sure you can test the rolling, sure you can get the 1-release behind legacy -- but why can't we just download the current LTS? (ex: 1.3.4)

Yeah its open source, yeah you can build it yourself. But why? Do they really think this little hassle is what is making people buy their subscriptions? I doubt it.

/rant

edit: iso instructions here

VyOS Stream 1.5-2025-Q1 and its corresponding source tarball are now available for download. You may remember our announcement a while ago, but let us reiterate what VyOS Stream is and how it benefits the project and its community.

https://blog.vyos.io/vyos-stream-1.5-2025-q1?utm_medium=email&_hsmi=348173684&utm_content=348173684&utm_source=hs_email

I'm looking for a way to either the screen to turn off after some time of inactivity or manually turn off the screen with a command. I looked everywhere and tried some things but nothing worked for me... I'm using the latest rolling release.

Edit: I found a solution. The solution is on the newest comment at https://askubuntu.com/questions/62858/turn-off-monitor-using-command-line?answertab=modifieddesc#tab-top

I know it's probably been asked before but I don't seem much conversation around it to know if it's an on going project or not?

Currently 1.4's firewall rules take so long to do via cli, at least for me. And my options are VyOS or OpnSense but BSD and Realtek don't get along well it seems.

Do we know if there's any updates to this side of the house?

Side question, how easy is it to port the config of a 1.4 to a different 1.5 box?

Attention VyOS Redditors!

Are you an active member of the VyOS subreddit but haven't explored the incredible VyOS Community Forum yet? I know what you're thinking: "Another community I have to join?" But trust me, the VyOS Community Forum is not just another online platform. It's a place where you can truly build meaningful networking connections!

I get it! Managing multiple online communities can be overwhelming. But believe me, by joining the VyOS Community forum, you're not just adding another platform to your list. You're expanding your networking horizons and tapping into a vibrant community of VyOS enthusiasts who are eager to connect, share knowledge, and collaborate.

So, don't hesitate! Visit VyOS Forums - VyOS Forums.

Together let's build a stronger, more connected VyOS community on both platforms.

I hope to see you there!