Quagga not coming up after pfSense restart



  • I had this problem a few years ago and it's creep'd back up with the newest round of updates. I have a hub and spoke network. Open VPN connects to our HQ, quagga handles the routing. After a reboot, OpenVPN connects, but quagga never works. The only thing I have been able to do to get it to reconnect is force a package reinstall, then it finds all it's neighbors and the route instantly.

    Netgate m1n1wall
    pfSense 2.13 Nanobsd
    Quagga 0.99.22.3 v0.6.1

    The issue a few years ago was Quagga would beat OpenVPN to the punch and load before the tunnel came up. It looks like this is the same issue. Quagga either doesn't start trying, or doesn't keep trying to form neighbors after OpenVPN establishes the tunnel.



  • i don't have this problem on my sites, but i do have interfaces assigned to all tunnels. Perhaps that could be a workaround?



  • I too have my tunnels assigned to interfaces.

    This is an issue that was reintroduced between the time 2.1 came out and maybe a month or two ago when I upgraded all of the routers again to 2.12 and now 2.13.



  • The issue appears to be resolved in v0.6.2. I am keeping my fingers crossed.



  • This issue still appears to be resolved on the full version of pfSense. But all of our embedded pfSense location still continue to have this issue. It still looks like it is the issue from a few years back. Quagga starts before the OpenVPN tunnel comes up. Then when the OpenVPN tunnel comes up, Quagga never tries to form relationships again. Last time, I added a 60 second wait in the quagga run script to fix this until an official fix was made.



  • Hi,

    we do encounter the problem again on very fast setups (SSDs and fast CPUs). With nanobsd, we don't have problems. Only with the full (installed) version of pfsense.

    We are on the latest version.

    If we restart the quagga services over the web interface after a restart, everything works fine. So there seems to be the mentioned timing issue discussed in the forum again…

    Any ideas?

    Can anyone give me a hint we to look? Where is openvpn started after a reboot in the scripts, where is quagga started in the scripts? How was the problem solved?

    kind regards

    trey



  • it might be best to open up a bugreport if this is easily reproducable on multiple systems.
    i just noticed, you already did. It might be best to include some more info on the hardware  & configuration.

    i believe @jimp is the maintainer of the quagga package, when he notices the bugreport, he'll figure something out.


  • Banned

    @Trey:

    Can anyone give me a hint we to look? Where is openvpn started after a reboot in the scripts, where is quagga started in the scripts? How was the problem solved?

    Was never solved in any way, dunno where did you get the impression. There is no concept of dependencies or anything in the hacked together autogenerated rc scripts. Your hacks (increase the sleep on line 338, check for openvpn daemon running, check ifconfig output for the OpenVPN interfaces and do something, or whatever similar crap) would go here:

    https://github.com/pfsense/pfsense-packages/blob/master/config/quagga_ospfd/quagga_ospfd.inc#L319


Log in to reply