Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    [SOLVED]openospf on one end / quagga ospf on the other

    Scheduled Pinned Locked Moved OpenVPN
    4 Posts 3 Posters 2.2k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • H
      heper
      last edited by

      Is there a way to make both implementations get along and distribute routes ?

      situation:

      PFA <–> PFB <--> PFC

      PFA & PFB run openOspf on pfsense 2.0.1
      PFC runs quagga on pfsense 2.1 Dev

      it would not be entirebly impossible to change all to quagga but i would have to go to all sites because i doubt its wise to do this from remote

      1 Reply Last reply Reply Quote 0
      • C
        cmb
        last edited by

        Sure, OSPF is OSPF. Will work fine.

        1 Reply Last reply Reply Quote 0
        • jimpJ
          jimp Rebel Alliance Developer Netgate
          last edited by

          I have a setup going now that is quagga on one end and openospfd on the other, and it does work fine.

          Though quagga has proven to be much more well-behaved than openospfd over time.

          Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

          Need help fast? Netgate Global Support!

          Do not Chat/PM for help!

          1 Reply Last reply Reply Quote 0
          • H
            heper
            last edited by

            I've tried it and it appears to work, but there is atleast one "issue"
            When adding interfaces to the Ospf, you can set a password. Between OpenOspf servers this works flawlessly in my setup.

            If i specify a password on the interface between a quagga host & openOspf, then no neighbours are found. Without password it works without any issues.

            I guess this is not this much of a problem in my case, as i use it for routing over openvpn lines that should be pretty secure on its own.
            When routing public ip networks it might pose a risk that anyone can join ?

            1 Reply Last reply Reply Quote 0
            • First post
              Last post
            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.