[1.2.0 RC5] OSPF Seems to be crashing and has problems

Two strange things are happening.

First off, this config fails to redistribute my static route (default gateway):

static {
     route 0.0.0.0/0 {
         next-hop xx.xx.xx.1 {
         }
     }
 }
ospf {
     area 0 {
         network 10.253.253.0/24
     }
     log-adjacency-changes {
     }
     parameters {
         abr-type cisco
         router-id 10.255.255.1
     }
     redistribute {
         connected {
             metric-type 2
         }
         static {
             metric-type 2
         }
     }
 }

Though that might be okay. I’m not sure if it’s supposed to redistribute 0.0.0.0/0. The bigger problem here is this config, that uses the “Default information” to redistribute the default route.

 ospf {
     area 0 {
         network 10.253.253.0/24
     }
     default-information {
         originate {
             always
             metric 10
             metric-type 2
         }
     }
     log-adjacency-changes {
     }
     parameters {
         abr-type cisco
         router-id 10.255.255.1
     }
     redistribute {
         connected {
             metric-type 2
         }
         static {
             metric-type 2
         }
     }
 }

This config works as expected. The default route gets distributed. The problem is after 10 or 15 minutes, it stops sending the default route. The only way to get it back is to force the ospfd daemon to restart (or reboot the box).

It’s worth mentioning it’s ONLY the default that’s not getting redistributed. The connected seem to stay connected.

For now I’ve rolled back to RC4 to see if the problem exists there.

Update: 2.5 hours on RC4 and it’s been stable. Switched back to RC5 and it immediately started happening again within 10-15 minutes.

1 Like

Just adding a note here. Created a Phabricator task. This appears to be an upstream issue with FRR that was fixed and should be eventually merged into VyOS.

Workaround create a static route to 0.0.0.0/1 and 128.0.0.0/1 and redistribute those instead of default information

This patch was merged, but it seems you have other issue

That’s a great idea, and definitely covers for the problem (which is still present), in a far better manner than I had going

1 Like