Its IKEv3, correct. Loglevel increased

@syncer why remove 1.2? Bug should be fixed in 1.2.x bugfix releases

Protocol rewrite is more then overdue now ... :)

tagNode has been renamed to dnssl

Problem was in the wrong IKEv2 definition, set vpn ipsec ike-group IKE-AZURE ikev2-reauth must be yes

disable-connected option on a neighbour would work, too.

That subsystem has now been completely rewritten and certain things are skipped if underlaying hardware is virtio or vmxnet.

Please provide real commands, else we can not reproduce the issue. Can you try it on a second installation?

DNS forwarding was last changed back in August by commit https://github.com/vyos/vyos-1x/commit/fdae741be5ffaa3719ce889d0342c3091ad3c92c

I can not reproduce this issue. I just upgraded to the specified version.

Please share commands to reproduce this. We do kot hve a 1.2.3 rolling version.

SNMP community should stay. If it should be removed it can be handled via dedicates task

backported 20822ca3 to crux

I pick this up as I did the rewrite of this whole stuff

@Viacheslav thank you for testing!

https://github.com/vyos/vyos-1x/pull/178

Wha cant the change which adds the completion helper be backported? Git best practice is you should group changes per commit. But in this commit you add the completion helper and also other regexes (BAD!)

Thanks

Can this please be splittet in a host and a port node? Only WireGuard uses this notation all other services have a desicated port node

Personally I would keep it under the interface itself but @dmbaturin should have the final decission

If FRR has all we need we should use it - drops one additional dependency

I just have a gut feeling its better suited under the interface instead of a dedicated service. For FRR, have a look into the BFD implementation

• What other nodes will be unter the prefix tagNode?
• How would namesevrers be configured?

On the other hand it still can live in the interface directly which would spare the migrator. VLANs are a good example - I‘ve written a common function to parse it in each interface. I am not fully convinced on any implementation be it under an interface or as dedicated service.

That is definately much better then before.

Works as expected. Now I can use VyOS 1.3 on my PPPoE link(s)