😔 Can anyone help me to solve my ipv6 issue with RM520N?

Hi,
i am using GL-inet GL-X3000 with RM520N 5G module.
Currently ipv6 settings on passthrough. but cant ping to ipv6 address from my windows pc. some time can’t ping on android mobile, some time can’t ping on Raspberry pi, some time can’t ping from windows… no issue with ipv4.

Many RM520N user having same problem with module and already posted on forum but no any solution found.

  • Current firmware : RM520NGLAAR01A07M4G

  • Already test bellow firmware but same issue.
    RM520NGLAAR01A08M4G
    RM520NGLAAR03A03M4G
    RM520NGLAAR03A04M4G

  • check bellow screenshots.
    got public ipv6 on network properties. but can’t ping to ipv6 address. also same on android get public ipv6 on wifi connection but can’t ping to ipv6 address.

Please help me to solve…
Thank you, @mikey @silvia @george.gao @keven.wu-Q @Great.Zheng-Q @Linkin-Q @Bean.Wang-Q

How is the RM520N connected?
Could you show the network topolgy?
About the GL-inet GL-X3000, is it developed by yourself?
As I guess it is the GL-inet GL-X3000 not working well and it do not support IPv6 fully. And you catch the wireshark log on the Windows PC.
And see whether you can see the router advertisement packet and whether it includes the correct ipv6 prefix and Ipv6 DNS.

  • I use GL-inet’s GL-X3000 5G CPE and RM520N use by company inside this 5G CPE. GL-x3000

  • GL-X3000 (router mode) > Asus GT-X11000 (Access point mode) > Windows PC (LAN) and all clients connected with Asus.

  • GL-X3000’s ipv6 settings on Passthrough

When run tracert [2404:6800:4009:829::200e] (google .com’s ipv6) on window command prompt get bellow wireshark log.

Please check the IPv6 Router Advertisement.
The GL-X3000 should send the RA to the Windows PC.

image
If this is the RA from the GL-X3000, it might get the ipv6.

Please also check

AT+CGDCONT?

AT+CGCONTRDP

AT+CGPADDR

AT+CGDCONT?

+CGDCONT: 1,"IPV4V6","jionet","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,0,,,,,,,,,"",,,,0
+CGDCONT: 2,"IPV4V6","ims","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,0,,,,,,,,,"",,,,0
+CGDCONT: 3,"IPV4V6","sos","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",0,0,0,1,,,,,,,,,"",,,,0

OK

AT+CGCONTRDP

+CGCONTRDP: 1,0,"jionet","36.9.64.193.16.24.234.43.128.0.0.0.0.0.0.0", "254.128.0.0.0.0.0.0.138.233.164.255.254.30.74.108", "36.5.2.0.8.0.0.0.0.0.0.0.0.0.0.17", "36.5.2.0.8.0.0.0.0.0.0.0.0.0.0.17"
+CGCONTRDP: 2,0,"ims","36.9.65.1.0.7.172.223.128.0.0.0.0.0.0.0", "254.128.0.0.0.0.0.0.138.233.164.255.254.10.168.216", "36.5.2.0.8.0.0.0.0.0.0.0.0.0.0.17", "36.5.2.0.8.0.0.0.0.0.0.0.0.0.0.17","36.5.2.0.6.179.180.113.0.33.0.0.0.0.0.20","36.5.2.0.6.13.180.113.0.33.0.0.0.0.1.62"

OK

AT+CGPADDR`

+CGPADDR: 1,"36.9.64.193.16.24.234.43.128.0.0.0.0.0.0.0"
+CGPADDR: 2,"36.9.65.1.0.7.172.223.128.0.0.0.0.0.0.0"
+CGPADDR: 3,"0.0.0.0","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0"

OK

Seems everything is fine.

You can try to ping the

2001:4860:4860::8888

If it is a RaspberryPi, maybe it is much easier to check.
You can show the ip -6 route and cat /etc/resolv.conf.

It is difficult to debug, it is better to contact with the local FAE and provide the qxdm log of the RM520N.
And we need to compare the wireshark log/tcpdump log with the qxdm log.

i had restore openwrt from tar.gz backup files that i had create after add static ips for clients. may be something is problem after restore from backup…
so, i reset router settings and now problem is solved. all devices got ipv6 and also working too.

:heart: Thank you very much @Bean.Wang-Q for your efforts and giving your valuable time to me.