Deepcuts
Regular Contributor
Hello,
I have a location with strange WiFi problems.
Had an old TP-Link WiFi router that would occasionally drop users from WiFi.
Disabled the WiFi radio on it and put a Cisco WAP321 as an AP.
Same story with the Cisco AP also. Sometimes clients are able to connect, too many times they are unable to connect.
So I got a brand new Asus RT-AC68U and set it up as a router and using the Cisco as an AP.
I kept the Cisco AP because of the location it is placed (center).
Same story. Sometimes clients are able to connect, too many times they are unable to connect.
So I took down the Cisco AP and the old TP-Link router and left the Asus RT-AC68U as a router and WiFi AP.
Wired internet works like a charm, but WiFi 2.4 Ghz in Auto mode does not.
Meaning, clients can't even see the SSID. The only way to connect to the WiFi network is to set the 2.4 Ghz to "Legacy" Wireless Mode.
Using Merlin's fw 380.62.1.
So, either there is some serious radio interference in the area or there is a firmware problem somehow.
Anyone else in the same boat as me?
I have a location with strange WiFi problems.
Had an old TP-Link WiFi router that would occasionally drop users from WiFi.
Disabled the WiFi radio on it and put a Cisco WAP321 as an AP.
Same story with the Cisco AP also. Sometimes clients are able to connect, too many times they are unable to connect.
So I got a brand new Asus RT-AC68U and set it up as a router and using the Cisco as an AP.
I kept the Cisco AP because of the location it is placed (center).
Same story. Sometimes clients are able to connect, too many times they are unable to connect.
So I took down the Cisco AP and the old TP-Link router and left the Asus RT-AC68U as a router and WiFi AP.
Wired internet works like a charm, but WiFi 2.4 Ghz in Auto mode does not.
Meaning, clients can't even see the SSID. The only way to connect to the WiFi network is to set the 2.4 Ghz to "Legacy" Wireless Mode.
Using Merlin's fw 380.62.1.
So, either there is some serious radio interference in the area or there is a firmware problem somehow.
Anyone else in the same boat as me?
Last edited: