Important note about SSL VPN compatibility for 20.0 MR1 with EoL SFOS versions and UTM9 OS. Learn more in the release notes.

Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 2 replies
  • Subscribers 39 subscribers
  • Views 8223 views
  • Users 0 members are here
Options
Suggested
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

Upgraded my Cyberoam NG25 to the new Sophos OS, how do I get my Sophos AP30 to connect to the wireless Protection?

CharlesHammett

Upgraded my Cyberoam NG25 to the new Sophos OS, how do I get my Sophos AP30 to connect to the wireless Protection?Upgraded my Cyberoam NG25 to the new Sophos OS, how do I get my Sophos AP30 to connect to the wireless Protection?Upgraded my Cyberoam NG25 to the new Sophos OS, how do I get my Sophos AP30 to connect to the wireless Protection?Upgraded my Cyberoam NG25 to the new Sophos OS, how do I get my Sophos AP30 to connect to the wireless Protection?



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

    first of all how did you connect the AP? Is it connected to internal interface?
    If you did things correctly, you should see AP inside Protection > Wireless Protection > Access Point.

    You should see a "Pending Access Point". Accept it and create a new wireless network by clicking on accepted AP.

    If you do not see the AP, also make sure that firmware 3.0.001 is downloaded from System > Administration >Updates

    Luk
  • 0 in reply to lferrara
    Thank you for getting back to me so quickly. I ended up figuring out later that night. The AP wasnt showing up in the Pending Access Points for some reason. When i went into the DHCP lease I could however click and configure the AP from that point. Once that was done it showed up in the approved AP list. It seems to be a bug in the OS that wont list the AP30 in the list of approved AP's. I have a 2nd firewall Im upgrading today with AP30's I will confirm if this happens again after that upgrade.
Reply
  • 0 in reply to lferrara
    Thank you for getting back to me so quickly. I ended up figuring out later that night. The AP wasnt showing up in the Pending Access Points for some reason. When i went into the DHCP lease I could however click and configure the AP from that point. Once that was done it showed up in the approved AP list. It seems to be a bug in the OS that wont list the AP30 in the list of approved AP's. I have a 2nd firewall Im upgrading today with AP30's I will confirm if this happens again after that upgrade.
Children
No Data
Unfiltered HTML