New to routing: radv Network not found?

Kevin P. Fleming lists.bird-users at kevin.km6g.us
Tue Apr 25 12:49:13 CEST 2023


On Tue, Apr 25, 2023, at 06:37, Alessandro Vesely wrote:
> Now it shows routes!  I have:
> 588-north:bird# birdc show route
> BIRD 2.0.7 ready.
> Table master6:
> ::/0                 unicast [kernel1 12:10:08.587] (10)
> 	dev ppp0
> 2a02:29e1:300:e922::/64 unicast [kernel1 12:10:08.587] (10)
> 	dev eth2r
>
> Thank you!

This shows the default IPv6 route table 'master6', because that's where the 'kernel' protocol places routes it exports unless you tell it otherwise.

>
> However, I thought that with static having
>
> 	route 2a02:29e1:300:e900::/56 unreachable;
>
> After learning the local interface addresses, bird would gather that (only) the 
> addresses not configured are unreachable.  It says:
>
> 589-north:bird# birdc show route for 2a02:29e1:300:e918::5
> BIRD 2.0.7 ready.
> Table master6:
> ::/0                 unicast [kernel1 12:10:08.587] (10)
> 	dev ppp0
>
> That IP should be unreachable.  How do I tell it that?

You put your static routes into a table named 'radv_routes'; if you want to analyze an address against that table, you need to specify it:

show route for 2a02:29e1:300:e918::5 table radv_routes

Otherwise 'show route' uses the default table 'master6'.

If you are only using Bird for the radv protocol, you should probably just let everything default to using the 'master6' table, and make your life simpler. You can remove the 'kernel' protocol completely, change the 'static' protocol and the 'radv' protocol to not specify a table name, and 'show route' will give you the result you are looking for without having to specify a table name.


More information about the Bird-users mailing list