FortAP220B DHCP no ACK

[andyh]

Hi, I' ve recently tried adding a 220B to cover a part of the building that the wifi signal from the fortigate 60C is not covering. Its my understanding that I need to add DHCP option 138 to the DHCP server first, which I' ve done as follows on a linux dnsmasq dhcp server: #wifi controller dhcp-option=138,10.0.0.254 10.0.0.254 being the fortigate 60c for example. However when checking the DHCP logs I get: Apr 3 11:45:38 localhost dnsmasq[5313]: DHCPDISCOVER(eth0) 00:09:0f:XX:XX:XX Apr 3 11:45:38 localhost dnsmasq[5313]: DHCPOFFER(eth0) 10.0.0.86 00:09:0f:XX:XX:XX There is no DHCPACK coming back from the 220B to take 10.0.0.86 as its IP. Could it be that the format I have used for the 138 option is wrong? Also is it possible to use fortiexplorer via USB to manage the 220B? Its worth noting that I have bridged the wifi and the lan on the fortigate 60C currently. The wifi works fine on the 60C, I am using v4 MR2 with the latest firmware for MR2 currently on the fortigate.

[Carl_Wallmark]

Hi, Is the FAP on the same subnet as the Fortigate ? If yes, then you dont need to use it. It´s only used when the Fortigate is on another subnet and not on the same L2 network.

[andyh]

Hmm yep, its on the same subnet (if it got an IP off DHCP) however the 220B is not taking an IP and I cannot see it on the fortigate webadmin panel.

[Carl_Wallmark]

hmmm.. start by removing the dhcp option, it´s not needed. which firmware do have on the FAP ?

[andyh]

I don' t know what firmware version it has as I can' t get it to take an IP off the DHCP server as yet. I presume I' ll have to connect to the default IP directly? The USB according to the instructions can' t be used just yet.

[Carl_Wallmark]

no the USB is not working, you can connect to it by IP or use the console, i think you need to upgrade the firmware before doing anything else

[andyh]

Theres a bug id 154429 on v4.0 MR2 Patch 10 which that patch supposedly fixes that does seem to point to a DHCP issue. I' ve managed to telnet it OK and it can take a fixed IP no problem, however I cannot see it on the fortigate 60c admin panel at all. Is there a command in telnet for the AP to show the firmware version its running?

[Carl_Wallmark]

Yes, type: fap-get-status

[andyh]

Version: FortiAP-220B v4.0,build214,110331 (MR3) Serial-Number: FAP22B3U11014328 BIOS version: 04000010 Regcode: E Hostname: FAP22B3U11014328 Branch point: 214 Release Version Information:MR3 The above is what I have on the FortiAP. And below is what I have on the Fortigate 60C Wifi: v4.0,build5904,120224 (MR2) The above seems to state MR3...if that is the case then I presume I should not have had any DHCP issue? I also assume that this means I have to either upgrade the 60C fortigate to MR3 (I' m not too keen on this) or downgrade the AP to an MR2 version. MR2 Patch 11 for example?

[Carl_Wallmark]

actually i would upgrade the FAP to build 224, and i assume you are using the special Wireless Controller MR2 Patch 10 ?