2.0 RC1 with openspf is unusable



  • Hi,

    I have configured ospf on the 2.0 RC1 release.  However I have been running into a very serious problem.

    We have a network called LAN (which has de pcs connected): 10.0.0.0/24
    Router 1: 10.0.0.1
    Router 2: 10.0.0.2

    Ospf is configured with the configuration bellow.

    
    router-id 10.0.0.1
    area 0.0.0.0 {
            interface em0_vlan100 {
                    router-priority 1
            }
    }
    
    router-id 10.0.0.2
    area 0.0.0.0 {
            interface em0_vlan100 {
                    router-priority 2
            }
    }
    
    

    When router1 is rebooted or shutdown, router2 looses connectivity to the lan.  The subnet is removed from the routing table!  So the router is unavailable on the lan network.

    I also upgraded to the latest snapshot, but I have the same problem.  Or am I missing something?

    Thanks!
    tommie



  • Can you run ospf with verbosity and bring the ospf logs and system logs here?



  • @ermal:

    Can you run ospf with verbosity and bring the ospf logs and system logs here?

    Can you tell me how I can turn on verbosity?  As there is no option in the gui?  And when I change the config, this gets overwritten by pfsense after a reboot?



  • I've also seen very weird things happen with OSPF running on pfSense. In one case OSPF had been running for about 24hrs with no issues when all the sudden it started routing everything in a loop to 127.0.0.1.  A reboot would temporarily fix it but then the issue would come back.  I've since removed the package and went back to static routes so I can't produce any logs at this time.



  • Hi,
    I have enabled extra logging, please find the log.  After rebooting router2 my subnet 10.0.0.0/24 is gone in the routing table of router 1.

    em0_vlan100 has index 7
    startup
    orig_rtr_lsa: area 0.0.0.0
    orig_rtr_lsa: stub net, interface em0_vlan100
    if_fsm: event UP resulted in action START and changing state for interface em0_vlan100 from DOWN to WAIT
    spf_calc: area 0.0.0.0 calculated
    nbr_fsm: event HELLO_RECEIVED resulted in action START_INACTIVITY_TIMER and changing state for neighbor ID 10.0.0.2 from DOWN to INIT
    nbr_fsm: event 2_WAY_RECEIVED resulted in action EVAL and changing state for neighbor ID 10.0.0.2 from INIT to 2-WAY
    if_act_elect: interface em0_vlan100 old dr none new dr 10.0.0.2, old bdr none new bdr 10.0.0.1
    nbr_fsm: event ADJ_OK resulted in action EVAL and changing state for neighbor ID 10.0.0.2 from 2-WAY to EXSTA
    orig_rtr_lsa: area 0.0.0.0
    orig_rtr_lsa: stub net, interface em0_vlan100
    orig_rtr_lsa: area 0.0.0.0
    orig_rtr_lsa: stub net, interface em0_vlan100
    if_fsm: event BACKUPSEEN resulted in action ELECT and changing state for interface em0_vlan100 from WAIT to BCKUP
    if_act_elect: interface em0_vlan100 old dr 10.0.0.2 new dr 10.0.0.2, old bdr 10.0.0.1 new bdr 10.0.0.1
    if_fsm: event NEIGHBORCHANGE resulted in action ELECT and changing state for interface em0_vlan100 from BCKUP to BCKUP
    nbr_fsm: event NEGOTIATION_DONE resulted in action SNAPSHOT and changing state for neighbor ID 10.0.0.2 from EXSTA to SNAP
    nbr_fsm: event SNAPSHOT_DONE resulted in action SNAPSHOT_DONE and changing state for neighbor ID 10.0.0.2 from SNAP to EXCHG
    nbr_fsm: event EXCHANGE_DONE resulted in action EXCHANGE_DONE and changing state for neighbor ID 10.0.0.2 from EXCHG to LOAD
    orig_rtr_lsa: area 0.0.0.0
    orig_rtr_lsa: transit net, interface em0_vlan100
    nbr_fsm: event LOADING_DONE resulted in action NOTHING and changing state for neighbor ID 10.0.0.2 from LOAD to FULL
    spf_calc: w id 10.0.0.2 type 1 has
        no link to v id 10.0.0.2 type 2
    spf_calc: area 0.0.0.0 calculated
    send_rtmsg: action 1, prefix 10.0.0.0/24: File exists
    spf_calc: area 0.0.0.0 calculated
    if_fsm: event WAITTIMER resulted in action NOTHING and changing state for interface em0_vlan100 from BCKUP to BCKUP
    orig_rtr_lsa: area 0.0.0.0
    orig_rtr_lsa: stub net, interface em0_vlan100
    if_act_elect: interface em0_vlan100 old dr 10.0.0.2 new dr 10.0.0.1, old bdr 10.0.0.1 new bdr none
    orig_rtr_lsa: area 0.0.0.0
    orig_rtr_lsa: stub net, interface em0_vlan100
    orig_rtr_lsa: area 0.0.0.0
    orig_rtr_lsa: stub net, interface em0_vlan100
    if_fsm: event NEIGHBORCHANGE resulted in action ELECT and changing state for interface em0_vlan100 from BCKUP to DR
    nbr_fsm: event 1_WAY_RECEIVED resulted in action CLEAR_LISTS and changing state for neighbor ID 10.0.0.2 from FULL to INIT
    spf_calc: area 0.0.0.0 calculated
    nbr_adj_timer: failed to form adjacency with 10.0.0.2
    nbr_fsm: neighbor ID 10.0.0.2, event ADJ_TIMEOUT not expected in state INIT
    ^Cnbr_fsm: event KILL_NBR resulted in action DELETE and changing state for neighbor ID 10.0.0.2 from INIT to DOWN
    route decision engine exiting
    kernel routing table decoupled
    orig_rtr_lsa: area 0.0.0.0
    orig_rtr_lsa: stub net, interface em0_vlan100
    if_fsm: event DOWN resulted in action RESET and changing state for interface em0_vlan100 from DR to DOWN
    ospf engine exiting
    terminating
    
    

    here is the routing table of router 1 after reboot of router 2.

    
    Destination        Gateway            Flags    Refs      Use  Netif Expire
    default            94.224.32.1        UGS         0  2527046 em0_vl
    10.0.0.1         link#7             UHS         0        0    lo0
    10.0.0.254         link#15            UH          0        0   vip2
    10.0.2.0/24        link#8             U           0   141572 em0_vl
    10.0.2.252         link#8             UHS         0        0    lo0
    10.0.2.254         link#14            UH          0        0   vip1
    10.0.3.0/25        10.0.3.250         UGS         0    19121 em0_vl
    10.0.3.248/29      link#13            U           0    38235 em0_vl
    10.0.3.252         link#13            UHS         0        0    lo0
    10.0.3.254         link#17            UH          0        0   vip4
    10.0.5.0/24        link#12            U           0  1434812 em0_vl
    10.0.5.252         link#12            UHS         0        0    lo0
    10.0.9.0/24        link#1             U           0        0    em0
    10.0.9.252         link#1             UHS         0        0    lo0
    10.0.9.254         link#16            UH          0        0   vip3
    10.1.0.0/24        10.1.3.1           UGS         0  2198510 ovpnc1
    10.1.3.1           link#18            UH          0   110824 ovpnc1
    10.1.3.2           link#18            UHS         0        0    lo0
    10.10.0.0/24       10.1.3.1           UGS         0    43303 ovpnc1
    79.132.245.104/29  link#11            U           0        1 em0_vl
    79.132.245.106     link#11            UHS         0        0    lo0
    94.224.32.0/21     link#10            U           0    11934 em0_vl
    94.224.38.12       link#10            UHS         0        0    lo0
    127.0.0.1          link#3             UH          0      131    lo0
    195.130.130.132    00:30:48:b1:04:e6  UHS         0        0 em0_vl
    195.130.131.132    00:30:48:b1:04:e6  UHS         0        0 em0_vl
    212.71.0.2         79.132.245.105     UGHS        0    11934 em0_vl
    
    


  • I just did another test, when rebooting the router2 with hard reset… after 10 or 20 seconds... the following happens.

    
    orig_rtr_lsa: area 0.0.0.0
    orig_rtr_lsa: stub net, interface em0_vlan100
    if_act_elect: interface em0_vlan100 old dr 10.0.0.1 new dr 10.0.0.1, old bdr 10.0.0.2 new bdr none
    orig_rtr_lsa: area 0.0.0.0
    orig_rtr_lsa: stub net, interface em0_vlan100
    if_fsm: event NEIGHBORCHANGE resulted in action ELECT and changing state for interface em0_vlan100 from DR to DR
    nbr_fsm: event INACTIVITY_TIMER resulted in action DELETE and changing state for neighbor ID 10.0.0.2 from FULL to DOWN
    spf_calc: area 0.0.0.0 calculated
    
    

    After this the subnet is gone from the routing table.



  • Can you draw me a schema or describe the router1 and router2?
    How are they connected to each other(switch, direct cable, carp)?


Log in to reply