Early Production Access
Sun, Feb 2
Ability to use Local PBR ref T439
Jun 16 2019
VyOS 1.2.1 ships PowerDNS 4.1.12
vyos 1.2.0-rolling+201906161308 has pdns_recursor 4.1.14, should this be marked as fixed?
Mar 3 2019
Sorry found it.
Feb 26 2019
Would it be possible to add an option to bind an specific interface to an routing table?
I have tested the scenario above and create only the routing table via protocol static.
After this I manual add:
Feb 24 2019
I added a log rule to:
why do we use fwmark in this case? As far as I can see ip rule give us all needed selectors:
Jan 21 2019
Jan 12 2019
Jan 11 2019
@syncer thats not true:
it can be some other issue though
will appreciate if it's possible to get procedure how to reproduce and we happy to work with frr devs to address that
VyOS is not affected by this issue
as it requires FRR build with certain options which we not use
The FRR devs have released binary packages including the fix and announced it on the FRR mailing lists. After considering the feedback on the list and discussing with FRR devs, we will postpone the experiments until Jan. 23rd, and have updated the schedule to reflect the delayed start and shorter timeline [A]. We will follow up with FRR devs and mailing lists/users.
Jan 10 2019
Jan 8 2019
Please unbreak now. The next test date was announced!!
We plan to resume the experiments January 16th (next Wednesday), and have updated the experiment schedule [A] accordingly. As always, we welcome your feedback.
Wow, this explains why all my sessions dropped yesterday.
Jan 6 2019
Jan 5 2019
Jan 4 2019
Thx for the feedback indeed it runs much better with the virtio-net driver. Bit the e1000 is the default if you choose Debian as OS in Virtualbox.
VyOS is not available in Virtualbox as OS Template. I think we should try to get an own template with nice defaults into Virtualbox. Should I open a case
in Virtualbox for it? Do we have a list of settings that would be optimal for an VyOS vm?
Jan 3 2019
Hi @rherold , these messages are verbose debug messages, change to virtio-net or to a different emulated driver to have them disappear. In general I recommend to use the virtio one which has a better performance too compared to emulated ones, plus less complex code. (https://github.com/MorteNoir1/virtualbox_e1000_0day)
Jan 1 2019
Dec 31 2018
I propose to proceed with a global change. Special case handling is always harder to test and the impact is only 5 seconds max in startup time - who cares on a 24/7 active device which is rarely rebootet?
instead of differentiating between raid and non raid installations - why not always wait 5 seconds for the discs to settle? As this is only done once on startup this is IMHO better then a special case.
I've added SNMP restart on hostname change, it will be in the next nightly build.
Hey @Merijn, sorry for late reply and thanks for the patch! I've merged it in and it will be in the next nightly build.
I've changed it to handle the situation gracefully. Actual display of connecting SAs is another story of course... The fix will be in the next nightly build.
Dec 30 2018
tested with most recent rolling version. problem still persists but it's not throwing errors.
Dec 29 2018
Thanks for testing that guys.
Dec 28 2018
And FYI max-ipv6-routes=10 and max-ipv4-routes=10 doesn't seem to help either.
@MrXermon , yes that sounds reasonable. I found in the code that they limit it to 100 routes, can you please try the following:
i played with different values and in my case (full table IPv6 router) the error continues during the following values:
3s, 5s, 10s, 20s, 30s
At 60s the CPU load starts to cycle between >30s full load, than it drops for a few seconds and raises again.