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 Verified Answer
  • Locked Locked
  • Replies 8 replies
  • Subscribers 40 subscribers
  • Views 38514 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

Unable to use Sophos Access Points with XG Firewall?

TalaRyu

I can not get my AP30 to show up in Protection > Wireless Protection > Access Points or Objects > Assets > Access Points.  The AP is connected to my LAN port and the lights look to be good.  It was also working fine with the UTM 9 software before I loaded the XG Firewall software.   The Log Viewer shows the entry: 

2015-11-11 00:22:29
Wireless Protection
-
-
[Unknown] unknown AP model encountered: AP30, dropping.
17999


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

    Shoot, I'm having the same exact problem. I just blew away our SG at the office tonight and loaded the new OS. Now we are without wireless. I'll keep poking around and hopefully I find something soon!

    Mine are AP55Cs FWIW, but getting the same exact message in the Log VIewer.  Quick Google search shows there might be an answer on the old UBB, but can't access it.

    EDIT:

    I was able to look in the old astaro.org site and found this thread.  I'll give it a try and let everyone know.  (Hopefully this pastes alright)

     


    Junior Member
    Join Date: May 2014
    Posts: 2
    #1 (permalink)  
    Old 08-25-2015, 07:02 PM
    Default Issue setting up AP 10
    An AP10 is the only AP I have around for testing right now. It worked fine in the Partner Alpha and now I get this. "[Unknown] unknown AP model encountered: AP10, dropping." It gives a Message ID 17999. I have Eth0, Eth2, and Eth3 in a bridge. AP10 is plugged into Eth2.
    Reply With Quote
    Senior Member
    Join Date: Aug 2011
    Location: /home/pub
    Posts: 124
    #2 (permalink)  
    Old 08-26-2015, 11:25 AM
    Default
    Perhaps it has been bricked during a firmware update recently. Could you use the reflash tool to recover it and then try again.
    I'm using an AP10 with the current BETA and all is well.
    Reply With Quote
    RFCat_vk's Avatar
    Wizard
    Join Date: Aug 2005
    Location: Victoria, Australia
    Posts: 5,758
    #3 (permalink)  
    Old 08-26-2015, 11:47 AM
    Default
    Hi,
    information you haven't included
    1/. how is the AP connected to Copernicus, bridged to LAN, seperate zone?
    2/. does the eth02 have its own DHCP server range?
    3/. is an IP address assigned to the AP?

    Ian
    __________________
    ASG Home User licence - v9.3** - VM guest on esxi 6 host, Sophos AP55c and AP10 (courtesy of Astaro). 
    ASG Home user licence - v9.3** - AP50, 8gb, SSD, (100/1 2 user 5-6 devices)
    SUM4 Home User licence - v4.*** on esxi 6 host
    Work essentials licence - v9.3xx - intel D with 2gb.
    Reply With Quote
    Junior Member
    Join Date: Jan 2002
    Location: Vancouver, BC Canada
    Posts: 6
    #4 (permalink)  
    Old 10-10-2015, 08:41 PM
    Default
    Very similar problem here. AP 100 on the LAN interface, has an IP from DHCP, is set to allowed in the network list. Message ID 17999 "[Unknown] unknown AP model encountered: AP100, dropping."

    Works fine on UTM 9.350. This is on SFOS 15.01.0 Beta-2
    Reply With Quote
    Junior Member
    Join Date: Jan 2002
    Location: Vancouver, BC Canada
    Posts: 6
    #5 (permalink)  
    Old 10-11-2015, 01:08 AM
    Default
    OK, unplugging the AP and waiting an hour allowed it to be discovered when reconnected. Odd.
Reply
  • 0

    Shoot, I'm having the same exact problem. I just blew away our SG at the office tonight and loaded the new OS. Now we are without wireless. I'll keep poking around and hopefully I find something soon!

    Mine are AP55Cs FWIW, but getting the same exact message in the Log VIewer.  Quick Google search shows there might be an answer on the old UBB, but can't access it.

    EDIT:

    I was able to look in the old astaro.org site and found this thread.  I'll give it a try and let everyone know.  (Hopefully this pastes alright)

     


    Junior Member
    Join Date: May 2014
    Posts: 2
    #1 (permalink)  
    Old 08-25-2015, 07:02 PM
    Default Issue setting up AP 10
    An AP10 is the only AP I have around for testing right now. It worked fine in the Partner Alpha and now I get this. "[Unknown] unknown AP model encountered: AP10, dropping." It gives a Message ID 17999. I have Eth0, Eth2, and Eth3 in a bridge. AP10 is plugged into Eth2.
    Reply With Quote
    Senior Member
    Join Date: Aug 2011
    Location: /home/pub
    Posts: 124
    #2 (permalink)  
    Old 08-26-2015, 11:25 AM
    Default
    Perhaps it has been bricked during a firmware update recently. Could you use the reflash tool to recover it and then try again.
    I'm using an AP10 with the current BETA and all is well.
    Reply With Quote
    RFCat_vk's Avatar
    Wizard
    Join Date: Aug 2005
    Location: Victoria, Australia
    Posts: 5,758
    #3 (permalink)  
    Old 08-26-2015, 11:47 AM
    Default
    Hi,
    information you haven't included
    1/. how is the AP connected to Copernicus, bridged to LAN, seperate zone?
    2/. does the eth02 have its own DHCP server range?
    3/. is an IP address assigned to the AP?

    Ian
    __________________
    ASG Home User licence - v9.3** - VM guest on esxi 6 host, Sophos AP55c and AP10 (courtesy of Astaro). 
    ASG Home user licence - v9.3** - AP50, 8gb, SSD, (100/1 2 user 5-6 devices)
    SUM4 Home User licence - v4.*** on esxi 6 host
    Work essentials licence - v9.3xx - intel D with 2gb.
    Reply With Quote
    Junior Member
    Join Date: Jan 2002
    Location: Vancouver, BC Canada
    Posts: 6
    #4 (permalink)  
    Old 10-10-2015, 08:41 PM
    Default
    Very similar problem here. AP 100 on the LAN interface, has an IP from DHCP, is set to allowed in the network list. Message ID 17999 "[Unknown] unknown AP model encountered: AP100, dropping."

    Works fine on UTM 9.350. This is on SFOS 15.01.0 Beta-2
    Reply With Quote
    Junior Member
    Join Date: Jan 2002
    Location: Vancouver, BC Canada
    Posts: 6
    #5 (permalink)  
    Old 10-11-2015, 01:08 AM
    Default
    OK, unplugging the AP and waiting an hour allowed it to be discovered when reconnected. Odd.
Children
No Data
Unfiltered HTML