Page 1 of 1

OSPF routes marked invalid

Posted: Fri Jul 03, 2020 8:30 pm
by mafiosa
I have established ospf neighborship with other mikrotik routers yet the ospf routes learnt are marked as invalid on the router running rosv7 beta 8

Re: OSPF routes marked invalid

Posted: Wed Jul 22, 2020 1:30 pm
by oreggin
Hi!
I have a ROS v7.1ß1 test setup with CHR on qemus and I have the same issue with OSPFv2. All of my ipv4 ospf routes duplicated and inactive:
[admin@rtr1.CPE] > routing/ospf/interface-state/print 
Flags: D - dynamic; V - virtual-interface 
 0 D  address=fe80::d012:2bff:fe83:2e99%Loopback0 area=backbone6 instance-id=0 state="DR" dr=10.0.10.11 bdr=0.0.0.0 

 1 D  address=10.0.10.11%Loopback0 area=backbone4 instance-id=0 state="DR" dr=10.0.10.11 bdr=0.0.0.0 

 2 D  address=fe80::a00:27ff:fe00:5102%ether2 area=backbone6 instance-id=0 state="Point-to-Point" 

 3 D  address=10.0.1.2%ether2 area=backbone4 instance-id=0 state="Point-to-Point" 
[admin@rtr1.CPE] > routing/ospf/neighbor-state/print  
Flags: X - disabled, I - inactive, D - dynamic 
 0 D address=fe80::a00:27ff:fe00:4101%ether2 router-id=10.0.10.1 state="Full" 

 1 D address=10.0.1.1 router-id=10.0.10.1 state="Full" 
[admin@rtr1.CPE] > ip route/print detail where ospf     
Flags: D - dynamic; X - disabled, I - inactive, A - active; C - connect, S - static, r - rip, b - bgp, o - ospf, d - dhcp, v - vpn, m - modem; + - ecmp 
   DIo  dst-address=10.0.0.0/30 routing-table=main gateway=ether2 type=unicast distance=110 scope=20 target-scope=10 

   DIo  dst-address=10.0.0.0/30 routing-table=main gateway="" type=unicast distance=110 scope=20 target-scope=10 

   DIo  dst-address=10.0.0.4/30 routing-table=main gateway=ether2 type=unicast distance=110 scope=20 target-scope=10 

   DIo  dst-address=10.0.0.4/30 routing-table=main gateway="" type=unicast distance=110 scope=20 target-scope=10 

   DIo  dst-address=10.0.0.8/30 routing-table=main gateway=ether2 type=unicast distance=110 scope=20 target-scope=10 

   DIo  dst-address=10.0.0.8/30 routing-table=main gateway="" type=unicast distance=110 scope=20 target-scope=10 

   DIo  dst-address=10.0.0.12/30 routing-table=main gateway=ether2 type=unicast distance=110 scope=20 target-scope=10 

   DIo  dst-address=10.0.0.12/30 routing-table=main gateway="" type=unicast distance=110 scope=20 target-scope=10 

etc...
Intersting is OSPFv3 works fine:
[admin@rtr1.CPE] > ipv6/route/print detail where ospf
Flags: D - dynamic; X - disabled, I - inactive, A - active; C - connect, S - static, r - rip, b - bgp, o - ospf, d - dhcp, v - vpn, m - modem; + - ecmp 
   DAo  dst-address=b00b::10:0:10:1 routing-table=main gateway=fe80::a00:27ff:fe00:4101%ether2 immediate-gw=fe80::a00:27ff:fe00:4101%ether2 type=unicast distance=110 scope=20 
        target-scope=10 

   DAo  dst-address=b00b::10:0:10:2 routing-table=main gateway=fe80::a00:27ff:fe00:4101%ether2 immediate-gw=fe80::a00:27ff:fe00:4101%ether2 type=unicast distance=110 scope=20 
        target-scope=10 

   DAo  dst-address=b00b::10:0:10:3 routing-table=main gateway=fe80::a00:27ff:fe00:4101%ether2 immediate-gw=fe80::a00:27ff:fe00:4101%ether2 type=unicast distance=110 scope=20 
        target-scope=10 

   DAo  dst-address=b00b::10:0:10:4 routing-table=main gateway=fe80::a00:27ff:fe00:4101%ether2 immediate-gw=fe80::a00:27ff:fe00:4101%ether2 type=unicast distance=110 scope=20 
        target-scope=10 

   DAo  dst-address=b00b::10:0:10:5 routing-table=main gateway=fe80::a00:27ff:fe00:4101%ether2 immediate-gw=fe80::a00:27ff:fe00:4101%ether2 type=unicast distance=110 scope=20 
        target-scope=10 

   DAo  dst-address=b00b::10:0:10:6 routing-table=main gateway=fe80::a00:27ff:fe00:4101%ether2 immediate-gw=fe80::a00:27ff:fe00:4101%ether2 type=unicast distance=110 scope=20 
        target-scope=10 

   DIo  dst-address=b00b::10:0:10:11 routing-table=main gateway=Loopback0 type=unicast distance=110 scope=20 target-scope=10 

   DAo  dst-address=b00b::10:0:10:12 routing-table=main gateway=fe80::a00:27ff:fe00:4101%ether2 immediate-gw=fe80::a00:27ff:fe00:4101%ether2 type=unicast distance=110 scope=20 
        target-scope=10 

   DAo  dst-address=b00b::10:0:10:13 routing-table=main gateway=fe80::a00:27ff:fe00:4101%ether2 immediate-gw=fe80::a00:27ff:fe00:4101%ether2 type=unicast distance=110 scope=20 
        target-scope=10 

   DAo  dst-address=b00b::10:0:10:14 routing-table=main gateway=fe80::a00:27ff:fe00:4101%ether2 immediate-gw=fe80::a00:27ff:fe00:4101%ether2 type=unicast distance=110 scope=20 
        target-scope=10 

   DAo  dst-address=b00b::10:0:10:15 routing-table=main gateway=fe80::a00:27ff:fe00:4101%ether2 immediate-gw=fe80::a00:27ff:fe00:4101%ether2 type=unicast distance=110 scope=20 
        target-scope=10 

   DAo  dst-address=b00b::10:0:10:16 routing-table=main gateway=fe80::a00:27ff:fe00:4101%ether2 immediate-gw=fe80::a00:27ff:fe00:4101%ether2 type=unicast distance=110 scope=20 
        target-scope=10 
[admin@rtr1.CPE] >

Re: OSPF routes marked invalid

Posted: Wed Jul 22, 2020 3:00 pm
by mrz
Does it start to work if you change interface type from point-to-point to broadcast?

Re: OSPF routes marked invalid

Posted: Thu Jul 23, 2020 12:05 am
by mafiosa
Does it start to work if you change interface type from point-to-point to broadcast?
No same issue even with point to point and broadcast!
Also for bgp nexthop is getting changed to :: which is invalid as a result all routes become invalid.

Re: OSPF routes marked invalid

Posted: Thu Jul 23, 2020 11:03 am
by mducharme
I am having this issue with only some of my OSPFv2 routes.

I have OSPFv2 routes across an L2TP tunnel to a RouterOS 6 device - these all show as invalid. I also have OSPFv2 routes to a RouterOS 6 device across an EoIP tunnel - these seem to work.

Re: OSPF routes marked invalid

Posted: Thu Jul 23, 2020 5:15 pm
by mrz
FYI problem is only on P2P interfaces (not ospf interface type but actual P2P interfaces like l2tp etc. )
We will fix the problem as soon as possible.

Re: OSPF routes marked invalid

Posted: Fri Jul 24, 2020 11:39 am
by oreggin
Does it start to work if you change interface type from point-to-point to broadcast?
Yes, thanks mrz for workaround.

Re: OSPF routes marked invalid

Posted: Sat Jul 25, 2020 3:20 pm
by mafiosa
FYI problem is only on P2P interfaces (not ospf interface type but actual P2P interfaces like l2tp etc. )
We will fix the problem as soon as possible.
Yes problem is with p2p as interface types and p2p tunnel interfaces

Re: OSPF routes marked invalid

Posted: Sat Aug 01, 2020 3:00 pm
by mafiosa
FYI problem is only on P2P interfaces (not ospf interface type but actual P2P interfaces like l2tp etc. )
We will fix the problem as soon as possible.
Hello I can confirm that with gre tunnel interface if I set network type to broadcast then the ospf routes work. However on enabling ospfv3 the cou usage increates to 50-70% and sometimes lan interfaces stop processing traffic (ipv4)