Map-t on Flint 3

Hello,

i have a Flint 3 at the latest stable firmware and i’m trying to use the connection from my provider, Sky Italia, using the MAP-T as described in their page.

I’ve tried both with the help of AI and following various discussion and guides for example:

But ending up swith the same situation and the issue persising, maybe because it’s about a different device or something else.

At this point i’ve reached this situation:

i have the Ethernet 1 port showing with a small triangle saying “The interface is connected, but the Internet can't be accessed with IPv4 protocol.”

in /etc/config/network , regarding the config mentioned in may other pages :

config interface 'wan'
option proto 'dhcp'
option metric '1'
option ipv6 '1'
option mtu '1520'
option device 'eth0.101'

config interface 'wan6'
option proto 'dhcpv6'
option disabled '0'
option metric '1'
option device 'eth0.101'

config globals 'globals'
option ula_prefix 'fd08:c762:ade7::/48'

I tried also installing the map module, but it was trying to create an interface wan4_6 that was keeping failing for the mapping, so i went in Luci, System, Software and looked for map and found that a package is already present for mapt (kmod-qca-nss-ppe-mapt) so i've removed map hoping to solve apossible conflict

At the moment in the GL-Inet admin panne i have:

  • ipv6 active in native mode with DNS authomatic
  • IGMP Snooping deactivated to avoid possible issues
  • Network Acceleration deactivated for same reason above

Please help.

Thanks.

The guide for the older Flint (GL-AX1800) should not be copied directly to Flint 3: eth0.101 may not be Flint 3’s WAN device. The warning is expected while native IPv6 works but the MAP-T IPv4 interface has not been created successfully. Also, kmod-qca-nss-ppe-mapt is a driver component and does not necessarily replace the OpenWrt MAP/netifd package, so please do not remove or install further packages yet.

Please run these commands over SSH and post the outputs, redacting public IPv6 addresses after the first half:

ubus call network.interface.wan6 status
logread | grep -Ei 'odhcp6c|map|wan6' | tail -n 80
opkg list-installed | grep -Ei '(^map |map-t|mapt|nat46)'

Also provide the exact Flint 3 firmware version shown under SYSTEM → Overview. This will establish whether Sky is supplying the DHCPv6 prefix/MAP rules and whether the failure is instead the Flint 3 interface mapping or a missing protocol component; the correct next configuration depends on that distinction.

This reply was generated by AI. Please verify its accuracy.

GL.iNet Technical Support reviews and responds to relevant threads on business days. Please allow time for a staff response.

ubus call network.interface.wan6 status
{
        "up": true,
        "pending": false,
        "available": true,
        "autostart": true,
        "dynamic": false,
        "uptime": 1822,
        "l3_device": "eth0.101",
        "proto": "dhcpv6",
        "device": "eth0.101",
        "metric": 1,
        "dns_metric": 0,
        "delegation": true,
        "ipv4-address": [

        ],
        "ipv6-address": [

        ],
        "ipv6-prefix": [
                {
                        "address": "2a0e:422:30aa::",
                        "mask": 48,
                        "preferred": 1778,
                        "valid": 1778,
                        "class": "wan6",
                        "assigned": {
                                "lan": {
                                        "address": "2a0e:422:30aa::",
                                        "mask": 60
                                }
                        }
                }
        ],
        "ipv6-prefix-assignment": [

        ],
        "route": [
                {
                        "target": "::",
                        "mask": 0,
                        "nexthop": "fe80::200:REDACTED",
                        "metric": 512,
                        "valid": 966,
                        "source": "2a0e:422:30aa::/48"
                }
        ],
        "dns-server": [
                "2a0e:404:0:a::1",
                "2a0e:404:0:a::2"
        ],
        "dns-search": [

        ],
        "neighbors": [

        ],
        "inactive": {
                "ipv4-address": [

                ],
                "ipv6-address": [

                ],
                "route": [

                ],
                "dns-server": [

                ],
                "dns-search": [

                ],
                "neighbors": [

                ]
        },
        "data": {
                "passthru": "REDACTED"
        }
}
logread | grep -Ei 'odhcp6c|map|wan6' | tail -n 80
Fri Oct  2 19:01:16 2026 daemon.notice netifd: Interface 'wwan6' is disabled
Fri Oct  2 19:01:16 2026 daemon.notice netifd: Interface 'wwan6' has link connectivity loss
Fri Oct  2 19:01:16 2026 daemon.err odhcp6c[20208]: Failed to send SOLICIT message to ff02::1:2 (Network unreachable)
Fri Oct  2 19:01:16 2026 daemon.notice netifd: Interface 'wwan6' is now down
Fri Oct  2 19:01:16 2026 kern.err kernel: [70565.932028] wlan: [5724:I:ANY] [UNSPECIFIED] vap-6(sta1):mlme_sta_swbmiss_timer_detach:disable bitmap is 0x2
Fri Oct  2 19:01:16 2026 user.notice kmwan: config json str={ "op": 3, "data": { "cells": [ "wwan6" ] } }
Fri Oct  2 19:01:16 2026 kern.warn kernel: [70566.344884] kmwan: Delete node:wwan6
Fri Oct  2 19:01:17 2026 user.notice firewall: Reloading firewall due to ifdown of wwan6 ()
Fri Oct  2 19:01:17 2026 daemon.info hostapd: wlan1: IEEE 802.11 driver had channel switch: iface->freq=5260, freq=5260, ht=1, vht_ch=0x0, he_ch=0x0, eht_ch=0x0, offset=1, width=5 (160 MHz), cf1=5250, cf2=0, puncturing_bitmap=0x0
Fri Oct  2 19:01:17 2026 daemon.info hostapd: wlan1: IEEE 802.11 driver had channel switch: iface->freq=5260, freq=5260, ht=1, vht_ch=0x0, he_ch=0x0, eht_ch=0x0, offset=1, width=5 (160 MHz), cf1=5250, cf2=0, puncturing_bitmap=0x0
Fri Oct  2 19:01:17 2026 daemon.info hostapd: wlan12: IEEE 802.11 driver had channel switch: iface->freq=5260, freq=5180, ht=1, vht_ch=0x0, he_ch=0x0, eht_ch=0x0, offset=1, width=5 (160 MHz), cf1=5250, cf2=0, puncturing_bitmap=0x0
Fri Oct  2 19:01:17 2026 daemon.info hostapd: wlan13: IEEE 802.11 driver had channel switch: iface->freq=5260, freq=5180, ht=1, vht_ch=0x0, he_ch=0x0, eht_ch=0x0, offset=1, width=5 (160 MHz), cf1=5250, cf2=0, puncturing_bitmap=0x0
Fri Oct  2 19:01:17 2026 daemon.info hostapd: wlan1: IEEE 802.11 driver had channel switch: iface->freq=5180, freq=5180, ht=1, vht_ch=0x0, he_ch=0x0, eht_ch=0x0, offset=1, width=5 (160 MHz), cf1=5250, cf2=0, puncturing_bitmap=0x0
Fri Oct  2 19:01:17 2026 daemon.info hostapd: wlan12: IEEE 802.11 driver had channel switch: iface->freq=5180, freq=5180, ht=1, vht_ch=0x0, he_ch=0x0, eht_ch=0x0, offset=1, width=5 (160 MHz), cf1=5250, cf2=0, puncturing_bitmap=0x0
Fri Oct  2 19:01:18 2026 daemon.info hostapd: wlan02: IEEE 802.11 driver had channel switch: iface->freq=2412, freq=2412, ht=1, vht_ch=0x0, he_ch=0x0, eht_ch=0x0, offset=1, width=2 (40 MHz), cf1=2422, cf2=0, puncturing_bitmap=0x0
Fri Oct  2 19:01:18 2026 daemon.info hostapd: wlan12: IEEE 802.11 driver had channel switch: iface->freq=5180, freq=5180, ht=1, vht_ch=0x0, he_ch=0x0, eht_ch=0x0, offset=1, width=5 (160 MHz), cf1=5250, cf2=0, puncturing_bitmap=0x0
Fri Oct  2 19:01:18 2026 daemon.info hostapd: wlan22: IEEE 802.11 driver had channel switch: iface->freq=6135, freq=6135, ht=1, vht_ch=0x0, he_ch=0x0, eht_ch=0x0, offset=-1, width=10 (320 MHz), cf1=6265, cf2=0, puncturing_bitmap=0x0
Fri Oct  2 19:01:18 2026 daemon.info hostapd: wlan13: IEEE 802.11 driver had channel switch: iface->freq=5180, freq=5180, ht=1, vht_ch=0x0, he_ch=0x0, eht_ch=0x0, offset=1, width=5 (160 MHz), cf1=5250, cf2=0, puncturing_bitmap=0x0
Fri Oct  2 19:01:18 2026 daemon.info hostapd: wlan03: IEEE 802.11 driver had channel switch: iface->freq=2412, freq=2412, ht=1, vht_ch=0x0, he_ch=0x0, eht_ch=0x0, offset=1, width=2 (40 MHz), cf1=2422, cf2=0, puncturing_bitmap=0x0
Fri Oct  2 19:01:18 2026 daemon.info hostapd: wlan13: IEEE 802.11 driver had channel switch: iface->freq=5180, freq=5180, ht=1, vht_ch=0x0, he_ch=0x0, eht_ch=0x0, offset=1, width=5 (160 MHz), cf1=5250, cf2=0, puncturing_bitmap=0x0
Fri Oct  2 19:01:19 2026 daemon.info hostapd: wlan23: IEEE 802.11 driver had channel switch: iface->freq=6135, freq=6135, ht=1, vht_ch=0x0, he_ch=0x0, eht_ch=0x0, offset=-1, width=10 (320 MHz), cf1=6265, cf2=0, puncturing_bitmap=0x0
opkg list-installed | grep -Ei '(^map |map-t|mapt|nat46)'
kmod-nat46 - 5.4.213+2022-09-19-4c5beee2-1
kmod-qca-nss-ppe-mapt - 5.4.213+gd34b66c-dirty-2

Firmware: 4.10.1

The output confirms that eth0.101 is the active Flint 3 WAN device and Sky is delegating an IPv6 /48. However, no dynamic MAP-T interface exists, and the standard OpenWrt map package is not installed; kmod-qca-nss-ppe-mapt and kmod-nat46 alone do not show that netifd can construct the MAP-T interface.

Please run the following without installing or removing anything:

ubus call network.interface.wan6_4 status
ls -l /lib/netifd/proto/map.sh /usr/lib/map /usr/lib/mapcalc /tmp/map* 2>&1
opkg list | grep -E '^map([[:space:]-]|$)'

The first command determines whether wan6_4 was attempted; the second checks for the MAP protocol scripts and generated rules; the third establishes whether firmware 4.10.1 offers a compatible map package. Please redact public addresses or prefixes from the output. The redacted data.passthru may contain Sky’s DHCPv6 MAP option, so keep its complete value private unless a support member requests it by private message.

This reply was generated by AI. Please verify its accuracy.

GL.iNet Technical Support reviews and responds to relevant threads on business days. Please allow time for a staff response.

i’ve installed map again and this is the issue with it:

ubus call network.interface.wan6_4 status
{
        "up": false,
        "pending": false,
        "available": true,
        "autostart": false,
        "dynamic": true,
        "proto": "map",
        "data": {
                "zone": "wan"
        },
        "errors": [
                {
                        "subsystem": "map",
                        "code": "INVALID_MAP_RULE"
                }
        ]
}

INVALID_MAP_RULE confirms that the map protocol handler is now being invoked, but it rejects the MAP-T rule derived from Sky’s DHCPv6 data. This may be malformed/missing ISP data or a compatibility issue in Flint 3 firmware 4.10.1; reinstalling packages will not distinguish those cases.

Please do not modify the network configuration further. Post these remaining outputs:

opkg list-installed | grep -E '^map '
ls -l /lib/netifd/proto/map.sh /usr/lib/map* /tmp/map* 2>&1
logread | grep -Ei 'map|wan6_4|odhcp6c' | tail -n 50

If /tmp/map-wan6_4.rules exists, do not post it unredacted because it can contain public addressing. You may show a redacted copy while preserving all prefix lengths (such as /48), PSID/EA lengths, offsets, and other numeric fields; those values are needed to determine why validation fails.

This reply was generated by AI. Please verify its accuracy.

GL.iNet Technical Support reviews and responds to relevant threads on business days. Please allow time for a staff response.

opkg list | grep -E '^map([[:space:]-]|$)'
map - 7 - Provides support for MAP-E (RFC7597), MAP-T (RFC7599) and Lightweight 4over6 (RFC7596) in /etc/config/network. MAP combines address and port translation with the tunneling of IPv4 packets over an IPv6 network
root@GL-BE9300:~# opkg list-installed | grep -E '^map '
map - 7
ls -l /lib/netifd/proto/map.sh /usr/lib/map* /tmp/map* 2>&1
ls: /usr/lib/map*: No such file or directory
ls: /tmp/map*: No such file or directory
-rwxr-xr-x    1 root     root          9238 Oct 17  2024 /lib/netifd/proto/map.sh

logread | grep -Ei 'map|wan6_4|odhcp6c' | tail -n 50

Empty

The map package and protocol script are installed, but the previous path check did not include the usual executable location, /usr/bin/mapcalc. INVALID_MAP_RULE can also occur if that executable is missing or cannot run.

Please run:

opkg files map
command -v mapcalc
ls -l /usr/bin/mapcalc 2>&1
/usr/bin/mapcalc 2>&1 | head -n 10

If mapcalc exists and runs, the next step will be to capture the exact MAP rule passed to it; that rule contains public prefixes, so it should be shared only in redacted form or privately with support. If it is missing or fails to execute, that instead indicates an incomplete or incompatible map package on firmware 4.10.1.

This reply was generated by AI. Please verify its accuracy.

GL.iNet Technical Support reviews and responds to relevant threads on business days. Please allow time for a staff response.

mapcalc is present just not in /usr/bin but in /usr/sbin

opkg files map
Package map (7) is installed on root and has the following files:
/lib/netifd/proto/map.sh
/usr/sbin/mapcalc
ls -l /usr/sbin/mapcalc 2>&1
-rwxr-xr-x    1 root     root         65499 Oct 17  2024 /usr/sbin/mapcalc
/usr/sbin/mapcalc 2>&1 | head -n 10
Usage: /usr/sbin/mapcalc <interface|*> <rule1> [rule2] [...]

mapcalc is installed and executable, so the package is not incomplete. The remaining issue is the specific MAP rule generated from Sky’s DHCPv6 data; its exact, unredacted value is needed to distinguish invalid ISP parameters from a firmware compatibility problem.

Because that data contains public prefixes, please send the complete wan6 data.passthru value and the latest ubus call network.interface.wan6_4 status output privately to support@gl-inet.com, referencing this topic and Flint 3 firmware 4.10.1. Do not post the unredacted MAP data publicly, and avoid further package or network changes until support has checked it.

This reply was generated by AI. Please verify its accuracy.

GL.iNet Technical Support reviews and responds to relevant threads on business days. Please allow time for a staff response.