I have no clue on how to fixed this problem. Its been a while and upgrading the FW or reset using the script did not help. Basically the WIFI is broken and no way out.
Current setup routeros 7.14.1 and wifi-qcom 7.14.1
Anyone know how to make this right?
thanks
Can you share your configuration ? Did you try to downgrade ROS to version your WiFi worked ?
Also:
Are you sure your wifi is not using a channel which your client devices can not see ?
AX tend to favor the higher frequencies but quite a lot of devices are unable to use them.
I had a similar problem which I posted a while back. 5GHz Wi-Fi disappeared although 2.4GHz Wi-Fi was fine. My problem was that I’d specified a single frequency for 5Ghz (5500) and a radar event was occurring. This ended up disabling the interface. IMO in situations like this, RouterOS should switch to auto but it doesn’t. My fix was to specify 5500, 5180 so there was a failover and implement as scheduled switch to put it back to 5500 every hour. These radar events are IMO fake.
But not sure if you’re using fixed frequency and as said, 2.4Ghz always kept working. Sounds like you’re getting nothing at all.
Indeed - some older kit struggles with channel 149 and above.
First of all, thank you for all the replies, I have tested for resetting and using the original script and this is failing since neither 2.4 nor 5 have been detected. Then I set it up manually in which the same outcome occurs.
for 5Ghz
for 2.4
Security using WPA2PSK and WPA3PSK
Country: Indonesia
Again I’m also successfully setting up the new hAP AX3 without problems so wondering why hAP AX2 fail
P.S. All the devices in the office won’t be able to find the SSID including mobile and PC and Laptop.
Can you see SSID when frequency set to auto ?
Aside: what does this do?
This is the frequency range of the first 80Mhz wide band. I know if you specify 5180, you get Ceee, 5200 eCee etc. Does RouterOS sort of do some check to see which extension band works best?
ROS tends to use standard wide channel (e.g. 80MHz) ranges. The range defines 80MHz channel number 42. When it comes to channel layout (Ceee, eCee, …), ROS again tends to select Ceee (and it seems that the picky clients prefer this layout as well), but if admin sets center frequency to value other than 5180, ROS will select channel layout in way it still fits the standard wide channel (e.g. if frequency is set to 5200, then ROS will select eCee)..
I’m not sure if ROS actually does measurements accross all 20MHz channels, members of inteded wide-channel, to select least occupied channel as Control channel. My (limited) experience doesn’t support his kind of theory.
Same here. The only reason I could see for specifying a range is if did find the best 20Mhz channel for the control channel. But does that actually help? I’ve suggested a few times that a detailed whitepaper and/or video on the logic behind Wi-Fi channels, failover, noise checking, DFS, CAG, Tx power etc. would be most useful as there seems to be a lot of guessing going on.
Wifi broken. Turns out: admin applied extra special configuration already. 101 of troubleshooting: start off with the most minimal. If working: change one setting at a time. Step by step. Observe. Revert one step in failure.
I first tested running Mikrotik scripts using Capsman to be sure and no SSID was found. Reset 2nd time and do manual installation, the outcome is still the same. Turn off 5Ghz and only 2.4 also no luck. Both SSID were not being able to discover.
In this complete thread… where have you once showed your current and complete config ?
It was already asked in the first response you got.
Wifi setting can be many things, and so many things can make it fail, complete config for wifi really needed here.
Not only config … What is the wifi interface status giving?
Same situation here…
Got second hand HAP AX2…
Router is not visible to AC devices at all…
RouterOS 7.14.3 with wifi-qcom…
I did reset - nothing changed,
netinstall ROS 7.14.3 + wifi-qcom - no result
then downgraded to ROS 7.7 and installed wifiwave2, did Reset configuration, but no SSIDs…
And I just see here people using the default configuration over and over, and still hoping it will work in their case for their client devices, by reset or re-install.
Well this is not the case for them. 802.11ax is advanced in possible frequencies that are used in the default configuration (as this default is very undefined because AUTO is used).
Resetting and Netinstall of recent ROS versions will not bring any improvement. Above ROS 7.12 version, chances of having a not suitable default config for your case are very high.
Get the basics right.
What is your Country? Is it set in the config (it never is set by default) ? What channels are allowed in your Country? Is a usable range selected? (the default may contain unusable channels for your country, an empty range is not OK then). Your client devices will only see usable channels for your country/region!
Did you at least wait the “radar detect” period (1 minute for radar, 10 minutes for weather channels) before checking on the availability of the SSID?
What is the wireless interface status? Do check it !
In addition to what @bpwl wrote (or to emphasize statement “802.11ax is advanced in possible frequencies”): it is possible that your ax2 selects frequency which is not supported by wifi clients. So when in doubt, try to manually set frequency to 5180 … it’s a channel available since The Big Bang (already in 802.11a), so almost certainly supported by all 5GHz wifi devices. Only if this setting doesn’t yield detectable wifi one may assume that there’s some hardware problem with the AP.
it is possible that your ax2 selects frequency which is not supported by wifi clients.
This isn’t just limited to AX, it’s a consideration with AC. In my (surprisingly visited) RouterOS document, I have this table:
Footnote 8 states “Some client devices can use this channel or above, e.g. generic Android tablets”. I avoid that channel anyway on hAX ax2 as the Tx power is only 9 (!). In some cases, the reason clients can’t see the interface is due to incorrect implementation of 802.11d whereby the access point (the hAP ax2) transmits the country code and the client then uses this to determine which frequencies are allowed. Under Windows, there is sometimes an option to disable 802.11d which then allows them to connect. No such luck on my cheap Android tablet. Realtek chipsets are the usual candidates.
Hello, old topic, but the same problem here - second hand hAP ax2, latest RouterOS 7.16.1, wifi-qcom 7.16.1. No matter what I do (reset, Netinstall ,Quick Set, automatic vs manual channel selecting, downgrade to AC/N), no SSID is transmitted. Moreover internal scanning tools do not work - “Scan” shows no data, “Freq. Usage” lists channels, but shows load 0-6 % with around -90 to -99 randomly even for busy channels. Looks like final stage in radio transmitter is busted, but I have no tool to verify electrically.
I wonder what is the cause, as I’m going to order some ax2 for a new project.
What is the wifi interface status giving?
Bottom line also important … “detecting radar”?
If false or real radar was detected, that transmission channel is out for 30 minutes !