BFD single-hop peer configured for user VRF does not work if interface parameter is not specified #5554
Description
- When reporting a crash, provide a backtrace
- When pasting configs, logs, shell output, backtraces, and other large chunks of text use Markdown code blocks
- Include the FRR version; if you built from Git, please provide the commit hash
- Write your issue in English
Describe the bug
A clear and concise description of what the bug is.
In FRR 7.2 released branch, when we configure BFD single-hop peer for non-default VRF without specifying the interface parameter.
e.g. <
bfd
peer 102.1.1.2 vrf Vrf-1
we see in tcpdump that BFD control packets are sent out on default VRF with destination address as 102.1.1.2. From socket statistics, it is clear that socket is not binded to user VRF as it is not a multihop scenario.
So, is specifying the interface name a mandatory parameter when we have a BFD single hop peer on user-VRF.
(put "x" in "[ ]" if you already tried following)
[x ] Did you check if this is a duplicate issue?
[ ] Did you test it on the latest FRRouting/frr master branch?
To Reproduce
Steps to reproduce the behavior:
- Go to '...'
- Click on '....'
- Scroll down to '....'
- See error
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Versions
- OS Kernel: [e.g. Linux, OpenBSD, etc] [version]
- FRR Version [version] 7.2
Additional context
Add any other context about the problem here.