- User Since
- Nov 2 2017, 5:03 PM (220 w, 2 d)
May 4 2020
Another affected by this! Several devices with more than 20K config lines cause our automation scripts to take really really long to complete, and also the devices take much time to boot.
It would be great having this fixed in 1.3 :-)
Mar 4 2020
Hi @rps ,
Very good summary of what is needed. I think what you state fits perfectly in our (and most) uses cases. We need to sync RAs with VRRP state, and we would need to use a "virtual IP" like fe80::1 to be announced to neighbors as the default gateway.
So for me makes absolutely sense, thanks for your effort!
If you need any help defining/testing, just let me know!
Jun 27 2019
I have upgraded a couple of clusters to 1.2.0-rolling+201906240337 and systems started successfully, and I also applied the hotfix indicated in thel pull request (https://github.com/vyos/vyatta-cfg-system/pull/102/files) to several productive clusters by just adding "/interfaces" to $VYATTACFG variable with the same successful results, so I can confirm that the fix provided by @mtudosoiu works great.
May 29 2019
I agree with @aibanez
In addition, sometimes it works (but only a very few) while almost always it crashes at startup and interfaces are messed.
Do you guys have any clue/suggestion or any other further test that can be done?
May 24 2019
May 22 2019
May 21 2019
Apr 25 2019
Now it seems to report guest info succesfully:
Tested in 1.2.0-rolling+201904250337, everything looks great now, no warnings arise and required config is in place, so I'll wait for 1.2.2 to get the fixed version of ethtool.
Thanks for your efforts, great work!
Apr 16 2019
Thanks @rherold! Good to know that radvd already supports link-local IPv6 selection!
Apr 11 2019
Apr 8 2019
Jun 1 2018
I also agree that option 2 seems cleaner. We'll have to deal with migrations, but the result is worthwhile.