7951 questions

9403 answers

15104 comments

12979 members

0 votes
57 views 6 comments
by

Hello,

The PDP is set to IPv4+IPv6, and the router gets IPv6 and DNS6 addresses from the mobile network. From the RUTX11 it is possible to ping the DNS6 addresses and other well known servers (yahoo ...). So far so good. 

From another device in the network it is possible to ping the IPv6 addresses of the br-lan interface but not the address of the qmimux0 one, the DNS6 ones, the default route doesn't work or IPv6 forwarding is inoperant.

The interfaces have the following IPv6 addresses:

root@lgrrutx:~# ip -6 a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 state UNKNOWN qlen 1000
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
12: wwan0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 16382 state UNKNOWN qlen 1000
    inet6 fe80::6643:d123:cd42:f0a/64 scope link stable-privacy 
       valid_lft forever preferred_lft forever
16: br-lan: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 state UP qlen 1000
    inet6 2a02:8440:6441:6d18::1/64 scope global noprefixroute 
       valid_lft forever preferred_lft forever
    inet6 fd69:267b:e6f6:10::1/64 scope global noprefixroute 
       valid_lft forever preferred_lft forever
    inet6 fe80::21e:42ff:fe2d:904f/64 scope link 
       valid_lft forever preferred_lft forever
22: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 state UP qlen 1000
    inet6 fe80::21e:42ff:fe2d:9051/64 scope link 
       valid_lft forever preferred_lft forever
23: wlan1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 state UP qlen 1000
    inet6 fe80::21e:42ff:fe2d:9052/64 scope link 
       valid_lft forever preferred_lft forever
24: qmimux0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 state UNKNOWN qlen 1000
    inet6 2a02:8440:6441:6d18:7bf7:f333:c406:e78b/64 scope global noprefixroute 
       valid_lft forever preferred_lft forever
    inet6 fe80::7bf7:f333:c406:e78b/64 scope link stable-privacy 
       valid_lft forever preferred_lft forever

and default routes:

root@lgrrutx:~# ip -6 route show | grep qmimux0 
default from 2a02:8440:6441:6d18::/64 via fe80::d0cf:1c46:4440:cb48 dev qmimux0 proto static metric 512 pref medium
fe80::/64 dev qmimux0 proto kernel metric 256 pref medium

ping6 of the global address of qmimux 0 gives:

[root@lgtsn ~]# ping6 -c 1 2a02:8440:6441:6d18:7bf7:f333:c406:e78b
PING 2a02:8440:6441:6d18:7bf7:f333:c406:e78b(2a02:8440:6441:6d18:7bf7:f333:c406:e78b) 56 data bytes
From 2a02:8440:6441:6d18:f694:14c9:a0c4:9742: icmp_seq=1 Destination unreachable: Address unreachable
--- 2a02:8440:6441:6d18:7bf7:f333:c406:e78b ping statistics ---
1 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms

The default route going through qmimux0 (fe80::d0cf:1c46:4440:cb48) doesn't appear in the ip -6 addr list, and cannot be modified with a ip -6 route change nor deleted and replaced by the link-local one (fe80::7bf7:f333:c406:e78b) a RTNETLINK error is returned. 

Where this fe80::d0cf:1c46:4440:cb48 address comes from ?

I have missed something ?

Regards,

by
Did you ever get any answer to this?
by
No, Teltonika is unable to replicate the issue. The same SIM in a Huaweii B525 works fine both for IPv4 and IPv6. Go figure ...

1 Answer

0 votes
by
Hello,

Regarding the IPv6 address that is not found in the addressing table, it's a Link-Local unicast address for the local network link only, automatically generated for each IPv6 network interface. Same as 169.254.0.0/16

Regards,
Mellow
by
Then it should appear in the ip -6 a list. But it doesn't and this is the issue.

Regards,
by

Hello, 

For the issue, you are having could you try to double-check with your ISP provider if the sim card is supporting IPv6 IP address it can provide network connectivity to the sim card using IPv6 address only. Because if you try pinging the inet6 IP address that is in your qmimux0 you cannot ping it from here: IPv6 Ping | IPv6 Now 

Kindly double-check and let me know.

Regards,
Mellow

by
The IPv6 address appearing above cannot be pinged from the outside this is normal it has changed several times since. The current one (2a02:8440:6240:74a1:7bf7:f333:c406:e78b) cannot either, this is annoying. tcpdump doesn't show anything, not even incoming echo requests.

According to the operator, IPv6 is known to work.

Regards,
by
Hello,

Kindly share with me a copy of the troubleshoot + the tcpdump file of the RUTX11 having this IPv6 address.

Thanks

Regards,
Mellow