The easiest way is to add a Patch for FRR 7.5.1 if possible.
We can't migrate to FRR 9.1 for 1.3.x

I have tested. It works
Daemon does not crush.
There is information in local database.

show tech-support report was rewritten in PR 1961 and the last vestiges of the original was removed earlier in PR 2260. See T5137.

PR created: https://github.com/vyos/vyos-1x/pull/2326

Is there anything I can do to improve this PR? I also noticed that there is no more example commit-archive output since vyos 1.4:

@Viacheslav This doesn't seem to be related. This PR is merged to 1.5 instead of 1.4.

PR created (for current): https://github.com/vyos/vyos-build/pull/432

Could be a cause of this bug https://forum.vyos.io/t/igmp-proxy-not-working-in-1-4-since-around-7-sept

PR migration https://github.com/vyos/vyos-1x/pull/2325

Please revert that commit (remove that hook) and use the excludes-file instead.

@n.fort Ahh yes.. I'm sorry, thats embarassing now.. I've probably always overlooked it since it's before the "<Enter>" which I usually always expect as the first option (from other OSs aswell).. And probably because I'm used to the command being after the pipe aswell.. Still good to know now that the feature exists..

You mean this existing option, or I am missing something?

vyos@vyos-suri:~$ conf
[edit]
vyos@vyos-suri# set int eth eth0 description TEST
[edit]
vyos@vyos-suri# set serv ssh port 8877
[edit]
vyos@vyos-suri# set system host-name foo
[edit]
vyos@vyos-suri# compare 
[interfaces ethernet eth0]
+ description "TEST"
[service ssh]
+ port "8877"
[system]
- host-name "vyos-suri"
+ host-name "foo"

I suppose the maintainers already considered the below but I got a suggestion on how to resolve this issue:

Created https://vyos.dev/T5622 which must first be resolved before T5593 can get successfully merged.

PR updated for part 1/2 (vyatta-cfg-system): https://github.com/vyos/vyatta-cfg-system/pull/209

PR updated for part 2/2 (vyos-build): https://github.com/vyos/vyos-build/pull/427

This should fix the problem: https://github.com/vyos/vyos-build/pull/428

show-dhcp-leases.pl under vyatta-op remains the only extant deadweight Vyatta script and needs to be removed.

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

It seems this problem is not caused by IPsec, but it was caused by GRE implementation.

PR for sagitta:
https://github.com/vyos/vyos-1x/pull/2315

PR: https://github.com/vyos/vyos-1x/pull/2314

Add option protocol, PR https://github.com/vyos/vyos-1x/pull/2313

set policy local-route rule 100 destination '192.0.2.12'
set policy local-route rule 100 protocol 'tcp'
set policy local-route rule 100 set table '100'

Adding use outline from PR for future reference; the dir vyos-1x-current below refers to a local copy of the vyos-1x source:

PR created for part 1/2 (vyatta-cfg-system): https://github.com/vyos/vyatta-cfg-system/pull/209

Fixed

Build was successful and smoketests are currently in progress.

If build and smoketests are successful a commit will arrive later today.

... of course, feel free to experiment; I have not yet considered the proposed idea.

@Apachez note that those legacy image install scripts will be removed following
https://vyos.dev/T4516
Work on completing that is active this week and should be finished soon. You may want to hold off on this investigation until then.

Point 1 might be solved by using a hooks/live-script for the binary part which is the part after the chroot have been created.

PR created: https://github.com/vyos/vyos-build/pull/426

Turned out to be little of a challenge do "just" strip all binaries (and libraries, modules etc).

Also added flowtable as nothing needs to be sequenced in there either:
https://github.com/JeffWDH/vyos-1x/commit/ac22cc054d9c15af010c824ac9a05f5cc71fc954

I have not contributed code to this project before so let me know if I've missed conventions...

Just to be clear, the build I'm going from is just my own build of current to my own build of current -- it says 1.4 because I only changed the version string to 1.5 after this build went through since i'm the only one using my build :)

I just noticed that this still is a problem. Excerpt below from downloading an upgrade:

PR for 1.3 https://github.com/vyos/vyos-1x/pull/2310

In T5497#160905, @JeffWDH wrote:

1.5-rolling-202309250022

Is there a reason why some global options and some address groups (not all) are included in the output? Seems unintentional to me.

Is there a reason why some global options and some address groups (not all) are included in the output? Seems unintentional to me.

We have fwmark for policy local-route
But it is only for match mark and routing decision

vyos@vyos-lns# set policy local-route rule 100 
Possible completions:
+  destination          Destination address or prefix
   fwmark               Match fwmark value
   inbound-interface    Inbound Interface
 > set                  Packet modifications
+  source               Source address or prefix

Have to add Debian package "binutils" to make "strip" work within the chroot of livebuild.

This is an artifact of the remaining use in 1.3 of the legacy XorpConfigParser: the last use of that legacy piece was removed from 1.4 in Sep 2021, but is still called by 'vyatta_interface_rescan' in 1.3, so will be seen after changing MAC addresses if the config is not saved. A quick summary of the history is here and quoted below:

Implement hooks-script for livebuild that recursively go through following directories using "strip --strip-all" (syntax to be verified):

Shouldnt that be default for lb then in the vyos buildscripts and how does --debug affect things other than logging during build?

What is the "system update-check url" supposed to be once its implemented?