Update.
My conf seems to work as expected, but it took a few hours for APs to find the 
controller. Since then even new APs find the controlles in a few minutes.
Controller: Alcatel-Lucent OmniVista 2500
APs: OAW-AP1321-RW

Thanks for your help!

On Mon, 10 May 2021 15:30:01 +0200
Radek <r...@int.pl> wrote:

> Thank you Denis,Stu,
> 
> I added option-138, the syntax is correct now but the AP doesn't connect to 
> the Controller. 
> Did I missed any other option(s) in my dhcpd.conf or should I look for the 
> reason at the Controller side?
> 
> subnet 10.109.3.0 netmask 255.255.255.0 {
>         option routers 10.109.3.254;
>         range 10.109.3.201 10.109.3.220;
> #option option-138 10.109.3.100;
> option option-138 A:6D:3:64;
> 
> host [...]
> 
> On Thu, 6 May 2021 11:45:43 +0200
> Denis Fondras <open...@ledeuns.net> wrote:
> 
> > Le Thu, May 06, 2021 at 10:48:55AM +0200, Radek a écrit :
> > > Hello,
> > > I want to use dhcpd server to push Wireless Controller's IP address to 
> > > the APs.
> > > 
> > > According to this:
> > > http://systemnetworksecurity.blogspot.com/2013/02/adding-custom-options-in-isc-dhcpds.html
> > > https://www.secuvera.de/blog/capwap-dhcp-option-138-auf-isc-dhcpd-server-einrichten/
> > > I need to add *option capwap* to /etc/dhcpd.conf
> > > 
> > > option capwap code 138 = ip-address; #Custom Option capwap
> > > option capwap 192.168.1.110; #WLAN-Controller-IP
> > > 
> > 
> > Have you tried something like :
> > 
> > option option-138 C0:A8:01:6E;
> > 
> > ?
> > 
> 
> 
> -- 
> Radek
> 


-- 
Radek

Reply via email to