" AP Profile" missing in web interface

[#1]

We are configuring FortiAPs using our Fortigate 300A as the wireless controller. FortiOS 4.02 MR2 is installed. The instructions for configuring the APs says to create an AP profile using " Wireless Controller/AP Profile" . The problem is that there is no " AP Profile" in the menu under " Wireless Controller" . Suggestions, other than using the CLI?

[cmberry]

Try the 3CDaemon instead. I had better luck with it. http://support.3com.com/software/3cdv2r10.zip

Downloaded it and confirmed it works well with FortiAP.

I would just love to know 2 things. -How thru any means CLI of the FAP or thru your FG110C to tell what Firm FAP really has. -How you flash it to the newer firmware it requires. I have tried the TFTP but keep having timeout erros or checksum errors.

per my previous posts, I can confirm what yzhang told you. Using telnet built into windows, and using the tftp server 3CDaemon, you can quickly and easily confirm and upgrade your AP firmware. I just did both in the last hour, here are my steps in case it helps someone: (1) download the AP firmware somewhere easy, in my case it was " C:\fortiap\FAP_22B_v4.3.0_b0212_fortinet.out" . (2) open 3CDaemon and under configure TFTP server, change upload/download directory to " C:\fortiap\" (3) Make sure that 3CDaemon is listed as a firewall exception in Windows (4) Make sure you have a fortinet firewall policy that allows the interface your AP is plugged into, to see the pc your are running the TFTP server on. See all those timeouts below? I hadn' t done this step at first. (5) launch telnet, open connection to the FortiAP, in my case " open 192.168.4.110" ENTER, then " admin" , then " restore <image filename on tftp sever> <tftp sever ip address>" In my case this was " restore FAP_22B_v4.3.0_b0212_fortinet.out 192.168.1.133" ENTER firmware downloaded, installed, and restarted WAY faster than I was expecting, less than 1 minute total. I then used telnet again to see what firmware I was running, and it now says MR3! Sweet. Thanks yzhang. Now, I still have not downgraded the firewall to 4.2.2 special build, so that' s next.

[wmiller]

Agreed and confirmed here too, less than 1 minute from the time you type admin to reboot and get-status !!!! yeah one win for man kind against FAP220B

[cmberry]

Just got a FortiAP. I knew beforehand I would need 4.3.0 or a special branch of 4.2.X to get wireless controller to work with my fortigate 200B. Seems odd, since with 4.2.4 under the wireless controller tab, everything seems to point that it should work, everthing is enabled, Fortigate " sees" the fortiAP, and vice versa, but the FortiAp has a yellow Status light, which means " FortiGate wireless controller had been found but FortiAp is not managed" . If anyone here knows how to get it managed without needing to upgrade to 4.3.0 in a production environment, I would love to know. The reason being, 4.3.0 is so unstable if you see the recent posts here. Now, I personally had a lot of issues with 4.2.2 regular branch with my 200B. I see that the special version needed to get the wireless controller is 4.2.2. HMMM, not good. Why is there not the " special" version for 4.2.3 or 4.2.4? Am I really stuck between choosing the special 4.2.2 or the 4.3.0? Both are confimed buggy, and I am in a production environment. The FortiAP has been out since about June 2010, how the heck did anyone get this AP unit working back then, since it still seems a confusing mess to do it now.

[Carl_Wallmark]

have you tried to upgrade the FortiAP ? i used to have 4.2.2 ( the wireless controller firmware ) and it worked very well

[ejhardin]

I personally had a lot of issues with 4.2.2 regular branch with my 200B

You have two options only... 4.2.2 special build or 4.3. If you go with 4.2.2 special build then be sure to install the fortiap 112 firmware. What issue are you having? I have a 200b with the special build and it works good. The only issue that I have is with wan opt/web cache and the issue were not fixed in 4.2.3 or 4.2.4.

[cmberry]

If you go with 4.2.2 special build then be sure to install the fortiap 112 firmware. What issue are you having?

Can I install 4.2.2 on my Fortigate, and THEN upgrade my fortiAP to 112 thru the web config on the firewall? Or do I need to do 112 first, via TFTP? The issues I had with the regular 4.2.2 were failed downloads for almost all download big or small, which I was issued a bug ID for way back when, but that went away with 4.2.3 (and remained fixed with 4.2.4). Seems unfortunate that I need to downgrade back to 4.2.2, and I am worried about losing settings. I think I may wait for 4.3.1, but that it going to be a very long time I think....

[cmberry]

wmiller or someone who has FortiAP running: I created an interface that I connected the ethernet wire coming from the FortiAP. This is labeled " Wireless AP" in the picture below. Added DHCP and other customizations, then the fortiAP was able to get an ip (192.168.4.110). I then loaded new firmware on the FortiAP and other things, per my previous posts in this thread. That was a few days ago, and now when I look at the interface tab in the webconfig, I see this new " wireless" interface, which I did not create. Sorry for dumb question, but do I need both interfaces, or just one of them? If need both, do I need to customize the new " wireless" interface, if so how? The ethernet from the FortiAP needs to be plugged in, so I dont think I can just delete that interface and move the settings to the auto generated " wireless" interface.

[ejhardin]

Check the " type" it is most likely a " VAP" which is a wireless SSID. It doesn’t have an IP address assigned to it so it is not active. If you don’t need it delete it? Go to the wireless controller tab and check your profiles. You should see the wireless and you can delete it from there.