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
Describe the bug
Upon a reboot the frr log will show a message like babeld[1308]: [ZPCFR-WY2XV][EC 100663299] setsockopt(IPV6_JOIN_GROUP) on interface 'enp6s0': Address already in use
and babel will never initialize requiring a restart of the frr service in order to come up and establish neighbors with other babel routers in the environment.
Did you check if this is a duplicate issue?
Did you test it on the latest FRRouting/frr master branch?
Expected behavior
Babel should correctly handle this situation on reboot and successfully exchange routes with other neighbors. I get similar warnings from ripngd however it has no issues exchanging routes after a reboot.
Versions
OS Version: Debian 12 bookworm
Kernel: Linux 6.3.3
FRR Version: 8.4.2
The text was updated successfully, but these errors were encountered:
I've updated my post with the config I'm running, I originally left it out because it's about the most basic babel configuration you can run. Let me know if there's any other information I can provide.
This issue is stale because it has been open 180 days with no activity. Comment or remove the autoclose label in order to avoid having this issue closed.
Describe the bug
Upon a reboot the frr log will show a message like
babeld[1308]: [ZPCFR-WY2XV][EC 100663299] setsockopt(IPV6_JOIN_GROUP) on interface 'enp6s0': Address already in use
and babel will never initialize requiring a restart of the frr service in order to come up and establish neighbors with other babel routers in the environment.
To Reproduce
Babel config used in my setup:
Expected behavior
Babel should correctly handle this situation on reboot and successfully exchange routes with other neighbors. I get similar warnings from ripngd however it has no issues exchanging routes after a reboot.
Versions
The text was updated successfully, but these errors were encountered: