AP 15 doesn't broadcast SSID after Firmware update

Hey guys,

my AP 15 doesn’t broadcast the SSID’s after an Firmware update. Interesting is the timechange in the log. The UTM runs as VM on Hyper-V with the correct time. Additionally the UTM synchs the time with pool.ntp.org .

What could be the problem and how can i fix it?

thanks in advance 

Best Regards

Arno

 

 

 

WebAdmin Live-Protokoll: Wireless Protection

 

2017:06:11-17:10:15 Sophos UTM 9.501-5 awed[4565]: Use of uninitialized value $sorted_channels[-1] in numeric gt (>) at awed_ng.pl line 1111.
2017:06:11-17:10:15 Sophos UTM 9.501-5 awed[4565]: [MASTER] AP Sophos AP 15: Local metadata updated
2017:06:11-17:10:15 Sophos UTM 9.501-5 awed[4565]: [MASTER] AP Sophos AP 15: Configuration change detected
2017:06:11-17:10:15 Sophos UTM 9.501-5 awed[4565]: [MASTER] end processing configuration change
2017:06:11-17:10:21 Sophos UTM 9.501-5 awed[4565]: [MASTER] new connection from 192.168.65.22:39325
2017:06:11-17:10:21 Sophos UTM 9.501-5 awed[8552]: [Sophos AP 15] AP15 from 192.168.65.22:39325 identified as Sophos AP 15
2017:06:11-17:10:21 Sophos UTM 9.501-5 awed[8552]: [Sophos AP 15] (Re-)loaded identity and/or configuration
2017:06:11-17:10:27 Sophos UTM 9.501-5 awed[8552]: [Sophos AP 15] sent firmware /etc/wireless/firmware/AP15.uimage to device, releasing connection.
2018:03:20-15:27:22 Sophos AP 15 aweclient[895]: aweclient.c (369) Writing firmware to '/dev/mtdblock4'.
2018:03:20-15:27:24 Sophos AP 15 kernel: [ 44.940000] random: nonblocking pool is initialized
2017:06:11-15:11:24 Sophos AP 15 aweclient[895]: aweclient.c (393) Firmware upgrade finished: quit and reboot.
2017:06:11-15:11:24 Sophos AP 15 aweclient[895]: Closing log...
2017:06:11-15:11:24 Sophos AP 15 procd: - shutdown -
2017:06:11-15:11:24 Sophos AP 15 procd:
2018:02:21-10:42:37 Sophos AP 15 logread[973]: Logread connected to 192.168.65.12:415
2018:02:21-10:42:38 Sophos AP 15 kernel: [ 21.290000] br-lan: port 1(eth0) entered forwarding state
2017:06:11-17:12:18 Sophos UTM 9.501-5 awed[4565]: [MASTER] new connection from 192.168.65.22:46279
2017:06:11-17:12:18 Sophos UTM 9.501-5 awed[8880]: [Sophos AP 15] AP15 from 192.168.65.22:46279 identified as Sophos AP 15
2017:06:11-17:12:18 Sophos UTM 9.501-5 awed[8880]: [Sophos AP 15] (Re-)loaded identity and/or configuration
2018:02:21-10:42:50 Sophos AP 15 aweclient[891]: Cloudclient not found on ubus.
2018:02:21-10:42:52 Sophos AP 15 kernel: [ 35.360000] cfg80211: Calling CRDA for country: DE
2018:02:21-10:42:52 Sophos AP 15 add_radio_mapping.sh: AP15 detected: Using on-the-fly ACS procedure
2018:02:21-10:42:52 Sophos AP 15 kernel: [ 35.460000] cfg80211: Regulatory domain changed to country: DE
2018:02:21-10:42:52 Sophos AP 15 kernel: [ 35.470000] cfg80211: DFS Master region: ETSI
2018:02:21-10:42:52 Sophos AP 15 kernel: [ 35.470000] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
2018:02:21-10:42:52 Sophos AP 15 kernel: [ 35.480000] cfg80211: (2400000 KHz - 2483000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
2018:02:21-10:42:52 Sophos AP 15 kernel: [ 35.490000] cfg80211: (5150000 KHz - 5250000 KHz @ 80000 KHz, 200000 KHz AUTO), (N/A, 2000 mBm), (N/A)
2018:02:21-10:42:52 Sophos AP 15 kernel: [ 35.500000] cfg80211: (5250000 KHz - 5350000 KHz @ 80000 KHz, 200000 KHz AUTO), (N/A, 2000 mBm), (0 s)
2018:02:21-10:42:52 Sophos AP 15 kernel: [ 35.510000] cfg80211: (5470000 KHz - 5725000 KHz @ 160000 KHz), (N/A, 2700 mBm), (0 s)
2018:02:21-10:42:52 Sophos AP 15 kernel: [ 35.520000] cfg80211: (57000000 KHz - 66000000 KHz @ 2160000 KHz), (N/A, 4000 mBm), (N/A)
2018:02:21-10:42:52 Sophos AP 15 kernel: [ 35.840000] device vxlan.100 entered promiscuous mode
2018:02:21-10:42:52 Sophos AP 15 kernel: [ 35.850000] device vxlan entered promiscuous mode
2018:02:21-10:42:52 Sophos AP 15 netifd: Interface 'vxlan' is enabled
2018:02:21-10:42:52 Sophos AP 15 netifd: Network device 'vxlan' link is up
2018:02:21-10:42:52 Sophos AP 15 netifd: Interface 'vxlan' has link connectivity
2018:02:21-10:42:52 Sophos AP 15 netifd: Interface 'vxlan' is setting up now
2018:02:21-10:42:52 Sophos AP 15 netifd: Interface 'vxlan' is now up
2018:02:21-10:42:52 Sophos AP 15 netifd: VLAN 'vxlan.100' link is up
2018:02:21-10:42:52 Sophos AP 15 kernel: [ 35.870000] br-vxlan100: port 1(vxlan.100) entered forwarding state
2018:02:21-10:42:52 Sophos AP 15 kernel: [ 35.870000] br-vxlan100: port 1(vxlan.100) entered forwarding state
2018:02:21-10:42:52 Sophos AP 15 netifd: Interface 'vxlan100' is enabled
2018:02:21-10:42:52 Sophos AP 15 netifd: Bridge 'br-vxlan100' link is up
2018:02:21-10:42:52 Sophos AP 15 netifd: Interface 'vxlan100' has link connectivity
2018:02:21-10:42:52 Sophos AP 15 netifd: Interface 'vxlan100' is setting up now
2018:02:21-10:42:52 Sophos AP 15 netifd: Interface 'vxlan100' is now up
2018:02:21-10:42:54 Sophos AP 15 kernel: [ 37.870000] br-vxlan100: port 1(vxlan.100) entered forwarding state
2017:06:11-17:12:39 Sophos UTM 9.501-5 awed[4565]: [MASTER] start processing configuration change
2017:06:11-17:12:40 Sophos UTM 9.501-5 awed[4565]: WARN -------------------------------------------------------
2017:06:11-17:12:40 Sophos UTM 9.501-5 awed[4565]: Use of uninitialized value $sorted_channels[-1] in numeric gt (>) at awed_ng.pl line 1111.
2017:06:11-17:12:40 Sophos UTM 9.501-5 awed[4565]: WARN -------------------------------------------------------
2017:06:11-17:12:40 Sophos UTM 9.501-5 awed[4565]: Use of uninitialized value $sorted_channels[-1] in numeric gt (>) at awed_ng.pl line 1111.
2017:06:11-17:12:40 Sophos UTM 9.501-5 awed[4565]: [MASTER] end processing configuration change
2017:06:11-17:13:04 Sophos AP 15 kernel: [ 80.020000] random: nonblocking pool is initialized

 

%%%%%%%%%%%%%%%%%%%%
%% Reboot
%%%%%%%%%%%%%%%%%%%%

2018:02:21-10:42:52 Sophos AP 15 netifd: VLAN 'vxlan.100' link is up
2018:02:21-10:42:52 Sophos AP 15 kernel: [ 35.870000] br-vxlan100: port 1(vxlan.100) entered forwarding state
2018:02:21-10:42:52 Sophos AP 15 kernel: [ 35.880000] br-vxlan100: port 1(vxlan.100) entered forwarding state
2018:02:21-10:42:52 Sophos AP 15 netifd: Interface 'vxlan100' is enabled
2018:02:21-10:42:52 Sophos AP 15 netifd: Bridge 'br-vxlan100' link is up
2018:02:21-10:42:52 Sophos AP 15 netifd: Interface 'vxlan100' has link connectivity
2018:02:21-10:42:52 Sophos AP 15 netifd: Interface 'vxlan100' is setting up now
2018:02:21-10:42:52 Sophos AP 15 netifd: Interface 'vxlan100' is now up
2018:02:21-10:42:54 Sophos AP 15 kernel: [ 37.880000] br-vxlan100: port 1(vxlan.100) entered forwarding state
2017:06:12-18:51:00 Sophos AP 15 kernel: [ 79.160000] random: nonblocking pool is initialized
2017:06:12-18:55:18 Sophos UTM 9.501-5 awed[4590]: [MASTER] start processing configuration change
2017:06:12-18:55:19 Sophos UTM 9.501-5 awed[4590]: WARN -------------------------------------------------------
2017:06:12-18:55:19 Sophos UTM 9.501-5 awed[4590]: Use of uninitialized value $sorted_channels[-1] in numeric gt (>) at awed_ng.pl line 1111.
2017:06:12-18:55:19 Sophos UTM 9.501-5 awed[4590]: WARN -------------------------------------------------------
2017:06:12-18:55:19 Sophos UTM 9.501-5 awed[4590]: Use of uninitialized value $sorted_channels[-1] in numeric gt (>) at awed_ng.pl line 1111.
2017:06:12-18:55:19 Sophos UTM 9.501-5 awed[4590]: [MASTER] AP Sophos AP 15: Local metadata updated
2017:06:12-18:55:19 Sophos UTM 9.501-5 awed[4590]: [MASTER] end processing configuration change
2017:06:12-18:55:32 Sophos UTM 9.501-5 awed[36880]: [Sophos AP 15] (Re-)loaded identity and/or configuration
2017:06:12-18:55:32 Sophos AP 15 aweclient[892]: aweclient.c (2462) Exit from main loop with no error. Get new configuration.
2017:06:12-18:55:33 Sophos AP 15 aweclient[892]: Cloudclient not found on ubus.
2017:06:12-18:55:34 Sophos AP 15 add_radio_mapping.sh: AP15 detected: Using on-the-fly ACS procedure

  • Hi Arno,

    can you please provide a bit more log output?
    In the last line you posted, the AP was still in the reconfiguration phase after the reboot.

    Can you please check if setting a channel manually also doesn't work for you?

    Regards,
      Reiner

  • In reply to reinerh:

    Hi Reiner,

     

    Thanks for your reply and sorry for my late response. I tried to reconnect the AP 15, by first deleting it and adding it again. The whole message log from Live-Protokoll: Wireless Protection is attached. Is there any other log wich is more detailed? (I'm a Sophos beginner)

    When I try to change the Channel, the only choosable option is "Auto", see the picture below.

     

     

    Thanks in advance.

     

    best regards

     

    Arno

     

    Live-Protokoll: Wireless Protection:

    2017:06:25-17:03:32 Sophos UTM 9.501-5 awed[4533]: Use of uninitialized value $sorted_channels[-1] in numeric gt (>) at awed_ng.pl line 1111.
    2017:06:25-17:03:32 Sophos UTM 9.501-5 awed[4533]: WARN -------------------------------------------------------
    2017:06:25-17:03:32 Sophos UTM 9.501-5 awed[4533]: Use of uninitialized value $sorted_channels[-1] in numeric gt (>) at awed_ng.pl line 1111.
    2017:06:25-17:03:32 Sophos UTM 9.501-5 awed[4533]: [MASTER] end processing configuration change
    2017:06:25-18:03:30 Sophos UTM 9.501-5 awed[4533]: [MASTER] start processing configuration change
    2017:06:25-18:03:30 Sophos UTM 9.501-5 awed[4533]: WARN -------------------------------------------------------
    2017:06:25-18:03:30 Sophos UTM 9.501-5 awed[4533]: Use of uninitialized value $sorted_channels[-1] in numeric gt (>) at awed_ng.pl line 1111.
    2017:06:25-18:03:30 Sophos UTM 9.501-5 awed[4533]: WARN -------------------------------------------------------
    2017:06:25-18:03:30 Sophos UTM 9.501-5 awed[4533]: Use of uninitialized value $sorted_channels[-1] in numeric gt (>) at awed_ng.pl line 1111.
    2017:06:25-18:03:30 Sophos UTM 9.501-5 awed[4533]: [MASTER] end processing configuration change
    2017:06:25-18:28:16 Sophos UTM 9.501-5 awed[4533]: [MASTER] start processing configuration change
    2017:06:25-18:28:16 Sophos UTM 9.501-5 awed[4533]: WARN -------------------------------------------------------
    2017:06:25-18:28:16 Sophos UTM 9.501-5 awed[4533]: Use of uninitialized value $sorted_channels[-1] in numeric gt (>) at awed_ng.pl line 1111.
    2017:06:25-18:28:16 Sophos UTM 9.501-5 awed[4533]: [MASTER] end processing configuration change
    2017:06:25-18:28:27 Sophos UTM 9.501-5 awed[4533]: [MASTER] start processing configuration change
    2017:06:25-18:28:27 Sophos UTM 9.501-5 awed[4533]: WARN -------------------------------------------------------
    2017:06:25-18:28:27 Sophos UTM 9.501-5 awed[4533]: Use of uninitialized value $sorted_channels[-1] in numeric gt (>) at awed_ng.pl line 1111.
    2017:06:25-18:28:27 Sophos UTM 9.501-5 awed[4533]: [MASTER] Sophos AP 15: Configuration change detected
    2017:06:25-18:28:27 Sophos UTM 9.501-5 awed[4533]: [MASTER] end processing configuration change
    2017:06:25-18:28:35 Sophos UTM 9.501-5 awed[4533]: [MASTER] start processing configuration change
    2017:06:25-18:28:35 Sophos UTM 9.501-5 awed[4533]: WARN -------------------------------------------------------
    2017:06:25-18:28:35 Sophos UTM 9.501-5 awed[4533]: Use of uninitialized value $sorted_channels[-1] in numeric gt (>) at awed_ng.pl line 1111.
    2017:06:25-18:28:35 Sophos UTM 9.501-5 awed[4533]: [MASTER] Sophos AP 15: Configuration change detected
    2017:06:25-18:28:35 Sophos UTM 9.501-5 awed[4533]: [MASTER] end processing configuration change
    2017:06:25-18:28:49 Sophos UTM 9.501-5 awed[4533]: [MASTER] start processing configuration change
    2017:06:25-18:28:50 Sophos UTM 9.501-5 awed[4533]: [MASTER] end processing configuration change
    2017:06:25-18:29:50 Sophos UTM 9.501-5 awed[4533]: [MASTER] start processing configuration change
    2017:06:25-18:29:50 Sophos UTM 9.501-5 awed[4533]: [MASTER] end processing configuration change
    2018:02:21-10:42:37 Sophos AP 15 logread[997]: Logread connected to 192.168.65.12:415
    2018:02:21-10:42:38 Sophos AP 15 kernel: [ 21.300000] br-lan: port 1(eth0) entered forwarding state
    2017:06:25-18:32:33 Sophos UTM 9.501-5 awed[4533]: [MASTER] new connection from 192.168.65.22:42971
    2018:02:21-10:42:50 Sophos AP 15 aweclient[894]: json_messages.c (460) Message type is different from expected.
    2018:02:21-10:42:51 Sophos AP 15 cloudclient[928]: curl.c:544/check_multi_info: Connection refused.
    2018:02:21-10:42:51 Sophos AP 15 aweclient[894]: aweclient.c (621) Invalid shared key, clear registered flag and retry.
    2018:02:21-10:42:51 Sophos AP 15 aweclient[894]: aweclient.c (2400) Cannot get a valid configuration, retry later.
    2018:02:21-10:43:06 Sophos AP 15 cloudclient[928]: curl.c:544/check_multi_info: Connection refused.
    2018:02:21-10:43:06 Sophos AP 15 aweclient[894]: aweclient.c (2470) Error in getting new configuration. Reconnecting (1)
    2018:02:21-10:43:06 Sophos AP 15 aweclient[894]: aweclient.c (2591) Failed to configure device.
    2018:02:21-10:43:06 Sophos AP 15 aweclient[894]: Closing log...
    2018:02:21-10:43:06 Sophos AP 15 procd: - shutdown -
    2018:02:21-10:43:06 Sophos AP 15 procd:
    2018:02:21-10:42:37 Sophos AP 15 logread[988]: Logread connected to 192.168.65.12:415
    2018:02:21-10:42:38 Sophos AP 15 kernel: [ 21.300000] br-lan: port 1(eth0) entered forwarding state
    2017:06:25-18:33:42 Sophos UTM 9.501-5 awed[4533]: [MASTER] new connection from 192.168.65.22:41070
    2017:06:25-18:33:43 Sophos UTM 9.501-5 awed[41936]: 1
    2017:06:25-18:33:43 Sophos UTM 9.501-5 awed[4533]: [MASTER] new AP with ID Sophos AP 15
    2018:02:21-10:42:50 Sophos AP 15 cloudclient[912]: curl.c:544/check_multi_info: Connection refused.
    2017:06:25-18:33:43 Sophos UTM 9.501-5 awed[4533]: [MASTER] start processing configuration change
    2017:06:25-18:33:43 Sophos UTM 9.501-5 awed[4533]: [MASTER] Sophos AP 15: Local metadata updated
    2017:06:25-18:33:43 Sophos UTM 9.501-5 awed[4533]: [MASTER] Sophos AP 15: Configuration change detected
    2017:06:25-18:33:43 Sophos UTM 9.501-5 awed[4533]: [MASTER] end processing configuration change
    2018:02:21-10:42:51 Sophos AP 15 aweclient[884]: aweclient.c (2572) Device registered. Reconnecting.
    2017:06:25-18:33:48 Sophos UTM 9.501-5 awed[4533]: [MASTER] new connection from 192.168.65.22:41073
    2017:06:25-18:33:49 Sophos UTM 9.501-5 awed[42046]: [Sophos AP 15] AP15 from 192.168.65.22:41073 identified as Sophos AP 15
    2017:06:25-18:33:49 Sophos UTM 9.501-5 awed[42046]: [Sophos AP 15] (Re-)loaded identity and/or configuration
    2017:06:25-18:33:49 Sophos UTM 9.501-5 awed[42046]: [Sophos AP 15] device not authorized yet, dropping.
    2018:02:21-10:42:56 Sophos AP 15 aweclient[884]: json_messages.c (460) Message type is different from expected.
    2018:02:21-10:42:56 Sophos AP 15 aweclient[884]: aweclient.c (2407) Device not yet authorized, retry later.
    2018:02:21-10:43:06 Sophos AP 15 cloudclient[912]: curl.c:544/check_multi_info: Connection refused.
    2017:06:25-18:34:04 Sophos UTM 9.501-5 awed[4533]: [MASTER] new connection from 192.168.65.22:41078
    2018:02:21-10:43:11 Sophos AP 15 aweclient[884]: aweclient.c (2470) Error in getting new configuration. Reconnecting (1)
    2017:06:25-18:34:04 Sophos UTM 9.501-5 awed[42148]: [Sophos AP 15] AP15 from 192.168.65.22:41078 identified as Sophos AP 15
    2017:06:25-18:34:04 Sophos UTM 9.501-5 awed[42148]: [Sophos AP 15] (Re-)loaded identity and/or configuration
    2017:06:25-18:34:04 Sophos UTM 9.501-5 awed[42148]: [Sophos AP 15] device not authorized yet, dropping.
    2018:02:21-10:43:11 Sophos AP 15 aweclient[884]: json_messages.c (460) Message type is different from expected.
    2018:02:21-10:43:11 Sophos AP 15 aweclient[884]: aweclient.c (628) Device not authorized, retry later.
    2018:02:21-10:43:11 Sophos AP 15 aweclient[884]: aweclient.c (2407) Device not yet authorized, retry later.
    2017:06:25-16:34:12 Sophos AP 15 cloudclient[912]: oauth.c:126/parse_oauth_token_error: access point got error: invalid_client -
    2017:06:25-16:34:18 Sophos AP 15 aweclient[884]: aweclient.c (2470) Error in getting new configuration. Reconnecting (2)
    2017:06:25-18:34:19 Sophos UTM 9.501-5 awed[4533]: [MASTER] new connection from 192.168.65.22:41083
    2017:06:25-18:34:19 Sophos UTM 9.501-5 awed[42199]: [Sophos AP 15] AP15 from 192.168.65.22:41083 identified as Sophos AP 15
    2017:06:25-18:34:19 Sophos UTM 9.501-5 awed[42199]: [Sophos AP 15] (Re-)loaded identity and/or configuration
    2017:06:25-18:34:19 Sophos UTM 9.501-5 awed[42199]: [Sophos AP 15] device not authorized yet, dropping.
    2017:06:25-16:34:18 Sophos AP 15 aweclient[884]: json_messages.c (460) Message type is different from expected.
    2017:06:25-16:34:18 Sophos AP 15 aweclient[884]: aweclient.c (628) Device not authorized, retry later.
    2017:06:25-16:34:18 Sophos AP 15 aweclient[884]: aweclient.c (2407) Device not yet authorized, retry later.
    2017:06:25-16:34:25 Sophos AP 15 kernel: [ 77.130000] random: nonblocking pool is initialized
    2017:06:25-16:34:28 Sophos AP 15 cloudclient[912]: oauth.c:126/parse_oauth_token_error: access point got error: invalid_client -
    2017:06:25-16:34:33 Sophos AP 15 aweclient[884]: aweclient.c (2470) Error in getting new configuration. Reconnecting (3)
    2017:06:25-18:34:34 Sophos UTM 9.501-5 awed[4533]: [MASTER] new connection from 192.168.65.22:41087
    2017:06:25-18:34:34 Sophos UTM 9.501-5 awed[42242]: [Sophos AP 15] AP15 from 192.168.65.22:41087 identified as Sophos AP 15
    2017:06:25-18:34:34 Sophos UTM 9.501-5 awed[42242]: [Sophos AP 15] (Re-)loaded identity and/or configuration
    2017:06:25-18:34:34 Sophos UTM 9.501-5 awed[42242]: [Sophos AP 15] device not authorized yet, dropping.
    2017:06:25-16:34:33 Sophos AP 15 aweclient[884]: json_messages.c (460) Message type is different from expected.
    2017:06:25-16:34:33 Sophos AP 15 aweclient[884]: aweclient.c (628) Device not authorized, retry later.
    2017:06:25-16:34:33 Sophos AP 15 aweclient[884]: aweclient.c (2407) Device not yet authorized, retry later.
    2017:06:25-16:34:44 Sophos AP 15 cloudclient[912]: oauth.c:126/parse_oauth_token_error: access point got error: invalid_client -
    2017:06:25-16:34:48 Sophos AP 15 aweclient[884]: aweclient.c (2470) Error in getting new configuration. Reconnecting (4)
    2017:06:25-18:34:49 Sophos UTM 9.501-5 awed[4533]: [MASTER] new connection from 192.168.65.22:41091
    2017:06:25-18:34:49 Sophos UTM 9.501-5 awed[42276]: [Sophos AP 15] AP15 from 192.168.65.22:41091 identified as Sophos AP 15
    2017:06:25-18:34:49 Sophos UTM 9.501-5 awed[42276]: [Sophos AP 15] (Re-)loaded identity and/or configuration
    2017:06:25-18:34:49 Sophos UTM 9.501-5 awed[42276]: [Sophos AP 15] device not authorized yet, dropping.
    2017:06:25-16:34:48 Sophos AP 15 aweclient[884]: json_messages.c (460) Message type is different from expected.
    2017:06:25-16:34:48 Sophos AP 15 aweclient[884]: aweclient.c (628) Device not authorized, retry later.
    2017:06:25-16:34:48 Sophos AP 15 aweclient[884]: aweclient.c (2407) Device not yet authorized, retry later.
    2017:06:25-16:35:00 Sophos AP 15 cloudclient[912]: oauth.c:126/parse_oauth_token_error: access point got error: invalid_client -
    2017:06:25-18:35:04 Sophos UTM 9.501-5 awed[4533]: [MASTER] new connection from 192.168.65.22:41095
    2017:06:25-16:35:03 Sophos AP 15 aweclient[884]: aweclient.c (2470) Error in getting new configuration. Reconnecting (5)
    2017:06:25-18:35:04 Sophos UTM 9.501-5 awed[42453]: [Sophos AP 15] AP15 from 192.168.65.22:41095 identified as Sophos AP 15
    2017:06:25-18:35:04 Sophos UTM 9.501-5 awed[42453]: [Sophos AP 15] (Re-)loaded identity and/or configuration
    2017:06:25-18:35:04 Sophos UTM 9.501-5 awed[42453]: [Sophos AP 15] device not authorized yet, dropping.
    2017:06:25-16:35:03 Sophos AP 15 aweclient[884]: json_messages.c (460) Message type is different from expected.
    2017:06:25-16:35:03 Sophos AP 15 aweclient[884]: aweclient.c (628) Device not authorized, retry later.
    2017:06:25-16:35:03 Sophos AP 15 aweclient[884]: aweclient.c (2407) Device not yet authorized, retry later.
    2017:06:25-18:35:04 Sophos UTM 9.501-5 awed[4533]: [MASTER] start processing configuration change
    2017:06:25-18:35:05 Sophos UTM 9.501-5 awed[4533]: [MASTER] Sophos AP 15: Local metadata updated
    2017:06:25-18:35:05 Sophos UTM 9.501-5 awed[4533]: [MASTER] Sophos AP 15: Configuration change detected
    2017:06:25-18:35:05 Sophos UTM 9.501-5 awed[4533]: [MASTER] end processing configuration change
    2017:06:25-18:35:19 Sophos UTM 9.501-5 awed[4533]: [MASTER] new connection from 192.168.65.22:41098
    2017:06:25-16:35:18 Sophos AP 15 aweclient[884]: aweclient.c (2470) Error in getting new configuration. Reconnecting (6)
    2017:06:25-16:35:18 Sophos AP 15 cloudclient[912]: oauth.c:126/parse_oauth_token_error: access point got error: invalid_client -
    2017:06:25-18:35:19 Sophos UTM 9.501-5 awed[42776]: [Sophos AP 15] AP15 from 192.168.65.22:41098 identified as Sophos AP 15
    2017:06:25-18:35:19 Sophos UTM 9.501-5 awed[42776]: [Sophos AP 15] (Re-)loaded identity and/or configuration
    2017:06:25-16:35:19 Sophos AP 15 kernel: [ 131.610000] ath: phy1: Unable to initialize hardware; initialization status: -5
    2017:06:25-16:35:19 Sophos AP 15 kernel: [ 131.610000] ath9k qca955x_wmac: failed to initialize device
    2017:06:25-16:35:19 Sophos AP 15 kernel: [ 131.620000] ath9k: probe of qca955x_wmac failed with error -5
    2017:06:25-16:35:20 Sophos AP 15 kernel: [ 132.920000] cfg80211: Calling CRDA for country: DE
    2017:06:25-16:35:20 Sophos AP 15 add_radio_mapping.sh: AP15 detected: Using on-the-fly ACS procedure
    2017:06:25-16:35:21 Sophos AP 15 kernel: [ 133.020000] cfg80211: Regulatory domain changed to country: DE
    2017:06:25-16:35:21 Sophos AP 15 kernel: [ 133.030000] cfg80211: DFS Master region: ETSI
    2017:06:25-16:35:21 Sophos AP 15 kernel: [ 133.030000] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
    2017:06:25-16:35:21 Sophos AP 15 kernel: [ 133.040000] cfg80211: (2400000 KHz - 2483000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
    2017:06:25-16:35:21 Sophos AP 15 kernel: [ 133.050000] cfg80211: (5150000 KHz - 5250000 KHz @ 80000 KHz, 200000 KHz AUTO), (N/A, 2000 mBm), (N/A)
    2017:06:25-16:35:21 Sophos AP 15 kernel: [ 133.060000] cfg80211: (5250000 KHz - 5350000 KHz @ 80000 KHz, 200000 KHz AUTO), (N/A, 2000 mBm), (0 s)
    2017:06:25-16:35:21 Sophos AP 15 kernel: [ 133.070000] cfg80211: (5470000 KHz - 5725000 KHz @ 160000 KHz), (N/A, 2700 mBm), (0 s)
    2017:06:25-16:35:21 Sophos AP 15 kernel: [ 133.080000] cfg80211: (57000000 KHz - 66000000 KHz @ 2160000 KHz), (N/A, 4000 mBm), (N/A)
    2017:06:25-16:35:21 Sophos AP 15 netifd: Interface 'vxlan' is enabled
    2017:06:25-16:35:21 Sophos AP 15 netifd: Network device 'vxlan' link is up
    2017:06:25-16:35:21 Sophos AP 15 netifd: Interface 'vxlan' has link connectivity
    2017:06:25-16:35:21 Sophos AP 15 netifd: Interface 'vxlan' is setting up now
    2017:06:25-16:35:21 Sophos AP 15 netifd: Interface 'vxlan' is now up
    2017:06:25-16:35:21 Sophos AP 15 netifd: VLAN 'vxlan.100' link is up
    2017:06:25-16:35:21 Sophos AP 15 kernel: [ 133.440000] device vxlan.100 entered promiscuous mode
    2017:06:25-16:35:21 Sophos AP 15 kernel: [ 133.450000] device vxlan entered promiscuous mode
    2017:06:25-16:35:21 Sophos AP 15 kernel: [ 133.470000] br-vxlan100: port 1(vxlan.100) entered forwarding state
    2017:06:25-16:35:21 Sophos AP 15 kernel: [ 133.470000] br-vxlan100: port 1(vxlan.100) entered forwarding state
    2017:06:25-16:35:21 Sophos AP 15 netifd: Interface 'vxlan100' is enabled
    2017:06:25-16:35:21 Sophos AP 15 netifd: Bridge 'br-vxlan100' link is up
    2017:06:25-16:35:21 Sophos AP 15 netifd: Interface 'vxlan100' has link connectivity
    2017:06:25-16:35:21 Sophos AP 15 netifd: Interface 'vxlan100' is setting up now
    2017:06:25-16:35:21 Sophos AP 15 netifd: Interface 'vxlan100' is now up
    2017:06:25-16:35:23 Sophos AP 15 kernel: [ 135.470000] br-vxlan100: port 1(vxlan.100) entered forwarding state
    2017:06:25-18:40:27 Sophos UTM 9.501-5 awed[4533]: [MASTER] start processing configuration change
    2017:06:25-18:40:27 Sophos UTM 9.501-5 awed[4533]: [MASTER] Sophos AP 15: Local metadata updated
    2017:06:25-18:40:27 Sophos UTM 9.501-5 awed[4533]: [MASTER] end processing configuration change
    2017:06:25-18:40:37 Sophos UTM 9.501-5 awed[42776]: [Sophos AP 15] (Re-)loaded identity and/or configuration
    2017:06:25-18:40:37 Sophos AP 15 aweclient[884]: aweclient.c (2462) Exit from main loop with no error. Get new configuration.
    2017:06:25-18:40:38 Sophos AP 15 aweclient[884]: Cloudclient not found on ubus.
    2017:06:25-18:40:39 Sophos AP 15 add_radio_mapping.sh: AP15 detected: Using on-the-fly ACS procedure

  • In reply to ArnoWalther:

    Hello

    i have exact the same issue with one Sophos AP15 after firmware upgrade

    channel selection is also not possible ... only auto .... 

    does someone knows how to fix that issue ?

    regards

    Walter

  • Hello,

     

    is there any solution or news for that topic?

    I have the same problem with one of mine ap15s... :(

     

     

    Regards, Andy

  • In reply to nd:

    Which Wireless Controller do you use? 

  • In reply to LuCar Toni:

    It is an AP15 Rev1 controlled by Sophos UTM Home 9.602-3....

    the problem lasts long time now....this evening I unearthed that AP and wanted to give it a try to revoke.

     

    Shell login via sophos utm into ap with awetool is possible, it is also recognized by the sophos...only the ssid will not be sent...

     

    the following stucked out:

    root@OpenWrt:/# cat /tmp/ap_caps
    
    allowed_channels=



  • In reply to reinerh:

    how would this be possible?

    anyone have a working configuration?

  • In reply to reinerh:

    2019:05:22-23:42:39 A40031AA01DF8F6 aweclient[1422]: aweclient.c (2503) Exit from main loop with no error. Get new configuration.
    2019:05:22-23:42:40 A40031AA01DF8F6 aweclient[1422]: Cloudclient not found on ubus.
    2019:05:22-23:42:41 A40031AA01DF8F6 aweclient: Config in flash changed, reboot.
    2019:05:22-23:42:41 A40031AA01DF8F6 procd: - shutdown -
    2019:05:22-23:42:42 A40031AA01DF8F6 procd:
    2019:05:22-23:42:42 A40031AA01DF8F6 dropbear[1966]: Early exit: Terminated by signal
    2019:05:29-13:05:12 A40031AA01DF8F6 logread[939]: Logread connected to 192.168.4.10:415
    2019:05:29-13:05:13 A40031AA01DF8F6 kernel: [ 21.290000] br-lan: port 1(eth0) entered forwarding state
    2019:05:22-23:43:36 sg115 awed[4772]: [MASTER] new connection from 192.168.4.106:50067
    2019:05:22-23:43:36 sg115 awed[6770]: [A40031AA01DF8F6] AP15 from 192.168.4.106:50067 identified as A40031AA01DF8F6
    2019:05:22-23:43:36 sg115 awed[6770]: [A40031AA01DF8F6] (Re-)loaded identity and/or configuration
    2019:05:29-13:05:25 A40031AA01DF8F6 aweclient[858]: Cloudclient not found on ubus.
    2019:05:29-13:05:27 A40031AA01DF8F6 kernel: [ 35.500000] cfg80211: Calling CRDA for country: DE
    2019:05:29-13:05:27 A40031AA01DF8F6 add_radio_mapping.sh: AP15 detected: Using on-the-fly ACS procedure
    2019:05:29-13:05:27 A40031AA01DF8F6 kernel: [ 35.600000] cfg80211: Regulatory domain changed to country: DE
    2019:05:29-13:05:27 A40031AA01DF8F6 kernel: [ 35.610000] cfg80211: DFS Master region: ETSI
    2019:05:29-13:05:27 A40031AA01DF8F6 kernel: [ 35.610000] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
    2019:05:29-13:05:27 A40031AA01DF8F6 kernel: [ 35.620000] cfg80211: (2400000 KHz - 2483000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
    2019:05:29-13:05:27 A40031AA01DF8F6 kernel: [ 35.630000] cfg80211: (5150000 KHz - 5250000 KHz @ 80000 KHz, 200000 KHz AUTO), (N/A, 2000 mBm), (N/A)
    2019:05:29-13:05:27 A40031AA01DF8F6 kernel: [ 35.640000] cfg80211: (5250000 KHz - 5350000 KHz @ 80000 KHz, 200000 KHz AUTO), (N/A, 2000 mBm), (0 s)
    2019:05:29-13:05:27 A40031AA01DF8F6 kernel: [ 35.650000] cfg80211: (5470000 KHz - 5725000 KHz @ 160000 KHz), (N/A, 2700 mBm), (0 s)
    2019:05:29-13:05:27 A40031AA01DF8F6 kernel: [ 35.660000] cfg80211: (57000000 KHz - 66000000 KHz @ 2160000 KHz), (N/A, 4000 mBm), (N/A)
    2019:05:29-13:05:27 A40031AA01DF8F6 netifd: Interface 'vxlan' is enabled
    2019:05:29-13:05:27 A40031AA01DF8F6 netifd: Network device 'vxlan' link is up
    2019:05:29-13:05:27 A40031AA01DF8F6 netifd: Interface 'vxlan' has link connectivity
    2019:05:29-13:05:27 A40031AA01DF8F6 netifd: Interface 'vxlan' is setting up now
    2019:05:29-13:05:27 A40031AA01DF8F6 netifd: Interface 'vxlan' is now up
    2019:05:29-13:05:27 A40031AA01DF8F6 netifd: VLAN 'vxlan.100' link is up
    2019:05:29-13:05:27 A40031AA01DF8F6 kernel: [ 35.920000] device vxlan.100 entered promiscuous mode
    2019:05:29-13:05:27 A40031AA01DF8F6 kernel: [ 35.920000] device vxlan entered promiscuous mode
    2019:05:29-13:05:27 A40031AA01DF8F6 kernel: [ 35.950000] br-vxlan100: port 1(vxlan.100) entered forwarding state
    2019:05:29-13:05:27 A40031AA01DF8F6 kernel: [ 35.950000] br-vxlan100: port 1(vxlan.100) entered forwarding state
    2019:05:29-13:05:27 A40031AA01DF8F6 netifd: Interface 'vxlan100' is enabled
    2019:05:29-13:05:27 A40031AA01DF8F6 netifd: Bridge 'br-vxlan100' link is up
    2019:05:29-13:05:27 A40031AA01DF8F6 netifd: Interface 'vxlan100' has link connectivity
    2019:05:29-13:05:27 A40031AA01DF8F6 netifd: Interface 'vxlan100' is setting up now
    2019:05:29-13:05:27 A40031AA01DF8F6 netifd: Interface 'vxlan100' is now up
    2019:05:22-23:43:39 sg115 awed[6029]: [A40031AA01DF8F6] ll_read: dead socket: Interrupted system call
    2019:05:22-23:43:39 sg115 awed[6029]: [A40031AA01DF8F6] disconnected. Close socket and kill process.
    2019:05:29-13:05:29 A40031AA01DF8F6 dropbear[1311]: Not backgrounding
    2019:05:29-13:05:29 A40031AA01DF8F6 aweclient[858]: aweclient.c (1844) A signal received during select.
    2019:05:29-13:05:29 A40031AA01DF8F6 kernel: [ 37.950000] br-vxlan100: port 1(vxlan.100) entered forwarding state
    2019:05:22-23:44:21 A40031AA01DF8F6 kernel: [ 79.940000] random: nonblocking pool is initialized
  • In reply to nd:

    awed restart:

    2019:05:22-23:54:29 sg115 awed[7930]: [MASTER] SIGTERM received, sending SIGTERM to siblings, exiting
    2019:05:22-23:54:29 sg115 awed[7946]: [A40031AA01DF8F6] ll_read: dead socket: Interrupted system call
    2019:05:22-23:54:29 sg115 awed[7946]: [A40031AA01DF8F6] disconnected. Close socket and kill process.
    2019:05:22-23:54:29 A40031AA01DF8F6 aweclient[858]: aweclient.c (2497) Exit from main loop.
    2019:05:22-23:54:29 A40031AA01DF8F6 aweclient[858]: facility_awed.c (196) Read error on socket: 146
    2019:05:22-23:54:29 A40031AA01DF8F6 aweclient[858]: aweclient.c (295) Failed to connect to 192.168.4.10.
    2019:05:22-23:54:29 A40031AA01DF8F6 aweclient[858]: facility_awed.c (196) Read error on socket: 146
    2019:05:22-23:54:29 A40031AA01DF8F6 aweclient[858]: aweclient.c (295) Failed to connect to 1.2.3.4.
    2019:05:22-23:54:29 A40031AA01DF8F6 aweclient[858]: facility_awed.c (196) Read error on socket: 146
    2019:05:22-23:54:29 A40031AA01DF8F6 aweclient[858]: aweclient.c (295) Failed to connect to 1.2.3.4.
    2019:05:22-23:54:29 A40031AA01DF8F6 aweclient[858]: aweclient.c (2401) Wait for 15 seconds before retry to connect.
    2019:05:22-23:54:30 sg115 awed[8135]: [MASTER] awed_ng starting
    2019:05:22-23:54:30 sg115 awed[8135]: [MASTER] new firmware detected for AP10: 9500-wifi-1138168-06181be7
    2019:05:22-23:54:30 sg115 awed[8135]: [MASTER] new firmware detected for AP100: 9500-wifi-075cccdf-06181be7
    2019:05:22-23:54:30 sg115 awed[8135]: [MASTER] new firmware detected for AP100C: 9500-wifi-075cccdf-06181be7
    2019:05:22-23:54:30 sg115 awed[8135]: [MASTER] new firmware detected for AP100X: 9500-wifi-075cccdf-06181be7
    2019:05:22-23:54:30 sg115 awed[8135]: [MASTER] new firmware detected for AP15: 9500-wifi-075cccdf-06181be7
    2019:05:22-23:54:30 sg115 awed[8135]: [MASTER] new firmware detected for AP15C: 9500-wifi-075cccdf-06181be7
    2019:05:22-23:54:30 sg115 awed[8135]: [MASTER] new firmware detected for AP30: 9500-wifi-1138168-06181be7
    2019:05:22-23:54:30 sg115 awed[8135]: [MASTER] new firmware detected for AP5: 1
    2019:05:22-23:54:30 sg115 awed[8135]: [MASTER] new firmware detected for AP50: 9500-wifi-1138168-06181be7
    2019:05:22-23:54:30 sg115 awed[8135]: [MASTER] new firmware detected for AP55: 9500-wifi-075cccdf-06181be7
    2019:05:22-23:54:30 sg115 awed[8135]: [MASTER] new firmware detected for AP55C: 9500-wifi-075cccdf-06181be7
    2019:05:22-23:54:30 sg115 awed[8135]: [MASTER] new firmware detected for RED15w: 1
    2019:05:22-23:54:30 sg115 awed[8135]: [MASTER] access point firmware available: AP15C:9500-wifi-075cccdf-06181be7 AP10:9500-wifi-1138168-06181be7 AP55C:9500-wifi-075cccdf-06181be7 RED15w:1 AP5:1 AP30:9500-wifi-1138168-06181be7 AP100C:9500-wifi-075cccdf-06181be7 AP100X:9500-wifi-075cccdf-06181be7 AP50:9500-wifi-1138168-06181be7 AP55:9500-wifi-075cccdf-06181be7 AP15:9500-wifi-075cccdf-06181be7 AP100:9500-wifi-075cccdf-06181be7
    2019:05:22-23:54:33 sg115 awed[8135]: [MASTER] start processing configuration change
    2019:05:22-23:54:33 sg115 awed[8135]: [MASTER] end processing configuration change
    2019:05:22-23:54:44 sg115 awed[8135]: [MASTER] new connection from 192.168.4.106:50079
    2019:05:22-23:54:44 sg115 awed[8159]: [A40031AA01DF8F6] AP15 from 192.168.4.106:50079 identified as A40031AA01DF8F6
    2019:05:22-23:54:44 sg115 awed[8159]: [A40031AA01DF8F6] (Re-)loaded identity and/or configuration
    2019:05:22-23:54:44 A40031AA01DF8F6 aweclient[858]: Cloudclient not found on ubus.