Wi-Fi in the metro, just like at home: how to connect and why it doesn't work

Have you noticed how some passengers on the metro automatically connect to the free Wi-Fi Without any unnecessary manipulation—as if you were at home? Meanwhile, your phone stubbornly demands authorization via SMS or browser every time you enter a tunnel. The difference isn't in luck, but in the correct settings. In this article, we'll look at how to make your smartphone automatically connected to Wi-Fi in the metro — and why this same trick might not work on a home network.

Spoiler: the problem lies not with your device, but with the architecture of the subway network. Free Wi-Fi in carriages uses port networks with forced authorization (captive portal), while home routers work on the principle WPA2-PSK or WPA3We'll show you how to "cheat" the system while maintaining security, and we'll explain why. On Android 14+ and iOS 17+, the connection algorithm has changed. - this is critical for owners of new smartphones.

Why doesn't the Wi-Fi in the metro behave like home Wi-Fi?

The main difference is in the authentication mechanism. The home router requires a password. once, then stores it in the device's memory. The metro uses dynamic authorization:

• 🔄 Captive portal: Every time you connect, a page opens asking you to enter your phone number or agree to the rules.
• ⏳ Time limit: the session lasts for 30-60 minutes, then re-authorization is required.
• 📡 Changing access points: when switching between stations, the device connects to the new one BSSID, which disrupts automatic connection.

Moreover, metro operators (for example, Mosmetro or St. Petersburg Metro) are used 802.1X EAP-SIM for authorization by phone number. This means that even if you entered the data once, the system may request it again if you change MAC addresses access points. Home routers don't do this—they bind to client MAC address, and not vice versa.

⚠️ Attention: Starting from Android 12 And iOS 15By default, systems block automatic connections to networks with a captive portal for security reasons. This means that even a saved metro network may require manual confirmation.

Method 1: Set up automatic connection on Android

On Android (versions 10–14) you can force the system to ignore the captive portal for known networks. Here are the step-by-step instructions:

1. Connect to the metro Wi-Fi manually (via SMS or browser).
2. Go to Settings → Wi-Fi, tap on the name of the metro network (for example, MT_FREE or SPB_METRO).
3. Enable the option "Connect automatically".
4. Activate Advanced Settings (or Additionally) and select:
   • 🔒 Security type: No (even if the network is secure).
   • 🔄 Proxy: No.
   • 📶 IP settings: DHCP (default).

Save the settings and restart Wi-Fi (turn airplane mode on/off).

For Android 14+ Additionally, you need to disable captive portal verification. This can be done through ADB:

adb shell settings put global captive_portal_detection_enabled 0

⚠️ Warning: Disabling captive portal verification reduces security. Do not use this method on public networks outside the metro (for example, in cafes or airports).

Connect to the metro Wi-Fi manually

Enable "Connect automatically"

Set security type to "None"

Disable proxy

Restart Wi-Fi-->

Method 2: Auto-connect on iPhone (iOS 15–17)

On iPhone The algorithm is more complex due to Apple's policies. However, there is a workaround:

1. Connect to the metro network through Safari (enter your phone number).
2. Go to Settings → Wi-Fi, tap the ⓘ icon next to the network name.
3. Activate Auto-connection.
4. Turn on Private Wi-Fi Address (this is important!), then turn it off it and turn it on again. This will reset it. MAC address for this network.
5. Return to Safari and refresh the login page (don't re-enter your information!). Close the browser.

For iOS 17+ Additionally, you will need to reset your network settings:

1. Go to Settings → General → Transfer or reset iPhone → Reset → Reset Network Settings.
2. After rebooting, try connecting to the Metro Wi-Fi again.

This method works because iOS caches authorization data for specific MAC addressResetting forces the system to create a new connection profile.

Android

iPhone (iOS)

Other (specify in comments)

I don't know-->

Why These Methods Don't Work at Home

Home routers use static authentication by password (WPA2/3-PSK), while in the metro it is used dynamic linked to a phone number. Here are the key differences:

Parameter	Wi-Fi in the metro	Home Wi-Fi
Authorization type	Captive portal + SMS	Password (PSK)
Client MAC address	Changes when changing the access point	Fixed to network
Session time	30–60 minutes	Unlimited
IP address	Dynamic (changes frequently)	Static or dynamic (DHCP)

If you try to apply the Metro settings to your home router, the following will happen:

• 🚫 The router will refuse to connect due to an invalid security type (No instead of WPA2).
• 🔄 The DHCP server may assign an incorrect IP address (for example, from the metro range) 10.0.0.0/8).
• 📵 The device will lose access to local resources (printers, NAS).

Problems and solutions: why doesn't it connect automatically?

Even after setting up automatic connection, issues may still occur. Let's look at common causes and troubleshooting steps:

1. The network disappears from the list

The culprit is a function Smart Connection (on Android) or Automatic connection (on iOS), which disables weak networks. Solution:

• 📶 On Android: Disable Settings → Wi-Fi → Advanced → Smart connection.
• 🍎 On iOS: Go to your network profile and turn it on Low Data Level (this will paradoxically increase the priority).

2. Requires authorization every time

There's a problem with the captive portal cache. Clear it:

• 🧹 On Android: Settings → Apps → Chrome → Storage → Clear Cache.
• 🍏 On iOS: Settings → Safari → Clear History and Data.

3. Connects, but without internet

This is because DNS problemsManually enter Google's DNS:

• 🌐 On Android/iOS: in the network settings, specify 8.8.8.8 And 8.8.4.4.
What to do if nothing helps?

If, after all these steps, Wi-Fi in the metro still doesn't connect automatically, check:

1. Software updates: Outdated firmware may block the captive portal.

2. Antivirus: Some (for example, Kaspersky) block "suspicious" networks.

3. Power saving mode: Disable it for the Wi-Fi module in the battery settings.

4. Alternative applications: Try it WiFi Map or Instabridge for automatic authorization.

Security: The Risks of Automatic Connection

Before setting up auto-connection, consider the risks:

• 🕵️ Traffic interception: Data is transmitted in the metro without encryption (HTTP). Use VPN (For example, ProtonVPN or Warp by Cloudflare).
• 📱 Personal data leakWhen authorizing via SMS, the metro operator receives your phone number. For anonymity, use a virtual number (for example, via TextNow).
• 🔄 MITM attacks: Attackers can spoof your access point. Always check the network name (MT_FREE, and not Free_Metro_WiFi).

The following will help minimize risks:

1. Disconnection automatic synchronization (Google Drive, iCloud) when connected to the metro.
2. Usage private DNS (For example, dns.google or 1.1.1.1).
3. Regularly clear the list of saved networks (Settings → Wi-Fi → Saved Networks).

⚠️ Attention: In 2026, cases of substitution of access points with the name were recorded in the Moscow and St. Petersburg metro MT_FREE_5GThese networks requested your Apple ID or Google account password. Never enter account information on public networks!

Alternative methods: auto-connect apps

If manual settings don't help, use specialized applications:

For Android will also work Tasker with plugin AutoInput. Create a task:

1. Condition: Status → Net → Wi-Fi connected → SSID: MT_FREE.
2. Action: Plugin → AutoInput → Click the "Get Code" button (coordinates of the button on the authorization page).

On iOS There is no similar functionality due to system limitations, but it can be used Shortcuts (Shortcuts) to open the authorization page in one tap.

FAQ: Frequently Asked Questions

Why did auto-connect stop working after updating iOS?

Starting from iOS 16.4Apple has tightened its security policy for captive portal networks. The system now requires manual confirmation the first time you connect to a new access point (even if the network is saved). Solution:

1. Remove the metro network from saved ones.
2. Reconnect via Safari.
3. Turn on Private Wi-Fi Address and reboot your device.

Can these settings be used for Wi-Fi on commuter trains or at airports?

Partially. In airports (For example, Sheremetyevo_Free) And electric trains (For example, RZD_Free) A captive portal is also used, but authorization algorithms may differ. For commuter trains, the following is often required:

• Entering a ticket number instead of a phone number.
• Confirmation via email.

Metro settings may not work. Check the current conditions on the carrier's website.

How can I be sure that my subway traffic isn't being hijacked?

Use network analysis applications:

• Fing (Android/iOS) - shows all devices on the network.
• NetGuard (Android) - Blocks suspicious connections.
• Wireshark (for advanced users) - analyzes packets.

Please note:

• Unknown devices with names like TP-Link_XXXX or Huawei_XXXX.
• DNS servers other than 8.8.8.8 or provider ones.

Why is Wi-Fi faster at some stations?

Speed ​​depends on:

• 📡 Number of access points: At transfer stations (for example, Komsomolskaya More equipment has been installed in Moscow.
• 👥 Loads: During peak hours, the speed drops to 1–2 Mbps.
• 📶 Frequencies: Some cars support 5 GHz (less loaded, but passes through walls worse).

To connect to 5 GHz:

1. In the Wi-Fi settings, select the network with the suffix _5G (For example, MT_FREE_5G).
2. If there is no such network, your device does not support it. 5 GHz or the access point only works on 2.4 GHz.

Is it possible to share Wi-Fi from the metro to other devices?

Technically yes, but:

• 🚫 Prohibited by the rulesIn most subways, distributing Wi-Fi is considered a violation of the user agreement.
• ⚠️ Speed ​​Limit: When distributing, the speed will drop to 0.5–1 Mbps.
• 🔒 MAC address blocking: The system may ban your device for "unusual use".

If you still need to share the Internet:

1. Connect to the metro Wi-Fi.
2. Activate modem mode (Settings → Access Point).
3. On the second device, connect to your access point (not the metro network!).

The risk of blocking is ~10% (according to user data) 4PDA for 2026).