[WENED]

There has been many posts about the 2.4Ghz band including many by myself.
I have mucked about a lot lately and have discovered some very interesting things for which I don't have any answers but may help others in developing a workable network.

My most recent configuration consists of three of my routers each running 2.4Ghz 20Mhz Channels 1, 6, 11 N/G Mode WPA2 Personal CCMP-128 (AES) and no VAP's

I was trying to shift some of the load to spread out amongst the 3 routers and was able to do so even though some signals are a bit weak to where I moved some cameras. However all did go well.

Almost immediately I began getting disconnects and my Android devices would not connect properly or at all.

Even though all three routers had the same 2.4Ghz configuration I was able to move devices around and ultimately stop all the drops.

ESP8266 devices are all connected to either the 1200 or 1900

Specific IP cameras work properly on when connected only to the 1200 or 1900 but others will only work on the 3200.

My Android 8.0.0 phones won't connect to the 3200 but work properly on the 1200 and 1900

My Android 8.1.0 TAB is opposite and will only connect to the 3200 unless I change the Mode on the other two to Mixed which then causes drops with ESP8266 devices and some cameras.

Definitely food for thought. Even though all three are configured the same, their 2.4Ghz is definitely different.

[ad19]

Have been facing this issue for the past few builds, which has forced me to go back to my 2018 build, where all works well.
I have 2 VAPs and it kills the 2.4g network in a few hours, with the same issue - android devices cannot connect and the bonjour printer also cannot be discovered.
Not sure if this is happening in non-Marvell devices but if it ain't then this could be related to the new firmware released a few months back by Marvell/ Linksys.

[blkt]

There has been an issue with VAP killing 2.4Ghz since late February and Marvell WRTs are not the only routers affected.

SVN has several tickets open from different users, not including forum reports.

Here's the most recent example.

[WENED]

**** 24 Hour Update *****

After 24 hours running all routers and devices remained stable without any re-connects or such.

At that point I fired up a second desktop to monitor my IP cameras. There is always one desktop constantly monitoring.

Almost immediately my Sonoff devices started to Stop/Start in the logs. Although none disconnected it appeared that they were having comm problems with the Internet now that the cameras were supplying two feeds out to the network.
After about two hours of this setup, my remote 1900 crashed and went into a reboot. Everything reconnected properly but the Sonoff devices continue to log entries.
I have turned off the second desktop to evaluate the effect and will report after a few hours.

Although I indicated earlier that Internet access through the network is imperative, it also appears that network traffic can also have a detrimental effect on the operation and for some reason will overload the 1900 V1 to a point where it can only recover by a reboot.

I have not seen a reboot with any other WRT routers with similiar setup but the 1900 V1 is the only one with half the RAM of any other wrt.

**** Latest Update *****

Have been running now 36+ hours with only minor glitches but overall extremely stable. Only one feed from my IP cameras to one Desktop.
Started a large download and fully loaded the Internet download, but had no disconnects on any devices.
Also the 1900 V1 has not rebooted.
It is apparent that the IP Camera firmware and ESP8266 firmware are extremely dependant on network/Internet access and when the network is heavily loaded they time out and cause disconnects/reconnects.
On the 1900 V1 I have 5 IP Wireless cameras, 3 IP wired cameras, and 5 Sonoff devices. The 1900 seems to be able to handle this volume until I activate a second Desktop requiring a second feed from the cameras. At this point all devices begin to have connectivity problems. It appears that this constant re-sync causes the Kernel to log considerable errors and ultimately crash the 1900.
I was considering downgrading the 1900 to r31924 as it listed as the most stable, but I am unable to find this release. If anyone out there knows of another stable release for the 1200 V1 & 1900 V1 I would appreciate the help. I Have tried a few older releases back into early 2019 but don't see any difference.
I mention the 1200 V1 because I have a constant log entry (about every 15 minutes) for two devices doing the Start/Stop stuff. Isn't causing any particular problems but I would like to also see if an older release eliminates this.