User Details
- User Since
- Jun 20 2017, 10:16 PM (376 w, 4 d)
Fri, Aug 9
Great! Thanks for improvement!
Jul 25 2024
I've got similar issue when I've upgraded 1.3.8 to 1.4.0: none of user can log in into system, resetting password via boot menu wont helped.
@lbv2rus Can you re-test it on VyOS 1.4?
I've just testd 40+ policies (with 40+ dedicated routing tables) on VyOS 1.4 - everything works fine.
Jul 23 2024
@Viacheslav
Have you read my comment?
What do you think about it?
Jul 17 2024
There is another approach to improve the config-sync: a "replace" option
About config-sync: maybe add option to exclude some patterns from config sync?
Jun 18 2024
Note for myself:
Logs from VM:
I've modified the protocol ospf settings to check if it will affect static routing or not.
The static routing are not affected (still no route to 0.0.0.0/0):
Hi!
Recently I've note that this bug is not affects only protocol failover, but also protocol static routers.
May 6 2024
Apr 28 2024
Feb 5 2024
One of my router heavily affected by this issue, so if you will wrote a fix - you may ask me to test the fix.
Jan 24 2024
I've made mistake while configuring my test stand so the WLB in my GNS3 was affected by contrack on host machine.
Looks like the WLB works as it should.
Sorry to bother you!
Found task named wan load balance issues with 3 or more WANs.
BTW, do you have any plans to use this mechanism for WAN failover?
Could you explain or send some examples?
Is it OK to discuss such topics here?
BTW, do you have any plans to use this mechanism for WAN failover?
Could you check it? Available in the latest rolling release
Dec 21 2023
@Viacheslav
First of all, thanks for the failover feature!
If you have enough time, please take a look at this bugreport.
Dec 8 2023
I've just tested the "protocols failover" function in the 1.4-rolling-202311021324 - it works well!
Jun 14 2023
Wow! Glad to see its moving on!
Apr 18 2023
That would be great!
Sorry, missed some messages.
Apr 4 2023
Is it possible to implement multiple test targets instead of just one?
Bug: unable to rename a failover route:
@Viacheslav Ok!
@Viacheslav, where is best place to discuss the feature (ask a question or report a bug)?
Nice feature. I'm testing it now.
Apr 2 2023
I can confirm this bug in rolling 1.3-2023-03-30.
Jun 23 2021
I've not checked later versions. Maybe it was already fixed on 1.2.7 or 1.3/1.4 ?
Jun 9 2021
Sep 3 2020
Looks like it's a floating bug - I've just sucscessfuly disabled a vti interface on another router (running vyos 1.2.6-epa1).
Jan 15 2020
Copy failed too.
Aug 29 2019
Aug 15 2019
Aug 13 2019
I've made some hacks to get vyatta-config-sync working with ssh-keys (and working at all).
Jan 25 2019
Just upgraded another router from 1.1.8 to 1.2.0-epa3 without this problem.
Jan 24 2019
Hmm... The config contains only one user - for which one I've reseted password. The user 'vyos' is completely missing!
Resetting password right now... Done, access granted!
It was lucky that I have access to console at this time...
Dec 25 2018
I have tested it in the 1.2.0-rc11. The problem only present when there is no established SAs exists.
Dec 17 2018
Nov 16 2018
Nov 11 2018
May 27 2018
Mar 1 2018
Nov 19 2017
Gentlemen, you've forgot to add this fix to the changelog.