Thanks. I sincerely appreciate the response. I’ve pretty much done exactly what you did (after the fact), in killing the dual-frequency setup. I guess I’m trying to figure out whether my camera-related connectivity issues are really just a Peplink issue. I.E. the camera is suddenly unable to even successfully connect to the Peplink, but having also discovered that my other existing (stable, in one place in the house) devices seem to be continuously hopping around (even before yesterday, when I eliminated the dual-frequency configuration), I’m now not certain whether I have a camera problem, or whether this Peplink “oddity” is actually an issue. Even with everything now frequency-segregated, the camera still won’t connect, so my gut tells me that IT is the problem, but the Peplink thing sorta leaves me less convinced that it has its head in the right place, too.
None of this is helped by the fact that both devices (Peplink and camera) had recent firmware updates. I did roll back to 8.1.1, and that didn’t help, but I also could see in the logs that the hopping was occurring there (for my other devices). I would have thought a device would not disassociate itself from a frequency unless it decided that it was problematic.
Much as you have done (because I am in a somewhat rural area) I had previously selected specific channels. I use WifiInfoView to check out what else is being used, to avoid any sharing. Even though I verified no collisions in that setup, I tried disabling my dedicated channels, just to see if that made a difference, but it did not.
Anyway, I guess I am just whining… I do appreciate your input, and (at least) knowing that someone else has seen the same frequency hopping behavior. I’m probably going to have to break down, and buy a new camera, if for no other reason that to definitively rule that out as the culprit.