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

    Quagga OSPF Problem - Losing Neighbor Relationship

    Scheduled Pinned Locked Moved pfSense Packages
    2 Posts 2 Posters 1.9k 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.
    • C
      codydearkland
      last edited by

      Ok, i'm at a loss on this one. I've been digging on it for a couple weeks now and haven't had any luck…

      I'm running pfSense in my lab. I've tried this on 2.2.6 as well as the 2.3 beta and experienced the same results.

      I'm currently leveraging VMware NSX Virtual Networking in my lab environment to simulate the same configuration I have at work. From an architecture perspective i currently have 1 Distributed Router, and 1 Enterprise Edge Service Gateway (ESG, up link to my physical network). These 2 are both configured with OSPF on area 20 and are establishing their neighbor relationship no problem. They exchange their routes - all is well.

      My distributed router has an uplink to the ESG area 20, the ESG has an uplink on area 0 to the backbone. For examples sake lets put it at 192.168.1.251. This is on my physical LAN, who's gateway is (for example) 192.168.1.100. I've installed the quagga OSPF package, and configured it. Nothing happens. As soon as I "attach" another interface (a second interface to the LAN one i would create by default....) OSPF fires up and starts chatting. Cool. This is where things get weird...

      After a little while, i receive the following messages in my logs - and the OSPF neighbor is lost. Routing drops for the NSX controlled subnets. All bad.

      Feb 12 15:24:11 ospfd 4040 AdjChg: Nbr 192.168.1.251 on em0:192.168.1.100: Full -> Deleted (InactivityTimer)
      Feb 12 15:24:11 ospfd 4040 DR-Election[1st]: Backup 192.168.1.100
      Feb 12 15:24:11 ospfd 4040 DR-Election[1st]: DR 192.168.1.100
      Feb 12 15:24:11 ospfd 4040 DR-Election[2nd]: Backup 0.0.0.0
      Feb 12 15:24:11 ospfd 4040 DR-Election[2nd]: DR 192.168.1.100
      Feb 12 15:24:11 ospfd 4040 SPF: Scheduled in 200 msec
      Feb 12 15:24:11 ospfd 4040 nsm_change_state(192.168.1.251, Full -> Deleted): scheduling new router-LSA origination

      If I remove a second interface from my Quagga configuration, hit save, and add it back - the neighbor relationship returns for a short period.

      To add additional weidrness, If i configure a VLAN on my pfSense switch, say 11.11.0.0/30, configure Quagga to use 11.11.0.1 as its router-id, configure my ESG to uplink to that instead, the neighbor relationship stays forever. No issues, no disappearance.

      i've pasted my ospfd.conf file below, with the details changed to match the example i've given above.

      This file was created by the pfSense package manager.  Do not edit!

      password totallysecretthough
      log syslog
      interface em0
      interface em0_vlan150

      router ospf
        ospf router-id 192.168.1.100
        log-adjacency-changes detail
        redistribute connected
        network 192.168.1.0/24 area 0.0.0.0
        network 10.0.0.0/24 area 0.0.0.0

      Any thoughts or feedback is appreciated!

      1 Reply Last reply Reply Quote 0
      • U
        usuarioforum
        last edited by

        Same to me. After 3 weeks working, the pfsense lose the neighbor. No config changes. No neighbor also after a reboot…

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