Question
FortAP220B DHCP no ACK
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.