I apologize if this is the incorrect place. Running 1.5-rolling-202412160007 in a qemu/kvm, and it appears to be missing the qemu guest agent ( qemu-guest-agent.service -> /usr/sbin/qemu-ga ).

I'm still seeing this in VyOS 1.3-rolling-202004170117

We took other steps that allows us to take the image back to a manageable size, and this task lost its immediate relevance.

This is confusing. While NTP used to work (listen on all interfaces) without any listen-address set, now it doesn't. This means any old config without listen-address set will now have a non-working NTP without any warning. There was no migration script to migrate the old behavior to the new. ntp should have a mandatory listen-address if this new behavior is kept.

Do you know what the outcome of this old task was?

While "interface ignore wildcard" configured, we got:

ntpq -c lpeer
 remote           refid      st t when poll reach   delay   offset  jitter
==============================================================================
 10.255.0.1      .INIT.          16 u    -   64    0    0.000    0.000   0.000

You are absolutely right. Was a stressful morning sorting this out, thanks for the response.

@LBegnaud if I read the source correct the command set vpn ipsec options disable-route-autoinstall is what you are looking for, it was implemented in T71.

Yes definitely just ran into this myself. I think i had the opposite problem of OP. I have only ipsec VTI on the router, but whenever a reset vpn ipsec-peer command was run, the peer IP was being added as default route for table 220. Furthermore, this was being respected as the default route for the system (I'm not sure how route priority works with tables, but i'm guessing table 220 has preference over table main?)

@dmbaturin ok, will address that in the next rewrite

@alkersan Looks good, thanks!

A pair of PRs were made in vyos-1x and vyatta-op.
Thought they would get linked to this task by phabricator automatically, but that didn't happen.

@dmbaturin is there any reason the IPv6 peer-group is under address-family ipv6-unicast and the IPv4 peer-group is not? Seems this one was missed during migration?

@syncer @dmbaturin - I'm experiencing this on upgrade from 1.1.8 to 1.2.1, is this expected behaviour that you have to chown it?