Varun Hegde

Hi @mnaiem81 , Would it be possible to share "show running-config" of problematic node and its one of the peer ? ( peer which has vpnv4 session with problematic node....

r1# show version FRRouting 10.3-dev-MyOwnFRRVersion-g7c1034087 (r1) on Linux(5.15.0-76-generic). Copyright 1996-2005 Kunihiro Ishiguro, et al. This is a git build of frr-10.3-dev-85-g7c1034087 Associated branch(es): local:master github/FRRouting/frr.git/master configured with: '--prefix=/usr' '--includedir=${prefix}/include' '--bindir=${prefix}/bin'...

Hey, We were able to write the topotest and find the solution. Will commit shortly Thanks Varun

======> cmd : show bfd peers json [ { "multihop":false, "peer":"2001:db8:1::1", "local":"2001:db8:1::2", "vrf":"default", "interface":"r2-eth0", "id":2411218638, "remote-id":38497228, "passive-mode":false, "log-session-changes":false, "status":"up", "uptime":4, "diagnostic":"ok", "remote-diagnostic":"ok", "type":"dynamic", "receive-interval":600, "transmit-interval":600, "echo-receive-interval":50, "echo-transmit-interval":0, "detect-multiplier":3, "remote-receive-interval":600, "remote-transmit-interval":600,...

> @varuntumbe are you still working on this? Hi @ton31337 , This solution is fundamentally wrong ( as I found out when one of the bfd topo test failed )....