-
Notifications
You must be signed in to change notification settings - Fork 41
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
panic: interface conversion: interface {} is nil, not string #35
Comments
Happens to me on ipv4, with lines: 192.0.2.1/32 blackhole [static1 2021-05-02 01:09:54] * (200) Also happens on IPv6 with my 100::/64 prefix. I think birdwatcher is tripping over seeing the blackhole first (with no interface) and then seeing the next route which HAS an interface. This
Was added to parseRouteLines on or around line 317 to diagnose the issue |
Trapping the panic allows birdwatcher to continue - but I also filtered out the blackhole advertisements on the RR and that fixed the issue as well. |
This fixes my issue
|
@tweippert Guessing |
With this i see my RPKI Routes, i currently had no blackhole or similar routes on this RR:
Will look on your fix if it also works on my issue, hopefully the next few days ... |
Interesting... Is there a reason you have your RPKI routes in your master table? Mine are in separate tables since birdwatcher+alice don't really need to show those. (just the tags set by the BGP policy) i.e.
|
I haven't. They are in roa tables, too. But a 'show route' shows me all tables:
My config looks similar:
This is with 2.08 on Alpine:
|
I have my alice-lg set to explicitly list table master and master6.... so maybe that's why I'm not tripping over it. [source.bird4] [source.bird6] |
Yes, this seems to "fix" the panic ... will keep an eye on it the next hours/days. No, it won't fix my issue, after few minutes the crash happens again ...
|
Merged the PR, however not sure if the problem is fixed. |
birdwatcher (v4) is bailing out with the following messages:
the v6 version is running without issues.
The text was updated successfully, but these errors were encountered: