RM500Q) udhcpc(with QCM) is ok. but ping fail to public_url(include DNS server)

Hello all,

I am using a RM500Q-GL on NXP i.MX8QM with kernel_5.10.52. (try with 5G)
I have compiled the newest “qmi_wwan_q.c” driver (v1.2.1) and QCM(v1.6.2).
and result log is looks like fine.
DHCP is OK, DNS is OK…

root@qm:~/QCM# ./quectel-CM/quectel-CM -s internet.lguplus.co.kr &
[1] 1207
[03-24_19:26:08:422] QConnectManager_Linux_V1.6.2
[03-24_19:26:08:423] Find /sys/bus/usb/devices/1-1 idVendor=0x2c7c idProduct=0x800, bus=0x001, dev=0x002
[03-24_19:26:08:424] Auto find qmichannel = /dev/cdc-wdm0
[03-24_19:26:08:424] Auto find usbnet_adapter = wwan0
[03-24_19:26:08:424] netcard driver = qmi_wwan_q, driver version = V1.2.1
[03-24_19:26:08:424] qmap_mode = 1, qmap_version = 9, qmap_size = 31744, muxid = 0x81, qmap_netcard = wwan0_1
[03-24_19:26:08:425] Modem works in QMI mode
[03-24_19:26:08:444] cdc_wdm_fd = 7
root@42dot-ak7:~/QCM# [03-24_19:26:09:445] QmiWwanInit message timeout
[03-24_19:26:10:726] Get clientWDS = 15
[03-24_19:26:10:758] Get clientDMS = 1
[03-24_19:26:10:790] Get clientNAS = 4
[03-24_19:26:10:822] Get clientUIM = 1
[03-24_19:26:10:853] Get clientWDA = 1
[03-24_19:26:10:886] requestBaseBandVersion RM500QGLABR11A01M4G_KR
[03-24_19:26:10:917] qmap_settings.rx_urb_size = 31744[   58.009831] net wwan0: ul_data_aggregation_max_datagrams=11, ul_data_aggregation_max_size=4096, dl_minimum_padding=0

[03-24_19:26:10:918] qmap_settings.ul_data_aggregation_max_datagrams  = 11
[03-24_19:26:10:918] qmap_settings.ul_data_aggregation_max_size       = 4096
[03-24_19:26:10:918] qmap_settings.dl_minimum_padding                 = 0
[03-24_19:26:11:046] requestGetSIMStatus SIMStatus: SIM_READY
[03-24_19:26:11:078] requestGetProfile[1] internet.lguplus.co.kr///0/IPV4V6
[03-24_19:26:11:078] requestSetProfile[1] internet.lguplus.co.kr///0/IPV4
[03-24_19:26:11:142] requestRegistrationState2 MCC: 450, MNC: 6, PS: Attached, DataCap: 5G_NSA
[03-24_19:26:11:173] requestQueryDataCall IPv4ConnectionStatus: DISCONNECTED
[03-24_19:26:11:174] ifconfig wwan0 down
[03-24_19:26:11:184] ifconfig wwan0_1 0.0.0.0
SIOCSIFFLAGS: Network is down
[03-24_19:26:11:192] ifconfig wwan0_1 down
[03-24_19:26:11:238] requestSetupDataCall WdsConnectionIPv4Handle: 0xe55cfae0
[   58.457773] net wwan0: link_state 0x0 -> 0x1
[03-24_19:26:11:370] change mtu 1500 -> 1428
[03-24_19:26:11:371] ifconfig wwan0 up
[   58.471752] IPv6: ADDRCONF(NETDEV_CHANGE): wwan0: link becomes ready
[03-24_19:26:11:381] ifconfig wwan0_1 up
[03-24_19:26:11:399] busybox udhcpc -f -n -q -t 5 -i wwan0_1
udhcpc: started, v1.33.2
udhcpc: sending discover
udhcpc: sending select for 10.221.240.40
udhcpc: lease of 10.221.240.40 obtained, lease time 7200
[03-24_19:26:11:668] /etc/udhcpc.d/50default: Adding DNS 106.101.252.4
[03-24_19:26:11:668] /etc/udhcpc.d/50default: Adding DNS 211.36.129.4
[   59.491868] IPv6: ADDRCONF(NETDEV_CHANGE): wwan0_1: link becomes ready

But It cannot be ping with common URL as like ‘www.google.com
DNS server that auto added by QCM is also same situation.

TRX count is little bit increased with ping and after_udhcpc

wwan0: flags=193<UP,RUNNING,NOARP>  mtu 1500
        inet6 fe80::fc7c:65ff:fe76:a97  prefixlen 64  scopeid 0x20<link>
        ether fe:7c:65:76:0a:97  txqueuelen 1000  (Ethernet)
        RX packets 2  bytes 632 (632.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 12  bytes 1312 (1.2 KiB)
        TX errors 0  dropped 10 overruns 0  carrier 0  collisions 0

wwan0_1: flags=193<UP,RUNNING,NOARP>  mtu 1428
        inet 10.221.240.40  netmask 255.255.255.240
        inet6 fe80::fc7c:65ff:fe76:a97  prefixlen 64  scopeid 0x20<link>
        ether fe:7c:65:76:0a:97  txqueuelen 1000  (Ethernet)
        RX packets 2  bytes 640 (640.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 12  bytes 1312 (1.2 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

AT+QGDCNT?
+QGDCNT: 560,0

OK
AT+QGDNRCNT?
+QGDNRCNT: 0,560

OK

So, I think it is Mobile carrier’s issue.
BUT, It works fine in Windows11 environment with driver_ver V.2.2.2 and same device/sim card.

In conclusion, It looks like a issue related to ‘Kernel config’ or ‘route setting’ I think.

Which part should I check?
I’d appreciate it if you could leave a simple hint.

Thanks! Have a nice day!

Sorry for late reply.

Can it succeed to ping 8.8.8.8?

Thanks for reply!
Actually, This issue is closed.

The reason is route table.
in my board, default route table is already added as below

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
0.0.0.0         192.168.16.254  0.0.0.0         UG    0      0        0 eth0
192.168.16.0    0.0.0.0         255.255.255.0   U     0      0        0 eth0

so, the packet which is target to DNS or gateway was transmitted via eth0 not wwan0_1

after remove route or set with netmask, wwan0_1 is working good.

Thasks!