Hi Najee,
first of all, thanks for your interest.
I'm sorry for this post, but it's sort of a double one: I already posted a more closely reasoned question on "client mode" here
https://thehivecommunity.aerohive.com/s/question/0D50c000074NcikCAC/hivemanager-connect-apparently-fails-to-configure-an-ap130-in-client-mode
Long story short, I'm after extending wireless coverage and I thought to rely upon a "client mode" AP (which looked to me like sort of bridging, to some extent). So I took a spare AP130 and followed those instructions
http://docs.aerohive.com/330000/docs/help/english/ng/Content/gui/configuration/configuring-aerohive-ap-client-mode.htm
and particularly I tried the first method, "using a wired connection and HiveManager device templates".
Unfortunately it didn't worked at all: I found that apparently it does not seem possible to configure the "WAN side" wireless as backhaul mesh link if the "LAN side" wireless is in "client mode", and moreover the wired intefaces doesn't work at all, even better, it "disappears" from configure settings if I enable a "client mode" on any of the wireless interfaces.
Seemingly this issue is not only mine: please have a look at
https://thehivecommunity.aerohive.com/s/feed/0D50c00006svykjCAA
So now I'm wondering whether such a "client mode" is either an exclusive feature of HM Select accounts (while I'm a Connect user), or the above linked relevant documentation is just wrong (at least about the first method).
Obviously there's a third option, that is the problem lies between keyboard and chair, as already said.
But in case that will be the best thing, as it can have a satisfactory solution: do you have an handy one, by chance?
