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
Regarding the issue with NHRP, I used version 10.2 of FRR to create a basic NHRP environment, but there was no direct communication between the two spoke nodes. At first, I thought it was my mistake that caused the problem. Later, I used the built-in test topology NHRP-REDUNDANCY/test_nhrpUREDUNDANCYPy in the FRR source code, and found that there was also a problem. NHC1 showed IP NHRP shortcut, but the display information was empty
Version
test@test:~/frr/tests/topotests$ sudo -E python3 -m pytest -s --topology-only nhrp_redundancy/test_nhrp_redundancy.py
=================================================================== test session starts ====================================================================
platform linux -- Python 3.12.3, pytest-8.3.4, pluggy-1.5.0
rootdir: /home/test/frr/tests/topotests
configfile: pytest.ini
plugins: xdist-3.6.1, asyncio-0.24.0
asyncio: mode=Mode.AUTO, default_loop_scope=module
collected 4 items
nhrp_redundancy/test_nhrp_redundancy.py
--- Munet CLI Starting ---
munet> nhc1 show ip nhrp sh
% No entries
munet> nhc1 show ip nhrp ?
<cr>
cache Forwarding cache information
json JavaScript Object Notation
nhs Next hop server information
opennhrp opennhrpctl style cache dump
shortcut Shortcut information
munet> nhc1 show ip nhrp shortcut
% No entries
munet> nhc2 show ip nhrp shortcut
% No entries
munet> nhs2 show ip nhrp shortcut
% No entries
munet> nhs1 show ip nhrp shortcut
% No entries
munet> nhc1 show ip nhrp sh
% No entries
munet> nhc1 show ip nhrp ?
cache Forwarding cache information
json JavaScript Object Notation
nhs Next hop server information
opennhrp opennhrpctl style cache dump
shortcut Shortcut information
munet> nhc1 show ip nhrp shortcut
% No entries
munet> nhc2 show ip nhrp shortcut
% No entries
munet> nhs2 show ip nhrp shortcut
% No entries
munet> nhs1 show ip nhrp shortcut
% No entries
Expected behavior
Two spots can communicate directly
Actual behavior
The two spokes did not achieve direct communication
Additional context
No response
Checklist
I have searched the open issues for this bug.
I have not included sensitive information in this report.
The text was updated successfully, but these errors were encountered:
Description
Regarding the issue with NHRP, I used version 10.2 of FRR to create a basic NHRP environment, but there was no direct communication between the two spoke nodes. At first, I thought it was my mistake that caused the problem. Later, I used the built-in test topology NHRP-REDUNDANCY/test_nhrpUREDUNDANCYPy in the FRR source code, and found that there was also a problem. NHC1 showed IP NHRP shortcut, but the display information was empty
Version
How to reproduce
test@test:~/frr/tests/topotests$ sudo -E python3 -m pytest -s --topology-only nhrp_redundancy/test_nhrp_redundancy.py
=================================================================== test session starts ====================================================================
platform linux -- Python 3.12.3, pytest-8.3.4, pluggy-1.5.0
rootdir: /home/test/frr/tests/topotests
configfile: pytest.ini
plugins: xdist-3.6.1, asyncio-0.24.0
asyncio: mode=Mode.AUTO, default_loop_scope=module
collected 4 items
nhrp_redundancy/test_nhrp_redundancy.py
--- Munet CLI Starting ---
munet> nhc1 show ip nhrp sh
% No entries
munet> nhc1 show ip nhrp ?
cache Forwarding cache information
json JavaScript Object Notation
nhs Next hop server information
opennhrp opennhrpctl style cache dump
shortcut Shortcut information
munet> nhc1 show ip nhrp shortcut
% No entries
munet> nhc2 show ip nhrp shortcut
% No entries
munet> nhs2 show ip nhrp shortcut
% No entries
munet> nhs1 show ip nhrp shortcut
% No entries
Expected behavior
Two spots can communicate directly
Actual behavior
The two spokes did not achieve direct communication
Additional context
No response
Checklist
The text was updated successfully, but these errors were encountered: