Guest User!

You are not Sophos Staff.

This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

AP30 is detected but cannot be accepted

Greetings, I'm using Sophos Firewall XG for my home lab and I'm trying to get an AP30 access point to work with it. The hardware the firewall is installed on is a Zotac CI321 (you can find it on Amazon by searching for B01AK9TC1I ).

 

After enabling the Wireless Protection feature on Port 1 under Device Access and connecting the AP30 to the PoE switch, it gets picked up in the pending list in about 3 minutes. But when I accept it and assign it to the WiFi network I created and click the Save button, it gives the error 'Access Point (big long serial number) could not be updated'.

 

I used the flash utility to reset the firmware on the AP30 and it still does the same thing. I also tried rebooting the Sophos XG system and it didn't make any difference.

 

I'm used to working with UTM9 and I can't seem to find the Wireless logs on this system to see what the problem is. How can I troubleshoot this situation?



This thread was automatically locked due to age.
Parents
  • Steve,

    what version of XG are you using?

    Connect to CLI using Putty and then choose option 4. Type:

    system wireless-controller global ap_autoaccept 1

    You can enable debug issuing he following command:

     

    system wireless-controller global_ap_debuglevel 15 to get debug logs.

Reply
  • Steve,

    what version of XG are you using?

    Connect to CLI using Putty and then choose option 4. Type:

    system wireless-controller global ap_autoaccept 1

    You can enable debug issuing he following command:

     

    system wireless-controller global_ap_debuglevel 15 to get debug logs.

Children
  • I'm running SFOS 15.01.0 MR-3.

     

    And thanks for the auto-accept command!! Once I issued that command at the console prompt and deleted the AP from pending access points, it redetected and accepted it.

     

    Also, once I got it working, I reissued the command with a '0' at the end to disable it. Figuring that's probably a safe move.

     

    Cheers and thanks again!