You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the current SRv6 implementation of FRR, the SRv6 SIDS are programmed into the data-plane via kernel netlink messages because in Linux kernel SRv6 SIDS are treated as if they are IP routes. Since the interface attribute field is mandatory for every netlink message, FRR by default assumes that there is a sr0 interface available and it will use sr0 for the netlink messages that carry the SRv6 static SIDs.
So, to enable FRR to program static SRv6 SIDs, we added code to create the dummy interface "sr0" upon system startup in SONiC msft-202412 images(Azure/sonic-buildimage-msft#517). However, this code is not available in SONiC master because people are looking for better solutions such as kernel bypassing in SRv6 SIDs programming. To make the SRv6 feature publicly available for the community in 202505 SONiC release, I created this issue to track the progress in developing the solution for the aforementioned problem.
The text was updated successfully, but these errors were encountered:
In the current SRv6 implementation of FRR, the SRv6 SIDS are programmed into the data-plane via kernel netlink messages because in Linux kernel SRv6 SIDS are treated as if they are IP routes. Since the interface attribute field is mandatory for every netlink message, FRR by default assumes that there is a sr0 interface available and it will use sr0 for the netlink messages that carry the SRv6 static SIDs.
So, to enable FRR to program static SRv6 SIDs, we added code to create the dummy interface "sr0" upon system startup in SONiC msft-202412 images(Azure/sonic-buildimage-msft#517). However, this code is not available in SONiC master because people are looking for better solutions such as kernel bypassing in SRv6 SIDs programming. To make the SRv6 feature publicly available for the community in 202505 SONiC release, I created this issue to track the progress in developing the solution for the aforementioned problem.
The text was updated successfully, but these errors were encountered: