OSPF Route not installed in Helium (but work on 1.0.3)

Bugs
, , ,
1

Hi to all.
I have a working OSPF configuration between a VyOS router (1.0.3) and 5 cisco router over 5 gre tunnel.

After upgrade VyOS to 1.1.4 it don’t work.
However the neighbors relationship came up but route aren’t installed on both side.

this is configuration on VyOS side

protocols {
    ospf {
        area 0 {
            area-type {
                normal
            }
            network 10.254.0.0/30
            network 10.254.3.0/30
            network 192.168.8.0/24
            network 10.252.0.4/30
            network 10.252.0.0/30
        }
    }

this is a tunnel template that I use

   tunnel tun0 {
        address 10.254.0.1/30
        encapsulation gre
        ip {
            ospf {
                bandwidth 2000
                dead-interval 40
                hello-interval 10
                priority 1
                retransmit-interval 5
                transmit-delay 1
            }
        }
        local-ip XXX.XXX.XXX.XXX
        mtu 1400
        multicast disable
        remote-ip XXX.XXX.XXX.XXX
    }

If I run

show ip ospf database

in VyOs I see the route in “Summary Link States”.

In VyOs log on 1.1.4 there are these lines

Mar 13 10:03:12 XXXX-vyos ospfd[1851]: Packet[DD]: Neighbor 0.0.0.1 state is 2-Way, packet discarded.
Mar 13 10:03:12 XXXX-vyos ospfd[1851]: Packet[DD]: Neighbor 2.0.0.1 state is 2-Way, packet discarded.
Mar 13 10:03:14 XXXX-vyos ospfd[1851]: Packet[DD]: Neighbor 0.0.0.2 state is 2-Way, packet discarded.
Mar 13 10:03:16 XXXX-vyos ospfd[1851]: Packet[DD]: Neighbor 3.0.0.1 state is 2-Way, packet discarded.
Mar 13 10:04:17 XXXX-vyos ospfd[1851]: ospf_maxage_lsa_remover: LSA[Type2:10.254.0.1]: No associated LSDB!
Mar 13 10:04:17 XXXX-vyos ospfd[1851]: ospf_maxage_lsa_remover: LSA[Type2:10.254.3.1]: No associated LSDB!
Mar 13 10:04:17 XXXX-vyos ospfd[1851]: ospf_maxage_lsa_remover: LSA[Type2:10.254.0.1]: No associated LSDB!
Mar 13 10:04:17 XXXX-vyos ospfd[1851]: ospf_maxage_lsa_remover: LSA[Type2:10.254.3.1]: No associated LSDB!

that there aren’t on 1.0.3 version.

Has anyone had the same problem ? Where I was wrong ? Again, if I return to 1.0.3 everything back to work )

Thanks in adance

2

Did you mean 1.1.3, talking about VyOs version?

There was bug about OSPF over tunnels in previous version. So if you are really in 1.0.3 I suggest you upgrade to 1.1.3.

3

I was in 1.0.3 VyOS version and in this version all work fine.
Then I upgrade to 1.1.4 and in this version there is this problem.

I will try to install 1.1.3 too…

Thanks

It seems that this bug is on 1.1.4 and 1.1.3 version too (I just tried the 1.1.3 release and the route still aren’t installed ). So I came back to 1.0.3 version and in this version all work.

4

I did other tests . With version 1.0.3 ( and 1.0.5 with that I have installed now ) everything works.

With Helium (I tried 1.1.3 and 1.1.4 ) it does not work .
Contrary to when said before the problem is not due to the fact that the state of neighbors remains " 2Way " . I redid the configuration from scratch . The status changes to "Full / Other " but the routes are still not installed . The same configuration works instead with Hydrogen

5

Can you test with a nightly build of lithium?

http://dev.packages.vyos.net/iso/lithium/

6

I just tried with “VyOS-livecd-1502270027-0732ac6-amd64.iso 27-Feb-2015” It does not work.

These are the outputs obtained on lithium:

show ip route ospf

show ip route ospf
Codes: K - kernel route, C - connected, S - static, R - RIP, O - OSPF,
       I - ISIS, B - BGP, > - selected route, * - FIB route

O   10.252.0.0/30 [110/200] is directly connected, tun2, 00:05:31
O   10.252.0.4/30 [110/200] is directly connected, tun21, 00:05:31
O   10.253.0.0/30 [110/10] is directly connected, tun1000, 00:05:31
O   10.254.0.0/30 [110/50] is directly connected, tun0, 00:05:31
O   10.254.0.4/30 [110/200] is directly connected, tun1, 00:05:31
O   10.254.3.0/30 [110/50] is directly connected, tun3, 00:05:31
O   192.168.8.0/24 [110/10] is directly connected, vtun0, 00:05:31

show ip ospf neigh

    Neighbor ID Pri State           Dead Time Address         Interface            RXmtL RqstL DBsmL
2.0.0.1           1 Full/Backup       32.895s 10.252.0.6      tun21:10.252.0.5         0     0     0
2.0.0.2           1 Full/Backup       34.323s 10.252.0.2      tun2:10.252.0.1          0     0     0
3.0.0.1           1 Full/Backup       34.325s 10.254.3.2      tun3:10.254.3.1          0     0     0
0.0.0.2           1 Full/Backup       33.013s 10.254.0.6      tun1:10.254.0.5          0     0     0
0.0.0.1           1 Full/Backup       36.671s 10.254.0.2      tun0:10.254.0.1          0     0     0

show ip ospf database

vega@amoruso-vyos:~$ show ip ospf database

       OSPF Router with ID (Z.Z.Z.Z)

                Router Link States (Area 0.0.0.0)

Link ID         ADV Router      Age  Seq#       CkSum  Link count
0.0.0.1         0.0.0.1           55 0x800000fe 0x06d5 7
0.0.0.2         0.0.0.2           55 0x800000ce 0xbcce 7
2.0.0.1         2.0.0.1           54 0x800000db 0xc129 6
2.0.0.2         2.0.0.2           55 0x800000e4 0x65de 6
3.0.0.1         3.0.0.1           56 0x80000110 0xae70 6
3.0.0.2         3.0.0.2          819 0x80000089 0xb535 4
Z.Z.Z.Z        Z.Z.Z.Z       49 0x80000091 0xd1d4 7

                Net Link States (Area 0.0.0.0)

Link ID         ADV Router      Age  Seq#       CkSum
10.252.0.1      Z.Z.Z.Z        49 0x80000001 0x4804
10.252.0.5      Z.Z.Z.Z        49 0x80000001 0x1237
10.254.0.1      Z.Z.Z.Z        49 0x80000001 0x0c41
10.254.0.5      Z.Z.Z.Z        49 0x80000001 0xf156
10.254.3.1      Z.Z.Z.Z        49 0x80000001 0x0c3b
192.168.3.251   3.0.0.1         1433 0x80000085 0x2719
192.168.253.2   2.0.0.2          864 0x80000087 0x0b34

                Summary Link States (Area 0.0.0.0)

Link ID         ADV Router      Age  Seq#       CkSum  Route
192.168.0.0     0.0.0.1          733 0x80000087 0x330e 192.168.0.0/24
192.168.0.0     0.0.0.2          436 0x80000087 0x2d13 192.168.0.0/24
192.168.99.0    0.0.0.1          733 0x80000089 0x8560 192.168.99.0/24
192.168.99.0    0.0.0.2          436 0x80000089 0x7f65 192.168.99.0/24
192.168.202.0   0.0.0.1          733 0x80000087 0x7cf9 192.168.202.0/24
192.168.202.0   0.0.0.2          436 0x80000087 0x76fe 192.168.202.0/24

                ASBR-Summary Link States (Area 0.0.0.0)

Link ID         ADV Router      Age  Seq#       CkSum
0.0.0.1         0.0.0.2         1443 0x80000086 0x644e
192.168.99.1    0.0.0.1          733 0x80000087 0x7174
192.168.99.1    0.0.0.2          436 0x80000087 0x6b79

                AS External Link States

Link ID         ADV Router      Age  Seq#       CkSum  Route
X.X.X.X   2.0.0.2          864 0x8000008a 0xc349 E2 X.X.X.X/32 [0x0]
192.168.1.0     0.0.0.1          733 0x80000087 0x1896 E2 192.168.1.0/24 [0x0]
192.168.1.0     192.168.99.1    1723 0x800001d1 0xbcd9 E2 192.168.1.0/24 [0x0]
192.168.2.0     2.0.0.1           45 0x80000087 0xfab0 E2 192.168.2.0/24 [0x0]
192.168.6.0     0.0.0.1          734 0x80000087 0x2bb0 E2 192.168.6.0/24 [0x0]
192.168.92.0    2.0.0.1         1288 0x80000089 0x153a E2 192.168.92.0/24 [0x0]
192.168.254.0   2.0.0.2          864 0x8000008a 0x991e E2 192.168.254.0/30 [0x0]

I reboot with 1.0.5 and it work again.
These are the outputs obtained on Hydrogen.
I noticed that there is a difference with 1.0.5 on the neighbors:

show ip ospf neighbor

    Neighbor ID Pri State           Dead Time Address         Interface            RXmtL RqstL DBsmL
2.0.0.1           1 Full/DROther      32.931s 10.252.0.6      tun21:10.252.0.5         0     0     0
2.0.0.2           1 Full/DROther      33.894s 10.252.0.2      tun2:10.252.0.1          0     0     0
3.0.0.1           1 Full/DROther      31.509s 10.254.3.2      tun3:10.254.3.1          0     0     0
0.0.0.2           1 Full/DROther      36.007s 10.254.0.6      tun1:10.254.0.5          0     0     0
0.0.0.1           1 Full/DROther      37.822s 10.254.0.2      tun0:10.254.0.1          0     0     0

show ip ospf database

       OSPF Router with ID (Z.Z.Z.Z)

                Router Link States (Area 0.0.0.0)

Link ID         ADV Router      Age  Seq#       CkSum  Link count
0.0.0.1         0.0.0.1          132 0x80000101 0xfed9 7
0.0.0.2         0.0.0.2          194 0x800000cf 0xbacf 7
2.0.0.1         2.0.0.1          322 0x800000dc 0xbf2a 6
2.0.0.2         2.0.0.2          136 0x800000e5 0x63df 6
3.0.0.1         3.0.0.1          214 0x80000111 0xac71 6
3.0.0.2         3.0.0.2         1346 0x80000089 0xb535 4
Z.Z.Z.Z      Z.Z.Z.Z       131 0x80000097 0x8616 12

                Net Link States (Area 0.0.0.0)

Link ID         ADV Router      Age  Seq#       CkSum
192.168.3.251   3.0.0.1         1960 0x80000085 0x2719
192.168.253.2   2.0.0.2         1391 0x80000087 0x0b34

                Summary Link States (Area 0.0.0.0)

Link ID         ADV Router      Age  Seq#       CkSum  Route
192.168.0.0     0.0.0.1         1261 0x80000087 0x330e 192.168.0.0/24
192.168.0.0     0.0.0.2          963 0x80000087 0x2d13 192.168.0.0/24
192.168.99.0    0.0.0.1         1261 0x80000089 0x8560 192.168.99.0/24
192.168.99.0    0.0.0.2          963 0x80000089 0x7f65 192.168.99.0/24
192.168.202.0   0.0.0.1         1261 0x80000087 0x7cf9 192.168.202.0/24
192.168.202.0   0.0.0.2          963 0x80000087 0x76fe 192.168.202.0/24

                ASBR-Summary Link States (Area 0.0.0.0)

Link ID         ADV Router      Age  Seq#       CkSum
0.0.0.1         0.0.0.2         1971 0x80000086 0x644e
192.168.99.1    0.0.0.1         1261 0x80000087 0x7174
192.168.99.1    0.0.0.2          963 0x80000087 0x6b79

                AS External Link States

Link ID         ADV Router      Age  Seq#       CkSum  Route
X.X.X.X   2.0.0.2         1391 0x8000008a 0xc349 E2 X.X.X.X/32 [0x0]
192.168.1.0     0.0.0.1         1261 0x80000087 0x1896 E2 192.168.1.0/24 [0x0]
192.168.1.0     192.168.99.1     261 0x800001d2 0xbada E2 192.168.1.0/24 [0x0]
192.168.2.0     2.0.0.1          573 0x80000087 0xfab0 E2 192.168.2.0/24 [0x0]
192.168.6.0     0.0.0.1         1261 0x80000087 0x2bb0 E2 192.168.6.0/24 [0x0]
192.168.92.0    2.0.0.1         1815 0x80000089 0x153a E2 192.168.92.0/24 [0x0]
192.168.254.0   2.0.0.2         1391 0x8000008a 0x991e E2 192.168.254.0/30 [0x0]

show ip route ospf

Codes: K - kernel route, C - connected, S - static, R - RIP, O - OSPF,
       I - ISIS, B - BGP, > - selected route, * - FIB route

O   10.252.0.0/30 [110/200] is directly connected, tun2, 00:03:59
O   10.252.0.4/30 [110/200] is directly connected, tun21, 00:03:59
O   10.253.0.0/30 [110/10] is directly connected, tun1000, 00:03:59
O   10.254.0.0/30 [110/50] is directly connected, tun0, 00:03:59
O   10.254.0.4/30 [110/200] is directly connected, tun1, 00:03:59
O   10.254.3.0/30 [110/50] is directly connected, tun3, 00:03:59
O>* 10.254.254.1/32 [110/50] via 10.254.0.2, tun0, 00:03:42
O>* 10.254.254.3/32 [110/51] via 10.254.3.2, tun3, 00:03:53
O>* 10.254.254.5/32 [110/100] via 10.254.0.2, tun0, 00:03:42
O>* 10.254.254.200/32 [110/100] via 10.254.0.2, tun0, 00:03:42
O>* 10.254.254.202/32 [110/100] via 10.254.3.2, tun3, 00:03:53
O>* 10.254.254.203/32 [110/50] via 10.254.3.2, tun3, 00:03:53
O>* 88.41.146.251/32 [110/10] via 10.254.0.2, tun0, 00:03:41
O>* 192.168.0.0/24 [110/61] via 10.254.0.2, tun0, 00:03:42
O>* 192.168.1.0/24 [110/20] via 10.254.0.2, tun0, 00:03:41
O>* 192.168.2.0/24 [110/20] via 10.254.0.2, tun0, 00:03:41
O>* 192.168.3.0/24 [110/51] via 10.254.3.2, tun3, 00:03:53
O>* 192.168.6.0/24 [110/20] via 10.254.0.2, tun0, 00:03:41
O   192.168.8.0/24 [110/10] is directly connected, vtun0, 00:03:59
O>* 192.168.92.0/24 [110/20] via 10.254.0.2, tun0, 00:03:41
O>* 192.168.99.0/24 [110/51] via 10.254.0.2, tun0, 00:03:42
O>* 192.168.202.0/24 [110/61] via 10.254.0.2, tun0, 00:03:42
O>* 192.168.253.0/24 [110/101] via 10.254.0.2, tun0, 00:03:42
O>* 192.168.254.0/30 [110/10] via 10.254.0.2, tun0, 00:03:41
7

Hi, try this:

set interfaces tunnel tun0 ip ospf network point-to-point

8

Thank you. That solved my full day of working the problem. I had a tunnel and a direct connect.