OSPF, missing external network prefix

Eugene M. Zheganin emz at norma.perm.ru
Tue Dec 8 07:28:00 CET 2015


Hi.

I have a bunch of bird routers. Recently I discovered that at least one
prefix from LSADB isn't installed in FIB:

(first here's what bird thinks about it)
# birdc
BIRD 1.4.4 ready.
bird> show ospf lsadb lsid 192.168.114.192

Global

 Type   LS ID           Router           Age  Sequence  Checksum
 0005  192.168.114.192 192.168.0.15      498  80000385    d906
bird> show route for 192.168.114.193
0.0.0.0/0          via 178.161.152.73 on vlan600 [bgpv4sat 2015-12-04] *
(100) [AS16285i]
bird> show route for 192.168.114.192/26
0.0.0.0/0          via 178.161.152.73 on vlan600 [bgpv4sat 2015-12-04] *
(100) [AS16285i]

(and the actual FIB)
# route -n get 192.168.114.193
   route to: 192.168.114.193
destination: 0.0.0.0
       mask: 0.0.0.0
    gateway: 178.161.152.73
        fib: 0
  interface: vlan600
      flags: <UP,GATEWAY,DONE,PROTO1>
 recvpipe  sendpipe  ssthresh  rtt,msec    mtu        weight    expire
       0         0         0         0      1500         1         0
[root at crystal-alpha:local/etc]# route -n get 192.168.114.192/26
route: writing to routing socket: No such process

I really want to inverstigate why. So far I have import ACL in bird, but
this prefix doesn't seem to match:

protocol ospf ospfv4 {
    rfc1583compat yes;

    export filter exportospfv4;
    import filter importospfv4;

    area 0.0.0.44 {
        interface "vlan1";
        interface "gre0";
        interface "gre1" {
            cost 15111;
        };
    };
}

filter importospfv4 {
    if net ~ [ 172.16.0.0/31, 172.16.1.80/31, 172.16.1.81/32,
172.16.1.80/32, 172.16.0.0/32, 172.16.0.1/32 ] then {
        print "ospfv4 import: net rejected: ", net;
        reject;
    }
    if net = 0.0.0.0/0 then {
        print "ospfv4 import: net rejected: ", net;
        reject;
    } else {
        print "ospfv4 import: net accepted: ", net;
        accept;
    }
}

Anyway, there's no signs of this missing prefix in logs.
I've also noticed one more thing, may be important: this prefix is
originating from a branch office. It's present and installed on all othe
area 0 routers, no matter what vendor they're from, but is missing on
the routers which aren't from area 0, but only if they're bird. It's
present on Cisco ones (may be a coincident though, since I doesn't have
any Cisco device connected with area 0 via bird).

Thanks.
Eugene.


More information about the Bird-users mailing list