Community discussions

MikroTik App
  4. RouterOS
  5. Forwarding Protocols

CRS309: packets go via the wrong gateway (OSPF)

Post Reply
 
crosswind
newbie
Topic Author
Posts: 46
Joined: Tue Feb 18, 2020 3:47 pm

CRS309: packets go via the wrong gateway (OSPF)

Fri Sep 08, 2023 9:56 pm

hello,

i did open a support ticket for this problem (SUP-127514) but i thought i'd ask here too in case i'm doing something wrong...

so i have a CRS309 running OSPF, with this routing table:
Code: Select all
> /ipv6/route/print
Flags: D - DYNAMIC; I - INACTIVE, A - ACTIVE; c - CONNECT, o - OSPF; H - HW-OFFLOADED
Columns: DST-ADDRESS, GATEWAY, DISTANCE
     DST-ADDRESS                 GATEWAY                             DISTANCE
DAoH ::/0                        fe80::764d:28ff:fe43:bf23%vlan4000       110
DAoH ::/96                       fe80::b696:91ff:fe45:a216%vlan102        110
DAoH 2001:8b0:aab5:1::/64        fe80::764d:28ff:fe43:bf23%vlan4000       110
DAoH 2001:8b0:aab5:2::1/128      fe80::1afd:74ff:fef8:7881%vlan102        110
DAoH 2001:8b0:aab5:2::2/128      fe80::1afd:74ff:fef8:7881%vlan102        110
DAoH 2001:8b0:aab5:2::3/128      fe80::1afd:74ff:fef8:7881%vlan102        110
DAcH 2001:8b0:aab5:103::/64      vlan103                                    0
DAcH 2001:8b0:aab5:104::/64      vlan104                                    0
DAoH 2001:8b0:aab5:402::/64      fe80::1afd:74ff:fef8:7881%vlan102        110
DAoH 2001:8b0:aab5:404::/64      fe80::1afd:74ff:fef8:7881%vlan102        110
DAoH 2001:8b0:aab5:405::/64      fe80::1afd:74ff:fef8:7881%vlan102        110
DAoH 2001:8b0:aab5:406::/64      fe80::1afd:74ff:fef8:7881%vlan102        110
DAoH 2001:8b0:aab5:407::/64      fe80::1afd:74ff:fef8:7881%vlan102        110
DAoH 2001:8b0:aab5:409::/64      fe80::1afd:74ff:fef8:7881%vlan102        110
DAoH 2001:8b0:aab5:d000::1/128   fe80::1afd:74ff:fef8:7881%vlan102        110
DAoH 2001:8b0:aab5:d000::2/128   fe80::1afd:74ff:fef8:7881%vlan102        110
DAoH 2001:8b0:aab5:d000::3/128   fe80::1afd:74ff:fef8:7881%vlan102        110
DAoH 2001:8b0:aab5:d000::4/128   fe80::1afd:74ff:fef8:7881%vlan102        110
DAc  2001:8b0:aab5:d100::1/128   loopback                                   0
DAoH 2001:8b0:aab5:d100::2/128   fe80::1afd:74ff:fef8:7881%vlan102        110
DAoH 2001:8b0:aab5:d100::3/128   fe80::764d:28ff:fe43:bf23%vlan4000       110
DAoH 2001:8b0:aab5:d100::4/128   fe80::2ec8:1bff:fe94:96f0%vlan102        110
DAoH 2001:8b0:aab5:d100::5/128   fe80::764d:28ff:fe8e:70c6%vlan102        110
DAoH 2001:8b0:aab5:d100::6/128   fe80::c6ad:34ff:fe18:b962%vlan102        110
DAoH 2001:8b0:aab5:d100::7/128   fe80::c6ad:34ff:fe00:3da1%vlan102        110
DAoH 2001:8b0:aab5:d100::8/128   fe80::764d:28ff:fe8e:7a89%vlan102        110
DIoH 2001:8b0:aab5:fffd::/64     vlan4000                                 110
DAcH 2001:8b0:aab5:fffd::/64     vlan4000                                   0
DAoH 2001:8b0:aab5:ffff::/64     fe80::1afd:74ff:fef8:7881%vlan102        110
DAoH 2001:8b0:aab5:ffff::2/128   fe80::1afd:74ff:fef8:7881%vlan102        110
DAcH fd12:8247:a481:100::/64     vlan100                                    0
D oH fd12:8247:a481:102::/64     vlan102                                  110
DAcH fd12:8247:a481:102::/64     vlan102                                    0
DAoH fd12:8247:a481:102::11/128  fe80::764d:28ff:fe8e:70c6%vlan102        110
DAoH fd12:8247:a481:102::12/128  fe80::c6ad:34ff:fe18:b962%vlan102        110
DAoH fd12:8247:a481:102::13/128  fe80::c6ad:34ff:fe00:3da1%vlan102        110
DAoH fd12:8247:a481:102::16/128  fe80::2ec8:1bff:fe94:96f0%vlan102        110
DAoH fd12:8247:a481:102::17/128  fe80::1afd:74ff:fef8:7881%vlan102        110
DAoH fd12:8247:a481:102::20/128  fe80::b696:91ff:fe45:a216%vlan102        110
DAoH fd12:8247:a481:e000::/64    fe80::764d:28ff:fe43:bf23%vlan4000       110
DAoH fd12:8247:a481:fffc::/64    fe80::764d:28ff:fe43:bf23%vlan4000       110
DAoH fd12:8247:a481:fffc::1/128  fe80::764d:28ff:fe43:bf23%vlan4000       110
DAoH fd12:8247:a481:fffe::/64    fe80::b696:91ff:fe45:a216%vlan102        110
DAoH fd12:8247:a481:fffe::/128   fe80::b696:91ff:fe45:a216%vlan102        110
DAoH fd12:8247:a481:ffff::2/127  fe80::b696:91ff:fe45:a216%vlan102        110
DAoH fd12:8247:a481:ffff::2/128  fe80::b696:91ff:fe45:a216%vlan102        110
DAoH fd7d:6c63:1000:405::/64     fe80::1afd:74ff:fef8:7881%vlan102        110
DAcH fe80::%lan/64               lan                                        0
DAcH fe80::%vlan102/64           vlan102                                    0
DAcH fe80::%vlan100/64           vlan100                                    0
DAcH fe80::%vlan4000/64          vlan4000                                   0
DAcH fe80::%vlan103/64           vlan103                                    0
DAcH fe80::%vlan104/64           vlan104                                    0
DAc  fe80::%loopback/64          loopback
according to this, packets to 2001:8b0:aab5:d100::8 should be going vlan102, which is directly connected. however, they're actually going via the default route (vlan4000):
Code: Select all
traceroute6 to 2001:8b0:aab5:d100::8 (2001:8b0:aab5:d100::8) from 2001:8b0:aab5:104:600f:4784:4d81:a278, 64 hops max, 12 byte packets
 1  2001:8b0:aab5:104::1  0.418 ms  0.288 ms  0.258 ms
 2  2001:8b0:aab5:fffd::2  0.332 ms  0.292 ms  0.275 ms
 3  2001:8b0:aab5:fffd::2  0.347 ms !P  0.311 ms !P  0.294 ms !P
(2001:8b0:aab5:104::1 is the CRS309; 2001:8b0:aab5:fffd::2 is the router advertising the default route.)

packets to 2001:8b0:aab5:d100::6, which is also connected via vlan102 with an identical route, go via the correct interface:
Code: Select all
traceroute6 to 2001:8b0:aab5:d100::6 (2001:8b0:aab5:d100::6) from 2001:8b0:aab5:104:600f:4784:4d81:a278, 64 hops max, 12 byte packets
 1  2001:8b0:aab5:104::1  0.368 ms  0.228 ms  0.218 ms
 2  2001:8b0:aab5:d100::6  0.498 ms  0.302 ms  0.301 ms
if i connect to the CRS309 and try from there, packets do go via the correct path:
Code: Select all
> /ping 2001:8b0:aab5:d100::8
  SEQ HOST                                     SIZE TTL TIME       STATUS
    0 2001:8b0:aab5:d100::8                      56  64 940us      echo reply
    1 2001:8b0:aab5:d100::8                      56  64 936us      echo reply
    sent=2 received=2 packet-loss=0% min-rtt=936us avg-rtt=938us max-rtt=940us

> /tool/traceroute 2001:8b0:aab5:d100::8
Columns: ADDRESS, LOSS, SENT, LAST, AVG, BEST, WORST, STD-DEV
#  ADDRESS                LOSS  SENT  LAST  AVG  BEST  WORST  STD-DEV
1  2001:8b0:aab5:d100::8  0%       3  1ms   0.9  0.9       1        0
since the route works from the switch itself but not from other hosts, it seems like the OSPF routes are not making it to the switch chip's routing table. has anyone else seen anything like this? i find it hard to believe that OSPF simply doesn't work on the CRS309, so i wonder if i've configured something wrongly to cause this.
Top
 
pedrotoscan
just joined
Posts: 2
Joined: Fri Feb 03, 2023 12:25 am

Re: CRS309: packets go via the wrong gateway (OSPF)

Mon Sep 11, 2023 4:33 pm

The both ingress and egress interfaces are L3HW active?
Top
 
User avatar
sirbryan
Member
Member
Posts: 383
Joined: Fri May 29, 2020 6:40 pm
Location: Utah
Contact:
Contact sirbryan

Re: CRS309: packets go via the wrong gateway (OSPF)

Mon Sep 11, 2023 6:42 pm

What version are you running? Have you disabled/enabled L3HW offload after you added all the VLAN interfaces and IP addresses?

Whenever my CRS300's stop routing properly, I have to disable/enable L3HW offload on the switch to get it to resync the bridge and routing tables from the CPU to the switch chip. Things have improved in 7.10 and even more so on the couple of switches I have running 7.11.
Top
 
crosswind
newbie
Topic Author
Posts: 46
Joined: Tue Feb 18, 2020 3:47 pm

Re: CRS309: packets go via the wrong gateway (OSPF)

Tue Sep 12, 2023 2:26 pm

The both ingress and egress interfaces are L3HW active?
yes, all interfaces have L3HW enabled:
Code: Select all
/interface/ethernet/switch> port/print
Columns: NAME, SWITCH, L3-HW-OFFLOADING, STORM-RATE
# NAME         SWITCH   L3-HW-OFFLOADING  STORM-RATE
0 te0          switch1  yes                      100
1 te1          switch1  yes                      100
2 te2          switch1  yes                      100
3 te3          switch1  yes                      100
4 te4          switch1  yes                      100
5 te5          switch1  yes                      100
6 te6          switch1  yes                      100
7 te7          switch1  yes                      100
8 ge0          switch1  yes                      100
9 switch1-cpu  switch1                           100
/interface/ethernet/switch> l3hw-settings/print
            autorestart: no
           fasttrack-hw: yes
                ipv6-hw: yes
    icmp-reply-on-error: yes
  hw-supports-fasttrack: yes
What version are you running?
7.11.2
Have you disabled/enabled L3HW offload after you added all the VLAN interfaces and IP addresses?
i haven't added/changed any VLAN interfaces here since the switch was last rebooted. i did add a new IP address on the switch (unrelated to the non-functional route) but i wasn't aware that required an L3HW restart; it doesn't seem to be on the list of things that require a restart in the documentation.

i did get a response from support but (unsurprisingly) there doesn't seem to be anything obviously wrong, so i'm going to see if i can find a way to reproduce the problem.
Top
 
User avatar
sirbryan
Member
Member
Posts: 383
Joined: Fri May 29, 2020 6:40 pm
Location: Utah
Contact:
Contact sirbryan

Re: CRS309: packets go via the wrong gateway (OSPF)

Tue Sep 12, 2023 4:30 pm

I had issues with 7.11.2 on my CCR2116; had to back it off to 7.11. My CRS310/318's are running 7.10, and my CRS317 and 2216's are on 7.11.

Whenever I have issues with L3HW offload, even for devices that have been running for hours or months, I end up bouncing it just to ensure it transfers everything.
Top
Post Reply

Who is online

Users browsing this forum: baragoon and 34 guests
  4. RouterOS
  5. Forwarding Protocols