1. Current Location: Home >  NAS >  Testing of NAS connected to WiFi: USB network card not recognized, wireless bridge has a weak spot

Testing of NAS connected to WiFi: USB network card not recognized, wireless bridge has a weak spot

Comparison of two NAS WiFi routes: direct connection via USB network card and Mesh sub-router wireless bridge, including copy speed test comparison and the critical point of instant disconnections

My N100 Feiniu has been struggling by the weak current box for two years. Every time I want to plug in a USB drive or check the hard drive light, I have to squat in front of the box and work with my neck twisted. In summer, when the box temperature gets high, I get creepy. I mentioned this in my article about organizing weak current boxes > doesn't install the three Jellyfin direct connection lines).

After moving in, I realized I was stuck on one fundamental issue: during the renovation of the TV cabinet, only two network ports were left — one for the TV, one for the IPTV box, and no third port for the NAS. You can't just openly cross the corridor, right? So I started thinking about "connecting NAS to WiFi." This matter lasted two weeks, and in the end, the machine was moved back to its original place. But I have actually run both paths and figured out both the accounts and the pitfalls.

First, let's clarify: "connecting to WiFi" on a NAS is two different paths, not the same thing

Many people search for "NAS connected to WiFi," but in fact, two completely different things are mixed in.

The first is direct connection via USB wireless card: plug a WiFi card into the NAS's USB port, allowing the NAS to connect to home WiFi on its own, just like a laptop.

Route 2 is the wireless bridge: place a router (the Mesh sub-router I use) next to the NAS, it connects to the main router via WiFi backhaul, then pulls a short network cable from its LAN port to the NAS. The NAS is wired throughout the entire process, and the "wireless" part is handled by the router.

The cost difference between the two routes is very different, and the pitfalls are completely different. There's also the third power cat. I discussed it in the article about rental remediation. Don't touch old wiring at home, so I won't go into detail this time. I tried Route One first, then switched to Route Two after being advised to quit.

Route 1 USB network card: The driverless Windows setup doesn't work on NAS

I happened to have an AX1800 USB network card (RTL8832BU chip) I bought for my desktop, plug-and-play on Windows, I even wrote an article about choosing a network card. Plugged directly into Feiniu's USB port—no response.

In Feiniu App Center, there's a 'Wireless Network Card' app. Install, open, and refresh the WiFi list, but it's empty. SSH logs in and type dmesg | tail -30 to check kernel logs, but there is no card recognition record at all. After researching, I finally understood: Linux's support for these USB WiFi chips is "lucky." The new RTW88 family kernel comes with the 8822BU driver, but the 8832BU's USB ID isn't always on the support list. If not, you have to go to GitHub to get the driver source code and compile it yourself—and that's the best part. Synology is even more straightforward, with the official knowledge center clearly listing DSM After version 6.1, drivers for WiFi and Bluetooth USB devices will no longer be updated, which is essentially the official policy of discouragement.

Here's a self-check method, so you don't have to wait: enter SSH and first type LSUSB, then check if Wireless LAN appears in the device list. Yes, it means the system recognized this card, which is a configuration issue; If you don't even make it onto the list, it's just that the driver hasn't kept up. Don't waste time—just change the SIM or the new route. My 8832BU was not even on the list; I struggled for half an hour before giving up.

Not giving up, I dug out a stash of my old MT7601 network card (2.4G single-band 150M type, bought for my old desktop over ten years ago). This part is driverless—plug it in and you'll recognize it—but 2.4G, folks, in actual tests, it's only about 25MB/s, and it takes thirteen minutes to copy a 20GB image. Plus, my home has more than a dozen smart devices on my 2.4G screen, and if it can stay at 20 during the evening peak, that's already a great deal.

Lu Yi's conclusion: Whether it works depends on whether your network card chip is in the system's supported list—it's just a lottery. If you win, the speed will be halved again and again. Makeshift emergency measures, don't even think about being the main force.

Road 2 wireless bridge: Mesh sub-router with a network cable, speed test in

the actual test

Here's how I set up the second router: I moved the Redmi AX3000 sub-router from the bedroom to the TV cabinet, which I had Mesh networking at home (bought back then, see Mesh networking article) from the bedroom to the TV cabinet. It connects wirelessly to the main router in the study, and the LAN port connects a half-meter Ethernet cable to the NAS. From the NAS perspective, you're basically a wired device—no need to add anything.

For the return trip: from the living room to the study, separated by a load-bearing wall, the sub-router shows the return signal at -58dBm, which is within the healthy range. Next is the actual test report, placing the numbers from the cable era side by

side : : , ,
Connection method negotiable speedSMB measured copy
Gigabit wired (original) 1000M108~112 MB/s
wireless bridge (5G backhaul) 2402M45~60 MB/s
USB network card 2.4G direct connection, 150Mconnection, 20~25 MB/s

What does 45 to 60 MB/s mean? When the TV is placed on a 4K original drive in the NAS, the average bitrate of 90MB/s is 11MB/s, and the peak 150MB is only 19MB/s—more than enough. And here's a bargain: both the TV and NAS are plugged into the sub-router's LAN, and the data between them is directly forwarded by the sub-router's switching chip, so it doesn't take up any wireless backhaul. I tried several high bitrate segments, and none of them lag.

To make this path run steadily, two things must be done well. First, the sub-router positioning: the backhaul signal can be seen in the sub-router backend, so try to keep it within -60dBm. If it drops below -70dBm, the return speed collapses, and the 45 to 60 rpm shown in the speed table cannot be maintained. Second, don't use automatic 5G channels for the main router; manually pin one down — this one was traded for in an accident, which I will explain below.

So when will the return trip get tense? When NAS deals with the "outside world." qBittorrent download goes backward (my download machine setup is in this post: NAS as the download machine), and copying NAS files from the study computer also goes backward. The two incidents collided and fought over each other, causing the copy speed to drop from 55 to just over 30. Running alone is fine, but when two are on together, it's crowded—this is the fate of sharing air, the same logic as the calculation I used when I was struggling over whether to go over 10 Mbps (calculated in that 10 Mbps article).

The real fatal flaw isn't slowness, but instant interruption

I

actually accept the speed drive; 60 MB/s is quite decent for home use. What made me decide to move back was that night three weeks ago.

No matter how stable WiFi is, there are moments of outrage: automatic channel optimization, fine-tuning roaming, and even occasional momentary interference can cause a brief downtime of one or two seconds. Watching videos on your phone feels nothing, and the video lag automatically reconnects instantly. But on NAS, it's all about long connections

, focusing on serious work

That night, the main router automatically optimized the channel, jumping the 5G channel from 149 to 36 (I wrote about the channel before: How to choose a Xiaomi router channel), and the return trip was instantly interrupted. Then three incidents occurred one after another: the study was copying 80GB of footage, Windows immediately popped up a red box saying "Network name no longer available," so half of it was copied and redone; QB's seed farming tasks were all disconnected and reconnected; The worst part was the rsync off-site backup failure at 3:40 AM—silence failure. If it weren't for my phone alarm ringing and waking me up, I wouldn't have discovered it three days later (backup link is in this post: two NAS remote backups, the alert is I did it when I used my phone to alert you).

These things don't exist in the cable era. Network cables are just dirt—if they don't disconnect, they just don't disconnect, and there's no 'metaphysics.' In two weeks, I've experienced this kind of instantaneous disconnection twice. The frequency isn't high, but every time it happens, it's a real loss. For a machine that stores family photos and does serious work, I can't stand that.

Three types of people were assigned accordingly, so I moved the machine back

Don't just dismiss it outright; the wireless bridge route is the right solution for some people

: on top of for temporary wireless storage . is all wired and
Your suggestion
No openings during renovation, NAS placement really can't be laidthe wireless bridge, return signal kept below -60, sufficient
transition (renovation period, renting, relocation evaluation)bridge can be reversed anytime, more decent than using open cables
NAS only does light work: photo backups and a wireless bridge fordrives, with minimal losses even when interrupted
The full suite of video library + downloader + scheduled backupreliable, don't try to beat around these two weeks

My wrap-up: moved the machine back to its original position in the study, plugged the network cable back into the switch, moved the sub-router back to the bedroom, and everything was restored. If you really want a NAS to take care of the TV cabinet, the proper way is to run a exposed cable from the weak current box through the wall corner cable duct. It's a matter of just over ten yuan, more impressive than any wireless solution. By the way, the rules for the exposed cable and the crystal connector setup are both the network cable crystal connector article, so I won't repeat it.

These two weeks weren't wasted; at least I figured out one thing: the NAS is the device that needs network cables at home, bar none. WiFi is meant for things you carry and go around; the NAS has been sitting for seven or eight years, all for stability.

Read More


Copyright Notice Scan to read on mobile
All Rights Reserved: 《SHUNOT》 => 《Testing of NAS connected to WiFi: USB network card not recognized, wireless bridge has a weak spot》
Article URL: https://www.shunot.com/en/nas/1160.html
Unless otherwise stated, all articles are original by 《SHUNOT》. Reposting is welcome! Please indicate the original URL when reposting, thank you.

Contact Us

Online Consultation: Click here to send me a message

WeChat ID: master_135

Scan to follow