Port Fix from FRR community for issue https://github.com/FRRouting/frr/issues/18493 in sonic-frr(FRR 10.0.1)

[sudhanshukumar22]

Why I did it

The fix from FRR (FRRouting/frr#18493) is taken as a patch in sonic(FRR 10.0.1).

Work item tracking

• Microsoft ADO (number only):

How I did it

How to verify it

Which release branch to backport (provide reason below if selected)

• 201811
• 201911
• 202006
• 202012
• 202106
• 202111
• 202205
• 202211
• 202305

Tested branch (Please provide the tested image version)

Description for the changelog

Link to config_db schema for YANG module changes

A picture of a cute animal (not mandatory but encouraged)

[mssonicbld]

/azp run Azure.sonic-buildimage

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[mssonicbld]

/azp run Azure.sonic-buildimage

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[StormLiangMS]

hi @sudhanshukumar22, do you have this patch tested?

[sudhanshukumar22]

Before the fix:
root@sonic:~# vtysh

Hello, this is FRRouting (version 10.0.1).
Copyright 1996-2005 Kunihiro Ishiguro, et al.

2025/03/30 06:08:39 [YDG3W-JND95] FD Limit set: 1048576 is stupidly large. Is this what you intended? Consider using --limit-fds also limiting size to 100000
sonic# config t
sonic(config)# ip prefix-list PL_LoopbackV4 permit 10.1.0.32/32
sonic(config)# ip prefix-list PL_LoopbackV4 permit 10.1.0.32/32
sonic(config)# ip prefix-list PL_LoopbackV4 permit 10.1.0.32/32
sonic(config)# ip prefix-list PL_LoopbackV4 permit 10.1.0.32/32
sonic(config)# do show running-config
Building configuration...

Current configuration:
!
frr version 10.0.1
frr defaults traditional
hostname sonic
log syslog informational
log facility local4
fpm address 127.0.0.1
no fpm use-next-hop-groups
agentx
no service integrated-vtysh-config
!
ip prefix-list PL_LoopbackV4 seq 5 permit 10.1.0.1/32
ip prefix-list PL_LoopbackV4 seq 10 permit 10.1.0.32/32
ip prefix-list PL_LoopbackV4 seq 15 permit 10.1.0.32/32
ip prefix-list PL_LoopbackV4 seq 20 permit 10.1.0.32/32
ip prefix-list PL_LoopbackV4 seq 25 permit 10.1.0.32/32
ip prefix-list DEFAULT_IPV4 seq 5 permit 0.0.0.0/0

After the fix:
sonic(config)# ip prefix-list PL_LoopbackV4 permit 10.1.0.32/32
sonic(config)# ip prefix-list PL_LoopbackV4 permit 10.1.0.32/32
sonic(config)# ip prefix-list PL_LoopbackV4 permit 10.1.0.32/32
sonic(config)# do show running-config
Building configuration...

Current configuration:
!
frr version 10.0.1
frr defaults traditional
hostname sonic
log syslog informational
log facility local4
zebra nexthop-group keep 1
fpm address 127.0.0.1
no fpm use-next-hop-groups
agentx
no service integrated-vtysh-config
!
ip prefix-list DEFAULT_IPV4 seq 5 permit 0.0.0.0/0
ip prefix-list PL_LoopbackV4 seq 5 permit 10.1.0.32/32
!
ipv6 prefix-list DEFAULT_IPV6 seq 5 permit ::/0
ipv6 prefix-list DEFAULT_IPV6 seq 10 permit ::/0
ipv6 prefix-list DEFAULT_IPV6 seq 15 permit ::/0

[kperumalbfn]

@sudhanshukumar22 could you please double check for IPV6?

[sudhanshukumar22]

sonic(config)#
sonic(config)# ipv6 prefix-list MY_DEFAULT_IPV6 permit ::/0
sonic(config)# ipv6 prefix-list MY_DEFAULT_IPV6 permit ::/0
sonic(config)# ipv6 prefix-list MY_DEFAULT_IPV6 permit ::/0
sonic(config)# ipv6 prefix-list MY_DEFAULT_IPV6 permit ::/0
sonic(config)# ipv6 prefix-list MY_DEFAULT_IPV6 permit ::/0
sonic(config)# do show running-config
Building configuration...

Current configuration:
!
frr version 10.0.1
frr defaults traditional
hostname sonic
log syslog informational
log facility local4
zebra nexthop-group keep 1
fpm address 127.0.0.1
no fpm use-next-hop-groups
agentx
no service integrated-vtysh-config
!
ip prefix-list DEFAULT_IPV4 seq 5 permit 0.0.0.0/0
ip prefix-list PL_LoopbackV4 seq 5 permit 10.1.0.1/32
!
ipv6 prefix-list DEFAULT_IPV6 seq 5 permit ::/0
ipv6 prefix-list MY_DEFAULT_IPV6 seq 5 permit ::/0
!

[mssonicbld]

/azp run Azure.sonic-buildimage

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[StormLiangMS]

LGTM

[StormLiangMS]

Hi @sudhanshukumar22 could you check the conflict to 202411? I would suggest to file a separate PR to 202411 branch.

[kperumalbfn]

Thanks @sudhanshukumar22 please create a separate PR for 202411

[sudhanshukumar22]

Hi @sudhanshukumar22 could you check the conflict to 202411? I would suggest to file a separate PR to 202411 branch.

Hi @StormLiangMS : Could you provide me a link to the conflict ? I am not able to find it.

[sudhanshukumar22]

Thanks @sudhanshukumar22 please create a separate PR for 202411

I have raised PR (#22198).

[mssonicbld]

Cherry-pick PR to 202411: