How to Fix Android Hotspot Not Working on Travel eSIM: APN Type dun & supl Guide (2026)

Why Android Hotspots Fail on Travel eSIMs: Root Causes and 'Connected Without Internet' Errors

When you activate a Wi-Fi hotspot on an Android device running a travel eSIM, client devices (like MacBooks, iPads, or secondary phones) frequently display a dreaded status: "Connected, no internet." While the host Android device browses the web seamlessly, downstream tethered devices fail to resolve DNS queries or exchange TCP/UDP packets.

This issue is rarely a hardware fault. Instead, it stems from how the Android operating system isolates network traffic, verifies carrier provisioning, and routes packets across roaming cellular interfaces.

+-----------------------------------------------------------------------+
|                        ANDROID HOST SYSTEM                            |
|                                                                       |
|  +---------------------------+       +-----------------------------+  |
|  |   Default Apps Traffic    |       |  Wi-Fi Hotspot Clients      |  |
|  |   (Browser, Social, etc.) |       |  (Subnet: 192.168.43.0/24)  |  |
|  +-------------+-------------+       +--------------+--------------+  |
|                |                                    |                 |
|                v                                    v                 |
|        [ Routing Table: Main ]             [ Routing Table: Tether ]  |
|                |                                    |                 |
|                | (APN Type: default)                | (APN Type: dun) |
|                v                                    v                 |
|    +-----------------------+            +-----------------------+     |
|    | Primary Data Path     |            | Tethering Upstream    |     |
|    | Interface: rmnet_data0|            | Interface: rmnet_data1|     |
|    +-----------+-----------+            +-----------+-----------+     |
+----------------|------------------------------------|-----------------+
                 |                                    |
                 | (Allowed)                          | (Blocked / Dropped)
                 v                                    v
       ========================================================
                      LOCAL ROAMING CELL TOWER
         (No DUN routing configured -> Tethering packets discarded)
       ========================================================

1. Android Network Stack Architecture: Upstream Interface Isolation

At the kernel level, Android separates on-device cellular traffic from tethered client traffic using dedicated Linux routing tables and packet filtering via iptables / nftables inside the netd (Network Daemon) subsystem.

• Modem Interface Separation: Qualcomm-based devices (Samsung Galaxy, Google Pixel, OnePlus) assign cellular data to virtual network interfaces named rmnet_data0, rmnet_data1, etc. MediaTek chipsets (common in Xiaomi and mid-range devices) utilize ccmni0, ccmni1.
• Subnet & NAT Routing: When you enable the hotspot, Android creates a local subnet (typically 192.168.43.0/24 or an IPv6 /64 prefix) and attempts to bind a Network Address Translation (NAT) rule from the Wi-Fi interface (wlan0 or ap0) to an upstream cellular interface.
• The APN Type Separation: If Android detects that the active mobile network requires separate paths for tethering, it refuses to route hotspot traffic through the standard default APN interface. Instead, it explicitly hunts for an upstream profile configured with the dun (Dial-Up Networking) APN type to spin up a secondary data bearer. If your travel eSIM profile lacks dun, Android routes hotspot traffic into a black hole or blocks forwarding outright.

2. Carrier Entitlement Checks and TETHER_DUN_REQUIRED

Android incorporates an internal carrier validation mechanism managed by CarrierConfigManager. In domestic carrier profiles, this triggers an entitlement check—a silent query sent to the operator to verify whether your plan includes tethering permissions.

When you use a travel eSIM abroad:

1. Unrecognized Roaming SIMs: The device connects via an international roaming IMSI (often based out of hubs like Austria, Hong Kong, or Poland). The host Android OS cannot find a matching domestic Carrier Bundle and falls back to default carrier rules.
2. Flag Enforcement: If the fallback profile enforces TETHER_DUN_REQUIRED = 1, the OS actively blocks traffic bridging across the default APN interface unless a separate dun profile is declared.
3. Gateway Packet Discard: Even if Android forwards the packets, the local partner network's Packet Gateway (PGW) or User Plane Function (UPF) inspects the packet header. If the APN protocol or bearer profile does not match roaming agreements, the upstream node silently discards tethered packets.

3. Dual-SIM Routing Table Collisions (DSDS)

Most international travelers run a Dual SIM Dual Standby (DSDS) configuration: a physical SIM for their home phone number (calls/SMS) and a travel eSIM for destination data.

+-------------------------------------------------------------------+
|                     Dual-SIM Routing Conflicts                    |
+--------------------+----------------------------------------------+
| Physical SIM (Home)| Priority: Voice/SMS (IMS Listener Active)    |
| Travel eSIM (Data) | Priority: Data Uplink                        |
| Tethering Subnet   | Conflict: Host binds DNS to primary SIM stack|
+--------------------+----------------------------------------------+

This setup frequently triggers routing table collisions:

• DNS Resolver Traps: Android's internal resolver daemon may route DNS lookups generated by tethered devices through the inactive or roaming-restricted DNS server of the primary physical SIM, causing instant DNS failure on connected clients.
• IP MTU Mismatches: Roaming eSIM encapsulations (e.g., GTP tunnels between the local visiting network and the eSIM's home routing gateway) reduce the effective Maximum Transmission Unit (MTU). While the phone's browser auto-negotiates Packet Size via Path MTU Discovery, connected laptops often send oversized packets (1500 bytes) that get dropped by intermediate mobile gateways without returning an ICMP fragmentation notice.

Using modern travel data providers like MollySIM mitigates these interface conflicts. MollySIM utilizes streamlined, multi-carrier APN architecture designed to bypass proprietary carrier entitlement blocks while auto-negotiating unified data paths. Furthermore, with MollySIM's 384kbps Fair Use Policy (FUP) limit—3x faster than the industry standard of 128kbps—mission-critical apps like Google Maps, Uber, WhatsApp voice messaging, and Apple Pay maintain active socket connections even if client devices run heavy background synchronizations.

Deconstructing Key APN Fields: The Crucial Roles of APN Type 'default,supl,dun' and Dual-Stack Protocols

An Access Point Name (APN) is the network gateway that defines the exact packet data protocol (PDP) context, routing rules, and authentication parameters an Android device must use to establish a data path with a mobile carrier’s Packet Data Network (PDN). Configuring an APN incorrectly—or omitting crucial flags—can leave standalone mobile data functioning while completely severing downstream tethering.

Below is an exhaustive breakdown of the critical parameters governing data routing, location assistance, and tethering handshakes.

The APN Type Hierarchy: Deconstructing default, supl, dun, mms, and hipri

Android determines which network interfaces handle outgoing sockets through the APN Type field. This field accepts a comma-separated string (strictly without spaces). Omitting a required token instructs the Android OS to block traffic from the associated system service or peripheral interface.

Standard Travel eSIM Payload: default,supl,dun
Legacy / Carrier-Locked Profile: default,mms (Blocks tethering bridge completely)

Why Missing dun Drops Tethered Packets

When a laptop or tablet connects to your Android Wi-Fi hotspot, Android’s upstream interface router checks the active PDP profile.

1. If the operator's SIM profile specifies that tethering requires the dun class, but the active APN string only contains default, Android drops the tethering bridge packets or attempts to negotiate a non-existent secondary carrier DUN APN.
2. In roaming contexts, the visited base station (VPLMN) queries the Home Public Land Mobile Network (HPLMN) policy server (PCRF). If dun is absent from the requested APN context, mobile network gateways (SGW/PGW) drop encapsulated tethered packets directly at the GTP (GPRS Tunneling Protocol) layer.

APN Protocol & APN Roaming Protocol: Solving the Dual-Stack Handshake Failure

The APN Protocol (used within your domestic coverage) and APN Roaming Protocol (active whenever your travel eSIM registers on an international partner network) dictate how local and roaming gateways assign IP addresses to your device.

Android allows three protocol states:

• IPv4 Only: Transmits strictly 32-bit addresses. Reliant on carrier-grade NAT (CGNAT). Highly compatible, but introduces latency and packet-header overhead.
• IPv6 Only: Transmits 128-bit addresses. Lacks backward compatibility with tethered legacy devices that do not support 464XLAT or DNS64/NAT64 translation layers, causing instant "Connected, no internet" errors on client hardware.
• IPv4/IPv6 (Dual-Stack): The optimal setting. Establishes dual PDP contexts, assigning both an IPv4 and an IPv6 interface address.

The Impact of GTP Tunneling and MTU Fragmentation Abroad

International data traveling over a travel eSIM passes through an encapsulated GTP tunnel running between the visiting local tower and the eSIM provider’s home PGW. This encapsulation adds significant protocol overhead:

• Default Ethernet/Wi-Fi MTU: 1500 bytes
• Typical Roaming GTP Mobile MTU: 1400 - 1440 bytes

When client laptops transmit unfragmented 1500-byte packets through an IPv4-only roaming link, intermediate mobile gateways drop the oversized packets without generating ICMP Destination Unreachable (Fragmentation Needed) replies. This causes secure TLS/SSL handshakes to hang indefinitely.

Enabling IPv4/IPv6 Dual-Stack activates modern Path MTU Discovery (PMTUD) and modern TCP Maximum Segment Size (MSS) clamping. This prevents silent packet drops and resolves connection drops on laptops connected to your hotspot.

Carrier Architecture: Why Modern Travel Providers Prevent Configuration Dropouts

Legacy travel SIMs rely on rigid, locked APN profiles that require manual carrier provisioning and throttle bandwidth severely when you exceed base allocations. In contrast, modern international providers like MollySIM utilize an adaptable, multi-carrier network core that pre-configures unified default,supl,dun strings and robust IPv4/IPv6 dual-stack protocols straight out of the box.

Additionally, should a tethered laptop trigger large background sync tasks (such as cloud drive updates), MollySIM’s 384kbps Fair Use Policy (FUP)—which is 3x faster than the 128kbps industry standard—ensures the primary connection retains sufficient socket bandwidth to run essential apps like Google Maps, Uber, WhatsApp voice messaging, and Apple Pay without network timeouts.

Step-by-Step Tutorial: Adding and Editing Custom APNs on Samsung One UI, Google Pixel, and Stock Android

Because Android OEMs heavily customize radio management menus, the exact navigational pathway to access point configurations differs across brands. Follow the hardware-specific instructions below to configure tether-compliant APN profiles.

1. Device-Specific Navigation Paths

2. Step-by-Step Configuration Sequence

Once you open the New APN / Edit Access Point screen, execute the following parameters sequentially:

Name:           Travel Hotspot (or provider name, e.g., MollySIM)
APN:            [Your Provider APN, e.g., globaldata or internet]
APN Type:       default,supl,dun
APN Protocol:   IPv4/IPv6
APN Roaming:    IPv4/IPv6
Bearer:         Unspecified

1. Input the Unified APN String: Tap APN Type and enter default,supl,dun.

Note: Ensure there are no spaces after commas. Typing default, supl, dun will cause parsing failures in the Android telephony framework.

1. Set Dual-Stack Encodings: Ensure both APN Protocol and APN Roaming Protocol are explicitly set to IPv4/IPv6. This prevents intermediate mobile gateways from dropping non-fragmented tethered packets due to MTU size limits.
2. Commit the Profile:

• On Samsung: Tap the three vertical dots (⋮) in the top right > tap Save.
• On Pixel/OxygenOS: Tap the three vertical dots (⋮) > tap Save (or tap the checkmark icon).

1. Select the Active APN: Return to the Access Point Names list and manually tap the radio button adjacent to your newly created profile to activate it.
2. Force RRC Connection Release (Airplane Mode Toggle): The baseband modem retains previous PDP contexts until forced to drop the radio resource connection. Toggle Airplane Mode ON, wait 10 to 15 seconds, and toggle it OFF.

3. Edge Cases: Bypassing Greyed-Out APN Fields

Certain carrier-branded firmware builds (especially Verizon, AT&T, or NTT Docomo carrier-locked devices) grey out or hide the APN Type input box, preventing manual string entries.

• Workaround A: Build a Fresh APN Profile: Never edit an existing, read-only APN pre-loaded by the SIM. Instead, tap the Add (+) icon to construct a fresh entry from scratch. Fresh profiles unlock grayed-out fields on 90% of Android handsets.
• Workaround B: Phone Info Diagnostic Menu: Open your dialer and enter ##4636## to trigger the hidden Android testing menu. Navigate to Phone Information, scroll down, and check the network provisioning state. Toggling Mobile Radio Power off and on here clears stale carrier locks without a factory reset.

4. Verifying IP Allocation and Gateway Status

To verify that the Android kernel has bound the tethering interface to your multi-bearer APN:

1. Connect your secondary device (laptop or tablet) to the Android hotspot.
2. Open a terminal (macOS/Linux) or Command Prompt (Windows) on the client machine and ping an external public IPv4 and IPv6 address:

   ping 8.8.8.8
   ping -6 2001:4860:4860::8888

1. If the host resolves public DNS addresses and transmits packets with 0% packet loss, the dual-stack roaming PDP context is established.

If you travel frequently and want to avoid complex APN debugging altogether, premium providers like MollySIM streamline this architecture. MollySIM automatically delivers compliant, pre-configured tethering profiles over-the-air upon landing.

Furthermore, if background laptop updates consume your high-speed quota, MollySIM drops to a 384kbps Fair Use Policy (FUP) speed limit. Because 384kbps is 3x faster than the restrictive 128kbps standard enforced by budget eSIMs, background tethered sockets won't choke low-latency mobile services like Google Maps, Uber, or Apple Pay on your primary device.

APN Parameter Troubleshooting & Carrier Tethering Restriction Matrix

When an Android handset successfully establishes an on-device data session but downstream tethered clients fail to access the internet, the root cause is almost always an incongruity between Android's local interface routing table and the upstream mobile network operator’s (MNO) Packet Data Protocol (PDP) context definitions.

The table below details the exact failure modes caused by incorrect Access Point Name (APN) field configurations on travel eSIMs, along with the verified configurations required to restore bidirectional tethered routing.

Rapid Diagnostic Matrix

Diagnosing Dynamic Carrier Throttling & Entitlement Checks

Even when APN parameters are correctly configured, mobile operators often enforce carrier-side entitlement checks or strict Fair Use Policies (FUP) that specifically penalize hotspot traffic.

1. Carrier Entitlement Probes: Certain carrier profiles send an explicit entitlement query to an upstream carrier server when tethering is toggled. If the travel eSIM profile returns an unentitled response code, Android's framework blocks the local packet bridge. Injecting dun into the APN type bypasses the dedicated entitlement daemon on most unlocked Android builds by merging internet and tethering contexts into a single pipeline.
2. Bandwidth Exhaustion on Tethered Links: Background client tasks (such as cloud backups or OS updates) can quickly exhaust high-speed data buckets. Budget travel eSIMs often throttle the connection down to an unworkable 128kbps—a tier that completely stalls modern HTTPS handshakes, leading to apparent connection drops on both the client and host.

To eliminate tethering bottlenecks abroad, providers like MollySIM deliver pre-provisioned APN profiles that eliminate manual dun context troubleshooting entirely.

Additionally, if client-side background sync exhausts your primary data allowance, MollySIM enforces a higher 384kbps Fair Use Policy (FUP) baseline. Because 384kbps is 3x faster than the 128kbps industry standard, it keeps the physical socket alive—allowing mission-critical host applications like Google Maps, Uber, and Apple Pay to function reliably without packet loss while you resolve downstream client consumption.

Advanced Bypasses: MVNO Types (SPN vs IMSI), Carrier Firmware Locks, and ADB Entitlement Overrides

When standard APN edits fail, the root cause is almost always low-level firmware restrictions. Carrier-branded Android devices (originally sold by operators like AT&T, Verizon, T-Mobile US, NTT Docomo, or KDDI) carry deep customizations inside the OEM telephony framework. These devices execute hidden entitlement scripts that ignore manual UI configurations or aggressively delete user-created APNs whenever the network refreshes.

To break past these hardware-level carrier locks, you must bind your APN to the exact MVNO identification protocol or force-override the framework routing tables via ADB.

Locking Custom APNs via MVNO Type (SPN vs. IMSI vs. GID)

When roaming across international borders, local base stations broadcast new PLMN IDs. If your custom APN lacks an exact MVNO match, Android assumes the profile is stale and defaults back to a locked, non-tetherable system profile.

Configuring the MVNO Type correctly permanently binds your custom default,supl,dun payload to the eSIM hardware profile:

Hardware Bypass via ADB: Bypassing Entitlement Daemons

If your carrier firmware has greyed out the APN Type field entirely or refuses to broadcast tethered data despite adding dun, Android’s internal TetheringManager is actively blocking packet forward requests.

You can force the telephony framework to treat hotspot traffic as standard default outbound data by pushing global settings overrides through ADB (Android Debug Bridge).

Step 1: Enable USB Debugging

1. Go to Settings > About Phone and tap Build Number 7 times to activate Developer Options.
2. Navigate to Settings > System > Developer Options and toggle USB Debugging to ON.
3. Connect your Android device to a PC/Mac with ADB platform-tools installed.

Step 2: Push Global Routing Flags

Open your command terminal and execute the following shell commands:

# 1. Verify device connection
adb devices

# 2. Disable carrier tether entitlement check
adb shell settings put global tether_dun_required 0

# 3. Force-enable hardware tethering capability
adb shell settings put global tether_supported 1

# 4. Optional: Unbind carrier provisioning daemon check
adb shell settings put global hotspot_carrier_entitlement_disabled 1

Technical Mechanics of the ADB Fix

Setting tether_dun_required to 0 changes the internal logic of the OS TetheringInterfaceHandler. Instead of looking for a dedicated DUN radio channel from the upstream carrier gateway, Android bypasses the hardware entitlement daemon and directly bridges downstream hotspot traffic (wlan0 / rndis0) onto the default primary data interface (rmnet_data0).

Avoiding Manual Overrides with Direct-Routing Travel eSIMs

Carrier firmware overrides and ADB shell scripts require technical maintenance that can easily revert following an OTA security update. To avoid APN lockouts entirely, enterprise-grade travel providers configure their profiles with native universal entitlement.

Profiles engineered by MollySIM deliver pre-provisioned APN tables that automatically map the correct MVNO parameters upon activation, avoiding manual dun injection or terminal workarounds. Furthermore, if secondary client devices exhaust high-speed tethering allocations, MollySIM’s built-in 384kbps Fair Use Policy (FUP) guarantees that the socket pipeline remains unchoked—ensuring 3x the throughput of legacy 128kbps caps so navigation tools, rideshare platforms, and financial apps like Apple Pay continue operating smoothly without manual interface resets.

Zero-Configuration Tethering: How MollySIM's Pre-Configured APNs Eliminate Roaming Hotspot Headaches

For technical travelers, executing ADB shell overrides and hunting down OEM-specific APN type configurations in terminal windows is a viable hotfix—but it is fundamentally a workaround for misconfigured carrier payloads. The root cause of Android tethering failures on travel eSIMs stems from poorly provisioned MVNO profiles that neglect the secondary radio bearers required for downstream interface sharing.

MollySIM resolves this architectural bottleneck at the core network level, delivering zero-touch, carrier-grade eSIM profiles engineered specifically for multi-device cross-border travel.

1. Pre-Provisioned Universal Entitlement & Open APN Tables

Standard budget travel eSIMs often deploy restricted PLMN profiles that require the device OS to negotiate hotspot privileges through an external carrier verification daemon. When an unbranded travel profile lacks the carrier-side authorization hooks, Android's TetheringManager drops the routing table.

MollySIM profiles arrive with universal entitlement flags pre-configured directly on the eUICC chip:

• Native default,dun,supl Permissiveness: MollySIM automatically passes valid APN configurations to the Android radio interface layer (RIL), eliminating "Carrier does not allow hotspot" popups.
• Zero-Touch Local Handshakes: As you cross borders, MollySIM negotiates direct roaming handshakes with Tier-1 local host networks (such as NTT DOCOMO in Japan, Vodafone in Europe, or AT&T in the USA) without requiring manual APN parameter rewrites or device reboots.

2. Dual-Stack IPv4/IPv6 Routing Without Packet Encapsulation Loss

A frequent culprit behind connected devices displaying "Connected, no internet" is broken IPv6-to-IPv4 packet translation (464XLAT) across the tethering bridge (wlan0 to rmnet_data0). Many roaming profiles assign IPv6-only addresses without a stable carrier-grade NAT (CGNAT) gateway for legacy IPv4 endpoints.

MollySIM utilizes a fully compliant dual-stack IPv4/IPv6 packet data network (PDN) architecture. Downstream clients—whether a macOS workstation, an iPad, or a Windows laptop—receive native local IP addressing through the host device’s DHCP daemon, preventing MTU black holes and DNS routing mismatches.

3. Architecture Comparison: Generic Travel eSIMs vs. MollySIM

4. Continuous Connectivity: The 384kbps Fallback Guarantee

Hotspotting multiple devices inevitably accelerates data consumption. Operating system updates, background cloud backups, and browser caching from connected laptops can deplete high-speed allotments unexpectedly.

Competitor FUP Throttle (128kbps):
[════════════] Socket Timeout (Maps / Payment Failure)

MollySIM FUP Safeguard (384kbps - 3x Faster):
[════════════════════════════════════] Responsive VoIP, GPS & POS Handshakes

When high-speed quotas are exhausted, most providers throttle throughput to 128kbps—a bandwidth ceiling that causes modern TLS/SSL handshakes to time out, breaking critical applications. MollySIM implements an engineered 384kbps Fair Use Policy (FUP) baseline. Delivering three times the throughput of industry-standard throttles, this bandwidth floor ensures that tethered devices maintain active, unchoked socket pipelines for essential travel workflows:

• Real-time turn-by-turn navigation (Google Maps, Waze)
• Secure contactless point-of-sale transactions and Apple Pay/Google Wallet authentication
• Remote work communication (Slack, WhatsApp voice calls, terminal SSH sessions)

By eliminating manual APN debugging and providing sustained baseline connectivity, MollySIM ensures your cross-device travel setup remains plug-and-play across more than 200 destinations worldwide.