How to enable IPv6 on a Mercury router? The switch is hidden deep inside the melogin.cn, and after turning it on, connecting remotely to the NAS is really convenient
started because I wanted to find a convenient remote solution for my Feiniu NAS at home. FRP penetration is free, but the speed is stuck around 3MB, and even looking at a photo takes a long time to look at it. Later, I saw a saying in Enshan: Your broadband actually has public IPv6. You can connect directly with the router by turning on a switch, and you can retire through that system. I excitedly rushed into the Mercury backend. Wow, the homepage scrolled down and couldn't find the IPv6 three characters—this switch was really well hidden, and in the end, it was dug out from the network parameters.
What is
IPv6? Explain it in one minute
Ten years ago,
home broadband was dominated by IPv4. There weren't enough house numbers, so operators could only let hundreds of households share a single public IP address. Most of the routers you got were internal network addresses, and those starting with 100.64 didn't even count as legitimate internal networks—in jargon, they were called carrier-level NAT. If you want to access your home NAS or camera from outside, you have to find a way to punch a hole in the wall. All the tricks like penetration and DDNAS come from there.
IPv6 is just to expand the number of house numbers. There are so many addresses that every device on Earth can have a public network, and operators give them away for free. Every phone and every NAS is directly connected to the global internet under "real-name registration," with no issue of who forwards information for whom. The v6 address looks different from the old one. Four digits are converted into a string of colons connected in hexadecimal, starting with 240e. It's a bit long, but you can just copy and paste it—no need to memorize it.
three domestic broadband providers basically default to issuance: Telecom addresses start with 240e, China Unicom 2408, and China Mobile 2409. No need to call to apply, no extra charge—all you're missing is the switch in the router's backend.
Some people say that opening IPv6 will result in "precise positioning," but in fact, phones have long been fully v6 under traffic usage, so you wouldn't be fine. The real focus is on firewalls, which will be explained later.
Before
start, check if the broadband side has IPv6
Don't rush into the backend; spend a minute first to confirm whether the carrier has provided it. The easiest way: keep data on your phone, open test-ipv6.com in your browser, and wait a dozen seconds for the results. Traffic can be measured (10 points), indicating the carrier's network is active; I connected to my home WiFi again and tested again. This time it showed no IPv6, so basically the router switch wasn't turned on—that's how I set the location, the problem isn't broadband at home.
If you can't even measure data under the traffic level, it means your area isn't covered, and running a router is pointless. Additionally, since 2019, almost all newly installed broadband devices have V6; Ten years ago, with old broadband, I would turn off the power on the optical modem and restart it once to test again, sometimes the address would be lost.
not relying on mobile data, here's a simple trick: connect your computer network cable directly to the optical modem's LAN port and check the address you get locally. If the gateway and local phone addresses contain files starting with 240e/2408/2409, it means the v6 on the optical modem side is active; the rest is purely a router issue. My mother-in-law's optical modem is old, and it was thanks to this trick that she confirmed the broadband was fine.
Mercury backend enables the full process, with the toggle in Network Parameters
Connect
phone or computer to Mercury's WiFi, enter melogin.cn browser (if you can't get in see the melogin.cn I wrote before I can't open that , both domain and IP paths have been discussed), enter the management password to enter the backend.
path is Advanced Settings → Network Parameters → IPv6. If the big cards on the homepage don't have it, you have to go to "Advanced Settings" and scroll down. First, turn on the IPv6 switch, keep your internet access mode "Automatic" (some firmware names it SLAAC or DHCPv6; don't worry about the name, just select Auto), then save. The router prompts to restart; wait two minutes.
after rebooting and returning to the same page's running state, check the WAN port information column. If an IPv6 address starts with a string of characters starting with 240e, it is correct. If you can't get the address, don't rush to reboot the big boot method. Looking at pit one, it's probably not the router's fault.
two additional points: First, after the switch is on, everything in V4 remains unchanged—broadband accounts, WiFi passwords, port forwarding, etc. v6 is another parallel running system, not a replacement; Second, I couldn't find the IPv6 switch in the Mercury Router app. For now, you have to use the web backend to open it. Opening the "Desktop Website" in your mobile browser works too.
by the way: if your backend doesn't have the "Network Parameters →IPv6" option, it means the machine's firmware doesn't include it. Try manually upgrading the firmware . The Mercury series does not have automatic upgrades, so you need to purchase it from the official website; If the latest firmware for your model doesn't have IPv6 on the official website, then the hardware is too old. My retired MAC1200R is like this—only a new machine has this feature.
how to verify after driving? Three points at a glance
first place is still test-ipv6.com. I tested the home WiFi again, and after turning it on, I scored 10. Second, check the router's operating status page; the WAN port IPv6 address is not empty. Third, when you open the WiFi section on your phone and scroll down, the IPv6 section is a long list starting with 240e. If you get one out of three, it's considered a success.
two small details: first, it takes a few minutes for the v6 address to be sent out, and prefix requests aren't replied to instantly, so don't panic if you can't detect it right after opening; Second, the phone needs to disconnect and reconnect to WiFi, or it will still hold onto the old v4-only message.
What exactly has changed after
opened? Tell me the truth
biggest change is that remote access to home devices no longer requires a to penetrate. My NAS now just enters its IPv6 address directly from the company browser to access the management page, and the speed runs across the entire home bandwidth upstream, which is more than ten times faster than FRP's 3Mbps. The WiFi camera at the entrance is the same. Previously, watching playback had to go through the vendor's cloud service, which was slow and charged, but now it connects directly through the app, making it as smooth as being at home. When I write about the three NAS remote access options, I hadn't fully grasped the IPv6 direct connection path. Looking back now, in environments with v6, it was the first choice, and both DDNS and penetration were downgraded to backup options.
Secondly, some websites and apps will run a bit smoother. Major domestic sites are basically dual-stack, and using V6 nodes sometimes results in lower latency. Gamers shouldn't expect too much. The NAT system follows the rules of the IPv4 world, while most game servers are still running on V4. The pain NAT3 is still present. To save the game, you have to follow the old recipe by opening UPnP and modifying bridges.
As for speed tests, nothing has changed—your 300 megabytes are still 300 megabytes. IPv6 doesn't increase speed; it just straightens the road, not widens it.
the two pitfalls I've encountered, both are harder to handle than the switch itself
Pitfall 1: IPv6 may not be in optical modem router mode. After my first trip, I couldn't get the address no matter what. After a long search, I found that the optical modem was dialing the number; it had "used" IPv6 and didn't transmit it downward. Two methods: turn on the IPv6 switch on the LAN side of the optical modem (different paths differ; some are hidden very deeply, the same backend encountered when check public IP); Or simply switch the optical modem to a bridge and let Mercury dial in, so V4 and V6 are managed by the router. I was too lazy to use the bridge, so I flipped through the optical modem and turned on the LAN side switch to fix it.
Pitfall 2: firewall blocks all incoming traffic by default . This is actually a good thing—every device in your home now has a public address, which means you're completely exposed on the internet, with the router's V6 firewall guarding your door. But if you want to access the NAS from outside, you have to access that port in the "security feature →IPv6 firewall" (sometimes called filtering rules). The symptoms of not letting me through are: the address pings through, but the port just won't get in. I was puzzled for half an hour. The logic is the same as forwarding ports on IPv4, except v6 doesn't need forwarding (the address is already public), so only the release step remains.
there's a small pitfall: some older devices run V6 and end up lagging. My family has a 2016 TV box. Some apps spin in circles because there is a problem with its v6 protocol stack. DNS parses to v6 addresses but cannot connect. This doesn't require the whole family to perish; just turn off the IPv6 of that device alone.
sit down according to the numbers, and here's the order of the actions
| your situation | should you turn it on |
| want to connect to the NAS, surveillance cameras, or home computer from outside | and turn it on with your eyes closed—this is the most valuable scenario of the V6 |
| just browsing the internet, watching videos, or playing games | you can turn it on or not, but turning it on doesn't hurt |
| If you have old devices at home (like a ten-year-old TV box), you | turn them on, but be cautious and turn them off if they lag separately |
| broadband side can't test V6 (nor does it have data usage), | stop fussing and find the carrier first |
sequence consists of five steps: traffic test-ipv6.com confirm broadband V6 → melogin.cn to turn on the background switch → Confirm running status and obtain the 240E address → If remote is needed, release the port to the firewall → If the old device has issues, roll back separately. The whole trip takes ten minutes, and without using the optical modem, there's zero risk. At worst, just turn the switch back on and nothing will break.
