Today, after package updates, in my DNS server using Debian Stretch, OSPF stopped working and thus the server does not belong to the DNS anycast group. When I try to do /etc/init.d/quagga start, the init.d script is no longer there. I shall say I am still using sysVinit, and not systemd. Nevertheless, I have quagga packages installed in the system. While I could in the past quagga had one package in Debian, nowadays it has installed the list bellow. The package version currently installed is 1.1.0-2 What is happening? $dpkg -l | grep quagga | awk ' { print $2 } ' libquagga0 quagga quagga-bgpd quagga-core quagga-isisd quagga-ospf6d quagga-ospfd quagga-pimd quagga-ripd quagga-ripngd

I have a network that is connected to the internet through Router 1 through cable, and separately through Router 2 on LTE. It is desired that in a situation where both cable and LTE are available, Router 1 and Router 2 both route their respective traffic through Router 1's cable connection. Only cable (or Router 1) fails, Router 2's LTE link is used. Once Router 1's link becomes available again, both go back to cable. I am trying to set up a routing daemon (Quagga) on both Router 1 and Router 2, so the two devices exchange available routes through the OSPF protocol. However, one of the fundamental assumptions of this concept seems to be that the router's kernel notifies Quagga when its link is dead; as such, Quagga will treat a removed LAN cable or a completely non-responsive router as a "dead" route, but not other modes of failure, such as the LTE modem losing association with the cellular network or the cable being removed from the cable modem (both of which do not cause any changes on the "local" side of the modem). Thus, my question: How can I instruct Quagga, or any other routing daemon, to periodically verify a route (e.g. by pinging a host that should be reachable through that route) and treat the route as failed if those pings fail. Thank you for any suggestions.

I need/want to migrate from Quagga to BIRD after several Quagga hiccups, namely https://unix.stackexchange.com/questions/331664/quagga-stopped-working-after-updates-in-stretch/331665 . BIRD is also more flexible and modern. I have my OSPF BIND anycast configuration in Quagga and would like to setup the OSPF service in a way similar on BIRD. What to do? My /etc/quagga/ospfd.conf is: ! ! Zebra configuration saved from vty ! 2011/03/22 21:17:11 ! hostname dns password 8 xxxxxxx enable password 8 xxxxxxx log stdout service password-encryption ! ! ! interface dummy0 ip ospf cost 100 ! interface dummy1 ip ospf cost 500 ! interface dummy2 ip ospf cost 1000 ! interface dummy3 ip ospf cost 900 ! interface eth0 ip ospf authentication message-digest ip ospf message-digest-key 5 md5 MySecretPassword ip ospf cost 1000 ! interface eth1 ip ospf cost 1000 ! interface lo ! router ospf ospf router-id 1.1.1.1 auto-cost reference-bandwidth 10000 network 1.1.1.0/22 area 0.0.0.0 network 2.2.2.2/32 area 0.0.0.0 network 3.3.3.3/32 area 0.0.0.0 network 4.4.4.4/32 area 0.0.0.0 network 5.5.5.5/32 area 0.0.0.0 area 0 filter-list prefix AREA_1_OUT out ! ip prefix-list AREA_1_OUT seq 5 permit 2.2.2.2/32 ip prefix-list AREA_1_OUT seq 10 permit 3.3.3.3/32 ip prefix-list AREA_1_OUT seq 15 permit 4.4.4.4/32 ip prefix-list AREA_1_OUT seq 20 permit 5.5.5.5/32 ip prefix-list AREA_1_OUT seq 25 deny any ! line vty !

I am migrating from Quagga to BIRD; however after setting things up, the other OSPF "routers" do not see me. I think I have not setup properly the MD5 directive. My similar setup in Quagga is: ip ospf authentication message-digest ip ospf message-digest-key 5 md5 SecreTPassword In BIRD I have done: area 0.0.0.0 { ... interface "eth0" { cost 1000; password "SecreTPassword"; authentication cryptographic; }; ... }; What is wrong?

In a previous post this was mentioned by @Celada in the Enhanced version section: https://unix.stackexchange.com/questions/255923/use-nic-bonding-with-independent-switches My situation: one centos 7.2 host with 4 100G NICs - all connected to ToR: NIC1: 10.0.2.1/24 NIC2: 10.0.2.2/24 NIC3: 10.0.2.3/24 NIC4: 10.0.2.4/24 Requirement: How to configure an extra loopback addr on the centos host and publish it as a single IP for HA/LB access for client machines within the rack, for iSCSI data-path access for storage.