Thread Info
  • State Suggested Answer
  • +1 person also asked this people also asked this
  • Locked Locked
  • Replies 9 replies
  • Answers 1 answer
  • Subscribers 4 subscribers
  • Views 22080 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

AP50 No Radio Broadcast 2,4GHz and 5Ghz

JulianTekook

Hi There,

 

I just bought my first AP50 for my UTM Home and tried to install it. I connected to the UTM successfully and gets marked as active, I can even configure it.

The weird thing is, it does not broadcast its radio. The two LEDs for 2,4GHz and 5GHz are off.

I took a look at the wireless log and found these lines:

 

2016:12:23-13:56:30 172.20.0.200 netifd: radio1 (1130): Could not find PHY for device 'radio1'
2016:12:23-13:56:30 172.20.0.200 netifd: radio0 (1129): Could not find PHY for device 'radio0'
2016:12:23-13:56:30 172.20.0.200 netifd: radio1 (1192): WARNING: Variable 'data' does not exist or is not an array/object
2016:12:23-13:56:30 172.20.0.200 netifd: radio0 (1199): WARNING: Variable 'data' does not exist or is not an array/object

If I take of the two antennae, the log shows a Data bus error, so I don't suspect the antennae to be defect.

If I try to configure a Wireless Network with only 5GHz enabled the UTM states, thatthe AP50 does not support operation on the 5 GHz band.


I am kinda lost here, could this be a firmware problem or is it a hardware problem?

 


I even attached the AP50 to my enterprise network at work, with the same result...

 

Attached you find the wireless log file.

Fullscreen wireless-2017-03-09.log Download 
2017:03:09-19:45:41 utm awed[62772]: [MASTER] new connection from 172.20.0.200:35553
2017:03:09-19:46:10 utm awed[62772]: [MASTER] new connection from 172.20.0.200:35553
2017:03:09-19:46:10 utm awed[44457]: WARN -------------------------------------------------------
2017:03:09-19:46:10 utm awed[44457]: Use of uninitialized value in concatenation (.) or string at awed_ng.pl line 347.
2017:03:09-19:46:10 utm awed[44457]: 1 main::awed_aphandler
2017:03:09-19:46:10 utm awed[44457]: 1
2017:03:09-19:46:13 utm awed[62772]: [MASTER] new AP with ID A400022BAE70DE3
2017:03:09-19:46:14 utm awed[62772]: [MASTER] start processing configuration change
2017:03:09-19:46:14 utm awed[62772]: [MASTER] AP A400022BAE70DE3: Local metadata updated
2017:03:09-19:46:14 utm awed[62772]: [MASTER] AP A400022BAE70DE3: Configuration change detected
2017:03:09-19:46:14 utm awed[62772]: [MASTER] end processing configuration change
2017:03:09-19:47:26 utm awed[62772]: [MASTER] start processing configuration change
2017:03:09-19:47:27 utm awed[62772]: [MASTER] end processing configuration change
2017:03:09-19:47:27 utm awed[62772]: [MASTER] start processing configuration change
2017:03:09-19:47:27 utm awed[62772]: [MASTER] AP A400022BAE70DE3: Local metadata updated
2017:03:09-19:47:27 utm awed[62772]: [MASTER] AP A400022BAE70DE3: Configuration change detected
2017:03:09-19:47:27 utm awed[62772]: [MASTER] end processing configuration change
2017:03:09-19:47:37 utm awed[62772]: [MASTER] start processing configuration change
2017:03:09-19:47:37 utm awed[62772]: WARN -------------------------------------------------------
2017:03:09-19:47:37 utm awed[62772]: Use of uninitialized value $sorted_channels[-1] in numeric gt (>) at awed_ng.pl line 1109.
2017:03:09-19:47:37 utm awed[62772]: WARN -------------------------------------------------------
2017:03:09-19:47:37 utm awed[62772]: Use of uninitialized value $sorted_channels[-1] in numeric gt (>) at awed_ng.pl line 1109.
2017:03:09-19:47:37 utm awed[62772]: [MASTER] AP A400022BAE70DE3: Configuration change detected
2017:03:09-19:47:37 utm awed[62772]: [MASTER] end processing configuration change
2017:03:09-19:48:36 utm awed[62772]: [MASTER] new connection from 172.20.0.200:60077
2017:03:09-19:48:36 utm awed[45094]: [A400022BAE70DE3] AP50 from 172.20.0.200:60077 identified as A400022BAE70DE3
2017:03:09-19:48:36 utm awed[45094]: [A400022BAE70DE3] (Re-)loaded identity and/or configuration
2017:03:09-19:48:41 utm awed[45094]: [A400022BAE70DE3] sent firmware /etc/wireless/firmware/AP50.uimage to device, releasing connection.
2017:03:09-19:50:29 utm awed[62772]: [MASTER] new connection from 172.20.0.200:38885
2017:03:09-19:50:29 utm awed[45388]: [A400022BAE70DE3] AP50 from 172.20.0.200:38885 identified as A400022BAE70DE3
2017:03:09-19:50:29 utm awed[45388]: [A400022BAE70DE3] (Re-)loaded identity and/or configuration
2017:03:09-19:50:32 utm awed[62772]: [MASTER] updating confd object for AP A400022BAE70DE3
2016:12:23-13:56:30 172.20.0.200 logread[884]: Logread connected to 172.20.0.250:415
2017:03:09-19:50:32 utm awed[62772]: [MASTER] start processing configuration change
2017:03:09-19:50:33 utm awed[62772]: WARN -------------------------------------------------------
2017:03:09-19:50:33 utm awed[62772]: Use of uninitialized value $sorted_channels[-1] in numeric gt (>) at awed_ng.pl line 1109.
2017:03:09-19:50:33 utm awed[62772]: WARN -------------------------------------------------------
2017:03:09-19:50:33 utm awed[62772]: Use of uninitialized value $sorted_channels[-1] in numeric gt (>) at awed_ng.pl line 1109.
2017:03:09-19:50:33 utm awed[62772]: [MASTER] AP A400022BAE70DE3: Local metadata updated
2017:03:09-19:50:33 utm awed[62772]: [MASTER] end processing configuration change
2016:12:23-13:56:31 172.20.0.200 aweclient: Config in flash changed, reboot.
2016:12:23-13:56:31 172.20.0.200 syslog: - shutdown -
2016:12:23-13:56:31 172.20.0.200 syslog: 
2017:03:09-19:51:30 utm awed[45388]: [A400022BAE70DE3] ll_read: dead socket: Resource temporarily unavailable
2017:03:09-19:51:30 utm awed[45388]: [A400022BAE70DE3] disconnected. Close socket and kill process.
2017:03:09-19:51:35 utm awed[62772]: [MASTER] new connection from 172.20.0.200:53170
2017:03:09-19:51:36 utm awed[45671]: [A400022BAE70DE3] AP50 from 172.20.0.200:53170 identified as A400022BAE70DE3
2017:03:09-19:51:36 utm awed[45671]: [A400022BAE70DE3] (Re-)loaded identity and/or configuration
2016:12:23-13:56:29 172.20.0.200 logread[882]: Logread connected to 172.20.0.250:415
2016:12:23-13:56:29 172.20.0.200 kernel: [   29.530000] device vxlan.100 entered promiscuous mode
2016:12:23-13:56:29 172.20.0.200 kernel: [   29.540000] device vxlan entered promiscuous mode
2016:12:23-13:56:29 172.20.0.200 kernel: [   29.550000] br-vxlan100: port 1(vxlan.100) entered forwarding state
2016:12:23-13:56:29 172.20.0.200 kernel: [   29.560000] br-vxlan100: port 1(vxlan.100) entered forwarding state
2016:12:23-13:56:29 172.20.0.200 netifd: Interface 'vxlan100' is enabled
2016:12:23-13:56:29 172.20.0.200 netifd: Network device 'vxlan' link is up
2016:12:23-13:56:29 172.20.0.200 netifd: Interface 'vxlan' has link connectivity 
2016:12:23-13:56:29 172.20.0.200 netifd: Interface 'vxlan' is setting up now
2016:12:23-13:56:29 172.20.0.200 netifd: Interface 'vxlan' is now up
2016:12:23-13:56:29 172.20.0.200 netifd: VLAN 'vxlan.100' link is up
2016:12:23-13:56:29 172.20.0.200 netifd: VLAN 'vxlan.100' link is down
2016:12:23-13:56:29 172.20.0.200 netifd: VLAN 'vxlan.100' link is up
2016:12:23-13:56:29 172.20.0.200 netifd: Bridge 'br-vxlan100' link is up
2016:12:23-13:56:29 172.20.0.200 netifd: Interface 'vxlan100' has link connectivity 
2016:12:23-13:56:29 172.20.0.200 netifd: Interface 'vxlan100' is setting up now
2016:12:23-13:56:30 172.20.0.200 netifd: radio1 (1133): Could not find PHY for device 'radio1'
2016:12:23-13:56:30 172.20.0.200 netifd: radio0 (1132): Could not find PHY for device 'radio0'
2016:12:23-13:56:30 172.20.0.200 netifd: radio1 (1195): WARNING: Variable 'data' does not exist or is not an array/object
2016:12:23-13:56:30 172.20.0.200 netifd: radio0 (1200): WARNING: Variable 'data' does not exist or is not an array/object
2016:12:23-13:56:31 172.20.0.200 kernel: [   31.560000] br-vxlan100: port 1(vxlan.100) entered forwarding state
2017:03:09-19:58:29 utm awed[62772]: [MASTER] new connection from 172.20.0.200:34305
2017:03:09-19:58:29 utm awed[46597]: [A400022BAE70DE3] AP50 from 172.20.0.200:34305 identified as A400022BAE70DE3
2017:03:09-19:58:29 utm awed[46597]: [A400022BAE70DE3] (Re-)loaded identity and/or configuration
2016:12:23-13:56:29 172.20.0.200 logread[880]: Logread connected to 172.20.0.250:415
2016:12:23-13:56:29 172.20.0.200 netifd: Interface 'vxlan' is enabled
2016:12:23-13:56:29 172.20.0.200 kernel: [   29.540000] device vxlan.100 entered promiscuous mode
2016:12:23-13:56:29 172.20.0.200 kernel: [   29.550000] device vxlan entered promiscuous mode
2016:12:23-13:56:29 172.20.0.200 kernel: [   29.570000] br-vxlan100: port 1(vxlan.100) entered forwarding state
2016:12:23-13:56:29 172.20.0.200 kernel: [   29.570000] br-vxlan100: port 1(vxlan.100) entered forwarding state
2016:12:23-13:56:29 172.20.0.200 netifd: Interface 'vxlan100' is enabled
2016:12:23-13:56:29 172.20.0.200 netifd: Network device 'vxlan' link is up
2016:12:23-13:56:29 172.20.0.200 netifd: Interface 'vxlan' has link connectivity 
2016:12:23-13:56:29 172.20.0.200 netifd: Interface 'vxlan' is setting up now
2016:12:23-13:56:29 172.20.0.200 netifd: Interface 'vxlan' is now up
2016:12:23-13:56:29 172.20.0.200 netifd: VLAN 'vxlan.100' link is up
2016:12:23-13:56:29 172.20.0.200 netifd: VLAN 'vxlan.100' link is down
2016:12:23-13:56:29 172.20.0.200 netifd: VLAN 'vxlan.100' link is up
2016:12:23-13:56:29 172.20.0.200 netifd: Bridge 'br-vxlan100' link is up
2016:12:23-13:56:29 172.20.0.200 netifd: Interface 'vxlan100' has link connectivity 
2016:12:23-13:56:29 172.20.0.200 netifd: Interface 'vxlan100' is setting up now
2016:12:23-13:56:29 172.20.0.200 netifd: Interface 'vxlan100' is now up
2016:12:23-13:56:30 172.20.0.200 netifd: radio1 (1130): Could not find PHY for device 'radio1'
2016:12:23-13:56:30 172.20.0.200 netifd: radio0 (1129): Could not find PHY for device 'radio0'
2016:12:23-13:56:30 172.20.0.200 netifd: radio1 (1192): WARNING: Variable 'data' does not exist or is not an array/object
2016:12:23-13:56:30 172.20.0.200 netifd: radio0 (1199): WARNING: Variable 'data' does not exist or is not an array/object
2017:03:09-19:58:32 utm awed[45671]: [A400022BAE70DE3] ll_read: dead socket: Interrupted system call
2017:03:09-19:58:32 utm awed[45671]: [A400022BAE70DE3] disconnected. Close socket and kill process.
2016:12:23-13:56:31 172.20.0.200 kernel: [   31.570000] br-vxlan100: port 1(vxlan.100) entered forwarding state
2017:03:09-20:01:12 utm awed[62772]: [MASTER] start processing configuration change
2017:03:09-20:01:12 utm awed[62772]: WARN -------------------------------------------------------
2017:03:09-20:01:12 utm awed[62772]: Use of uninitialized value $sorted_channels[-1] in numeric gt (>) at awed_ng.pl line 1109.
2017:03:09-20:01:12 utm awed[62772]: WARN -------------------------------------------------------
2017:03:09-20:01:12 utm awed[62772]: Use of uninitialized value $sorted_channels[-1] in numeric gt (>) at awed_ng.pl line 1109.
2017:03:09-20:01:12 utm awed[62772]: [MASTER] AP A400022BAE70DE3: Configuration change detected
2017:03:09-20:01:12 utm awed[62772]: [MASTER] end processing configuration change
2017:03:09-20:01:16 utm awed[46597]: [A400022BAE70DE3] (Re-)loaded identity and/or configuration
2017:03:09-20:01:16 172.20.0.200 aweclient[710]: aweclient.c (2462) Exit from main loop with no error. Get new configuration.
2017:03:09-20:01:17 172.20.0.200 aweclient[710]: Cloudclient not found on ubus.
2017:03:09-20:01:18 172.20.0.200 add_radio_mapping.sh: AP50 detected: Using on-the-fly ACS procedure
2017:03:09-20:01:19 172.20.0.200 netifd: radio1 (1587): Could not find PHY for device 'radio1'
2017:03:09-20:01:19 172.20.0.200 netifd: radio0 (1586): Could not find PHY for device 'radio0'
2017:03:09-20:01:19 172.20.0.200 netifd: radio1 (1612): WARNING: Variable 'data' does not exist or is not an array/object
2017:03:09-20:01:19 172.20.0.200 netifd: radio0 (1618): WARNING: Variable 'data' does not exist or is not an array/object
2017:03:09-20:03:08 utm awed[62772]: [MASTER] start processing configuration change
2017:03:09-20:03:08 utm awed[62772]: WARN -------------------------------------------------------
2017:03:09-20:03:08 utm awed[62772]: Use of uninitialized value $sorted_channels[-1] in numeric gt (>) at awed_ng.pl line 1109.
2017:03:09-20:03:08 utm awed[62772]: WARN -------------------------------------------------------
2017:03:09-20:03:08 utm awed[62772]: Use of uninitialized value $sorted_channels[-1] in numeric gt (>) at awed_ng.pl line 1109.
2017:03:09-20:03:08 utm awed[62772]: [MASTER] end processing configuration change
2017:03:09-20:04:50 utm awed[62772]: [MASTER] start processing configuration change
2017:03:09-20:04:50 utm awed[62772]: WARN -------------------------------------------------------
2017:03:09-20:04:50 utm awed[62772]: Use of uninitialized value $sorted_channels[-1] in numeric gt (>) at awed_ng.pl line 1109.
2017:03:09-20:04:50 utm awed[62772]: WARN -------------------------------------------------------
2017:03:09-20:04:50 utm awed[62772]: Use of uninitialized value $sorted_channels[-1] in numeric gt (>) at awed_ng.pl line 1109.
2017:03:09-20:04:50 utm awed[62772]: [MASTER] AP A400022BAE70DE3: Configuration change detected
2017:03:09-20:04:50 utm awed[62772]: [MASTER] end processing configuration change
2017:03:09-20:05:02 utm awed[62772]: [MASTER] start processing configuration change
2017:03:09-20:05:02 utm awed[62772]: WARN -------------------------------------------------------
2017:03:09-20:05:02 utm awed[62772]: Use of uninitialized value $sorted_channels[-1] in numeric gt (>) at awed_ng.pl line 1109.
2017:03:09-20:05:02 utm awed[62772]: WARN -------------------------------------------------------
2017:03:09-20:05:02 utm awed[62772]: Use of uninitialized value $sorted_channels[-1] in numeric gt (>) at awed_ng.pl line 1109.
2017:03:09-20:05:02 utm awed[62772]: [MASTER] end processing configuration change
2017:03:09-20:05:04 utm awed[46597]: [A400022BAE70DE3] (Re-)loaded identity and/or configuration
2017:03:09-20:05:04 172.20.0.200 aweclient[710]: aweclient.c (2462) Exit from main loop with no error. Get new configuration.
2017:03:09-20:05:05 172.20.0.200 aweclient[710]: Cloudclient not found on ubus.
2017:03:09-20:05:06 172.20.0.200 add_radio_mapping.sh: AP50 detected: Using on-the-fly ACS procedure
2017:03:09-20:05:07 172.20.0.200 netifd: lan (769): Sending renew...
2017:03:09-20:05:07 172.20.0.200 netifd: lan (769): Received SIGTERM
2017:03:09-20:07:38 utm awed[46597]: [A400022BAE70DE3] ll_read: dead socket: Resource temporarily unavailable
2017:03:09-20:07:38 utm awed[46597]: [A400022BAE70DE3] disconnected. Close socket and kill process.
2017:03:09-20:24:21 utm awed[62772]: [MASTER] new connection from 172.20.0.200:37533
2017:03:09-20:24:21 utm awed[51194]: [A400022BAE70DE3] AP50 from 172.20.0.200:37533 identified as A400022BAE70DE3
2017:03:09-20:24:21 utm awed[51194]: [A400022BAE70DE3] (Re-)loaded identity and/or configuration
2016:12:23-13:56:29 172.20.0.200 kernel: [   29.020000] cfg80211:  DFS Master region: ETSI
2016:12:23-13:56:29 172.20.0.200 kernel: [   29.020000] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
2016:12:23-13:56:29 172.20.0.200 kernel: [   29.030000] cfg80211:   (2400000 KHz - 2483000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
2016:12:23-13:56:29 172.20.0.200 kernel: [   29.040000] cfg80211:   (5150000 KHz - 5250000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A)
2016:12:23-13:56:29 172.20.0.200 kernel: [   29.050000] cfg80211:   (5250000 KHz - 5350000 KHz @ 80000 KHz), (N/A, 2000 mBm), (0 s)
2016:12:23-13:56:29 172.20.0.200 kernel: [   29.060000] cfg80211:   (5470000 KHz - 5725000 KHz @ 80000 KHz), (N/A, 2700 mBm), (0 s)
2016:12:23-13:56:29 172.20.0.200 kernel: [   29.060000] cfg80211:   (57240000 KHz - 65880000 KHz @ 2160000 KHz), (N/A, 4000 mBm), (N/A)
2016:12:23-13:56:29 172.20.0.200 kernel: [   29.630000] device vxlan.100 entered promiscuous mode
2016:12:23-13:56:29 172.20.0.200 kernel: [   29.640000] device vxlan entered promiscuous mode
2016:12:23-13:56:29 172.20.0.200 add_radio_mapping.sh: AP50 detected: Using on-the-fly ACS procedure
2016:12:23-13:56:29 172.20.0.200 logread[882]: Logread connected to 172.20.0.250:415
2016:12:23-13:56:29 172.20.0.200 netifd: Interface 'vxlan' is enabled
2016:12:23-13:56:29 172.20.0.200 kernel: [   29.660000] br-vxlan100: port 1(vxlan.100) entered forwarding state
2016:12:23-13:56:29 172.20.0.200 kernel: [   29.660000] br-vxlan100: port 1(vxlan.100) entered forwarding state
2016:12:23-13:56:29 172.20.0.200 netifd: Interface 'vxlan100' is enabled
2016:12:23-13:56:29 172.20.0.200 netifd: Network device 'vxlan' link is up
2016:12:23-13:56:29 172.20.0.200 netifd: Interface 'vxlan' has link connectivity 
2016:12:23-13:56:29 172.20.0.200 netifd: Interface 'vxlan' is setting up now
2016:12:23-13:56:29 172.20.0.200 netifd: Interface 'vxlan' is now up
2016:12:23-13:56:29 172.20.0.200 netifd: VLAN 'vxlan.100' link is up
2016:12:23-13:56:29 172.20.0.200 netifd: VLAN 'vxlan.100' link is down
2016:12:23-13:56:29 172.20.0.200 netifd: VLAN 'vxlan.100' link is up
2016:12:23-13:56:29 172.20.0.200 netifd: Bridge 'br-vxlan100' link is up
2016:12:23-13:56:29 172.20.0.200 netifd: Interface 'vxlan100' has link connectivity 
2016:12:23-13:56:29 172.20.0.200 netifd: Interface 'vxlan100' is setting up now
2016:12:23-13:56:29 172.20.0.200 netifd: Interface 'vxlan100' is now up
2016:12:23-13:56:30 172.20.0.200 netifd: lan (771): Received SIGTERM
2016:12:23-13:56:37 172.20.0.200 logread[882]: Logread connected to 172.20.0.250:415
2017:03:09-20:25:28 utm awed[62772]: [MASTER] start processing configuration change
2017:03:09-20:25:28 utm awed[62772]: WARN -------------------------------------------------------
2017:03:09-20:25:28 utm awed[62772]: Use of uninitialized value $sorted_channels[-1] in numeric gt (>) at awed_ng.pl line 1109.
2017:03:09-20:25:28 utm awed[62772]: [MASTER] end processing configuration change
2017:03:09-20:26:18 utm awed[62772]: [MASTER] start processing configuration change
2017:03:09-20:26:18 utm awed[62772]: [MASTER] end processing configuration change
2017:03:09-20:27:06 utm awed[62772]: [MASTER] new connection from 172.20.0.200:43840
2017:03:09-20:27:06 utm awed[51931]: [A400022BAE70DE3] AP50 from 172.20.0.200:43840 identified as A400022BAE70DE3
2017:03:09-20:27:06 utm awed[51931]: [A400022BAE70DE3] (Re-)loaded identity and/or configuration
2016:12:23-13:56:29 172.20.0.200 kernel: [   29.670000] device vxlan.100 entered promiscuous mode
2016:12:23-13:56:29 172.20.0.200 kernel: [   29.670000] device vxlan entered promiscuous mode
2016:12:23-13:56:29 172.20.0.200 kernel: [   29.700000] br-vxlan100: port 1(vxlan.100) entered forwarding state
2016:12:23-13:56:29 172.20.0.200 kernel: [   29.700000] br-vxlan100: port 1(vxlan.100) entered forwarding state
2016:12:23-13:56:29 172.20.0.200 logread[882]: Logread connected to 172.20.0.250:415
2016:12:23-13:56:29 172.20.0.200 netifd: Interface 'vxlan' is enabled
2016:12:23-13:56:29 172.20.0.200 netifd: Interface 'vxlan100' is enabled
2016:12:23-13:56:29 172.20.0.200 netifd: Network device 'vxlan' link is up
2016:12:23-13:56:29 172.20.0.200 netifd: Interface 'vxlan' has link connectivity 
2016:12:23-13:56:29 172.20.0.200 netifd: Interface 'vxlan' is setting up now
2016:12:23-13:56:29 172.20.0.200 netifd: Interface 'vxlan' is now up
2016:12:23-13:56:29 172.20.0.200 netifd: VLAN 'vxlan.100' link is up
2016:12:23-13:56:29 172.20.0.200 netifd: VLAN 'vxlan.100' link is down
2016:12:23-13:56:29 172.20.0.200 netifd: VLAN 'vxlan.100' link is up
2016:12:23-13:56:29 172.20.0.200 netifd: Bridge 'br-vxlan100' link is up
2016:12:23-13:56:29 172.20.0.200 netifd: Interface 'vxlan100' has link connectivity 
2016:12:23-13:56:29 172.20.0.200 netifd: Interface 'vxlan100' is setting up now
2016:12:23-13:56:29 172.20.0.200 netifd: Interface 'vxlan100' is now up
2016:12:23-13:56:30 172.20.0.200 netifd: lan (782): Received SIGTERM
2016:12:23-13:56:30 172.20.0.200 netifd: Interface 'lan' is now down
2017:03:09-20:27:09 utm awed[51194]: [A400022BAE70DE3] ll_read: dead socket: Interrupted system call
2017:03:09-20:27:09 utm awed[51194]: [A400022BAE70DE3] disconnected. Close socket and kill process.
2016:12:23-13:56:37 172.20.0.200 logread[882]: Logread connected to 172.20.0.250:415
2017:03:09-20:27:27 utm awed[62772]: [MASTER] start processing configuration change
2017:03:09-20:27:26 172.20.0.200 aweclient[709]: aweclient.c (2456) Exit from main loop.
2017:03:09-20:27:26 172.20.0.200 aweclient[709]: aweclient.c (2470) Error in getting new configuration. Reconnecting (1)
2017:03:09-20:27:26 172.20.0.200 aweclient[709]: aweclient.c (277) Failed to connect to 0.0.0.0.
2017:03:09-20:27:27 utm awed[62772]: [MASTER] end processing configuration change
2017:03:09-20:27:27 utm awed[62772]: [MASTER] new connection from 172.20.0.200:43841
2017:03:09-20:27:27 172.20.0.200 aweclient[709]: json_messages.c (461) Message type is different from expected.
2017:03:09-20:27:28 172.20.0.200 aweclient[709]: aweclient.c (621) Invalid shared key, clear registered flag and retry.
2017:03:09-20:27:28 172.20.0.200 aweclient[709]: aweclient.c (2400) Cannot get a valid configuration, retry later.
2017:03:09-21:14:21 utm awed[62772]: [MASTER] new connection from 172.20.0.200:37533
2017:03:09-21:14:21 utm awed[59961]: WARN -------------------------------------------------------
2017:03:09-21:14:21 utm awed[59961]: Use of uninitialized value in concatenation (.) or string at awed_ng.pl line 347.
2017:03:09-21:14:21 utm awed[59961]: 1 main::awed_aphandler
2017:03:09-21:14:21 utm awed[59961]: 1
2017:03:09-21:14:24 utm awed[62772]: [MASTER] new AP with ID A400022BAE70DE3
2017:03:09-21:14:24 utm awed[62772]: WARN -------------------------------------------------------
2017:03:09-21:14:24 utm awed[62772]: Use of uninitialized value in concatenation (.) or string at awed_ng.pl line 1673.
2017:03:09-21:14:24 utm awed[62772]: [MASTER] start processing configuration change
2017:03:09-21:14:25 utm awed[62772]: [MASTER] AP A400022BAE70DE3: Local metadata updated
2017:03:09-21:14:25 utm awed[62772]: [MASTER] AP A400022BAE70DE3: Configuration change detected
2017:03:09-21:14:25 utm awed[62772]: [MASTER] end processing configuration change
2017:03:09-21:14:28 utm awed[62772]: [MASTER] new connection from 172.20.0.200:37534
2017:03:09-21:14:28 utm awed[60057]: [A400022BAE70DE3] AP50 from 172.20.0.200:37534 identified as A400022BAE70DE3
2017:03:09-21:14:28 utm awed[60057]: [A400022BAE70DE3] (Re-)loaded identity and/or configuration
2017:03:09-21:14:28 utm awed[60057]: [A400022BAE70DE3] device not authorized yet, dropping.
2017:03:09-21:14:43 utm awed[62772]: [MASTER] new connection from 172.20.0.200:37535
2017:03:09-21:14:43 utm awed[60089]: [A400022BAE70DE3] AP50 from 172.20.0.200:37535 identified as A400022BAE70DE3
2017:03:09-21:14:43 utm awed[60089]: [A400022BAE70DE3] (Re-)loaded identity and/or configuration
2017:03:09-21:14:43 utm awed[60089]: [A400022BAE70DE3] device not authorized yet, dropping.
2017:03:09-21:14:58 utm awed[62772]: [MASTER] new connection from 172.20.0.200:37536
2017:03:09-21:14:58 utm awed[60127]: [A400022BAE70DE3] AP50 from 172.20.0.200:37536 identified as A400022BAE70DE3
2017:03:09-21:14:58 utm awed[60127]: [A400022BAE70DE3] (Re-)loaded identity and/or configuration
2017:03:09-21:14:58 utm awed[60127]: [A400022BAE70DE3] device not authorized yet, dropping.
2017:03:09-21:15:04 utm awed[62772]: [MASTER] start processing configuration change
2017:03:09-21:15:05 utm awed[62772]: [MASTER] AP A400022BAE70DE3: Local metadata updated
2017:03:09-21:15:05 utm awed[62772]: [MASTER] AP A400022BAE70DE3: Configuration change detected
2017:03:09-21:15:05 utm awed[62772]: [MASTER] end processing configuration change
2017:03:09-21:15:13 utm awed[62772]: [MASTER] new connection from 172.20.0.200:37537
2017:03:09-21:15:13 utm awed[60405]: [A400022BAE70DE3] AP50 from 172.20.0.200:37537 identified as A400022BAE70DE3
2017:03:09-21:15:13 utm awed[60405]: [A400022BAE70DE3] (Re-)loaded identity and/or configuration
2016:12:23-13:57:23 172.20.0.200 kernel: [   83.220000] cfg80211:  DFS Master region: ETSI
2016:12:23-13:57:23 172.20.0.200 kernel: [   83.240000] cfg80211:   (5150000 KHz - 5250000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A)
2016:12:23-13:57:23 172.20.0.200 kernel: [   83.250000] cfg80211:   (5250000 KHz - 5350000 KHz @ 80000 KHz), (N/A, 2000 mBm), (0 s)
2016:12:23-13:57:23 172.20.0.200 kernel: [   83.260000] cfg80211:   (5470000 KHz - 5725000 KHz @ 80000 KHz), (N/A, 2700 mBm), (0 s)
2016:12:23-13:57:23 172.20.0.200 kernel: [   83.270000] cfg80211:   (57240000 KHz - 65880000 KHz @ 2160000 KHz), (N/A, 4000 mBm), (N/A)
2016:12:23-13:57:23 172.20.0.200 kernel: [   83.790000] device vxlan.100 entered promiscuous mode
2016:12:23-13:57:23 172.20.0.200 kernel: [   83.800000] device vxlan entered promiscuous mode
2016:12:23-13:57:23 172.20.0.200 add_radio_mapping.sh: AP50 detected: Using on-the-fly ACS procedure
2016:12:23-13:57:23 172.20.0.200 logread[908]: Logread connected to 172.20.0.250:415
2016:12:23-13:57:23 172.20.0.200 netifd: Interface 'vxlan' is enabled
2016:12:23-13:57:23 172.20.0.200 kernel: [   83.810000] br-vxlan100: port 1(vxlan.100) entered forwarding state
2016:12:23-13:57:23 172.20.0.200 kernel: [   83.810000] br-vxlan100: port 1(vxlan.100) entered forwarding state
2016:12:23-13:57:23 172.20.0.200 netifd: Interface 'vxlan100' is enabled
2016:12:23-13:57:23 172.20.0.200 netifd: Network device 'vxlan' link is up
2016:12:23-13:57:23 172.20.0.200 netifd: Interface 'vxlan' has link connectivity 
2016:12:23-13:57:23 172.20.0.200 netifd: Interface 'vxlan' is setting up now
2016:12:23-13:57:23 172.20.0.200 netifd: Interface 'vxlan' is now up
2016:12:23-13:57:23 172.20.0.200 netifd: VLAN 'vxlan.100' link is up
2016:12:23-13:57:23 172.20.0.200 netifd: VLAN 'vxlan.100' link is down
2016:12:23-13:57:23 172.20.0.200 netifd: VLAN 'vxlan.100' link is up
2016:12:23-13:57:23 172.20.0.200 netifd: Bridge 'br-vxlan100' link is up
2016:12:23-13:57:23 172.20.0.200 netifd: Interface 'vxlan100' has link connectivity 
2016:12:23-13:57:23 172.20.0.200 netifd: Interface 'vxlan100' is setting up now
2016:12:23-13:57:23 172.20.0.200 netifd: Interface 'vxlan100' is now up
2016:12:23-13:57:24 172.20.0.200 netifd: radio1 (1154): Could not find PHY for device 'radio1'
2016:12:23-13:57:24 172.20.0.200 netifd: radio0 (1153): Could not find PHY for device 'radio0'
2016:12:23-13:57:24 172.20.0.200 netifd: radio1 (1221): WARNING: Variable 'data' does not exist or is not an array/object
2016:12:23-13:57:24 172.20.0.200 netifd: radio0 (1226): WARNING: Variable 'data' does not exist or is not an array/object
2016:12:23-13:57:25 172.20.0.200 kernel: [   85.810000] br-vxlan100: port 1(vxlan.100) entered forwarding state
2017:03:09-21:16:46 utm awed[62772]: [MASTER] new connection from 172.20.0.200:37533
2017:03:09-21:16:46 utm awed[60911]: [A400022BAE70DE3] AP50 from 172.20.0.200:37533 identified as A400022BAE70DE3
2017:03:09-21:16:46 utm awed[60911]: [A400022BAE70DE3] (Re-)loaded identity and/or configuration
2016:12:23-13:56:29 172.20.0.200 logread[960]: Logread connected to 172.20.0.250:415
2016:12:23-13:56:29 172.20.0.200 netifd: Interface 'vxlan' is enabled
2016:12:23-13:56:29 172.20.0.200 kernel: [   29.580000] device vxlan.100 entered promiscuous mode
2016:12:23-13:56:29 172.20.0.200 kernel: [   29.590000] device vxlan entered promiscuous mode
2016:12:23-13:56:29 172.20.0.200 kernel: [   29.600000] br-vxlan100: port 1(vxlan.100) entered forwarding state
2016:12:23-13:56:29 172.20.0.200 kernel: [   29.610000] br-vxlan100: port 1(vxlan.100) entered forwarding state
2016:12:23-13:56:29 172.20.0.200 netifd: Interface 'vxlan100' is enabled
2016:12:23-13:56:29 172.20.0.200 netifd: Network device 'vxlan' link is up
2016:12:23-13:56:29 172.20.0.200 netifd: Interface 'vxlan' has link connectivity 
2016:12:23-13:56:29 172.20.0.200 netifd: Interface 'vxlan' is setting up now
2016:12:23-13:56:29 172.20.0.200 netifd: Interface 'vxlan' is now up
2016:12:23-13:56:29 172.20.0.200 netifd: VLAN 'vxlan.100' link is up
2016:12:23-13:56:29 172.20.0.200 netifd: VLAN 'vxlan.100' link is down
2016:12:23-13:56:29 172.20.0.200 netifd: VLAN 'vxlan.100' link is up
2016:12:23-13:56:29 172.20.0.200 netifd: Bridge 'br-vxlan100' link is up
2016:12:23-13:56:29 172.20.0.200 netifd: Interface 'vxlan100' has link connectivity 
2016:12:23-13:56:29 172.20.0.200 netifd: Interface 'vxlan100' is setting up now
2016:12:23-13:56:30 172.20.0.200 kernel: [   30.380000] Data bus error, epc == 82802170, ra == 82802164
2016:12:23-13:56:30 172.20.0.200 kernel: [   30.380000] Oops[#1]:
2016:12:23-13:56:30 172.20.0.200 kernel: [   30.380000] CPU: 0 PID: 1327 Comm: iw Not tainted 3.10.49 #3
2016:12:23-13:56:30 172.20.0.200 kernel: [   30.380000] task: 838a7aa0 ti: 82b1e000 task.ti: 82b1e000
2016:12:23-13:56:30 172.20.0.200 kernel: [   30.380000] $ 0   : 00000000 0050a134 deadc0de 00000080
2016:12:23-13:56:30 172.20.0.200 kernel: [   30.380000] $ 4   : 828e8010 0000801c 00000080 00000000
2016:12:23-13:56:30 172.20.0.200 kernel: [   30.380000] $ 8   : 00000000 00000000 585d2d0f 0000052f
2016:12:23-13:56:30 172.20.0.200 kernel: [   30.380000] $12   : 02000000 82addd24 00000000 00080001
2016:12:23-13:56:30 172.20.0.200 kernel: [   30.380000] $16   : 828e8010 828e5cd4 00000010 0000002c
2016:12:23-13:56:30 172.20.0.200 kernel: [   30.380000] $20   : 00000004 828e8404 00000004 00000024
2016:12:23-13:56:30 172.20.0.200 kernel: [   30.380000] $24   : 00000000 777bc364                  
2016:12:23-13:56:30 172.20.0.200 kernel: [   30.380000] $28   : 82b1e000 82b1fae8 00000008 82802164
2016:12:23-13:56:30 172.20.0.200 kernel: [   30.380000] Hi    : 00000027
2016:12:23-13:56:30 172.20.0.200 kernel: [   30.380000] Lo    : 001797ba
2016:12:23-13:56:30 172.20.0.200 kernel: [   30.380000] epc   : 82802170 ath9k_hw_init_global_settings+0x118/0x400 [ath9k_hw]
2016:12:23-13:56:30 172.20.0.200 kernel: [   30.380000]     Not tainted
2016:12:23-13:56:30 172.20.0.200 kernel: [   30.380000] ra    : 82802164 ath9k_hw_init_global_settings+0x10c/0x400 [ath9k_hw]
2016:12:23-13:56:30 172.20.0.200 kernel: [   30.380000] Status: 1000d403	KERNEL EXL IE 
2016:12:23-13:56:30 172.20.0.200 kernel: [   30.380000] Cause : 1080001c
2016:12:23-13:56:30 172.20.0.200 kernel: [   30.380000] PrId  : 00019374 (MIPS 24Kc)
2016:12:23-13:56:30 172.20.0.200 kernel: [   30.380000] Modules linked in: ath9k ath9k_common ath9k_hw ath ledtrig_netdev mac80211 cfg80211 compat arc4 crypto_blkcipher ledtrig_timer ledtrig_default_on gpio_button_hotplug
2016:12:23-13:56:30 172.20.0.200 kernel: [   30.380000] Process iw (pid: 1327, threadinfo=82b1e000, task=838a7aa0, tls=7783f440)
2016:12:23-13:56:30 172.20.0.200 kernel: [   30.380000] Stack : 00000004 00000007 00000004 00000024 828e5440 828e5cd4 828e8010 00000000
2016:12:23-13:56:30 172.20.0.200 kernel: [   30.380000] 	  00000004 00000007 00000004 00000024 00000008 82862e4c 000000d0 80095444
2016:12:23-13:56:30 172.20.0.200 kernel: [   30.380000] 	  00030002 800817f0 82a99300 828e4120 00000000 00000010 828e4ac0 82f95968
2016:12:23-13:56:30 172.20.0.200 kernel: [   30.380000] 	  82addd00 00000014 00000000 00000014 828dfa00 828e4000 00000000 ffffffff
2016:12:23-13:56:30 172.20.0.200 kernel: [   30.380000] 	  ffffffff 82ed6ef0 82a99300 82a99300 00000000 8019e564 00000029 82b04630
2016:12:23-13:56:30 172.20.0.200 kernel: [   30.380000] 	  ...
2016:12:23-13:56:30 172.20.0.200 kernel: [   30.380000] Call Trace:
2016:12:23-13:56:30 172.20.0.200 kernel: [   30.380000] [<82802170>] ath9k_hw_init_global_settings+0x118/0x400 [ath9k_hw]
2016:12:23-13:56:30 172.20.0.200 kernel: [   30.380000] [<82862e4c>] ath9k_ps_restore+0xf0/0x8f8 [ath9k]
2016:12:23-13:56:30 172.20.0.200 kernel: [   30.380000] 
2016:12:23-13:56:30 172.20.0.200 kernel: [   30.380000] 
2016:12:23-13:56:30 172.20.0.200 kernel: [   30.380000] Code: 8e1300c0  02002021  3405801c <0053001b> 8e020000  0040f809  00009812  08a00866  7c542dc0 
2016:12:23-13:56:30 172.20.0.200 kernel: [   30.560000] ---[ end trace 5c9108b814015780 ]---
2016:12:23-13:56:30 172.20.0.200 netifd: radio1 (1226): Segmentation fault
2017:03:09-21:16:49 utm awed[62772]: [MASTER] updating confd object for AP A400022BAE70DE3
2017:03:09-21:16:50 utm awed[60405]: [A400022BAE70DE3] ll_read: dead socket: Interrupted system call
2017:03:09-21:16:50 utm awed[60405]: [A400022BAE70DE3] disconnected. Close socket and kill process.
2016:12:23-13:56:31 172.20.0.200 kernel: [   31.610000] br-vxlan100: port 1(vxlan.100) entered forwarding state
2017:03:09-21:16:53 utm awed[62772]: [MASTER] start processing configuration change
2017:03:09-21:16:53 utm awed[62772]: [MASTER] AP A400022BAE70DE3: Local metadata updated
2017:03:09-21:16:53 utm awed[62772]: [MASTER] AP A400022BAE70DE3: Configuration change detected
2017:03:09-21:16:53 utm awed[62772]: [MASTER] end processing configuration change
2017:03:09-21:17:48 utm awed[60911]: [A400022BAE70DE3] ll_read: dead socket: Resource temporarily unavailable
2017:03:09-21:17:48 utm awed[60911]: [A400022BAE70DE3] disconnected. Close socket and kill process.
2017:03:09-21:20:31 utm awed[62772]: [MASTER] new connection from 172.20.0.200:45842
2017:03:09-21:20:31 utm awed[61538]: [A400022BAE70DE3] AP50 from 172.20.0.200:45842 identified as A400022BAE70DE3
2017:03:09-21:20:31 utm awed[61538]: [A400022BAE70DE3] (Re-)loaded identity and/or configuration
2016:12:23-13:57:59 172.20.0.200 kernel: [  119.190000] cfg80211:   (5250000 KHz - 5350000 KHz @ 80000 KHz), (N/A, 2000 mBm), (0 s)
2016:12:23-13:57:59 172.20.0.200 kernel: [  119.210000] cfg80211:   (57240000 KHz - 65880000 KHz @ 2160000 KHz), (N/A, 4000 mBm), (N/A)
2016:12:23-13:57:59 172.20.0.200 kernel: [  119.780000] device vxlan.100 entered promiscuous mode
2016:12:23-13:57:59 172.20.0.200 kernel: [  119.780000] device vxlan entered promiscuous mode
2016:12:23-13:57:59 172.20.0.200 logread[884]: Logread connected to 172.20.0.250:415
2016:12:23-13:57:59 172.20.0.200 netifd: Interface 'vxlan' is enabled
2016:12:23-13:57:59 172.20.0.200 kernel: [  119.800000] br-vxlan100: port 1(vxlan.100) entered forwarding state
2016:12:23-13:57:59 172.20.0.200 kernel: [  119.800000] br-vxlan100: port 1(vxlan.100) entered forwarding state
2016:12:23-13:57:59 172.20.0.200 netifd: Interface 'vxlan100' is enabled
2016:12:23-13:57:59 172.20.0.200 netifd: Network device 'vxlan' link is up
2016:12:23-13:57:59 172.20.0.200 netifd: Interface 'vxlan' has link connectivity 
2016:12:23-13:57:59 172.20.0.200 netifd: Interface 'vxlan' is setting up now
2016:12:23-13:57:59 172.20.0.200 netifd: Interface 'vxlan' is now up
2016:12:23-13:57:59 172.20.0.200 netifd: VLAN 'vxlan.100' link is up
2016:12:23-13:57:59 172.20.0.200 netifd: VLAN 'vxlan.100' link is down
2016:12:23-13:57:59 172.20.0.200 netifd: VLAN 'vxlan.100' link is up
2016:12:23-13:57:59 172.20.0.200 netifd: Bridge 'br-vxlan100' link is up
2016:12:23-13:57:59 172.20.0.200 netifd: Interface 'vxlan100' has link connectivity 
2016:12:23-13:57:59 172.20.0.200 netifd: Interface 'vxlan100' is setting up now
2016:12:23-13:57:59 172.20.0.200 netifd: Interface 'vxlan100' is now up
2016:12:23-13:58:00 172.20.0.200 netifd: radio1 (1183): Could not find PHY for device 'radio1'
2016:12:23-13:58:00 172.20.0.200 netifd: radio0 (1182): Could not find PHY for device 'radio0'
2016:12:23-13:58:00 172.20.0.200 netifd: radio1 (1238): WARNING: Variable 'data' does not exist or is not an array/object
2016:12:23-13:58:00 172.20.0.200 netifd: radio0 (1251): WARNING: Variable 'data' does not exist or is not an array/object
2017:03:09-21:20:34 utm awed[62772]: [MASTER] updating confd object for AP A400022BAE70DE3
2017:03:09-21:20:34 utm awed[62772]: [MASTER] start processing configuration change
2017:03:09-21:20:34 utm awed[62772]: [MASTER] AP A400022BAE70DE3: Local metadata updated
2017:03:09-21:20:34 utm awed[62772]: [MASTER] AP A400022BAE70DE3: Configuration change detected
2017:03:09-21:20:34 utm awed[62772]: [MASTER] end processing configuration change
2016:12:23-13:58:01 172.20.0.200 kernel: [  121.800000] br-vxlan100: port 1(vxlan.100) entered forwarding state
2017:03:09-21:20:46 utm awed[61538]: [A400022BAE70DE3] (Re-)loaded identity and/or configuration
2016:12:23-13:58:13 172.20.0.200 aweclient[709]: aweclient.c (2462) Exit from main loop with no error. Get new configuration.
2016:12:23-13:58:14 172.20.0.200 aweclient[709]: Cloudclient not found on ubus.
2016:12:23-13:58:15 172.20.0.200 add_radio_mapping.sh: AP50 detected: Using on-the-fly ACS procedure
2016:12:23-13:58:16 172.20.0.200 netifd: radio1 (1515): Could not find PHY for device 'radio1'
2016:12:23-13:58:16 172.20.0.200 netifd: radio0 (1514): Could not find PHY for device 'radio0'
2016:12:23-13:58:16 172.20.0.200 netifd: radio1 (1540): WARNING: Variable 'data' does not exist or is not an array/object
2016:12:23-13:58:16 172.20.0.200 netifd: radio0 (1546): WARNING: Variable 'data' does not exist or is not an array/object
2017:03:09-21:22:34 utm awed[61538]: [A400022BAE70DE3] ll_read: dead socket: Resource temporarily unavailable
2017:03:09-21:22:34 utm awed[61538]: [A400022BAE70DE3] disconnected. Close socket and kill process.

 

Any ideas?

 

Kind Regards,

Julian

 

 



This thread was automatically locked due to age.
  • 0

    Hi,

    I suspect I know,but need more information.

    You need to setup wireless networks, add your AP to groups etc

    Please provide details of your wifi setup.

    XG115W - v20.0.2 MR-2 - Home

    XG on VM 8 - v21 GA

    If a post solves your question please use the 'Verify Answer' button.

  • 0 in reply to rfcat_vk

    Hi,

    thanks for the answer.

    Here are my Global Settings:

    My Wireless Networks:

    AccessPoint and Group:

     

    Guest Network Interface:

    DHCP-Server:

     

    Need anything further?

    I manually configured it, did not use the creation wizard...

     

    Kind Regards,

    Julian

  • 0 in reply to JulianTekook

    Hi and thank you for replying in detail,

    You said that the AP had been accepted as active but the wireless is not enabled, that doesn't make sense to me.

    How are you power feeding the AP?

    Next silly question how is the AP connected to the UTM, what level of switching is involved?

    XG115W - v20.0.2 MR-2 - Home

    XG on VM 8 - v21 GA

    If a post solves your question please use the 'Verify Answer' button.

  • 0

    Hi Julian,

    I would like to see a picture of the Wireless Network Definitions, make sure you enabled them.

    Restart awed service taking SSH to the UTM and if that doesn't help flash the AP using the KBA here.

    To restart awed service run the following command from shell: /var/mdw/scripts/awed

    Hope that helps.

    Sachin Gurung
    Team Lead | Sophos Technical Support
    Knowledge Base  |  @SophosSupport  |  Video tutorials
    Remember to like a post.  If a post (on a question thread) solves your question use the 'This helped me' link.

  • 0 in reply to rfcat_vk

    Yes the AP has been accepted and is active. But the LED on the AP itself for "2.4GHz" and "5Ghz" are turn off.

    It has it's own power supply.

    The AP is connection through my providers "router". It has 5 Lan Ports. So it's a Layer2-Switch online.

    The AP gets a reserved DHCP Adresse, and my default gateway is the UTM in "Network Server".

     

    I took the AP to our office (where we have multiple AP10 und AP30 running) and put in into the same switch as other APs, and connected it to our Office UTM.

    Same result...

     

    Kind Regards,

    Julian

  • 0 in reply to sachingurung

    Hi,

    I'm currently in the office, I reflashed the AP already, will try again this afternoon and report back.

    My Network Interfaces:

    The WiFi Interface:

     

    I'll report back later when I tried if after the reflash.

     

    Kind Regards,

    Julian

  • 0 in reply to sachingurung

    Hi sachingurung,

     

    I tried to connect the AP to my utm now.

    It took a while, but the LEDs for 2,4GHz and 5GHz were on! For like a minute or so.

    Here is my wireless log.

    Fullscreen wireless.log Download 
    2017:03:10-11:07:43 utm awed[62772]: [MASTER] start processing configuration change
2017:03:10-11:07:44 utm awed[62772]: WARN -------------------------------------------------------
2017:03:10-11:07:44 utm awed[62772]: Use of uninitialized value $sorted_channels[-1] in numeric gt (>) at awed_ng.pl line 1109.
2017:03:10-11:07:44 utm awed[62772]: [MASTER] end processing configuration change
2017:03:10-11:07:52 utm awed[62772]: [MASTER] start processing configuration change
2017:03:10-11:07:52 utm awed[62772]: WARN -------------------------------------------------------
2017:03:10-11:07:52 utm awed[62772]: Use of uninitialized value $sorted_channels[-1] in numeric gt (>) at awed_ng.pl line 1109.
2017:03:10-11:07:52 utm awed[62772]: WARN -------------------------------------------------------
2017:03:10-11:07:52 utm awed[62772]: Use of uninitialized value $sorted_channels[-1] in numeric gt (>) at awed_ng.pl line 1109.
2017:03:10-11:07:52 utm awed[62772]: [MASTER] end processing configuration change
2017:03:10-11:08:22 utm awed[62772]: [MASTER] start processing configuration change
2017:03:10-11:08:22 utm awed[62772]: WARN -------------------------------------------------------
2017:03:10-11:08:22 utm awed[62772]: Use of uninitialized value $sorted_channels[-1] in numeric gt (>) at awed_ng.pl line 1109.
2017:03:10-11:08:22 utm awed[62772]: WARN -------------------------------------------------------
2017:03:10-11:08:22 utm awed[62772]: Use of uninitialized value $sorted_channels[-1] in numeric gt (>) at awed_ng.pl line 1109.
2017:03:10-11:08:22 utm awed[62772]: [MASTER] end processing configuration change
2017:03:10-14:31:44 utm awed[4391]: WARN -------------------------------------------------------
2017:03:10-14:31:44 utm awed[4391]: Use of uninitialized value $sorted_channels[-1] in numeric gt (>) at awed_ng.pl line 1109.
2017:03:10-14:31:44 utm awed[4391]: WARN -------------------------------------------------------
2017:03:10-14:31:44 utm awed[4391]: Use of uninitialized value $sorted_channels[-1] in numeric gt (>) at awed_ng.pl line 1109.
2017:03:10-14:31:44 utm awed[4391]: [MASTER] AP A400022BAE70DE3: Local metadata updated
2017:03:10-14:31:44 utm awed[4391]: [MASTER] AP A400022BAE70DE3: Configuration change detected
2017:03:10-14:31:44 utm awed[4391]: [MASTER] end processing configuration change
2017:03:10-14:31:57 utm awed[4391]: [MASTER] start processing configuration change
2017:03:10-14:31:57 utm awed[4391]: WARN -------------------------------------------------------
2017:03:10-14:31:57 utm awed[4391]: Use of uninitialized value $sorted_channels[-1] in numeric gt (>) at awed_ng.pl line 1109.
2017:03:10-14:31:57 utm awed[4391]: WARN -------------------------------------------------------
2017:03:10-14:31:57 utm awed[4391]: Use of uninitialized value $sorted_channels[-1] in numeric gt (>) at awed_ng.pl line 1109.
2017:03:10-14:31:57 utm awed[4391]: [MASTER] end processing configuration change
2017:03:10-16:25:25 utm awed[4391]: [MASTER] new connection from 172.20.0.200:38582
2017:03:10-16:25:25 utm awed[25654]: [A400022BAE70DE3] AP50 from 172.20.0.200:38582 identified as A400022BAE70DE3
2017:03:10-16:25:25 utm awed[25654]: [A400022BAE70DE3] (Re-)loaded identity and/or configuration
2017:03:10-16:25:25 utm awed[25654]: [A400022BAE70DE3] device sends DEV2ASG_INITIALCONTACT twice, dropping.
2017:03:10-16:30:42 utm awed[4391]: [MASTER] new connection from 172.20.0.200:49648
2017:03:10-16:30:42 utm awed[26394]: [A400022BAE70DE3] AP50 from 172.20.0.200:49648 identified as A400022BAE70DE3
2017:03:10-16:30:42 utm awed[26394]: [A400022BAE70DE3] (Re-)loaded identity and/or configuration
2017:03:10-16:30:42 utm awed[26394]: [A400022BAE70DE3] device sends DEV2ASG_INITIALCONTACT twice, dropping.
2017:03:10-16:40:13 utm awed[4391]: [MASTER] new connection from 172.20.0.200:49696
2017:03:10-16:40:14 utm awed[28116]: [A400022BAE70DE3] AP50 from 172.20.0.200:49696 identified as A400022BAE70DE3
2017:03:10-16:40:14 utm awed[28116]: [A400022BAE70DE3] (Re-)loaded identity and/or configuration
2017:03:10-16:40:14 utm awed[28116]: [A400022BAE70DE3] device sends DEV2ASG_INITIALCONTACT twice, dropping.
2017:03:10-16:41:15 utm awed[4391]: [MASTER] new connection from 172.20.0.200:49696
2017:03:10-16:41:15 utm awed[28234]: [A400022BAE70DE3] AP50 from 172.20.0.200:49696 identified as A400022BAE70DE3
2017:03:10-16:41:15 utm awed[28234]: [A400022BAE70DE3] (Re-)loaded identity and/or configuration
2017:03:10-16:41:15 utm awed[28234]: [A400022BAE70DE3] device sends DEV2ASG_INITIALCONTACT twice, dropping.
2017:03:10-16:42:15 utm awed[4391]: [MASTER] new connection from 172.20.0.200:49648
2017:03:10-16:42:16 utm awed[28357]: [A400022BAE70DE3] AP50 from 172.20.0.200:49648 identified as A400022BAE70DE3
2017:03:10-16:42:16 utm awed[28357]: [A400022BAE70DE3] (Re-)loaded identity and/or configuration
2017:03:10-16:42:16 utm awed[28357]: [A400022BAE70DE3] device sends DEV2ASG_INITIALCONTACT twice, dropping.
2017:03:10-16:43:17 utm awed[4391]: [MASTER] new connection from 172.20.0.200:49648
2017:03:10-16:43:17 utm awed[28486]: [A400022BAE70DE3] AP50 from 172.20.0.200:49648 identified as A400022BAE70DE3
2017:03:10-16:43:17 utm awed[28486]: [A400022BAE70DE3] (Re-)loaded identity and/or configuration
2017:03:10-16:43:17 utm awed[28486]: [A400022BAE70DE3] device sends DEV2ASG_INITIALCONTACT twice, dropping.
2017:03:10-16:44:17 utm awed[4391]: [MASTER] new connection from 172.20.0.200:43253
2017:03:10-16:44:18 utm awed[28611]: [A400022BAE70DE3] AP50 from 172.20.0.200:43253 identified as A400022BAE70DE3
2017:03:10-16:44:18 utm awed[28611]: [A400022BAE70DE3] (Re-)loaded identity and/or configuration
2017:03:10-16:44:18 utm awed[28611]: [A400022BAE70DE3] device sends DEV2ASG_INITIALCONTACT twice, dropping.
2017:03:10-16:45:19 utm awed[4391]: [MASTER] new connection from 172.20.0.200:43253
2017:03:10-16:45:19 utm awed[28794]: [A400022BAE70DE3] AP50 from 172.20.0.200:43253 identified as A400022BAE70DE3
2017:03:10-16:45:19 utm awed[28794]: [A400022BAE70DE3] (Re-)loaded identity and/or configuration
2017:03:10-16:45:19 utm awed[28794]: [A400022BAE70DE3] device sends DEV2ASG_INITIALCONTACT twice, dropping.
2017:03:10-16:46:20 utm awed[4391]: [MASTER] new connection from 172.20.0.200:43253
2017:03:10-16:46:20 utm awed[28917]: [A400022BAE70DE3] AP50 from 172.20.0.200:43253 identified as A400022BAE70DE3
2017:03:10-16:46:20 utm awed[28917]: [A400022BAE70DE3] (Re-)loaded identity and/or configuration
2017:03:10-16:46:20 utm awed[28917]: [A400022BAE70DE3] device sends DEV2ASG_INITIALCONTACT twice, dropping.
2017:03:10-16:47:22 utm awed[4391]: [MASTER] new connection from 172.20.0.200:43253
2017:03:10-16:47:22 utm awed[29405]: [A400022BAE70DE3] AP50 from 172.20.0.200:43253 identified as A400022BAE70DE3
2017:03:10-16:47:22 utm awed[29405]: [A400022BAE70DE3] (Re-)loaded identity and/or configuration
2017:03:10-16:47:22 utm awed[29405]: [A400022BAE70DE3] device sends DEV2ASG_INITIALCONTACT twice, dropping.
2017:03:10-16:52:38 utm awed[4391]: [MASTER] new connection from 172.20.0.200:59847
2017:03:10-16:52:39 utm awed[30258]: [A400022BAE70DE3] AP50 from 172.20.0.200:59847 identified as A400022BAE70DE3
2017:03:10-16:52:39 utm awed[30258]: [A400022BAE70DE3] (Re-)loaded identity and/or configuration
2017:03:10-16:52:39 utm awed[30258]: [A400022BAE70DE3] device sends DEV2ASG_INITIALCONTACT twice, dropping.
2017:03:10-16:55:57 utm awed[4391]: [MASTER] start processing configuration change
2017:03:10-16:55:57 utm awed[4391]: [MASTER] end processing configuration change
2017:03:10-17:02:14 utm awed[4391]: [MASTER] new connection from 172.20.0.200:44201
2017:03:10-17:02:14 utm awed[32189]: WARN -------------------------------------------------------
2017:03:10-17:02:14 utm awed[32189]: Use of uninitialized value in concatenation (.) or string at awed_ng.pl line 347.
2017:03:10-17:02:14 utm awed[32189]: 1 main::awed_aphandler
2017:03:10-17:02:14 utm awed[32189]: 1
2017:03:10-17:02:17 utm awed[4391]: [MASTER] new AP with ID A400022BAE70DE3
2017:03:10-17:02:18 utm awed[4391]: [MASTER] start processing configuration change
2017:03:10-17:02:18 utm awed[4391]: [MASTER] AP A400022BAE70DE3: Local metadata updated
2017:03:10-17:02:18 utm awed[4391]: [MASTER] AP A400022BAE70DE3: Configuration change detected
2017:03:10-17:02:18 utm awed[4391]: [MASTER] end processing configuration change
2017:03:10-17:02:47 utm awed[4391]: [MASTER] new connection from 172.20.0.200:60409
2017:03:10-17:02:47 utm awed[32315]: [A400022BAE70DE3] AP50 from 172.20.0.200:60409 identified as A400022BAE70DE3
2017:03:10-17:02:47 utm awed[32315]: [A400022BAE70DE3] (Re-)loaded identity and/or configuration
2017:03:10-17:02:47 utm awed[32315]: [A400022BAE70DE3] device not authorized yet, dropping.
2017:03:10-17:03:10 utm awed[4391]: [MASTER] start processing configuration change
2017:03:10-17:03:10 utm awed[4391]: [MASTER] AP A400022BAE70DE3: Local metadata updated
2017:03:10-17:03:10 utm awed[4391]: [MASTER] AP A400022BAE70DE3: Configuration change detected
2017:03:10-17:03:10 utm awed[4391]: [MASTER] end processing configuration change
2017:03:10-17:11:10 utm awed[4391]: [MASTER] new connection from 172.20.0.200:59854
2017:03:10-17:11:10 utm awed[33719]: [A400022BAE70DE3] AP50 from 172.20.0.200:59854 identified as A400022BAE70DE3
2017:03:10-17:11:10 utm awed[33719]: [A400022BAE70DE3] (Re-)loaded identity and/or configuration
2017:03:10-17:11:13 utm awed[33719]: [A400022BAE70DE3] sent firmware /etc/wireless/firmware/AP50.uimage to device, releasing connection.
2017:03:10-17:12:57 utm awed[4391]: [MASTER] new connection from 172.20.0.200:37533
2017:03:10-17:12:57 utm awed[33922]: [A400022BAE70DE3] AP50 from 172.20.0.200:37533 identified as A400022BAE70DE3
2017:03:10-17:12:57 utm awed[33922]: [A400022BAE70DE3] (Re-)loaded identity and/or configuration
2016:12:23-13:56:30 172.20.0.200 logread[986]: Logread connected to 172.20.0.250:415
2016:12:23-13:56:31 172.20.0.200 aweclient: Config in flash changed, reboot.
2016:12:23-13:56:31 172.20.0.200 syslog: - shutdown -
2016:12:23-13:56:32 172.20.0.200 syslog: 
2017:03:10-17:13:58 utm awed[33922]: [A400022BAE70DE3] ll_read: dead socket: Resource temporarily unavailable
2017:03:10-17:13:58 utm awed[33922]: [A400022BAE70DE3] disconnected. Close socket and kill process.
2017:03:10-17:14:26 utm awed[4391]: [MASTER] new connection from 172.20.0.200:45840
2017:03:10-17:14:26 utm awed[34123]: [A400022BAE70DE3] AP50 from 172.20.0.200:45840 identified as A400022BAE70DE3
2017:03:10-17:14:26 utm awed[34123]: [A400022BAE70DE3] (Re-)loaded identity and/or configuration
2016:12:23-13:57:14 172.20.0.200 logread[989]: Logread connected to 172.20.0.250:415
2016:12:23-13:57:14 172.20.0.200 add_radio_mapping.sh: AP50 detected: Using on-the-fly ACS procedure
2016:12:23-13:57:15 172.20.0.200 netifd: Interface 'vxlan' is enabled
2016:12:23-13:57:15 172.20.0.200 kernel: [   75.200000] device vxlan.100 entered promiscuous mode
2016:12:23-13:57:15 172.20.0.200 kernel: [   75.200000] device vxlan entered promiscuous mode
2016:12:23-13:57:15 172.20.0.200 kernel: [   75.220000] br-vxlan100: port 1(vxlan.100) entered forwarding state
2016:12:23-13:57:15 172.20.0.200 kernel: [   75.230000] br-vxlan100: port 1(vxlan.100) entered forwarding state
2016:12:23-13:57:15 172.20.0.200 netifd: Interface 'vxlan100' is enabled
2016:12:23-13:57:15 172.20.0.200 netifd: Network device 'vxlan' link is up
2016:12:23-13:57:15 172.20.0.200 netifd: Interface 'vxlan' has link connectivity 
2016:12:23-13:57:15 172.20.0.200 netifd: Interface 'vxlan' is setting up now
2016:12:23-13:57:15 172.20.0.200 netifd: Interface 'vxlan' is now up
2016:12:23-13:57:15 172.20.0.200 netifd: VLAN 'vxlan.100' link is up
2016:12:23-13:57:15 172.20.0.200 netifd: VLAN 'vxlan.100' link is down
2016:12:23-13:57:15 172.20.0.200 netifd: VLAN 'vxlan.100' link is up
2016:12:23-13:57:15 172.20.0.200 netifd: Bridge 'br-vxlan100' link is up
2016:12:23-13:57:15 172.20.0.200 netifd: Interface 'vxlan100' has link connectivity 
2016:12:23-13:57:15 172.20.0.200 netifd: Interface 'vxlan100' is setting up now
2016:12:23-13:57:15 172.20.0.200 netifd: Interface 'vxlan100' is now up
2016:12:23-13:57:16 172.20.0.200 kernel: [   76.590000] device wlan8 entered promiscuous mode
2016:12:23-13:57:16 172.20.0.200 kernel: [   76.590000] br-vxlan100: port 2(wlan8) entered forwarding state
2016:12:23-13:57:16 172.20.0.200 kernel: [   76.600000] br-vxlan100: port 2(wlan8) entered forwarding state
2016:12:23-13:57:16 172.20.0.200 kernel: [   76.690000] device wlan0 entered promiscuous mode
2016:12:23-13:57:16 172.20.0.200 kernel: [   76.690000] br-vxlan100: port 3(wlan0) entered forwarding state
2016:12:23-13:57:16 172.20.0.200 kernel: [   76.700000] br-vxlan100: port 3(wlan0) entered forwarding state
2016:12:23-13:57:16 172.20.0.200 netifd: radio0 (1409): Configuration file: /var/run/hostapd-phy0.conf
2016:12:23-13:57:16 172.20.0.200 netifd: radio0 (1409): eapol_version=1
2016:12:23-13:57:16 172.20.0.200 netifd: radio0 (1409): eapol_version=1
2016:12:23-13:57:16 172.20.0.200 netifd: radio0 (1409): nl80211: TDLS supported
2016:12:23-13:57:16 172.20.0.200 netifd: radio0 (1409): nl80211: TDLS external setup
2016:12:23-13:57:16 172.20.0.200 netifd: radio0 (1409): nl80211: Supported cipher 00-0f-ac:1
2016:12:23-13:57:16 172.20.0.200 netifd: radio0 (1409): nl80211: Supported cipher 00-0f-ac:5
2016:12:23-13:57:16 172.20.0.200 netifd: radio0 (1409): nl80211: Supported cipher 00-0f-ac:2
2016:12:23-13:57:16 172.20.0.200 netifd: radio0 (1409): nl80211: Supported cipher 00-0f-ac:4
2016:12:23-13:57:16 172.20.0.200 netifd: radio0 (1409): nl80211: Supported cipher 00-0f-ac:6
2016:12:23-13:57:16 172.20.0.200 netifd: radio0 (1409): nl80211: Using driver-based off-channel TX
2016:12:23-13:57:16 172.20.0.200 netifd: radio0 (1409): Allowed channel: mode=0 chan=11 freq=2462 MHz max_tx_power=20 dBm
2016:12:23-13:57:16 172.20.0.200 netifd: radio0 (1409): Allowed channel: mode=0 chan=12 freq=2467 MHz max_tx_power=20 dBm
2016:12:23-13:57:16 172.20.0.200 netifd: radio0 (1409): Allowed channel: mode=0 chan=13 freq=2472 MHz max_tx_power=20 dBm
2016:12:23-13:57:16 172.20.0.200 netifd: radio0 (1409): Channel 14 (2484)is disabled!!
2016:12:23-13:57:16 172.20.0.200 netifd: radio0 (1409): ACS: Automatic channel selection started, this may take a bit
2016:12:23-13:57:16 172.20.0.200 netifd: radio0 (1409): ACS: skipping channel 14 (2484)
2016:12:23-13:57:16 172.20.0.200 netifd: radio0 (1409): ACS: Scanning 1 / 5
2016:12:23-13:57:16 172.20.0.200 netifd: radio0 (1409): wlan0: nl80211: scan request
2016:12:23-13:57:16 172.20.0.200 netifd: radio0 (1409): nl80211: Scan frequency 2412 MHz
2016:12:23-13:57:16 172.20.0.200 netifd: radio0 (1409): nl80211: Scan frequency 2417 MHz
2016:12:23-13:57:16 172.20.0.200 netifd: radio0 (1409): nl80211: Scan frequency 2422 MHz
2016:12:23-13:57:16 172.20.0.200 netifd: radio0 (1409): nl80211: Scan frequency 2427 MHz
2016:12:23-13:57:16 172.20.0.200 netifd: radio0 (1409): nl80211: Scan frequency 2432 MHz
2016:12:23-13:57:16 172.20.0.200 netifd: radio0 (1409): nl80211: Scan frequency 2437 MHz
2016:12:23-13:57:16 172.20.0.200 netifd: radio0 (1409): nl80211: Scan frequency 2442 MHz
2016:12:23-13:57:16 172.20.0.200 netifd: radio0 (1409): nl80211: Scan frequency 2447 MHz
2016:12:23-13:57:16 172.20.0.200 netifd: radio0 (1409): nl80211: Scan frequency 2452 MHz
2016:12:23-13:57:17 172.20.0.200 kernel: [   77.190000] br-vxlan100: port 2(wlan8) entered disabled state
2016:12:23-13:57:17 172.20.0.200 kernel: [   77.190000] br-vxlan100: port 3(wlan0) entered disabled state
2016:12:23-13:57:17 172.20.0.200 kernel: [   77.230000] br-vxlan100: port 1(vxlan.100) entered forwarding state
2016:12:23-13:57:17 172.20.0.200 netifd: radio1 (1410): command failed: No such device (-19)
2016:12:23-13:57:17 172.20.0.200 netifd: radio0 (1409): nl80211: Scan frequency command failed: No such device (-19)
2016:12:23-13:57:19 172.20.0.200 kernel: [   79.330000] br-vxlan100: port 2(wlan8) entered forwarding state
2016:12:23-13:57:19 172.20.0.200 kernel: [   79.340000] br-vxlan100: port 2(wlan8) entered forwarding state
2016:12:23-13:57:19 172.20.0.200 netifd: Network device 'wlan8' link is up
2016:12:23-13:57:19 172.20.0.200 kernel: [   79.360000] device wlan9 entered promiscuous mode
2016:12:23-13:57:19 172.20.0.200 kernel: [   79.370000] br-lan: port 2(wlan9) entered forwarding state
2016:12:23-13:57:19 172.20.0.200 kernel: [   79.370000] br-lan: port 2(wlan9) entered forwarding state
2016:12:23-13:57:19 172.20.0.200 netifd: Network device 'wlan9' link is up
2016:12:23-13:57:21 172.20.0.200 kernel: [   81.340000] br-vxlan100: port 2(wlan8) entered forwarding state
2016:12:23-13:57:21 172.20.0.200 kernel: [   81.370000] br-lan: port 2(wlan9) entered forwarding state
2016:12:23-13:57:24 172.20.0.200 kernel: [   84.370000] br-vxlan100: port 3(wlan0) entered forwarding state
2016:12:23-13:57:24 172.20.0.200 kernel: [   84.370000] br-vxlan100: port 3(wlan0) entered forwarding state
2016:12:23-13:57:24 172.20.0.200 netifd: Network device 'wlan0' link is up
2016:12:23-13:57:24 172.20.0.200 kernel: [   84.400000] device wlan1 entered promiscuous mode
2016:12:23-13:57:24 172.20.0.200 kernel: [   84.410000] br-lan: port 3(wlan1) entered forwarding state
2016:12:23-13:57:24 172.20.0.200 kernel: [   84.410000] br-lan: port 3(wlan1) entered forwarding state
2016:12:23-13:57:24 172.20.0.200 netifd: Network device 'wlan1' link is up
2016:12:23-13:57:26 172.20.0.200 kernel: [   86.370000] br-vxlan100: port 3(wlan0) entered forwarding state
2016:12:23-13:57:26 172.20.0.200 kernel: [   86.410000] br-lan: port 3(wlan1) entered forwarding state
2017:03:10-17:14:54 utm awed[4391]: [MASTER] updating confd object for AP A400022BAE70DE3 with new channels ( -> 1,44)
2017:03:10-17:14:54 utm awed[4391]: [MASTER] start processing configuration change
2017:03:10-17:14:54 utm awed[4391]: [MASTER] end processing configuration change
2017:03:10-17:15:54 utm awed[34123]: [A400022BAE70DE3] ll_read: dead socket: Resource temporarily unavailable
2017:03:10-17:15:54 utm awed[34123]: [A400022BAE70DE3] disconnected. Close socket and kill process.
2017:03:10-17:16:01 utm awed[4391]: [MASTER] new connection from 172.20.0.200:44030
2017:03:10-17:16:01 utm awed[34438]: [A400022BAE70DE3] AP50 from 172.20.0.200:44030 identified as A400022BAE70DE3
2017:03:10-17:16:01 utm awed[34438]: [A400022BAE70DE3] (Re-)loaded identity and/or configuration
2016:12:23-13:56:44 172.20.0.200 add_radio_mapping.sh: AP50 detected: Using on-the-fly ACS procedure
2016:12:23-13:56:44 172.20.0.200 netifd: Interface 'vxlan' is enabled
2016:12:23-13:56:44 172.20.0.200 kernel: [   44.950000] device vxlan.100 entered promiscuous mode
2016:12:23-13:56:44 172.20.0.200 kernel: [   44.960000] device vxlan entered promiscuous mode
2016:12:23-13:56:44 172.20.0.200 kernel: [   44.970000] br-vxlan100: port 1(vxlan.100) entered forwarding state
2016:12:23-13:56:45 172.20.0.200 kernel: [   44.980000] br-vxlan100: port 1(vxlan.100) entered forwarding state
2016:12:23-13:56:45 172.20.0.200 netifd: Interface 'vxlan100' is enabled
2016:12:23-13:56:45 172.20.0.200 netifd: Network device 'vxlan' link is up
2016:12:23-13:56:45 172.20.0.200 netifd: Interface 'vxlan' has link connectivity 
2016:12:23-13:56:45 172.20.0.200 netifd: Interface 'vxlan' is setting up now
2016:12:23-13:56:45 172.20.0.200 netifd: Interface 'vxlan' is now up
2016:12:23-13:56:45 172.20.0.200 netifd: VLAN 'vxlan.100' link is up
2016:12:23-13:56:45 172.20.0.200 netifd: VLAN 'vxlan.100' link is down
2016:12:23-13:56:45 172.20.0.200 netifd: VLAN 'vxlan.100' link is up
2016:12:23-13:56:45 172.20.0.200 netifd: Bridge 'br-vxlan100' link is up
2016:12:23-13:56:45 172.20.0.200 netifd: Interface 'vxlan100' has link connectivity 
2016:12:23-13:56:45 172.20.0.200 netifd: Interface 'vxlan100' is setting up now
2016:12:23-13:56:45 172.20.0.200 netifd: Interface 'vxlan100' is now up
2017:03:10-17:16:04 utm awed[4391]: [MASTER] updating confd object for AP A400022BAE70DE3
2016:12:23-13:56:45 172.20.0.200 netifd: radio0 (1286): Could not find PHY for device 'radio0'
2016:12:23-13:56:45 172.20.0.200 netifd: radio1 (1287): Could not find PHY for device 'radio1'
2016:12:23-13:56:46 172.20.0.200 netifd: radio0 (1348): WARNING: Variable 'data' does not exist or is not an array/object
2016:12:23-13:56:46 172.20.0.200 netifd: radio1 (1350): WARNING: Variable 'data' does not exist or is not an array/object
2016:12:23-13:56:46 172.20.0.200 kernel: [   46.980000] br-vxlan100: port 1(vxlan.100) entered forwarding state
2017:03:10-17:16:07 utm awed[4391]: [MASTER] start processing configuration change
2017:03:10-17:16:07 utm awed[4391]: WARN -------------------------------------------------------
2017:03:10-17:16:07 utm awed[4391]: Use of uninitialized value $sorted_channels[-1] in numeric gt (>) at awed_ng.pl line 1109.
2017:03:10-17:16:07 utm awed[4391]: WARN -------------------------------------------------------
2017:03:10-17:16:07 utm awed[4391]: Use of uninitialized value $sorted_channels[-1] in numeric gt (>) at awed_ng.pl line 1109.
2017:03:10-17:16:07 utm awed[4391]: [MASTER] AP A400022BAE70DE3: Local metadata updated
2017:03:10-17:16:07 utm awed[4391]: [MASTER] AP A400022BAE70DE3: Configuration change detected
2017:03:10-17:16:07 utm awed[4391]: [MASTER] end processing configuration change
2017:03:10-17:16:16 utm awed[34438]: [A400022BAE70DE3] (Re-)loaded identity and/or configuration
2016:12:23-13:56:57 172.20.0.200 aweclient[710]: aweclient.c (2462) Exit from main loop with no error. Get new configuration.
2016:12:23-13:56:58 172.20.0.200 aweclient[710]: Cloudclient not found on ubus.
2016:12:23-13:57:00 172.20.0.200 add_radio_mapping.sh: AP50 detected: Using on-the-fly ACS procedure
2016:12:23-13:57:01 172.20.0.200 netifd: radio1 (1622): Could not find PHY for device 'radio1'
2016:12:23-13:57:01 172.20.0.200 netifd: radio0 (1621): Could not find PHY for device 'radio0'
2016:12:23-13:57:01 172.20.0.200 netifd: radio1 (1647): WARNING: Variable 'data' does not exist or is not an array/object
2016:12:23-13:57:01 172.20.0.200 netifd: radio0 (1653): WARNING: Variable 'data' does not exist or is not an array/object

     

    When I accepted the AP, under advanced I could see the 5GHz channel:

    The LEDs were online right after it got stated as active.

    Soon after in the Log I found: 

    2016:12:23-13:57:17 172.20.0.200 netifd: radio1 (1410): command failed: No such device (-19)
    2016:12:23-13:57:17 172.20.0.200 netifd: radio0 (1409): nl80211: Scan frequency command failed: No such device (-19)
     
    And I think it restarted afterwards:
    2017:03:10-17:14:54 utm awed[4391]: [MASTER] end processing configuration change
    2017:03:10-17:15:54 utm awed[34123]: [A400022BAE70DE3] ll_read: dead socket: Resource temporarily unavailable
    2017:03:10-17:15:54 utm awed[34123]: [A400022BAE70DE3] disconnected. Close socket and kill process.
    2017:03:10-17:16:01 utm awed[4391]: [MASTER] new connection from 172.20.0.200:44030
    2017:03:10-17:16:01 utm awed[34438]: [A400022BAE70DE3] AP50 from 172.20.0.200:44030 identified as A400022BAE70DE3
     
     
    AFter that the LEDs were off again, and now in the WebAdmin I cannot see any 5GHz Configs...
    Log States:
    2016:12:23-13:56:45 172.20.0.200 netifd: radio0 (1286): Could not find PHY for device 'radio0'
    2016:12:23-13:56:45 172.20.0.200 netifd: radio1 (1287): Could not find PHY for device 'radio1'
    2016:12:23-13:56:46 172.20.0.200 netifd: radio0 (1348): WARNING: Variable 'data' does not exist or is not an array/object
    2016:12:23-13:56:46 172.20.0.200 netifd: radio1 (1350): WARNING: Variable 'data' does not exist or is not an array/object
     
     
    Could this be a firmware problem?
     
     
    I restarted AWED but the problem still persists..
     
    My UTM is running on the newest version: 9.411-3
     
    Kind Regards,
    Julian
     
     
     

     

  • 0 in reply to JulianTekook

    Hi,

     

    I tried reflashing it again, no chance.

    Anyone with an AP50 on the latest Version of UTM?

     

    The WiFi seems to be working up until the frequency are scanned.

    After that, the whole AP does not do wifi anymore..

    2016:12:23-13:57:16 172.20.0.200 netifd: radio0 (1409): nl80211: Scan frequency 2442 MHz
    2016:12:23-13:57:16 172.20.0.200 netifd: radio0 (1409): nl80211: Scan frequency 2447 MHz
    2016:12:23-13:57:16 172.20.0.200 netifd: radio0 (1409): nl80211: Scan frequency 2452 MHz
    2016:12:23-13:57:17 172.20.0.200 kernel: [ 77.190000] br-vxlan100: port 2(wlan8) entered disabled state
    2016:12:23-13:57:17 172.20.0.200 kernel: [ 77.190000] br-vxlan100: port 3(wlan0) entered disabled state
    2016:12:23-13:57:17 172.20.0.200 kernel: [ 77.230000] br-vxlan100: port 1(vxlan.100) entered forwarding state
    2016:12:23-13:57:17 172.20.0.200 netifd: radio1 (1410): command failed: No such device (-19)

     

    Kinda lost..

     

    Kind Regards,

    Julian

  • 0 in reply to JulianTekook
    Hi Julian, Raise a RMA request with the support to get it replaced. Thanks

    Sachin Gurung
    Team Lead | Sophos Technical Support
    Knowledge Base  |  @SophosSupport  |  Video tutorials
    Remember to like a post.  If a post (on a question thread) solves your question use the 'This helped me' link.

Unfiltered HTML