PR392 was merged in VyOS 1.4-rolling-202309070021.

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

PR for Sagitta (draft until dependency PR 2207 is merged to Sagitta):
https://github.com/vyos/vyos-1x/pull/2215

Sounds great @jestabro I'm happy to assist in any way possible

In case there are other just like me who didnt know about "action continue":

Something else to consider is to increase the readcache of squashfs by changing this:

Looking at the kernel configs from both arm and x86 arch:

So what needs to be done is to copy that block and make a separate question regarding:

According to https://github.com/vyos/vyos-1x/blob/current/src/init/vyos-router it should be named:

@anthr76 T5520 would be unrelated to an upgrade from 1.4-rolling-202212310809, as the change to using Bookworm did not occur until 2023. We can take a look at the specific errors that you encountered.

There is a similar case going on at the forum with different workarounds which might help?

@sdev take a look over these repository :

The steps above i can try as a last ditch effort but that means I need to be on site with the device and will require lots of time (and downtime)

I have two scripts
Is it ok?

vyos@r14:~$ sudo ls -la /config/scripts/vyos-postconfig-boot*
-rwxrwxr-x 1 root vyattacfg 413 Sep  6 15:04 /config/scripts/vyos-postconfig-boot.script
-rwxrwxr-x 1 root vyattacfg 230 Jun 27 06:17 /config/scripts/vyos-postconfig-bootup.script
vyos@r14:~$

@Viacheslav Sure. I am on VyOS 1.4-rolling-202309040919 and the issue is fixed. Config gets build correctly

@Niklasthegeek Could you re-check and close it if it was fixed?

@

I think that would be a bad idea comparing to other vendors where you can select if you want to do IPv4 routing and/or IPv6 routing. If both are disabled the device will only do switching/bridging.

Related task T2133
I guess we should drop this option ipv6 disable-forwarding

Ehm, are you sure you operate on the correct config?

Firewall can be turned off. It does not affect the result.

In T5521#158836, @c-po wrote:

Please re-test with latest rolling-release if the issue persists.

A workaround was provided in T5428 for the specific issue.

Cannot pass smoketest for virtual-server which also uses vrrp

PR for current:
https://github.com/vyos/vyos-1x/pull/2211

Now I'm using this build: VyOS 1.4-rolling-202301071830
It's working fine as with active as with passive FTP.

@svd135 Can you provide a version string when you last had it working? Seeing the firewall config might also be helpful.

Please re-test with latest rolling-release if the issue persists.

Thanks for the help so far @Apachez !

My apologies @Apachez this was on 1.4-rolling-202212310809.

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

PR for Sagitta:
https://github.com/vyos/vyos-1x/pull/2207

Well in that case it boils down to if the FRR/vrrpd supports namespaces, various tracking (interface etc) aswell as multicast vs unicast which keepalived seems to support them all.

@dmbaturin Can we close it?

@mhamzahkhan Will be fixed in the next rolling release, could you re-check it?

In T2444#158779, @Apachez wrote:

If the FRR/vrrpd is good enough then the main benefit is that the FRR/vrrpd is already included so no need to also include and use keepalived (unnecessary files and binaries and dependencies).

Things to verify however before a switch is performed (and keepalived is thrown out) is support for vrf/namespaces, various interface and other tracking and multicast vs unicast (it seems that keepalived supports them all - dunno about FRR/vrrpd).

https://docs.frrouting.org/en/latest/vrrp.html

One can enable snmp module through:

I will put this as resolved under protest :-)

To check if it works just use ss -tin, for example:

vyos@r14:~$ ss -tin
State                    Recv-Q                    Send-Q                                        Local Address:Port                                        Peer Address:Port                     Process                                                                                                                                                                                          
ESTAB                    0                         0                                            192.168.122.14:22                                         192.168.122.1:45446                    
	 bbr wscale:7,7 rto:201 rtt:0.103/0.048 ato:40 mss:1448 pmtu:1500 rcvmss:1448 advmss:1448 cwnd:140 ssthresh:138 bytes_sent:126383 bytes_acked:126383 bytes_received:20969 segs_out:2460 segs_in:2592 data_segs_out:2445 data_segs_in:341 bbr:(bw:503652048bps,mrtt:0.018,pacing_gain:1.25,cwnd_gain:2) send 15745242718bps lastsnd:3003449 lastrcv:3005252 lastack:3003448 pacing_rate 623269416bps delivery_rate 503652168bps delivered:2446 app_limited busy:2029ms rcv_space:14600 rcv_ssthresh:64076 minrtt:0.018 snd_wnd:64128
ESTAB                    0                         36                                           192.168.122.14:22                                         192.168.122.1:51320                    
	 bbr wscale:7,7 rto:201 rtt:0.427/0.555 ato:40 mss:1448 pmtu:1500 rcvmss:1448 advmss:1448 cwnd:148 ssthresh:136 bytes_sent:1779503 bytes_retrans:68 bytes_acked:1779399 bytes_received:167865 segs_out:12061 segs_in:12088 data_segs_out:11899 data_segs_in:3996 bbr:(bw:530564808bps,mrtt:0.068,pacing_gain:1.25,cwnd_gain:2) send 4015063232bps lastsnd:30 lastrcv:31 lastack:31 pacing_rate 525259160bps delivery_rate 458772272bps delivered:11899 app_limited busy:27667ms unacked:1 retrans:0/1 dsack_dups:1 rcv_rtt:392993 rcv_space:65229 rcv_ssthresh:84348 minrtt:0.024 snd_wnd:1344128
vyos@r14:~$

It should be disabled by default for all daemons. I guess it will be implemented in T4020
For your issue solution is set system frr snmp ldpd.

I dont know if something would break to run migrate from within another VyOS version but you could test something like this, preferly from last version that worked without errors ("5: 1.4-rolling-202306030305"?):