As you can see in the image above, I'm standing next to a WAP, and it's not noticing that I'm in range.
This is not the first WAP i've added to my network, this is a second one about a hundred blocks away from the first one. Both have no range boosters.

The issue is likely in the detection of when infinity mode is enabled, as after it drains the infinity energy completely, it can still be opened, only then does the tooltip says it's in range of a WAP.

Compared to the previous issues, this is (relatively) minor, but still sort of annoying =)

I believe the issue is in the WCTGuiObject class, rangeCheck() function.

If field myWap is not null, it will always test to that WAP, and there doesn't seem to be any checks to invalidate the WAP cached in the myWap field, probably causing it to continuously only test against that initially cached WAP, it probably doesn't help that the getWAP method just retrieves the first WAP in the network.... and caches it.

ah...i didnt even think about this..it's such an old AE mechanic for the wireless terminals...good catch! yeah..it's totally just that I'm checking for the first WAP rather than a full collection of them...I'll work on this as soon as I have time..thanks for the good reports!