Self sign-up has been disabled due to increased spam activity. If you want to get access, please send an email to a project owner (preferred) or at gitlab(at)nic(dot)cz. We apologize for the inconvenience.
Here is a simple and typical example of BIRD used as an OSPF router. Router has several interfaces: eth0 is connected to the local ethernet switch, eth1 and eth2 are ethernet ptp links to other routers, ath0 is a local wifi AP and ath1, ath2 are wifi ptp links to other routers. Wifi devices are Atheros with madwifi driver, hence athX device names.
Here is a simple and typical example of BIRD used as an OSPF
router. Router has several interfaces: eth0 is connected to the local
ethernet switch, eth1 and eth2 are ethernet ptp links to other
routers, ath0 is a local wifi AP and ath1, ath2 are wifi ptp links to
other routers. Wifi devices are Atheros with madwifi driver, hence
athX device names.
Fast ethernet links use cost 5 and (slower) wifi links use cost 100. Default OSPF parameters (_hello_, _dead_, ...) are changed, because default ones are too conservative. _dead_ parameter on wifi links is larger, because these devices sometimes experience a drop-out for tens seconds.
Fast ethernet links use cost 5 and (slower) wifi links use cost
100. Default OSPF parameters (_hello_, _dead_, ...) are changed,
because default ones are too conservative. _dead_ parameter on wifi
links is larger, because these devices sometimes experience a drop-out
for tens seconds.
Static protocol is used for leaf networks hidden behind a neighor
router that does not speak OSPF. These static routes are propagated to
OSPF, because they are accepted in the OPSF export filter, where also
type 1 OSPF metric of 1000 is assigned to them.
Static protocol is used for leaf networks hidden behind a neighor router that does not speak OSPF. These static routes are propagated to OSPF, because they are accepted in the OPSF export filter, where also type 1 OSPF metric of 1000 is assigned to them.