WIKIABOUT

FOR TIPS, gUIDES & TUTORIALS

subscribe to our Youtube

GO TO YOUTUBE

14455 questions

17168 answers

28195 comments

0 members

Most popular tags

rut955 rut240 rut950 rutx11 rms vpn to openvpn wifi not sms trb140 firmware connection - ipsec on rutx12 rutx09 modbus
We are migrating to our new platform at https://community.teltonika.lt. Moving forward, you can continue discussions on this new platform. This current platform will be temporarily maintained for reference purposes.

IPv6 IP successfully retreived from SLAAC, but no route is added

0 votes
338 views 7 comments
by anonymous

My teltonika is successfully getting an IPv6 using SLAAC but it seems it's not routable.

root@RUTX11:~# ip -6 addr
14: br-lan: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 state UP qlen 1000
    inet6 2001:9b1:dfc:a500::1/64 scope global dynamic noprefixroute
       valid_lft 85412sec preferred_lft 53012sec
    inet6 2001:9b1:dfc:a510::1/64 scope global deprecated dynamic
       valid_lft 6382sec preferred_lft 0sec
    inet6 fd6c:813b:41d9:10::1/64 scope global deprecated dynamic
       valid_lft 6382sec preferred_lft 0sec
    inet6 fd6c:813b:41d9::1/64 scope global noprefixroute
       valid_lft forever preferred_lft forever
    inet6 fe80::21e:42ff:fe35:9622/64 scope link
       valid_lft forever preferred_lft forever

root@RUTX11:~# ping -6 ftp.sunet.se
PING ftp.sunet.se (2001:6b0:19::163): 56 data bytes
^C
--- ftp.sunet.se ping statistics ---
4 packets transmitted, 0 packets received, 100% packet loss

What can I do to further debug this issue?

1 Answer

+1 vote
by anonymous

Hello,

Would it be possible to see the routing table:

ip -6 route show

and the rules table:

ip -6 rule show

To try to see what is going on you can do a tcpdump from another console:

tcpdump -i any -n -v 'icmp6'

What do you see when you execute the ping ?

Regards,

Best answer
by anonymous

root@RUTX11:~# ip -6 route show
default from 2001:9b1:dfc:a500::/56 via fe80::a67b:2cff:fe9e:ea01 dev eth1 proto static metric 512 pref medium
2001:9b1:dfc:a500::/64 dev br-lan proto static metric 1 pref medium
unreachable 2001:9b1:dfc:a500::/56 dev lo proto static metric 2147483647 pref medium
fd60:371a:3575::/64 dev br-lan proto static metric 1 pref medium
unreachable fd60:371a:3575::/48 dev lo proto static metric 2147483647 pref medium
fe80::/64 dev br-lan proto kernel metric 256 pref medium
fe80::/64 dev eth1 proto kernel metric 256 pref medium

root@RUTX11:~# ip -6 rule show
0:      from all lookup local
32766:  from all lookup main
4200000000:     from 2001:9b1:dfc:a500::1/60 iif br-lan unreachable
4200000001:     from all iif lo failed_policy
4200000003:     from all iif eth1 failed_policy
4200000003:     from all iif eth1 failed_policy
4200000013:     from all iif br-lan failed_policy
 

root@RUTX11:~# tcpdump -i any -n -v 'icmp6'
tcpdump: listening on any, link-type LINUX_SLL (Linux cooked v1), capture size 262144 bytes
02:00:45.475582 IP6 (flowlabel 0x7a94b, hlim 64, next-header ICMPv6 (58) payload length: 64) 2001:9b1:dfc:a500::1 > 2001:6b0:19::165: [icmp6 sum ok] ICMP6, echo request, seq 0
02:00:46.310043 IP6 (flowlabel 0xaa3d2, hlim 64, next-header ICMPv6 (58) payload length: 116) ::1 > ::1: [icmp6 sum ok] ICMP6, destination unreachable, unreachable port, ::1 udp port 33780
02:00:46.475904 IP6 (flowlabel 0x7a94b, hlim 64, next-header ICMPv6 (58) payload length: 64) 2001:9b1:dfc:a500::1 > 2001:6b0:19::165: [icmp6 sum ok] ICMP6, echo request, seq 1
02:00:47.476229 IP6 (flowlabel 0x7a94b, hlim 64, next-header ICMPv6 (58) payload length: 64) 2001:9b1:dfc:a500::1 > 2001:6b0:19::165: [icmp6 sum ok] ICMP6, echo request, seq 2
02:00:48.476534 IP6 (flowlabel 0x7a94b, hlim 64, next-header ICMPv6 (58) payload length: 64) 2001:9b1:dfc:a500::1 > 2001:6b0:19::165: [icmp6 sum ok] ICMP6, echo request, seq 3
02:00:49.476866 IP6 (flowlabel 0x7a94b, hlim 64, next-header ICMPv6 (58) payload length: 64) 2001:9b1:dfc:a500::1 > 2001:6b0:19::165: [icmp6 sum ok] ICMP6, echo request, seq 4
02:00:50.477185 IP6 (flowlabel 0x7a94b, hlim 64, next-header ICMPv6 (58) payload length: 64) 2001:9b1:dfc:a500::1 > 2001:6b0:19::165: [icmp6 sum ok] ICMP6, echo request, seq 5
02:00:51.477519 IP6 (flowlabel 0x7a94b, hlim 64, next-header ICMPv6 (58) payload length: 64) 2001:9b1:dfc:a500::1 > 2001:6b0:19::165: [icmp6 sum ok] ICMP6, echo request, seq 6
02:00:51.948014 IP6 (hlim 255, next-header ICMPv6 (58) payload length: 32) :: > ff02::1:ff60:c853: [icmp6 sum ok] ICMP6, neighbor solicitation, length 32, who has fe80::ba27:ebff:fe60:c853
          unknown option (14), length 8 (1):
          0x0000:  c674 b151 2abe
02:00:51.948014 IP6 (hlim 255, next-header ICMPv6 (58) payload length: 32) :: > ff02::1:ff60:c853: [icmp6 sum ok] ICMP6, neighbor solicitation, length 32, who has fe80::ba27:ebff:fe60:c853
          unknown option (14), length 8 (1):
          0x0000:  c674 b151 2abe

Added eth1 output

root@RUTX11:~# tcpdump -i eth1 -n -v 'icmp6'
tcpdump: listening on eth1, link-type EN10MB (Ethernet), capture size 262144 bytes
02:08:47.375798 IP6 (flowlabel 0x7a94b, hlim 64, next-header ICMPv6 (58) payload length: 64) 2001:9b1:dfc:a500::1 > 2001:6b0:19::165: [icmp6 sum ok] ICMP6, echo request, seq 0
02:08:48.376101 IP6 (flowlabel 0x7a94b, hlim 64, next-header ICMPv6 (58) payload length: 64) 2001:9b1:dfc:a500::1 > 2001:6b0:19::165: [icmp6 sum ok] ICMP6, echo request, seq 1
02:08:49.376423 IP6 (flowlabel 0x7a94b, hlim 64, next-header ICMPv6 (58) payload length: 64) 2001:9b1:dfc:a500::1 > 2001:6b0:19::165: [icmp6 sum ok] ICMP6, echo request, seq 2
02:08:50.376760 IP6 (flowlabel 0x7a94b, hlim 64, next-header ICMPv6 (58) payload length: 64) 2001:9b1:dfc:a500::1 > 2001:6b0:19::165: [icmp6 sum ok] ICMP6, echo request, seq 3
02:08:51.377132 IP6 (flowlabel 0x7a94b, hlim 64, next-header ICMPv6 (58) payload length: 64) 2001:9b1:dfc:a500::1 > 2001:6b0:19::165: [icmp6 sum ok] ICMP6, echo request, seq 4
02:08:52.377456 IP6 (flowlabel 0x7a94b, hlim 64, next-header ICMPv6 (58) payload length: 64) 2001:9b1:dfc:a500::1 > 2001:6b0:19::165: [icmp6 sum ok] ICMP6, echo request, seq 5
02:08:53.377761 IP6 (flowlabel 0x7a94b, hlim 64, next-header ICMPv6 (58) payload length: 64) 2001:9b1:dfc:a500::1 > 2001:6b0:19::165: [icmp6 sum ok] ICMP6, echo request, seq 6
02:08:54.378066 IP6 (flowlabel 0x7a94b, hlim 64, next-header ICMPv6 (58) payload length: 64) 2001:9b1:dfc:a500::1 > 2001:6b0:19::165: [icmp6 sum ok] ICMP6, echo request, seq 7
02:08:54.402591 IP6 (hlim 255, next-header ICMPv6 (58) payload length: 32) fe80::21e:42ff:fe35:9623 > fe80::a67b:2cff:fe9e:ea01: [icmp6 sum ok] ICMP6, neighbor solicitation, length 32, who has fe80::a67b:2cff:fe9e:ea01
          source link-address option (1), length 8 (1): 00:1e:42:35:96:23
02:08:54.404794 IP6 (class 0xc0, hlim 255, next-header ICMPv6 (58) payload length: 32) fe80::a67b:2cff:fe9e:ea01 > fe80::21e:42ff:fe35:9623: [icmp6 sum ok] ICMP6, neighbor advertisement, length 32, tgt is fe80::a67b:2cff:fe9e:ea01, Flags [router, solicited, override]
          destination link-address option (2), length 8 (1): 00:00:5e:00:01:6b
02:08:55.378369 IP6 (flowlabel 0x7a94b, hlim 64, next-header ICMPv6 (58) payload length: 64) 2001:9b1:dfc:a500::1 > 2001:6b0:19::165: [icmp6 sum ok] ICMP6, echo request, seq 8
02:08:56.378655 IP6 (flowlabel 0x7a94b, hlim 64, next-header ICMPv6 (58) payload length: 64) 2001:9b1:dfc:a500::1 > 2001:6b0:19::165: [icmp6 sum ok] ICMP6, echo request, seq 9
02:08:57.378955 IP6 (flowlabel 0x7a94b, hlim 64, next-header ICMPv6 (58) payload length: 64) 2001:9b1:dfc:a500::1 > 2001:6b0:19::165: [icmp6 sum ok] ICMP6, echo request, seq 10
02:08:58.379420 IP6 (flowlabel 0x7a94b, hlim 64, next-header ICMPv6 (58) payload length: 64) 2001:9b1:dfc:a500::1 > 2001:6b0:19::165: [icmp6 sum ok] ICMP6, echo request, seq 11
02:08:59.379771 IP6 (flowlabel 0x7a94b, hlim 64, next-header ICMPv6 (58) payload length: 64) 2001:9b1:dfc:a500::1 > 2001:6b0:19::165: [icmp6 sum ok] ICMP6, echo request, seq 12
02:09:00.380057 IP6 (flowlabel 0x7a94b, hlim 64, next-header ICMPv6 (58) payload length: 64) 2001:9b1:dfc:a500::1 > 2001:6b0:19::165: [icmp6 sum ok] ICMP6, echo request, seq 13
02:09:01.380358 IP6 (flowlabel 0x7a94b, hlim 64, next-header ICMPv6 (58) payload length: 64) 2001:9b1:dfc:a500::1 > 2001:6b0:19::165: [icmp6 sum ok] ICMP6, echo request, seq 14
02:09:02.380668 IP6 (flowlabel 0x7a94b, hlim 64, next-header ICMPv6 (58) payload length: 64) 2001:9b1:dfc:a500::1 > 2001:6b0:19::165: [icmp6 sum ok] ICMP6, echo request, seq 15
02:09:03.380988 IP6 (flowlabel 0x7a94b, hlim 64, next-header ICMPv6 (58) payload length: 64) 2001:9b1:dfc:a500::1 > 2001:6b0:19::165: [icmp6 sum ok] ICMP6, echo request, seq 16
^C
19 packets captured
19 packets received by filter
0 packets dropped by kernel
 

by anonymous

So nothing comes back. Redo the tcpdump with:

tcpdump -i eth1 -n -v 'icmp6'

and retry the ping. What do you see ?

 

by anonymous
The echo request goes out on eth1 as can be seen on the tcpdump output, so this part is correct. What do you have at the other end of eth1 ?
by anonymous
The echo request goes out on eth1 as can be seen on the tcpdump output, so this part is correct. What do you have at the other end of eth1 ?
That would be media converter for the fibre.
I feel that there have to be some error with how the router gets the routing details for ipv6, it just gets its ipv6-range and then is happy with that.

by anonymous

The default route looks correct:

default from 2001:9b1:dfc:a500::/56 via fe80::a67b:2cff:fe9e:ea01 dev eth1 proto static metric 512 pref medium

and the echo request goes out as expected so the issue must be somewhere else. What is the equipment facing the router ?

by anonymous
It's a inteno device. It's very common here in Sweden for fibre installation, it's screwed to the wall so I don't want to tear it down, but it should be similar to this linked item. The exact model could be something else.

https://www.tradera.com/item/121407/592087090/inteno-xg6846-r1-cpe-fiberkonverterare-mediaomvandlare-

IPv6 has worked before so it might be something the ISP has messed  up if everything looks alright to you. I'll try lodge a ticket to them and see what they say.
by anonymous
update!

I talked to the ISP and they told they have had some issues with IPv6 and it is fixed now, so it seems the error was in their end. Thanks for the support to pinpoint the error though.