LTE is working but no Internet connection TL-MR6400

[kmazurek]

Hi,

I'm trying to launch Internet via TP-Link TL-MR6400v5. Everything seems correct, but the device doesn't want to run Internet. What am I doing wrong? The original firmware of TP-Link works very well but I need to install VPN client on the router and I lost many days trying to connect to Internet over the router. Probably firewall blocks the connection. I tried different options but no result.

Below the settings:

root@OpenWrt:~# uqmi -d /dev/cdc-wdm0 --get-data-status
"connected"

root@OpenWrt:~# uqmi -d /dev/cdc-wdm0 --get-signal-info
{

•    "type": "lte",*
  

•    "rssi": -73,*
  

•    "rsrq": -10,*
  

•    "rsrp": -101,*
  

•    "snr": 18.200000*
  

}

root@OpenWrt:~# uqmi -d /dev/cdc-wdm0 --get-serving-system
{

•    "registration": "registered",*
  

•    "plmn_description": "Oy▒}.\u0003",*
  

•    "plmn_mcc": 260,*
  

•    "plmn_mnc": 3,*
  

•    "mnc_length": 2,*
  

•    "roaming": false*
  

}

root@OpenWrt:~# uqmi -d /dev/cdc-wdm0 --get-current-settings
"Out of call"

Thank you in advance

[bmork]

You have to use --set-client-id and manage your ids carefully if you want to inspect call settings. They are associated with one specific QMI_WDS client-id, and void when you release it.

Look at how /lib/netifd/proto/qmi.sh does it.

This is not a problem for QMI_NAS stuff like signal-info and serving-system since these settings are global. So they will be the same for all QMI_NAS clients.

[mrhaav]

Hi

Can you paste the LTE setup from your syslog?

logread -e "your LTEinterface name"

[kmazurek]

Fri Jun 17 00:11:57 2022 daemon.notice netifd: Interface 'lte' is setting up now
Fri Jun 17 00:11:59 2022 daemon.notice netifd: lte (1896): PINcode disabled
Fri Jun 17 00:11:59 2022 daemon.notice netifd: lte (1896): Data format set to raw-ip
Fri Jun 17 00:11:59 2022 daemon.notice netifd: lte (1896): sh: write error: Resource busy
Fri Jun 17 00:12:00 2022 daemon.notice netifd: lte (1896): Default profile number: 1
Fri Jun 17 00:12:00 2022 daemon.notice netifd: lte (1896): Change default profile
Fri Jun 17 00:12:00 2022 daemon.notice netifd: lte (1896): authentication: CHAP to chap
Fri Jun 17 00:12:01 2022 daemon.notice netifd: lte (1896): Airplane mode off
Fri Jun 17 00:12:02 2022 daemon.notice netifd: lte (1896): registered on 26003
Fri Jun 17 07:17:38 2022 daemon.notice netifd: lte (1896): Registered to Oy▒}. on LTE
Fri Jun 17 07:17:39 2022 daemon.notice netifd: lte (1896): Default profile connected with ipv4
Fri Jun 17 07:17:39 2022 daemon.notice netifd: lte (1896): Setting up wwan0
Fri Jun 17 07:17:40 2022 daemon.notice netifd: Interface 'lte' is now up
Fri Jun 17 07:17:40 2022 daemon.notice netifd: Interface 'lte_4' is enabled
Fri Jun 17 07:17:40 2022 daemon.notice netifd: Interface 'lte_4' has link connectivity
Fri Jun 17 07:17:40 2022 daemon.notice netifd: Interface 'lte_4' is setting up now
Fri Jun 17 07:17:40 2022 daemon.notice netifd: lte_4 (2711): udhcpc: started, v1.33.2
Fri Jun 17 07:17:40 2022 daemon.notice netifd: lte_4 (2711): udhcpc: sending discover
Fri Jun 17 07:17:40 2022 user.notice firewall: Reloading firewall due to ifup of lte (wwan0)
Fri Jun 17 07:17:43 2022 daemon.notice netifd: lte_4 (2711): udhcpc: sending discover
Fri Jun 17 07:17:46 2022 daemon.notice netifd: lte_4 (2711): udhcpc: sending discover

[kmazurek]

Below screenshot and settings of the interfaces

root@OpenWrt:/lib/netifd/proto# logread -e "lte_4"
Fri Jun 17 07:17:40 2022 daemon.notice netifd: Interface 'lte_4' is enabled
Fri Jun 17 07:17:40 2022 daemon.notice netifd: Interface 'lte_4' has link connectivity
Fri Jun 17 07:17:40 2022 daemon.notice netifd: Interface 'lte_4' is setting up now
Fri Jun 17 07:17:40 2022 daemon.notice netifd: lte_4 (2711): udhcpc: started, v1.33.2
Fri Jun 17 07:17:40 2022 daemon.notice netifd: lte_4 (2711): udhcpc: sending discover
Fri Jun 17 07:17:43 2022 daemon.notice netifd: lte_4 (2711): udhcpc: sending discover
Fri Jun 17 07:17:46 2022 daemon.notice netifd: lte_4 (2711): udhcpc: sending discover

root@OpenWrt:/lib/netifd/proto# logread -e "wwan"
Fri Jun 17 00:12:03 2022 daemon.notice netifd: wwan (1996): udhcpc: sending discover
Fri Jun 17 07:17:37 2022 daemon.notice netifd: wwan (1996): udhcpc: sending discover
Fri Jun 17 07:17:39 2022 daemon.notice netifd: lte (1896): Setting up wwan0
Fri Jun 17 07:17:40 2022 daemon.notice netifd: Network alias 'wwan0' link is up
Fri Jun 17 07:17:40 2022 user.notice firewall: Reloading firewall due to ifup of lte (wwan0)

[mrhaav]

I think you need to turn off DHCP for your LTE interface:

uci set network.lte.dhcp=0
uci commit network

Which version of OpenWrt and uqmi are you using?

[kmazurek]

OpenWrt 21.02.3 r16554-1d4dea6d4f
uqmi 2021-12-22-0.4

[kmazurek]

One step forward. Now interface LTE shows IP but still no internet access.

[mrhaav]

How does your routing and default gateway looks, since you have multiple wan interfaces.

[kmazurek]

root@OpenWrt:~# route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 10.104.131.41 0.0.0.0 UG 0 0 0 wwan0
10.104.131.32 0.0.0.0 255.255.255.240 U 0 0 0 wwan0
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 br-lan

root@OpenWrt:~# ip route
default via 10.104.131.41 dev wwan0
10.104.131.32/28 dev wwan0 scope link src 10.104.131.40
192.168.1.0/24 dev br-lan scope link src 192.168.1.1

[kukulo]

I would remove the duplicate WWAN interface and keep just the LTE interface. This seems to be quite confusing, it has the same MAC address as the LTE interface. Since you have WAN port as well I would add metric to the interface. Assign lower metric to the LTE interface.

Then check the routing with ip route show .

[kmazurek]

It's working! Thank you all for the help.

root@OpenWrt:~# ip route
default via 10.110.88.214 dev wwan0
10.110.88.212/30 dev wwan0 scope link src 10.110.88.213
79.188.222.38 via 10.110.88.214 dev wwan0
192.168.1.0/24 dev br-lan scope link src 192.168.1.1