-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
BGP session remains down, nexthop_set failed, bgp_getsockname() failed #12792
Comments
Also, why does it print '(Unknown)' in :'%ADJCHANGE: neighbor 196.250.236.nnn(Unknown)' log entry? Does not seem to be a DNS reverse lookup. |
Update: Rebooted the router - this time all the BGP sessions came up without any issues. Did not make any changes. |
Unknown means that BGP FQDN Capability is not received which means unknown FQDN. Regarding |
Hi, thanks for answering the 'Unknown' question. BGP sessions all started after a 2nd reboot, but I still think something caused that one session to break, and only start after taking down and bringing up the interface. Do you have a test for larger numbers of interfaces with longer than usual names? |
I just ran into this same thing today. Only a single interface was affected. The connected devices could ping each other just fine, ip address showed up in kernel but not in frr. Resolved immediately by I have not yet found a way to reliably reproduce the issue, as I have only encountered it just this once after maybe 50 - 100 times configuring interfaces exactly like this. FRR:
|
Hi, for the record ,
Mine was several lines like this
Only with the IPv4 address of the peer. IPv6 was working fine.
Same here.
I only removed my IPv4 address on that interface and I added it again.
same
5.10.0-21-amd64
same |
Hi Can I request that this ticket / issue be opened again? |
I got same error (nexthop_set failed, resetting connection - intf 0x0) with FRR 8.2.2 (Fedora 36, Kernel: 5.17.12-300) and it fixed after a restarting, is this issue fixed at 8.5? @ton31337
|
Hi I just noticed this problem in v8.5.1 - not resolved yet. |
Hi Pretty much exactly the same thing happened with new FRR version (8.5.1). BGP session did not come up. Had to down and up the VLAN interface. From the log:
|
I still have this problem in 8.5.4 on OPNsense 23.7.10-1 |
Describe the bug
I upgraded from FRR 8.4.1 to FRR 8.4.2 and rebooted the router. All v4 and v6 BGP sessions came back up, except for one v4 session on a vlan interface. I had to down and up the interface for the BGP session to come back up.
I remember running into a similar situation a while back, it was a netlink buffer size thing: issue #10404.
I suspect the vlan interface name maybe confused zebra in some way, or maybe there was a limit to the number of interfaces it was happy with: vtysh -c "show interface brief" | wc -l = 56
I noticed the following in the log file:
I could ping the neighbor v4 IP, and the IPv6 BGP session on the same interface was up.
I then used ifdown to bring down the vlan interface and brought it back up:
ifdown enp3s0.1576
ifup enp3s0.1576
After this both the v4 and v6 BGP sessions on the interface were up, with the following in the log:
To Reproduce
Hard to say. I'm not sure what caused the problem.
Expected behavior
Start with all BGP sessions coming back up.
Versions
The text was updated successfully, but these errors were encountered: