Help with ENH 200 in Client Bridge Mode

[davidh]

It works for my MacBook Pro and my iPad, but NOT my shinny new Nest thermostats!

DSL modem connected to Net Gear N600 router in building A. ENH200 (client bridge) with EAP 300 wireless AP attached in building B. Nest seems to attach to the AP (I can see it in the "attached devices" screeen) and stays attached for about 90 seconds, then fails to connect to the internet. Can't figure out why some things work and others don't. I've tried every combination of settings I can think of. ANY suggestions greatly appreciated.

I carried the EAP 300 back to building A and plugged into the Net Gear router, then disabled the Net Gear radio, thus forcing all wireless traffic through the EAP 300. The Nest thermostats worked just fine. That would lead me to the ENH 200 as the problem, but I can't figure out how to isolate that piece if I carried it back to building A.

Reposted from General Questions. Thanks!

[davidh]

Made it work!

Somewhere in another thread on this forum I found a reference to a problem with the enh200 in bridge mode. Something about "transparent bridging" in a document that Engenius sent to someone. The issue was that the enh200 wasn't passing DHCP along. For the record my setup is as follows:

DSL Modem ==> NetGear WNDR3700 set as AP ==> ENH 200 in Client Bridge ==> EAP 300

I did not have the DHCP server enabled on the EAP 300 because I assumed that that service would be provided by the WNDR3700. In fact, it must have provided it in some fashion because my MacBook Pro and iPad DID connect over this link and function properly. The issues was with my new wireless Nest thermostats which report into a web service and can be controlled from any browser on the internet.

So I enabled the DHCP function on the EAP 300 and bingo, the thermostat connected. BTW, the MacBook Pro and the iPad still work, so there must be some difference in the way they connect to the internet.

Hope this helps someone else....