Only IPv6 addresses are obtained in the cellular dial, but only IPv4 addresses are available on the Intranet. How do I enable the Intranet to access the Internet properly
/etc/config/network
config globals 'globals'
#option ula_prefix 'fd00:1234:5678::/48'
config interface 'lan'
option type 'bridge'
option ifname 'eth0.1'
option proto 'static'
option ipaddr '192.168.10.1'
option netmask '255.255.255.0'
option mtu '1500'
#option ip6assign '64'
config interface 'wan1'
option ifname 'eth0.2'
option mtu '1500'
option metric '10'
option peerdns '1'
option advance '0'
option proto 'dhcp'
config interface 'wan6'
option ifname 'cell_wwan0'
option proto 'dhcpv6'
Thanks，get v6 address through relay mode and surf the Internet, I have implemented，my test scenario was to access a v6 network through a v4 Intranet.Can map-t implement my application scenario?
A v4 network cannot reach a v6 only site. There is no concept of v6 addresses in v4. A tunneling technique (v6 request, v4 transport, v6 site) could be used, but it doesn't apply to your situation since you have native v6 transport from the ISP.
MAP-T is a 4 to 6 to 4 method (v4 request, v6 transport, v4 site) so I don't think that is what you are asking about either.
A v6 only ISP almost always provides the outside end of some sort of 6 to 4 proxy / tunnel for their customers. You have to find out what standard they implement. For Telekom and T-Mobile USA, that standard is NAT64.
You need to use IPv6 DNS server assigned by your provider.
See if you have it in AT+CGCONTRDP=1 response or in ifstatus {ipv6 interface name} and use it on nslookup command line.
Run AT+CGPIAF=1,1,1,0 first to get the proper formatting of IPv6 addresses.
Then run AT+CGCONTRDP=1 again and take one of the two addresses at the end - these are your primary and secondary DNS servers (240e:56:4000::218 and 240e:56:4000:8000::69).
Then add the DNS address to the end of the previously used nslookup command: nslookup {name} {server address}
The goal of the exercise is to see if Pref64 discovery works that is needed for 464xlat to operate and also to check if provider offers DNS64/NAT64 capability.
NAT46 (I assume that means conventional NAT44 before 464xlat aka CLAT) is useful to support IPv4 only applications on the LAN.
In a proper DNS64/NAT64 deployment, a modern browser on a v6 capable LAN device will treat IPv4 websites as v6. They are directly accessible as IPv6 using the "fake" V6 IPs served up by DNS64. NAT46 handles relatively little of the traffic, only edge cases from legacy clients or where a V4 IP is only available (server IP hard coded into the app, or using a private DNS which does not serve DNS64)
Legacy clients after passing through NAT46 have destination V6 addresses exactly the same as the "fake native" V6 IPs from DNS64.
Both have to be backed by a NAT64 aka PLAT on the other side of the v6 only link to the ISP. Any v6 attempt to access a v4 site has to be translated on the Internet side of the ISP and routed into the v4 Internet. As the customer setting up your own router, you need to find out what translation methods are available on your ISP.
The two major tests for this have already been described by others here. The first one is to DNS a site known to be v4 only and see if any AAAA (IPv6 address) record is returned, which means that DNS64 is supported. This as noted must be directed to the ISPs DNS server.
The other test is to attempt to use the "well known" NAT64 prefix 64:ff9b through the IPv6 connection to reach a v4 site on the Internet. The last 32 bits of the test address are the IPv4 of the site, in hex. If the ISP is NAT64 compliant, this prefix will be routed to their NAT64 machine and on to the v4 Internet, and the ping will succeed.
