VyOS Networks Blog

Building an open source network OS for the people, together.

1.1.0 release

Daniil Baturin
Posted 10 Oct, 2014

1.1.0 release is now available for download from http://packages.vyos.net/iso/release/1.1.0/, and from the mirrors once they sync.

Detailed information about this release can be found in release notes.

Release highlights include:

  • Unmanaged L2TPv3
  • Dummy interfaces (functionally identical to multiple loopbacks in IOS)
  • 802.1ad QinQ
  • Event handler that executes something when it finds a pattern in logs or command output.
  • IGMP proxy (pulled from EdgeOS)
  • | commands conf mode filter that converts config output to set commands.
  • | strip-private filter that removes private information from the config for pasting and the like.
  • Ability to administratively disable PPPoE sessions.
  • Ability to specify required authentication protocol for remote access VPN.
  • Ability to reject OpenVPN clients for which no explicit configuration exists.
  • Configurable ARP filter settings.
  • Persistent tunnel (–persist-tun) option for OpenVPN.
  • TWA hazards protection settings.
  • Configurable Ctrl-Alt-Del behaviour.
  • Per-interface IP source validation settings.
  • Initial MOBIKE and IKEv2 support.
  • IPv6 RA DNS option.
  • …and more.

There are also experimental features that were contributed late in the release cycle and weren’t tested thoroughly. Feel free to try them and report any bugs you find. They include:


Even though the release is still based on Debian Squeeze, a number of packages were upgraded. The biggest improvement is 3.13 kernel, with lots of new features and new drivers.

Upgrade notes

Both legacy VC setups and VyOS installations can be upgraded the usual way, with “add system image”. AWS instances can be upgraded that way too.

Known issues

  • The bug in clustering that makes it fail to start after boot is not fixed. The workaround is to restart it manually.
  • The bug with recursive routes via addresses not on the same subnet is not fixed. This affects customers of companies like OVH, online.net and some others that issue /32 addressses to customers. The workaround is to create a route to the gateway manually with sudo ip route add x.x.x.x/32 dev ethX, you can put it in /config/scripts/vyatta-postconfig-bootup.script to make it permanent.
  • In newer kernels, if an interface has IPv6 addresses, they are permanently removed when it goes down. We made a workaround for it, a simple daemon that watches interface status, looks up IPv6 addresses in the config and adds them back, but this is prone to race conidions. I did my best at testing it, but if you spot any problems, please report.
  • Credits

    Thanks to everyone who contributed and made this possible, including Kim Hagen, Alex Harpin, Yuya Kusakabe, Patrick van Staveren, Toni Cunyat , Ewald van Geffen, Hiroyuki Sato, Ryan Riske, Jeff Leung, Paul Gear, Abdelouahed Haitoute, ftoyama, hydrajump, Ralf Ertzinger, Ivan Malyarchuk, Paweł Pierścionek, neutralrockets and Shane Short.


    Also, VyOS turns 1 today. A year ago on this day we forked the VC code on github (which took a whole day, if you ask me!).

The post categories: