unknown net, unknown gateway, unknown interface - bird2 + birdwatcher about alice-lg

[annikahannig]

This looks like a parsing issue in the birdwatcher.

[annikahannig]

I'll use your show protocols all dump to debug this :)

[dylancmds]

Let me know if I can get you anything else!

[ijg00]

I'm also seeing the same problem. I've since updated to the latest commit of alice-lg and birdwatcher. The output has changed slightly (removing the "Unknown x" part) but still present:

Similar to @dylancmds clicking through shows valid attributes so my instance is also parsing some data from Bird.

[JackMarik]

Same issue with Bird 1.6

EDIT: Solved, it was indeed a parsing issue. In particular, this line from parser.go
regex.routes.startDefinition = regexp.MustCompile(^([0-9a-f\.\:\/]+)\s+via\s+([0-9a-f\.\:]+)\s+on\s+([\w\.]+)\s+\[([\w\.:]+)\s+([0-9\-\:\s]+)(?:\s+from\s+([0-9a-f\.\:\/]+)){0,1}\]\s+(?:(\*)\s+){0,1}\((\d+)(?:\/\d+){0,1}\).*)

This depends on the word "via" on the first line of the "show route all" output from bird. But if the route is not reachable the world via is not there (neither is the IP or interface) (it says unreachable instead), thus the line won't pass the regex.

Here's an example line that should pass the regex.
8.8.8.8/32 via 9.9.9.9 on eth0 [client1 2024-05-20 12:00:00 from 1.1.1.1] * (100/?) [i]
When you the route is unreachable, the line will look like this and won't pass regex.
8.8.8.8/32 unreachable [client1 2024-05-20 12:00:00 from 1.1.1.1] * (100/?) [i]

Solved it by making sure all routes are reachable.