Quantcast
Channel: MikroTik
Viewing all articles
Browse latest Browse all 21138

Beginner Basics • IPv6 default route marked as inactive, despite being pingable

$
0
0
Hello everyone.

I am trying to set up IPv6 on my CRS-326-24G-2S+RM switch, but i'm running into an issue where the default route keeps being marked as inactive, despite being pingable.

My existing routes:
Code:
Flags: D - DYNAMIC; I - INACTIVE, A - ACTIVE; c - CONNECT, s - STATIC; H - HW-OFFLOADEDColumns: DST-ADDRESS, GATEWAY, DISTANCE#      DST-ADDRESS               GATEWAY                    DISTANCE0  IsH ::/0                      fe80::1xxx:xxxx:xxxx:xxxe         1  DAcH 260x:xxxx:xxxx:7100::/64  sfp-sfpplus1                      0  DAcH 260x:xxxx:xxxx:7101::/64  bellflower                        0  DAcH fe80::%sfp-sfpplus1/64    sfp-sfpplus1                      0  DAcH fe80::%bridge/64          bridge                            0  DAcH fe80::%aconite/64         aconite                           0  DAcH fe80::%bellflower/64      bellflower                        0  DAcH fe80::%gardenia/64        gardenia                          0  DAcH fe80::%iris/64            iris                              0  DAcH fe80::%periwinkle/64      periwinkle                        0  DAcH fe80::%senna/64           senna                             0
As you can see, number 0 on the list, the default route, has the "I" flag, which means the route is being marked as inactive.

Ping results when I ping the link-local address specified in the default route:
Code:
[primrose@hyacinth] /ipv6/route> /ping interface=sfp-sfpplus1 fe80::xxxx:xxxx:xxxx:543e  SEQ HOST                                     SIZE TTL TIME       STATUS          0 fe80::xxxx:xxxx:xxxx:543e                  56  64 364us      echo reply      1 fe80::xxxx:xxxx:xxxx:543e                  56  64 328us      echo reply      2 fe80::xxxx:xxxx:xxxx:543e                  56  64 328us      echo reply      3 fe80::xxxx:xxxx:xxxx:543e                  56  64 296us      echo reply      4 fe80::xxxx:xxxx:xxxx:543e                  56  64 307us      echo reply      5 fe80::xxxx:xxxx:xxxx:543e                  56  64 328us      echo reply      sent=6 received=6 packet-loss=0% min-rtt=296us avg-rtt=325us    max-rtt=364us [primrose@hyacinth] /ipv6/route>
I would like to mention that I can ping the uplink interface on the switch from the firewall, and vice versa, but outgoing IPv6 traffic from the switch is always met with a "no route to host" message when pinging an external host, because the default route keeps being marked as inactive for whatever reason, despite being pingable.

If there is any more information that I need to provide, please let me know.

Thanks for taking a look at this post, and thank you in advance for the help.

Statistics: Posted by primrose — Sat Jan 06, 2024 5:35 am



Viewing all articles
Browse latest Browse all 21138

Trending Articles