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.
- Feed Queries
- All Stories
- Search
- Feed Search
- Transactions
- Transaction Logs
Jun 22 2019
Jun 18 2019
Jun 17 2019
Jun 16 2019
Jun 13 2019
Jun 12 2019
Jun 11 2019
Jun 10 2019
Jun 1 2019
May 26 2019
May 21 2019
May 20 2019
May 7 2019
May 3 2019
There are things that should be simply incorrect grammar, and this is one of them, as of me.
Apr 23 2019
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.
Apr 21 2019
Apr 20 2019
@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:
Apr 19 2019
Apr 16 2019
Apr 15 2019
Apr 14 2019
Apr 12 2019
Apr 11 2019
Apr 7 2019
Apr 6 2019
Mar 31 2019
Mar 27 2019
Mar 26 2019
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.