Good info, Aaron.
First...I'm hoping it was just a typo, but you seem to be indicating that you setup both APs with a static address of 192.168.1.101
If that's the case, it shouldn't be causing the primary problem....but it's still an issue that would need correcting.
If you followed that billeted list of commands, I see one major potential issue (not sure why they included this one command).
This one:
- bridge channel-list 5GHz 36,40,44,48
With this command, you're setting up the client-bridge AP so that it will only ever look for host APs that are operating on those 4 channels. If there are none nearby on those channels though, it will never be able to connect to anything, right?
I'd highly recommend including all of the possible channels that your 'host' APs are capable of operating on (or if statically assigned, those channels)
Or....set the Channel to "Smart"...which will more directly reflect how a normal wireless client behaves....it scans all channels looking for APs.
1 - Do I have to configure any bridging properties on the AP#1 that is connected to the wired network with internet access? None of the guides I've read mention anything about configuration on the "host" AP, but since I can't get this working I'm wondering if some configuration is necessary on AP#1.
Answer: NO. When setting up client-bridge APs, the only work that needs to be done is on the client-bridge APs themselves.
2 - Do I have to load a special firmware version to be able to access bridging configuration in the web GUI? Right now none of those configuration options are there and I have to do everything through ssh/command line. I know this was the case for some APs in the past that didn't have a web GUI at all and you had to download the firmware that included the GUI.
Answer: The very early releases of WiNG code (if I recall correctly) only allowed for the client-bridge setup via the CLI. The newest versions of WiNG code allow for full configuration via the GUI.