TL-MR6400 V4 Router | LTE (umts) wan | QMI | NO ipv4 - IP4 not working

Installing and Using OpenWrt Network and Wireless Configuration
1

Hello together,

TL-MR6400 V4 Router as a second back-up LTE (umts) wan gateway and have installed OpenWrt 23.05 with the package luci-proto-qmi.

(I also need it as a dump wifi access point, so want to use it with vlan to my main OpenWrt router, which is connected to a cable modem with ipv6 and also ipv4 over ds-lite internal in cable-model)

Everything works absolutely really fine, I get internet access over a ipv6 and also uqmi is really nice, many thanks and big praise to the developers. Also sending sms, etc. works fine.

But I only get an ipv6 address, how can I use my internal ipv4 network to connect it?

  • I have tried different provider sim cards
  • Also tried to install this ds-lite package, but I do not know what to input at peeraddr (DS-Lite AFTR address)
config interface 'lte'
        option proto 'qmi'
        option device '/dev/cdc-wdm0'
        option apn 'internet'
        option pincode 'xxxx'
        option auth 'none'
        option pdptype 'ipv4v6'

config interface 'lte4'
        option proto 'dslite'
        option peeraddr '::'
        option encaplimit 'ignore'
2

openwrt_mr6400
openwrt_mr64001121×734 77.7 KB


root@OpenWrt:~# uqmi -d /dev/cdc-wdm0 --get-serving-system
{
        "registration": "registered",
        "plmn_mcc": 262,
        "plmn_mnc": 1,
        "plmn_description": "▒2▒▒~▒]▒2",
        "roaming": false
}
root@OpenWrt:~# uqmi -d /dev/cdc-wdm0 --get-system-info
{
        "wcdma": {
                "service_status": "none",
                "true_service_status": "none",
                "preferred_data_path": false
        },
        "lte": {
                "service_status": "available",
                "true_service_status": "available",
                "preferred_data_path": false,
                "domain": "cs-ps",
                "service": "cs-ps",
                "roaming_status": "off",
                "forbidden": false,
                "mcc": "262",
                "mnc": "01",
                "tracking_area_code": 12049,
                "enodeb_id": 103071,
                "cell_id": 3,
                "voice_support": false,
                "ims_voice_support": true,
                "cell_access_status": "all calls",
                "registration_restriction": 0,
                "registration_domain": 0
        }
}

`

3

Delete dslite and install 464xlat, see Unable to get Quectel EC25-E to connect in QMI mode - #21 by AndrewZ

Check if Pref64 discovery works: CLAT/464XLAT not working in 19.07.1 - #5 by AndrewZ

4

unfortunately it does not work here..
interface LTE_6 is this clat interface (464xlat) with the same, simple config as above

config interface 'clat'
        option proto '464xlat'

syslog repeats always interface LTE_6 down....

Mon Nov  6 12:06:40 2023 daemon.notice netifd: Interface 'LTE' is setting up now
Mon Nov  6 12:06:40 2023 daemon.notice netifd: Interface 'LTE_6' is setting up now
Mon Nov  6 12:06:41 2023 daemon.notice netifd: LTE (1801): Waiting for SIM initialization
Mon Nov  6 12:06:41 2023 daemon.notice netifd: Interface 'LTE_6' is now down
Mon Nov  6 12:06:44 2023 daemon.notice netifd: LTE (1801): Failed to parse message data
Mon Nov  6 12:06:44 2023 daemon.notice netifd: LTE (1801): PIN already verified
Mon Nov  6 12:06:45 2023 daemon.notice netifd: LTE (1801): Device does not support 802.3 mode. Informing driver of raw-ip only for wwan0 ..
Mon Nov  6 12:06:45 2023 daemon.notice netifd: LTE (1801): Waiting for network registration
Mon Nov  6 12:06:46 2023 daemon.notice netifd: LTE (1801): Starting network LTE
Mon Nov  6 12:06:47 2023 daemon.notice netifd: LTE (1801): Setting up wwan0
Mon Nov  6 12:06:47 2023 daemon.notice netifd: Interface 'LTE' is now up
Mon Nov  6 12:06:48 2023 daemon.notice netifd: Interface 'LTE_6' is setting up now
Mon Nov  6 12:06:49 2023 user.notice firewall: Reloading firewall due to ifup of LTE (wwan0)
Mon Nov  6 12:08:17 2023 daemon.notice netifd: Interface 'LTE_6' is now down
Mon Nov  6 12:08:17 2023 daemon.notice netifd: Interface 'LTE_6' is setting up now
Mon Nov  6 12:08:18 2023 user.notice firewall: Reloading firewall due to ifupdate of LTE (wwan0)
Mon Nov  6 12:08:20 2023 daemon.notice netifd: Interface 'LTE_6' is now down
Mon Nov  6 12:08:20 2023 daemon.notice netifd: Interface 'LTE_6' is setting up now
Mon Nov  6 12:08:24 2023 daemon.notice netifd: Interface 'LTE_6' is now down
Mon Nov  6 12:08:24 2023 daemon.notice netifd: Interface 'LTE_6' is setting up now
Mon Nov  6 12:08:27 2023 daemon.notice netifd: Interface 'LTE_6' is now down
Mon Nov  6 12:08:27 2023 daemon.notice netifd: Interface 'LTE_6' is setting up now
Mon Nov  6 12:08:30 2023 daemon.notice netifd: Interface 'LTE_6' is now down
Mon Nov  6 12:08:30 2023 daemon.notice netifd: Interface 'LTE_6' is setting up now
Mon Nov  6 12:08:34 2023 daemon.notice netifd: Interface 'LTE_6' is now down
Mon Nov  6 12:08:34 2023 daemon.notice netifd: Interface 'LTE_6' is setting up now
5

Please return to the initial IPv6 only state, take no action to configure IPv4, CLAT, etc.
Make sure there're no changes to the default DNS configuration. Change pdptype to 'ipv6'.
Check the following:

nslookup ipv4only.arpa.
nslookup ipv4.tlund.se
1 Like
6

yes of course I copied the config setting (changed pdtype and ipv6 and clat)

> 
> config interface 'LTE'
>         option proto 'qmi'
>         option device '/dev/cdc-wdm0'
>         option apn 'internet'
>         option pincode 'xxxx'
>         option auth 'none'
>         option ipv6 '1'
>         option pdptype 'ipv6'
> 
> config interface 'LTE_6'
>         option proto '464xlat'

nslookup ipv4.only.arpa
Server:         127.0.0.1
Address:        127.0.0.1:53
** server can't find ipv4.only.arpa: NXDOMAIN
** server can't find ipv4.only.arpa: NXDOMAIN


nslookup ipv4.tlund.se
Server:         127.0.0.1
Address:        127.0.0.1:53

Non-authoritative answer:
Name:   ipv4.tlund.se
Address: 193.15.228.195
Non-authoritative answer:
7

you don't need this

My understanding you need to use internet.v6.telekom as APN.

8

hey, sorry you exactley wrote this here:
"Delete dslite and install 464xlat, see ... "

Whatever...
No APN does not matter, I tried everything, also ipv6 is working always properly.

9

But later on I wrote "take no action to configure IPv4, CLAT, etc." :wink:

Anyway... Check if you can ping 64:ff9b::c10f:e4c3 from the router.

10

whatever, I tried all these settings :wink:

As I said, I can reach all ipv6 adresses from the router also from the internal lan!

Also when I ping openwrt:
PING openwrt.org (2a03:b0c0:3:d0::1af1:1): 56 data bytes
64 bytes from 2a03:b0c0:3:d0::1af1:1: seq=0 ttl=51 time=75.264 ms

your adress is not valid
ping 64:ff9b::c10f:e4c3

11

OK, please try this configuration:

config interface 'lte'
        option proto 'qmi'
        option device '/dev/cdc-wdm0'
        option apn 'internet.v6.telekom'
        auth 'both'
        username 'telekom'
        password 'tm'
        option ipv6 '1'
        option pdptype 'ipv6'
        option peerdns '0'
        list dns '2001:4860:4860::64'

You don't need clat/464xlat interface at this point.
Then reboot and try nslookup and ping against ipv4.tlund.se

To be on a safe side the APN needs to be adjusted on the modem itself, see my recommendations from TP-Link TL-MR6400 v5 - LTE but no internet connection - #14 by AndrewZ and below.

12

I tried 'your' config, it has got some syntax errors also pin is missing.
It also work, but just for ipv6 not ipv4!
(So auth you don't need, also apt is oft not really necessary.)

I'm not sure if you understood my problem:
My LTE ipv6 connection over the cdc-wdm0 device is working absolutely fine.
I can reach all address from the router and also forwarded from the lan interface all over ipv6 but not ipv4 (which I need for my internal network, specially my VPN wireguard to my server)

13

I fully understand your problem )
In IPv6 only environment you're dependant on DNS64/NAT64 and 464xlat in order to keep IPv4 connectivity. DNS server should provide a synthetic IPv6 address for IPv4 only hostname.

What's the current result of

nslookup ipv4.tlund.se
ping ipv4.tlund.se
14

Server: 127.0.0.1
Address: 127.0.0.1:53

Non-authoritative answer:
Name: ipv4.tlund.se
Address: 193.15.228.195

Non-authoritative answer:
Name: ipv4.tlund.se
Address: 64:ff9b::c10f:e4c3

root@OpenWrt:~# ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8): 56 data bytes
ping: sendto: Network unreachable
root@OpenWrt:~# ping ipv4.tlund.se

PING ipv4.tlund.se (64:ff9b::c10f:e4c3): 56 data bytes
64 bytes from 64:ff9b::c10f:e4c3: seq=0 ttl=51 time=161.243 ms
64 bytes from 64:ff9b::c10f:e4c3: seq=1 ttl=51 time=61.920 ms
64 bytes from 64:ff9b::c10f:e4c3: seq=2 ttl=51 time=60.500 ms

--- ipv4.tlund.se ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 60.500/94.554/161.243 ms
root@OpenWrt:~# ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8): 56 data bytes
ping: sendto: Network unreachable

root@OpenWrt:~# ping openwrt.de
PING openwrt.de (64:ff9b::40be:3f6f): 56 data bytes
64 bytes from 64:ff9b::40be:3f6f: seq=0 ttl=50 time=46.404 ms
64 bytes from 64:ff9b::40be:3f6f: seq=1 ttl=50 time=48.779 ms

--- openwrt.de ping statistics ---
2 packets transmitted, 2 packets received, 0% packet loss
round-trip min/avg/max = 46.404/47.591/48.779 ms

15

Great, NAT64 works with standard prefix. Now add an interface:

config interface 'clat'
	option proto '464xlat'
	option ip6prefix '64:ff9b::/96'

and configure its firewall zone as 'wan'.
Then reboot and try pinging any IPv4 literal like 8.8.8.8

1 Like