DHCP Across Wireless Bridge
anthony.hoppe at gmail.com
Mon Dec 30 22:14:29 UTC 2013
Just wanted to confirm that setting the EnGenius WAP to "WDS Bridge" did
not work. It also has a "WDS Client" mode, which I don't quite
understand. In this mode, it claimed that it had associated with my
wireless network, but it and all devices behind it were unreachable.
I am still curious as to why Cisco's implementation of DHCP seems to
work in this setup. I will do some dhcpdump-ing with the Cisco DHCP
server enabled, see how it looks compared to isc-dhcp-server, and report
back (I will reply to my response to Glenn).
On 12/29/2013 10:39 AM, Anthony Hoppe wrote:
> Hi Simon,
> I have always been under the impression that if I set the EnGenius WAP
> to "WDS bridge", it will only be able to associate with other EnGenius
> WAPs that are in "WDS bridge" mode. In my current setup, the EnGenius
> WAP associates with a Meraki MR16 WAP. I suppose I could give it a try
> and see what happens.
> Though, the interesting thing is that Cisco's DHCP server seems to work
> fine with the current setup. I wonder what it does differently...
> ~ Anthony
> On Sun, Dec 29, 2013 at 9:54 AM, Simon Hobson <simon at thehobsons.co.uk
> <mailto:simon at thehobsons.co.uk>> wrote:
> Anthony Hoppe wrote:
> > I am using an EnGenius WAP (I can't find and/or recall the model
> at the moment) in client bridge mode.
> I have some EnGenius stuff in use at work - and when setting up a
> bridge there is a bit of a gotcha. Working from memory (it's a long
> time since I set htem up), you need to set the client end into WDS
> mode, not client bridge mode. I know it seems back to front, but in
> client bridge mode, all the clients appear to come from the MAC
> address fo the client bridge; in WDS mode, you get to see the client
> MACs. If the MAC address is mangled, the client won't get the right
> packet back - and DHCP won't work.
> dhcp-users mailing list
> dhcp-users at lists.isc.org <mailto:dhcp-users at lists.isc.org>
More information about the dhcp-users