What isn't matching (redux)??

I continue to be plagued by CPE disconnections that don’t resolve themselves in a timely manner because the CPE claims that no network satisfies its explicit connection parameters, so it proceeds to wander around indiscriminately asking every AP in the vicinity, "are you my mommy?" until it lucks onto the right one and re-establishes contact.

My problem is that I am unable to see any reason why the CPE would claim that “no network satisfies connect list.” To my eyeballs, the specification on both sides is identical.

Here is one example. Here is the configuration of the AP:
Screen Shot 2013-03-29 at 5.13.24 PM.jpg
Here is the configuration of the CPE:
Screen Shot 2013-03-29 at 6.03.46 PM.jpg
I can discern no difference between the parameters the AP is supplying, and the parameters the CPE is requesting. (Yes, all the starred out fields are exactly equal; keep in mind that the CPE does eventually match up with the right network.)

Yet, here’s the behavior I get upon disconnection:
Screen Shot 2013-03-29 at 5.22.24 PM.jpg
Is there a mismatch somewhere in here that I am overlooking? Are there some other panels I should be examining?

Boy, I wish that there was some sort of a debug flag I could turn on that would log why the CPE doesn’t think it matched each of the networks. Even if it only gave me one disqualifier at a time, I could eventually conform the two sides. This way, it’s all guesswork. :frowning: