Pepwave SOHO MK3, FW 8.1.2, frequency hopping

Just wondering if anyone has seen this. I’m not sure how long this has been going on, and only discovered it when attempting to resolve a connectivity issue with a camera. Note that all of my WiFi networks have always been configured with both their 2.4 and 5.0 GHz networks enabled.

Specifically, in the AP Event Logs I am seeing that multiple connected devices are, every few minutes, hopping back and forth between the two frequencies. These devices are not being moved around (within the premises) when this is happening. it makes no sense to me why they would hop around. Am I just missing something obvious?

Thanks for any/all input.

Hello and Good Day

I have had that happen also in the past.
I made separate ssid for the two frequencies and it solved the problem.
So for devices that only work on the 2.4 have their own AP.
And devices that have 5 capability have their own AP.

So if the ssid is, CAM WiFi only tic the 2.4
And this ssid is, iPad WiFi only tic the 5
Here is our setup.

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.

Thanks again.

Hi Serenity. I also use 2.4 and 5GHz devices with my SOHO MK3 without “hopping” issues with a single SSID. I have “Band Steering” set to FORCE in Advanced AP settings—this means any device capable of 5GHz must use it and the others use 2.4. Hope this helps.

1 Like

Oh wow!! Gosh… I semi-hate the question-mark thingees. I had tried like the dickens to be sure that I had clicked all of those things, to review what sat behind them. Obviously, many are just “help” related, but I COMPLETELY missed that one, and (obviously) had NO idea that capability existed. Well, I’m going to have to go back and completely re-read the manual, to see what other things I missed when I set all of this up a few years back.

THANKS for that. That will at least assist in better isolating where the fault lies (and it is what should have been done in the first place, regardless of my current problems).

And if you decide you may need new cams. This is a great option.

I try not to plug products but……

They are very versatile and cost effective. We have ten of these cams and never have a problem.

Thanks for the tip!


This whole problem that I was chasing is (was) a Peplink bug. ANYONE WHO IS RUNNING 8.1.2. on a Surf SOHO MK3, needs to IMMEDIATELY go to the Downloads page (NOT the Beta Firmware page), and download the version “8.1.2s052”, that you will see there, and install it NOW.

As alluded to earlier, what I was seeing was what seemed to be serious issues with my WiFi, which I eventually deduced as likely being specific to the 2.4 spectrum. It turns out that 8.1.2 seriously frak’ed up that spectrum. A camera (that is 2.4 only) that had been working perfectly fine, seemed to now not even be able to see the network it had been on, and I even ordered a new one, just to figure out if the camera was the problem. The new one arrived today, and was doing the exact same thing, and in doing another search (“Google is your friend…”), I stumbled onto a post where someone pointed out that “yesterday” a new firmware was released, and “lo and behold” it definitely fixed my problem.

All for what it is worth…

1 Like

I can’t find what 8.1.2.S052 fixes. I see the release notes for 8.1.2 but not the s052 variant. Anybody know what this fixed?

@tcpip95, this should be what you are after.

WeiMing… As I started this thread (having had this issue), just a suggestion, OR, maybe I’m just not on the right mailing list(??). Certainly, my email address is a part of several different Peplink systems, as I would assume to be the case for numerous other Peplink users. You guys should be making better use of that “pool” of addresses. If anything EVER deserved an “email blast” about a problem, this situation did.

As you alluded to in your post above, one of the first things that I did was use the system’s “feature” that allowed me to reboot, and restore 8.1.1. Obviously, whatever this bug entailed, caused/allowed it to “diddle with the hardware”, somehow “latching” the hardware into a state that made it (for lack of a better way to describe it), permanently impaired, thereby leaving the 8.1.1 (and earlier) firmware, no better off than the 8.1.2 firmware. Obviously, the s052 update included some bit of code that “unwound” (in the hardware) whatever problem had been created by the 5011 build, but for those of us unlucky enough to have applied 5011, we were pretty much “pulling out hair out” trying to understand what had happened to our environment. (The fact that rolling back, didn’t remove the problem, just made ME start thinking that the problem HAD to be in my other hardware components. That led to a whole lot of frustrating, and wasted, time and effort.)

So, again, this was a perfect example of “when” someone should have considered sending a blast to the community. Not just for the final s052 update, but the instant that someone realized that 8.1.2 had semi-permanently impaired the 2.4Ghz environment on these devices (i.e. impaired enough that it required a new “chunk of code” to undo the damage).

If there’s something else I should be “signing up for” at Peplink that would give me better visibility to ongoing issues (and/or even just “when” beta and production firmware releases occur, instead of me having to just perform recurring checks of the website), some of that additional communication to the customer base would at least “lessen” the damage and frustration caused by this specific event.

All for what it is worth…

@Serenity, maybe you can subscribe to the “Announcements” section, so, when there are any known issues published you will get notified?

Way to subscribe and get notified.

Do you think that help?

1 Like

thanks for the screen cap. I had briefly looked at those some time ago, but never snapped on the fact that the “bell”, at the far right, was the critical component that made all of the stuff (at the far left), generate messaging.