Replies: 3 comments 2 replies
-
someone help plz ... |
Beta Was this translation helpful? Give feedback.
2 replies
-
also maybe this helps, after clearing and stopping ipsec service and reload everything, output of tail -f /var/log/syslog:
|
Beta Was this translation helpful? Give feedback.
0 replies
-
anyone there ? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi, sorry if my question is simple or something else. I want to connect FRR as spoke to Cisco as a hub. So, I chose the BGP routing protocol and selected DMVPN style in FRR (using the nhrpd) because there are multiple branches. I also configured strongSwan for IPsec and phases 1 and 2 established without any problems.
Without using an IPsec profile under the GRE tunnel, BGP will be established with Cisco and NHRP is working too, everything is fine as expected. However, BGP gets down and change state to Connect when activating the IPSEC Profile under the tunnel interface(gre tunnel). The output of "sudo journalctl -u frr -f" is:
I suspect the /32 prefix used in the GRE tunnel is causing NHRP formation issues, and as a result, the next IP address (2.1.99.1) is unreachable for the BGP daemon, despite running NHRP as described below:
frr-virtual# show ip nhrp Iface Type Protocol NBMA Claimed NBMA Flags Identity Tunnel328 static 2.1.99.1 32.8.8.8 - Tunnel328 local 2.1.99.2 100.106.9.114 100.106.9.114 -
Also, no ping to 2.1.99.1(cisco).
"The attachment contains the configuration of Cisco and FRR as required."
cisco.txt
frr.txt
FRR Version:
10-1
Kernel version:
6.8.0-31-generic
Linux Version:
Ubuntu 24.04
Beta Was this translation helpful? Give feedback.
All reactions