[rinja]

EOC-5610 is set as client/bridge with LAN/WAN DCHP forwarder configured...two host computers (windows & ubuntu) will not receive DHCP lease thru EOC-5610...tried connecting EOC-5610 to different UBNT APs (PS2 & NS2) & different security (WPA & WEP) but no DHCP lease to host computer...host computers will work fine thru EOC-5610 when static IP set on host computers...maybe i'm just overlooking something in EOC-5610 configuration...any ideas?....thanks...;-}

[Sash]

i never used it

but why dont u use wds-ap/sta? client bridge is buggy imho

[rinja]

yea, i already knew it was buggy, but i'm successfully using an EOC-2610 client/bridge & DHCP forwarder turned on for another application...when i only have one device (laptop) to connect to a distant AP, it's really sweet using something like EOC5610 as a really powerful client device in places like Afghanistan...;-}

[rinja]

k...done some more testing & here's what i found:

the EOC-5610 in client/bridge mode will not issue DHCP leases to host computer when EOC-5610 set as "DHCP Forwarder" and trying to connect to any AP...when EOC-5610 set as "DHCP Server and Server Disabled" it will allow DHCP leases to host computer if EOC-5610 is connecting to anything but Ubiquity (tested PS2 & NS2), but DNS will not resolve when connecting to any AP (to include Linksys, etc), so you have to set DNS manually...the EOC-5610 with native Engenius fw will receive DHCP leases without any problems as a client/bridge to various other APs (UBNT, Engenius, Linksys, etc)...with dd-wrt installed on the EOC-5610 the client/bridge mode will not issue DHCP leases to host computer when connecting to Ubiquity APs with native AirOS...so, bottom line in my opinion; it doesn't seem to be a hardware issue since client/bridge works with native Engenius fw but not dd-wrt...not necessarily a problem since all u have to do is assign a static IP/DNS if wanting to use client/bridge mode...the only issue is if wanting to use this mode in a DHCP only network...cheers...;-}