Hello, the latest quectel-CM consultation

What is the latest version of quectel-CM? I’m using his version 1.6.4 can only get IPV6 can’t send it down, can’t get IPV6PD, is this something that needs to be set?

Do you see any evidence that your carrier can assign a prefix?

Yes, if I use mbim mode, it can assign ipv6PD

The mode is local to you, so your carrier have no visibility of MBIM, QMI, etc.
In which mode you can’t get the prefix then? Is it QMI?
What modem do you have? Assuming it is something like RM5XX, I suggest using ECM + IPPT, then run some DHCPv6 client and see what it will get.
I don’t know what OS and which dhcpv6 client you use, but from the past I know that on plain Ubuntu Linux wide-dhcpv6 client was able to obtain a prefix from the mobile carrier.
I’m curious what you will see in response to


I use Openwrt as the system, use qmi to run quectel-CM-4-6 to get IPV4 and IPV6, but there is no IPV6PD, so I can’t send IPV6 to my secondary device.

[10-23_01:10:41:165] qmap_settings.rx_urb_size = 15360
[10-23_01:10:41:165] qmap_settings.ul_data_aggregation_max_datagrams = 11
[10-23_01:10:41:165] qmap_settings.ul_data_aggregation_max_size = 8192
[10-23_01:10:41:165] qmap_settings.dl_minimum_padding = 0
[10-23_01:10:41:186] requestGetSIMStatus SIMStatus: SIM_READY
[10-23_01:10:41:189] requestGetProfile[1] ///0/IPV4V6
[10-23_01:10:41:192] requestRegistrationState2 MCC: 460, MNC: 1, PS: Attached, DataCap: 5G_SA
[10-23_01:10:41:194] requestQueryDataCall IPv4ConnectionStatus: DISCONNECTED
[10-23_01:10:41:197] requestQueryDataCall IPv6ConnectionStatus: DISCONNECTED
[10-23_01:10:41:197] ifconfig rmnet_mhi0 down
[10-23_01:10:41:203] ifconfig rmnet_mhi0.1
[10-23_01:10:41:206] ifconfig rmnet_mhi0.1 down
[10-23_01:10:41:637] requestSetupDataCall WdsConnectionIPv4Handle: 0x38153ff0
[10-23_01:10:41:661] requestSetupDataCall WdsConnectionIPv6Handle: 0x38222cf0
[10-23_01:10:41:670] ifconfig rmnet_mhi0 up
[10-23_01:10:41:677] ifconfig rmnet_mhi0.1 up
[10-23_01:10:41:683] busybox udhcpc -f -n -q -t 5 -i rmnet_mhi0.1
udhcpc: started, v1.33.2
udhcpc: sending discover
udhcpc: sending select for
udhcpc: lease of obtained, lease time 7200
[10-23_01:10:42:058] udhcpc: ifconfig rmnet_mhi0.1 netmask broadcast +
[10-23_01:10:42:065] udhcpc: setting default routers:
[10-23_01:10:42:172] ip -6 address flush dev rmnet_mhi0.1
[10-23_01:10:42:178] ip -6 address add 2408:8459:1020:2153:3ca4:a878:4dae:1edc/64 dev rmnet_mhi0.1
[10-23_01:10:42:182] ip -6 route add default dev rmnet_mhi0.1
[10-23_01:10:44:247] requestDeactivateDefaultPDP WdsConnectionIPv4Handle
[10-23_01:10:44:251] requestDeactivateDefaultPDP WdsConnectionIPv6Handle
[10-23_01:10:44:311] ifconfig rmnet_mhi0 down
[10-23_01:10:44:324] ifconfig rmnet_mhi0.1
[10-23_01:10:44:332] ifconfig rmnet_mhi0.1 down
[10-23_01:10:44:361] QmiWwanThread exit
[10-23_01:10:44:361] qmi_main exit

In OpenWrt you need to run something like this:
odhcp6c -e -v -P{prefix size or 0 for auto} -t120 {interface name}

How is this command different from adding a dhcp V6 client to a web page?