Great! Thanks for improvement!

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.

@Viacheslav
Have you read my comment?
What do you think about it?

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?

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.

One of my router heavily affected by this issue, so if you will wrote a fix - you may ask me to test the fix.

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

@Viacheslav
First of all, thanks for the failover feature!
If you have enough time, please take a look at this bugreport.

I've just tested the "protocols failover" function in the 1.4-rolling-202311021324 - it works well!

Wow! Glad to see its moving on!

That would be great!

In T1237#146839, @Viacheslav wrote:

@Harliff Could you re-check?

Sorry, missed some messages.

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.

I can confirm this bug in rolling 1.3-2023-03-30.

I've not checked later versions. Maybe it was already fixed on 1.2.7 or 1.3/1.4 ?

In T2855#95665, @Viacheslav wrote:

I can't reproduce it in 1.2.7

Looks like it's a floating bug - I've just sucscessfuly disabled a vti interface on another router (running vyos 1.2.6-epa1).

Copy failed too.

I've made some hacks to get vyatta-config-sync working with ssh-keys (and working at all).

Just upgraded another router from 1.1.8 to 1.2.0-epa3 without this problem.

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...

I have tested it in the 1.2.0-rc11. The problem only present when there is no established SAs exists.

Gentlemen, you've forgot to add this fix to the changelog.