This hasn't been possible because it links to vyconf, which makes a UNIX cultural assumption. However, I'm moving the tree handling modules and the parsers into a reusable library that can be used by both vyconf and libvyosconfig, and custom applications as well. Then it should be possible.

I think it may be a good idea.

Builds work again.

I'm not sure if I can think of a situation when a master script can be used without a backup/fault script, but I suppose it's a fair point.
We likely want to save the state on every transition.

The application got rejected.

The ISO builds has been fixed, then broken again recently, then fixed again... :)
If anyone runs into a broken build, please reopen.

The wiki, sadly, was so hard to protect from spam that it became nearly impossible to edit for humans indeed.
I've updated the banner to tell people about migration to readthedocs and the github repository everyone is now welcome to contribute to.

There are things that should be simply incorrect grammar, and this is one of them, as of me.

The usual procedure is to create a route-map that sets the nexthop to a blackholed address if the advertisment has a specific community string set.
So when a customer advertises an address (rather a /32 network) to you with that string set, it automatically ends up blackholed.

@spectre3500 Now that I think of it, did you build it with build-ami or the AWS target of the vyos-build scripts?

...oh, and remove "disable-password-authentication" from the SSH settings of course.

I wonder if this issue will ever stop re-occuring. Every time it happens, it's for some new reason. I think this time it may be related to ongoing work of @Unicron.

Related task: T1334

Here's a commented reference config from Vyatta 6.5 for testing:

Curiously, I can't reproduce it in the latest rolling, even though the code hasn't changed. We need to test in latest crux builds.

The packages were out of sync with reality for some time. Should be fine now.

The packages were out of sync with reality, it should work as expected now.

@tomjepp Could you share the patch or tell us what and where you had to modify?

@danhusan IPv6 should not be affected. Workaround for IPv4:

@primoz Adding staticd to the daemons config fixes the issue reproducibly on affected systems, even after reboot?

@jmlccdmd Ok, I'll re-test with in/out then.

Since this is a trivial cosmetic issue, we are about to freeze 1.2.0, and the installer is due for a rework in 1.3.0, I'm going to ignore this for now.

Works for me in the latest build.

vyos@vyos-test-2# set protocols static route6 ::/0 blackhole distance 10
[edit]
vyos@vyos-test-2# commit
[edit]
vyos@vyos-test-2# run show ipv6 route ::/0
Routing entry for ::/0
  Known via "static", distance 10, metric 0, best
  Last update 00:00:10 ago
  * unreachable (blackhole)