My (older, now) computer has started having issues with the WiFi cutting out.

I looked at the connection strength and saw it was sometimes dropping to 0, so I picked up a WiFi extender, and now it’s signal strength is usually around 70% (Windows only shows a percentage). However, even while monitoring the strength via a PowerShell script to watch the connection strength, it still drops out while the connection strength is > 70%. When it “drops out” I’ll run a speed test and see that it is basically uploading/downloading with kbps speeds instead of Mbps.

My other devices in the same room don’t seem to have any issues, so I’m wondering if my antenna or WiFi card (built in to the motherboard) are just failing.

I know PCIe WiFi cards are better, but unfortunately, as it’s an older computer (can’t even support Windows 11), the motherboard only has one PCIe slot that is in-use by the GPU.

So, any suggestions for a USB WiFi card that actually works? (Or additional ways of troubleshooting a failing wifi connection…)

Hi all, I've had a Netgear XR300 serve me fairly well for the past 5 or so years, but in the last few months I've had increasingly frustrating levels of failure. Things like sustained 100% CPU utilization, individual machines connected but unable to access internet, being unable to access the router admin page, individual machines suddenly having their ping go to 500-2000ms and bandwidth down to the kB range (I have symmetric 300Mbps up/down).

As a potential, I've been eying the Firewalla Purple to become my new router for a few reasons (Netgear not getting security updates, Firewalla has Wireguard support, etc.). The Firewalla only has short-range wifi, so my question is this:

Would using a Firewalla as a router and using the Netgear device as an access point for wireless connectivity be likely to mitigate these kinds of issues?

I've realized I lack the knowledge on which aspects of connectivity would be handled by two discrete devices, so I'm hoping to suss out if this is a viable solution.

Hi everyone, I recently finally setup the Ruckus AP unleased system that came with my townhome. After spending a long night learning how to properly configure the system I finally set it up in a way that provided me the best speeds/range without interference.

This was achieved by setting my Ruckus APs to manually sit on the DFS channels (60-140) via the Ruckus configuration app (shown here)

This has been working great as I'm avoiding the 10~ other wifi networks in the area that are all set to the standard 36-48 and 149-160 channels (wifi analyzer screenshot here) but I'm concerned I may be inadvertently violating FCC guidelines. Note I do not live near any military installations, but I am about 13 miles away from a major airport. Will the Ruckus APs automatically change channels if they detect radar interference or am I causing trouble for someone?

I'm sharing in case some of you are having a similar issue at work or at home, and to hear your opinion and/or similar stories!

I've been using Ubiquiti access points in my home for a few years now, and overall, they've worked very well. 3 APs giving near perfect 5GHz VHT80 coverage on DFS channels. LAN transfers are about 600-650mbit on laptops, which has proven to be plenty for wireless clients in my home. Keep in mind that this is a pretty basic setup... besides the APs, there's just the ISP provided GPON ONT which is also a typical all-in-one ISP solution (router, switch, AP, firewall, DHCP server...) with it's Wi-Fi turned off.

As I said, I was pretty happy with the results, however there was one feature that I could never get to work just right; roaming. You could be walking around the house watching a live stream and the stream would pause for 5-8 seconds until the roaming transition was over. Strangely, with VoIP calls, roaming would be about 3-5 seconds. Even enabling fast roaming features (which I believe is simply 802.11r) on the AP's controller would not give the results I was looking for. After days of tweaking TX power settings, channel selection and trying to implement Minimum RSSI (which I ended up not using), I finally gave up and resigned myself to the 4-6 seconds (oh, the humanity) of roaming time.

Fast forward to about two months ago and I added a new router to the setup (UBNT ER-4) and a switch (UBNT USW-24). Setup went smooth, already had some cat.6 cabling around the house, now it was time to actually use it. Had some fun setting up a guest Wi-Fi network on it's own VLAN, which was always a concern of mine; having "untrusted" devices connect to my network. The access points do client isolation on guest networks by default, but in my mind it wasn't enough as I have some file servers and time machines on the network.

Anyways, a few days after doing the setup I'm walking around the house with a livestream on my mobile and suddenly realize that it's not losing the connection. I try with a VoIP call and it worked flawlessly. I start walking around faster and still, the phone is roaming without an issue. I was very excited!

I'm thinking it must be the router that somehow solved the roaming issue. My first theory was that the DHCP server on the ER-4 was doing it's thing much faster than the ISP's device, allowing the wireless clients to actually roam faster. So I do a web search and I find some very relevant info. It was a thread on a forum and reddit thread with a sysadmin that was about to give up on the APs because of roaming issues. In both threads, there were replies about what switch were they using.

Apparently, some switches (Cisco and HP were mentioned), have a "MAC aging" interval setting which is way too high by default, or they simply have bugged firmware that doesn't allow the switch to "re-learn" the MAC address of a device on a different switch port. I assume that ISP provided "el-cheapo" gear has similar issues.

So, if you're having roaming issues with your wireless clients, check your switches!!!

Anyways, just wanted to share this story. Thank you for reading. :-)