Should VyOS adopt the new logo or not? Participate in the poll.

We realized that we've been doing it wrong. We asked this question, but didn't give the readers an easy way to answer it!

Well, this is fixed now. Please participate in the poll:

If you don't have a Phabricator account, it's a good chance to create one, as Bugzilla will be eventually phased out. If you don't want to register a new account, you can register through Github, Google, or Facebook.

Should VyOS adopt the new logo or not?

The logo is hardly the most important thing in the world, but that's what's displayed on the website and what people put on mugs and shirts, so we'd better decide.

A while ago, a new logo was proposed. You can view it in different variations here: 

In the discussion in the old blog and the phabricator post above, a number of people told us which variation they prefer, but no one asnwered the most important question: should we drop the old logo and start using the new one or not?

Please do answer it. If you like the old logo and don't want to change anything, say it. If you think the new logo is better and we should start using it, then say it too.

Since we are going to update the main website (there's even a draft of its content, which everyone is invited to review:, and we started working on its design, we need to make this decision.


VyOS usage report on AWS

Once in a while people ask how many people are using VyOS on AWS. Since AWS sends us usage reports, this is something we can find out.

Note that this is about the AMI we distribute through the marketplace, we know nothing about instances people deploy from community AMIs.

Anyway, on May the 29th, there were 418 users of the marketplace AMI who ran 466 active instances (roughly 1.1 instance per user).

Breakdown by country

There were users from 32 countries. Countries with the largest numbers of users are the USA (232), Japan (57), United Kingdom (25), and Australia (18). Most other users are in other european countries and a few are in american countries other than the USA and asian countries other than Japan.

Breakdown by instances

The most popular instance type is, unsurprisingly, the free tier eligible t2.micro (202 instances). It is followed by 100 m3.medium, 54 t2.small, 48 t2.medium, and 13 c4.large instances. The remaining larger 49 instances include various large and xlarge ones, including some m4.4xlarge and c3.8xlarge (I sure would like to hear from those people about their use cases!).


Conclusion? What conclusion? I'm not sure if 418 users on AWS is a failure or an achievement. Maybe when we make images for other cloud platforms, we'll have something to compare it with.

Would you participate in a VyOS conference if it existed?

Hi everyone,

Please note: this is not a call for papers or anything like that, this is absoluitely theoretical and no specific plans whatsoever were made, and we clearly have more important things to worry about, but we want to gauge interest to find out if there's a reason to ever think about it or not.

If we were to have a VyOS conference, would you participate? What would be preferred location? How far would you agree to travel to attend it? What would you like to see there? What would you like to speak or listen about?

VyOS 1.1.7 OVA image for VMware

Back then we used to make OVA images, which didn't attract any interest at the time and the idea was abandoned.

Perhaps it's time to do it again and gauge the interest. We made one for 1.1.7 and it's available from and from the mirrors.

This OVA uses an embedded signature made with an object code signing certificate issued to Sentrium, to simplify deployment.

This one was made with VMware and uses VM hardware version 9. It should be compatible with ESXi 5.5 and later and VMware Workstation 9 and later.

Theoretically it may work in other systems with OVA support, but from my experience OVF, despite technically standardized, doesn't work that way. Please tell us if you've had any luck with it and if you know how to make it friendly to multiple systems.

Have you got any spare hardware for the VyOS testbed?

We've had an idea to put together a testbed for testing new VyOS releases for a while, as having different people test different interoperability issues is not always all that handy, but we didn't have a place to host it, so we never even made any specific plans.

However, syncer (the other guy at Sentrium) offered to host it in his closet, so we can think about details.

The idea is to setup a testbed with a few VyOS boxes and hardware by various vendors where we can test if everything is working as expected. Ideally we'd like to offer access to every contributor so they can live test their changes, but for this we'll have to come up with some reservation system (do you know of any ready to use implementations?).

But first of all, we need hardware. We've already got an EdgeRouterLite, probably a Cisco 870, and a RasperryPi for a host simulator. If you've got a device you can part with, consider donating or leasing it to us.

What we definitely don't have:

  • Some Juniper (SRX or smaller JSeries perhaps?)
  • Some Mikrotik
  • Cisco ASA (5505?)
  • One more managed switch
  • A couple more rpi's or other small boards for host simulators

If you've got anything else you think if worth adding to the testbed, let us know, join our conference here

Social network integration for VyOS 2.0

There are still many design decisions we have to make for the next generation VyOS.

No project can become successful these days if it lacks social network integration. For this reason we started working on it right away.

When you install VyOS, you will be prompted to link it to at least one supported social network, Facebook or Twitter. If you choose to use Facebook, you will be prompted to join the official VyOS group and join or create a group for your network.

One of the functions of social networks is to connect like-minded people and let them tell one another about their interests. For this reason we are adding "likes" to the command line interface. You will be able to like a particular feature and see who else likes it.

We will be using the number of likes to prioritize features. Features that get the most likes will get the most attention, so make sure to like the features you use.

Knowing who else likes features you use will also help you find people to share experience or ask for help.

vyos@vyos# like protocols ospf

vyos@vyos# run show likes protocols ospf
dmbaturin likes OSPF
syncer likes OSPF
jrandomhacker likes OSPF

The other important function is to let other people know what you are up to. VyOS 2.0 will automatically post information about new commits, image upgrades, and other events to Facebook and Twitter. You can also choose to send all log messages to your Twitter account. While there is no mechanism in place for this, in the future VyOS may be able to post screenshots of error messages to Instagram.

And, it's a while off, but maybe at some point you will be able to control your routers through posts in social network groups. We call this concept SDN (Socially Defined Networking). Stay tuned!

phabricator maintenance

Hi everyone,

phabricator migration to new VM is now complete, but it experiences performances problems because it's still re-importing all the repositories and, given there's a kernel fork there, it takes a long time. It's borderline usable now, but sometimes it fails to load its CSS on first attempt, and sometimes it just takes a long time to respond. Sorry for the inconvenience!

One repository import is complete, we'll need to do some more maintenance on the network at that site, but it's not going to take as long. Then this will hopefully be over and things will get back to normal.