abdullah salahaldin
Occasional Visitor
Awesome, thanks for the update
Have you seen this thread:Hi Merlin,
Did 386.3.2 include all the vulnerabilities which were addressed with stock ASUS Version 3.0.0.4.386.45375
2021/08/31? Based on someone else's post in a TPLINK forum, I noticed ASUS made several updates to WPA in the 8/31 release as follows and I'm wondering if this is what is causing many of our TP-Link Smart Bulb WIFI disconnect issues once we upgraded from 386.3.2 to 386.4. I'm just trying to isolate so we can get TP-Link to fix.
WPA Vulnerabilities addressed with 3.0.0.4.386.45375 included:
- CVE-2021-30004
- CVE-2021-27803
- CVE-2019-11555
- CVE-2019-9499
- CVE-2019-9498
- CVE-2019-9497
- CVE-2019-9496
- CVE-2019-9495
- CVE-2019-9494
- CVE-2017-13086
- CVE-2017-13084
- CVE-2017-13082
- CVE-2016-4476
- CVE-2015-8041
The problem isn't pertinent to TP-Link devices only, my LG washer and dryer are experiencing the same problem, they connected fine with my GT-AX11000 router running 386.3-2 version firmware, but not with the 386.4 upgrade.
All my IoT devices were working fine with my GT-AX11000 router running ASUS original firmware up to version GT_AX11000_300438644266, and since I had connection problems with all their newer firmwares, that was why I switched to Merlin firmware, but now it happens again.......
AX88/386.4_0: The bulbs are KL-130. One is about 10 yards from the house. I do not use guest. I do use an AImesh, and looking at connections, it shows most are connected to an AC68 mesh station and an AC88 mesh station. So that could very well be the difference. I also have in wall switches HS200/HS220, along with a variety of plugs (HS100/HS105/HS107/KP400). Some of those are connected to AX88, but others to the mesh. While the TP-Links are fairly stable, I am having problems with Amazon Echoes often not reconnecting.HI Elmer,
What model bulbs are you using? If newer than mine, maybe I'll upgrade them all so I can use the newer firmware. Also, are you running yours in a guest network? Did you change any other settings on the 2.4 ghz radio?
I have tried both the 2.4ghz channel on both auto and channel 6 (least congested channel) and and could not get any of the bulbs to stay connected. No AImesh activated, only one AX88U router in my house. I tried turning off universal beamforming and airtime fairness and it did not help. Ironically, all my bulbs work with 386.3.2 with both Airtime fairness and universal beam forming enabled.
@CLK had the same problem as me and can only get his bulbs to connect if he sets his 2.4ghz wireless mode to legacy which would not work for me given the bandwidth limitations for non IOT devices.
Awesome so it will work its way into merlin eventually since asus knows it is their faultHave you seen this thread:
https://www.snbforums.com/threads/a...devices-tp-link-hs200-hs105-switch-etc.76590/
It looks like ASUS release a beta firmware on Jan 5 that address this issue with TP-Link / Kasa bulbs and switches.
Did you clear the InstantGuard settings on the Android? If not Instant guard will never work.Neither asus app clean install nor instant guard clean install didn't fix the issue. On official Asus firmware right before uodtae it was working just fine. Now its not.
Yeah, I guess we wait then... I have a lot of TP-Link devices too. Ugh.Awesome so it will work its way into merlin eventually since asus knows it is their fault
YEs tried that and no difference. Only legacy mode works.
Too many Elmers…AX88/386.4_0: The bulbs are KL-130. One is about 10 yards from the house.
SSID: hancockvfa2 | Mode: AP | |||
Noise: -89 dBm | Channel: 40/80 | BSSID: F0:2F:74:xx:xx:xx | ||
DFS State: Idle | Time elapsed: 0h 0m 0s | Channel cleared for radar: 40/160 |
SSID: hancockvfa3 | Mode: AP | |||
Noise: -89 dBm | Channel: 149/80 | BSSID: F0:2F:74:xx:xx:xx | ||
I don't remember. Check in the changelog, it's always documented there every time I upgrade to a newer GPL code base.What factory firmware is 386.3.2 based upon?
Some but not all (and I don't have an accurate list to share, sorry).Did 386.3.2 include all the vulnerabilities which were addressed with stock ASUS Version 3.0.0.4.386.45375
2021/08/31?
DFS channel isn't used on the second radio.One little nit-noid issue, under the wireless log tab, the DFS Status line is not displayed for 5 GHz-2. However, the DFS status information is present if you view low level details. Example below
I've had weird problems with a number of RTL USB 2.0 adapters over the years. I had to disable "Protected Management Frames" before the device could connect, though in my scenario I could see the network but not be able to connect - across many versions of firmware.
Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!