It seems to be a bug in the FRR that delete isisd configuration completely

router isis VyOS
 net 49.0001.1920.0200.0011.00
 lsp-mtu 1460
 redistribute ipv4 connected level-2
!
!
interface eth1
 ip router isis VyOS
 ipv6 router isis VyOS
!
interface tun0
 ip router isis VyOS
 ipv6 router isis VyOS
!

check

r1# conf t
r1(config)# router isis VyOS
r1(config-router)#  net 49.0001.1920.0200.0011.00
r1(config-router)#  lsp-mtu 1460
r1(config-router)#  redistribute ipv4 connected level-2
r1(config-router)# !
r1(config-router)# !
r1(config-router)# interface eth1
r1(config-if)#  ip router isis VyOS
r1(config-if)#  ipv6 router isis VyOS
r1(config-if)# !
r1(config-if)# interface tun0
r1(config-if)#  ip router isis VyOS
vtysh: error reading from isisd: Success (0)Warning: closing connection to isisd because of an I/O error!
r1(config-if)#  ipv6 router isis VyOS
Warning: connecting to isisd...failed!
isisd is not running
r1(config-if)# !
r1(config-if)# end
Warning: connecting to isisd...failed!
r1# 
r1#

OK, I will.

Did you try to start this service in VRF?

Create please a PR if it works for you.

++

++

++

I've tested this flag in both version 1.4 / 1.5 , it seems to work as expected :

Make sure conntrack-sync works with active-active HA configuration with BGP environment & IPv6

Command show zone-policy is no longer available in 1.4, and neither in 1.5
I'm closing this task.

tested on 1.4-rolling-202311080309

I'm marking this one as resolved since ZBF was already re-introduced.

Can we mark this one as resolved for 1.5? Seems it wasn't back-ported yet to Saggita @sdev

Verified with VyOS 1.5-rolling-202311081451.

submitted PR: https://github.com/vyos/vyatta-op-vpn/pull/37

@c-po It seems you only implement the "type bridge_slave neigh_suppress on"
And "type bridge_slave learning on" is not implemented in this PR.
Will you add this also?
Thank you

set protocols static neighbor-proxy arp 192.0.2.1 interface eth1

check

vyos@r4# sudo ip nei show proxy
192.0.2.1 dev eth1 proxy 
[edit]
vyos@r4#

It looks like maybe there’s just some op mode command changes.

According to firewall-version.xml.i, the firewall config version was not updated to 12. Was this intentional?

@Viacheslav My addition of the onlink option is really brute-force, applied blindly to everything just to see if that was a solution and give you more information. I do not think my "fix" is really ready for a PR.

@giuavo I didn't test "default route", only regular routes for some prefixes, and it worked.
Could you create a PR?

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

Tested in 1.3. Everything works

Tested in 1.5

Backport to 1.4 https://github.com/vyos/vyos-1x/pull/2449