Many thanks. I think it was actually fixed earlier than 1.3.7 - I've been using VRF to allow SSH access only from a separate private management network, on a router that routes only public IP addresses (BGP, OSPF, PPPoE) otherwise, since about 1.3.5 or so.

Thanks for the comment! I'm responding on the github page so we aren't in two places at once.

As already commented in the PR itself:

Hard agree with the points Apachez made above, the packages should be added. I tried adding the packages to vyos-1x/debian/control and vyos-build/data/live-build-config/archives/trixie.list.chroot + vyos-build/data/live-build-config/archives/trixie.pref.chroot without any luck. Perhaps it was an issue with my docker setup or something similarly silly (I am very new to VyOS) but I am not sure how to add these packages. Any ideas?

PR here https://github.com/vyos/vyos-build/pull/614

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

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

@dmbaturin, I propose removal of upnp stuff from 1.5 and 1.4

(commenting as the root cause of this issue ;) While one could argue that you could configure the other FRR not to use multi-topology, some devices might use IS-IS multi-topology as the default setting, so it would be nice to have it tunable.

The original feature/bug is solved
The stop script executed is executing.
The locks are a separate task/bug.

I changed the stop script to this:

#!/bin/vbash

Any update on this PR? (thanks for the work put into this!!)

Since some of the required children are other node or tagnode types I belive it would be better to change the schema to the following:

Checking a recent 1.5 build (1.5-rolling-202405090225), I do not see the discrepancy mentioned in the description: the result for 1.5 is also (just) missing vif entries, and one can observe that the syntax error in vif 2 causes cascading syntax errors in the other vif sections.
The following script recreates the effect of the XorpConfigParser:

This PR merged. Closing the issue

https://github.com/vyos/vyos-build/pull/612

Merged, closing the issue

Migration requires the config file to be in the standard syntax, such as produced by the system itself (set/del; commit; save) --- in this case, a configuration that can be loaded and saved on VyOS 1.3.5 would not be missing braces as above. If one needs to hand edit a config file, at the very least one needs to load/save on the source system before migration. The only weird corner case, linked above, is when a change of mac address triggers a rewrite by the ealry-legacy parser (only used in <= 1.3.x, and only in one remaining place in 1.3.x: vyatta_interface_rescan) --- that does produce incorrect syntax and is a known problem as described in the comment in T5611; that case is also restored by saving the config on the source image before system update and the resulting migration on reboot.