How to make bird now its own connectivity (OSPF)

[Ondrej Zajicek]

On Sat, Oct 23, 2021 at 01:38:37PM +0200, Maximilian Wilhelm wrote:
> > Why does no protocol in Bird want to take responsibility for the router's own connectivity?
> > How on earth is this supposed to work?
> 
> OSPF does that :)
> 
> I would propose a configuration for R1 like
> 
> protocol ospf {
> 	import all;	# Learn all routes from OSPF
> 	export none;	# Do not export (redistribute) any routes from
> 			# birds main table into OSPF
> 
> 	area 0 {
> 		# Interface conncted to R2 should be part of OSPF and
> 		# "speak" OSPF (send hello packets)
> 		interface "eth0";
> 
> 		# Interface connected to the local network should be
> 		# part of OSPF but NOT "speak" OSPF (do NOT send hello
> 		# packets, so no machine there can join OSPF)
> 		interface "eth1" { stub yes; };

Also note that you can just add:

  interface "*" { stub yes; };

after all other interface definitions if you want all remaining
interfaces be configured as stub.

-- 
Elen sila lumenn' omentielvo

Ondrej 'Santiago' Zajicek (email: santiago at crfreenet.org)
OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net)
"To err is human -- to blame it on a computer is even more so."