-
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
frr 4.x fails to start with an active tun interface on FreeBSD #2338
Comments
compiling with debug flags,
|
cat /var/tmp/quagga.zebra.crashlog
|
@mdtancsa Are you able to reproduce it with FRR 5.0 ? I didn't see this problem with my work-in-progress FRR 5.0 port, and because I didn't see any mention of this bug in the release notes and didn't understand why it didn't crash anymore.
|
It starts up for me as well. I still get the all those warnings. Not sure if thats an issue or not, or there are other silent problems :( I built and tested using the default config instructions. I did notice a boat load of )# zebra -d -A127.0.0.1 Hello, this is FRRouting (version 5.0-MyOwnFRRVersion). User Access Verification Password: |
I confirm this bug on 4.0:
On 5.x this crash is not happening. My guess it that one of these two commits fixed the problem: 60c0687 or f52d0a1. I need to leave now but I'll check once I get back home. Regarding the warnings, they are harmless, but I'll try to find a way to silence them. |
#2590 should fix the problem. I also introduced a new commit to silence the SIOCGIFMEDIA warning. The other warning ( |
@rwestphal have any news about: |
fixed |
I noticed that if a tunnel interface created by OpenVPN on FreeBSD 11 (AMD64) is active at the time zebra tries to start up, it fails.
Starting with truss shows
If openvpn is not running, it starts up, but still with many warnings that 3.x did not generate:
This is from the port
config.log shows
The text was updated successfully, but these errors were encountered: