wiki.vyos.net now uses the new recaptcha (meaning: way easier to edit)

Hi everyone,

I like to joke about "wiki.vyos.net, a free encyclopedia no one bothers to edit", but there was a thing that actually made it rather inconvenient to edit for people, regardless of their willingness to edit it.

I mean the subnet captcha. If you haven't seen it, it made you calculate a broadcast address of a random subnet to register an account or edit a page. Everyone hated it, including me, and I had to add a number of active editors to a group that is exempt from it, by hand, so that it doesn't keep haunting them.

What's worse is that after a MediaWiki update it stopped working for a mysterious reason which I couldn't quickly debug, so I thought it may be a good time to reconsider it. Now there's the new reCAPTCHA instead, the one that wants you to click an "I'm not a robot" checkbox. For most users, it is trivial to solve, and it proved fairly effective at mitigating spam, so I think at least for now it may be the best solution for everyone.

Still, it's not entirely without controversy. There still may be accessibility converns and, since it's a third-party service, privacy concerns. If the captcha is giving you troubles, we still may make you exempt from it if you tell us your account and explain the issue.

If you, luckily for you, haven't seen the introduction of the subnet captcha, the story was that the wiki (a Vyatta wiki  back then, vyattawiki.net) had all its content replaced with spam overnight, and the original reCAPTCHA did nothing to protect it. We had been having spam problems for a long time by that moment, and after that event, we thought we have to come up with something that will stop spam forever, and so I wrote the subnet captcha plugin, and it worked very well. Except making edits inconvenient for legitimate users of course. Now when it's gone, I hope we'll be getting more editors.

I hope more people will come and edit some pages. We are seriously lacking in the documentation department, but if everyone does a small bit, it's not really that hard. You don't need to write big chunks at once and document complete features, a brief description and a config example is a lot better than nothing.

vyos.net → wiki.vyos.net redirect

You may have noticed (or will notice soon) that http://vyos.net redirects to http://wiki.vyos.net. Don't worry, this is normal.

It's the first step in preparation to roll out the new website. When it goes live, the vyos.net and vyos.io domains will point to the new website, and the wiki will live on its own wiki.vyos.(net|io) domain.

Meanwhile you can view the future website at http://vyos.io/ and give us your feedback, if you haven't already.


dead.vyos.net and contributing to VyOS

Hi everyone,

This is a bit embarassing. For almost a day http://www.vyos.net (but not http://vyos.net) was sending people to the http://dead.vyos.net website, until someone on the IRC pointed it out (thanks for this!).

It happened due to an oddity in the way Apache HTTPD handles host aliases, and it's fixed now.

The dead.vyos.net website was created as a joke for giving the link to people who ask if VyOS project is dead. While the website is indeed a joke, the issue with lack of contributors is very real, and it does slow things down.

If you want to contribute to VyOS, there is a lot of work to be done, and the maintainers on the IRC and in phabricator will be happy to point you to beginner-friendly tasks and answer questions about the code and the patch submission process.


VyOS Project news

Hello, Community!

We have some great news to share! 

As some of you may already know, we are planning to run virtual meeting event for VyOS devs and users in near future.

So in case you want to participate, just fill up this form and of course join us on our dev. portal to stay in touch.

May admit that this summer is productive in all aspects:

Tremendous work towards VyOS 1.2 done and we going to present 1.2.0 beta 2 in some weeks! Thanks, to our super team!

We revived OVA distribution of VyOS some months ago and continued work in the direction of extensive VMWare Platform support; we also plan to deliver supported images for all other standard hypervisors like KVM, MS Hyper-V and VyOS on clouds markets for AWS, Azure, GCE.

VyOS is now available on SolidRun ClearFog device, credits for this great work to UnicronNL, this opens new applications for VyOS.

Ansible starting from version 2.2 able to configure VyOS, so if you using Ansible, give it a try! We on other hand working on standalone management library for Python.

We receive many requests regarding GUI, and yes we are listening to them. Last four months we dedicated a lot of time to studies regarding possible ways of delivery such  UI. Apart from technical challenges, there are other problems to take into account(like service providers don't want GUI, while SMBs and ROBOs show high demand). We are working to bring satisfaction to all users without sacrifices from any side. So basically yes, it will be GUI in near future, but there are not ETAs for now.  

We believe that affordable open source routing platform and NFV should be accessible to everyone out there

Want to participate???

Join us on social networks and spread the word about VyOS - Twitter, Reddit, FaceBook, Google+, Linkedin 

Participate in discussions on forum and of course join us on development portal 

VyOS is a community-driven Linux-based network operating system for routers and firewalls

Saludos,

Yuriy

Commercial support and professional services for VyOS

From earlier posts, you may remember Sentrium S.L., an IT consulting company founded by one of the VyOS maintainers and two long time VyOS users and community members.
In this post I (Daniil Baturin, that is) speak as a Sentrium founder, so "we" refers to all Sentrium employees, not to all VyOS maintainers as usual.

Now Sentrium is ready to offer commercial support and professional services for VyOS.

We plan to use funds towards VyOS project in various ways, including hiring people for both short-term/long-term tasks like bugfix and feature implementation, documentation improvements, VyOS events, building VyOS testing labs available for all contributors, development of training and certification programs and much more

Small businesses, educational institutions, and nonprofits may be eligible for discounts (subject to review, please contact us for details).

If you are interested, drop us an email to sales@sentrium.io or visit our website (http://www.sentrium.io/).

Commercial support

We offer two types of support plans at a fixed price:

  • Basic: email support only, response within two business days, 1500 eur/year
  • Standard: email support only, response within one business day, 5000 eur/year
To clarify it: it’s not 1500 or 5000 for each router, it’s for the entire company (single legal entity) no matter how many routers it uses.

VyOS support includes answering questions that you may have about VyOS, its installation and upgrade process, features and their usage and so on. We also can review customer network diagrams and config files and suggest what features and protocols to use and what changes can be made to optimize performance and scalability.

If you find any bugs or have any feature requests, we will help you figure out the details and reproducing procedure (in case of a bug) and communicate it to VyOS developers. We also offer external monitoring and emergency security notifications as part of support plans.

Custom support plans with different terms, such as included phone support, shorter response times or 24/7 support, hands-on assistance, etc. are also available since everyone's needs are different, and it's hard to devise a one size fits all solution, the cost is negotiated on case by case basis.

Professional Services

Professional services include VyOS installation, upgrade, migration from competing platforms, configuration according to requirements, troubleshooting and so on.

The base rate is 200 eur/hour, though depending on the complexity of the task and environment it may be lower or higher.

UPD:
updated offering published here

Servers maintenance: phabricator and jessie build host

Hi everyone,

I bet you are all tired of this stuff already, but then again, so we are. We ourselves hope it's the last big maintenance we get to do at that site and then everything will stay stable for a while.

We are moving all VMs to new servers with more optimal hardware configuration and optimizing some configs. Among the VMs that will go down, likely for a few hours, are phabricator and jessie build host.

Things should get back to normal once we are done, we'll make another post when it's complete.