Why does Feiniu FN Connect sometimes move faster, sometimes slowly? When you disassemble it, it has two legs. After streamlining IPv6, the speed increased tenfold

last week on a business trip, I was at the office wanting to pull a 1.2GB compressed file from my Feiniu NAS at home. The Feiniu app connects smoothly to the FN ID, but the progress bar is sluggish. I glanced at the speed: 500KB/s fluctuates around 500KB/s. One GB takes more than half an hour. I couldn't wait and switched to a cloud drive transfer to get everything done. At that time, I concluded with FN Connect: at this speed, just check the file list.

ended up video calling my wife at night. She helped my mom tidy up the house, and when she had free time, she used her phone to browse through the NAS photo album at home. Photos popped up rapidly, never laging. With the same FN Connect and the same NAS, I was at work at a slow pace, but her phone data was smooth. I stared at these two things and finally realized that this service isn't just one path—it's two legs walking together, and which one depends on the network conditions at both ends.

first clarify what FN Connect is

Feiniu fnOS's built-in remote access service, located in the settings→ → FN Connect, log in to your Feiniu account, set up your FN ID, and turn it on and off to complete the process. Its biggest selling point is three "no uses": no public IP required, no port mapping, no domain name. It doesn't matter how many layers the NAS is hidden behind the internal network; when going out, just bring your FN ID to the app or browser and you can get it home.

Why did I drive it in the first place? Because my main router is a Xiaomi AX3000T, the official firmware doesn't have VPN server functionality, so if you want to use WireGuard to get home, you have to flash the device, which I find troublesome; DDNS plus port forwarding is possible, but pushing the NAS management port to the public internet always makes me a bit uneasy. A one-click feature like FN Connect is perfect for those who don't want to mess around. When I gave my mom a remote access phone, I was also looking for this. I just logged into the app with my FN ID, and she didn't have to remember any address.

break it down, it has three states: LAN, relay, and P2P

night, I went through the whole story. When FN Connect connects to a NAS, it actually experiences one of three states: when people are at home on the same local network and use local direct connection , the speed is just the internal network speed, unrelated to FN Connect; When you're away, the phone and NAS first try to "punch holes" to establish point-to-point direct connections, which is P2P; If you can't get through, the traffic will be rerouted through Feiniu's official servers, using relay . I wrote about this trick once before when I dismantled the Synology QuickConnect. Both companies used the same approach: first connect the wires, then punch holes, and if the relay fails,

my own scenario works perfectly: the company's WiFi isn't IPv6, the outlet is still dual-layer NAT, punching holes is impossible, so I can only use relay, 500KB/s is a typical relay setup; My wife's phone uses cellular data, and the carrier's network comes with IPv6 by default. My router's IPv6 is also enabled long ago, with V6 on both ends. Drilling a hole once succeeds, and the P2P direct connection runs right up to my home. The same service has two fates; the difference isn't the NAS, but the network access to the other end.

By the way, the official client doesn't have a bold status bar labeled "Current: Relay." I used speed as the referee: 1MB/s up and down, so it's 90% of the time. If it can run close to your home's uplink bandwidth, it's a direct . My home has 50MB of broadband uplink, and the ceiling for direct connections is just over 6MB/s. If this number matches, the judgment won't be wrong.

the leg of the relay is so slow and specific

slow relay isn't mystical, but an obvious channel limitation. In my tests, free relay was around 500KB/s, and other community members did the same, fluctuating around 4Mbps. The official FAQ mentions "privilege bandwidth" as a theoretical peak; in reality, it doesn't reach the network, but the community's conclusion is straightforward: speed limit is only the relay channel; P2P and direct traffic are point-to-point and not through Feiniu's servers.

What does

500KB/s mean? Let's reconcile it with a few things I do at home. Looking through the album and photos, after compressing two or three MB, the relay can only come out in a second or two. My wife's brushing method actually holds up for most of the relay as well; Upload a document report of several dozen MB, and it can be done within a minute—it's usable. There's another rule: during the 7 or 8 PM rush hour, the relay is discounted, and at that time, the photo in the album sometimes spins, but if you miss it for an hour, you'll be back in sync. But dragging video is a different story—online 1080P bitrate two to three megabytes per second, 4K goes up to 20 megapixels, and a 4Mbps relay channel can't even fill 1080P, let alone the dozens of gigabytes of original files in my NAS. If you want to watch the NAS at home on your mother-in-law's TV, relay is out of the picture.

Gained a Speed-Up Track: Streamline Both Ends of IPv6

want FN Connect to automatically switch to P2P, the most cost-effective way is IPv6, which costs nothing. The principle is simple: drilling holes requires conditions from both ends. NAS the router and optical modem on one end have IPv6 enabled, and the network on the other end also has IPv6. Only with both ends connected can you connect directly to the ; missing either end means you have to return to the relay. In community tests, after streamlining IPv6, FN Connect automatically switches direct connections and peaks reach 10MB/s—there are countless examples. My home has 50MB uplink, and in real tests, just over 5MB/s, just above the ceiling.

NAS I've written in detail before how to turn on this side of the router: On the router side, Xiaomi has a IPv6 switch in the 31.1 internet settings, and the modem on the optical modem has different for bridging and routing modes. On the other end of the visit, you don't have to worry about it—your phone naturally has V6 data, but you need to remember this rule: connect to the NAS with data outside, it's most likely a direct connection speed; Even company WiFi and mall WiFi are mentally prepared to be relayed Later, I switched to a different approach at work: I let my phone hotspot run on my computer and ride it, which immediately boosted speed. Although it used a bit of data, it was worth it when I was in a hurry.

there's a caveat to remind you: IPv6 is enabled but the router's firewall blocks all inbound entries, which is basically a free access. My Xiaomi was already allowing the NAS address through the firewall, so don't miss this step. Whether you let go or not, verification is simple: when you're out, connect your phone data to the NAS to drag a file, and if the speed keeps upstream, it's clear. If it's stuck at 1MB/s, go back and check again.

who should take a different path, and who doesn't need to move at all

FN Connect is not the only solution, nor is it the fastest solution. If your home has a genuine public IP with broadband, DDNS plus port forwarding is the right path. The speed limit is your uplink speed, and in the middle is no more than any vendor's server. I've written a complete three-lane comparison I've written about of these three routes. How do you check if you have a public network IP and you can also do a three-step self-check. If you have an ASUS router or are willing to put in some effort, you can build a WireGuard tunnel on the router to home. It's fast, stable, and even brings the entire internal network out. NAS is just a side benefit.

my advice is simple: first check if your home has a public IP address. If you do, use DDNS; No, FN Connect plus IPv6 is the most cost-effective combination, with zero cost and zero monthly fees, and speeds comparable to direct connection. As for external running naked WebDAV or SMB ports, don't touch them early. Passwords are clearly displayed on the public network, just like putting your house key locked in.

Finishing: First decide which leg to take, then decide whether to make a move

arrange the entire inspection and decision-making sequence into a table, moving from top to bottom:

my current situation is: both IPv6 ends are available, FN Connect is connected year-round, my wife goes to her parents' house to browse her album, my mom goes out to look at her grandson's photos it's all enough; If I really want to drag on big documents, I'll be at home or just wait until I get home. The free version is enough for me—keeping the slow leg in the middle as a backup, and connecting directly to the fast leg is my daily routine. Once you understand the logic of switching between two legs, this service becomes more reassuring to use.