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

Issues getting AP15C to "work"

Hi

Just received a "second hand" AP15C for use on Home UTM. This is new territory for me.

The AP15C is wired into a standard AP point connected to the UTM LAN.

Did the following :

Created a new network interface type “Ethernet” with new IP address/netmask for the "Seperate Zone"
Enabled DHCP.
Enabled DNS.
Create a NAT rule to mask the wireless network to WAN.
Created a basic packet filter rules to allow traffic from and to the wireless network.

I am able to get the AP15C to become an "Active Access Point" - but it is not broadcasting the SSID.

I'm seeing the following in the log but have no clue if or what they could be...

2021:03:12-10:59:59 A4004ECA1C61124 add_radio_mapping.sh: AP15C detected: Using on-the-fly ACS procedure
2021:03:12-11:00:00 A4004ECA1C61124 astaro-cfg.sh: Configuration is not valid in UCI, retrying...
 
Cheers
Craig

This is the Log from a reboot to final state:

2021:03:12-10:59:35 A4004ECA1C61124 logread[952]: Logread connected to 192.168.12.1:415
2021:03:12-10:59:35 A4004ECA1C61124 kernel: [ 21.190000] br-lan: port 1(eth0) entered forwarding state
2020:09:07-00:41:45 box awed[7840]: [MASTER] new connection from 192.168.12.16:58705
2020:09:07-00:41:45 box awed[10046]: [A4004ECA1C61124] AP15C from 192.168.12.16:58705 identified as A4004ECA1C61124
2020:09:07-00:41:45 box awed[10046]: [A4004ECA1C61124] (Re-)loaded identity and/or configuration
2021:03:12-10:59:48 A4004ECA1C61124 aweclient[874]: Cloudclient not found on ubus.
2021:03:12-10:59:50 A4004ECA1C61124 kernel: [ 35.790000] cfg80211: Calling CRDA for country: NZ
2021:03:12-10:59:50 A4004ECA1C61124 kernel: [ 35.790000] cfg80211: Regulatory domain changed to country: NZ
2021:03:12-10:59:50 A4004ECA1C61124 kernel: [ 35.800000] cfg80211: DFS Master region: ETSI
2021:03:12-10:59:50 A4004ECA1C61124 kernel: [ 35.800000] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
2021:03:12-10:59:50 A4004ECA1C61124 kernel: [ 35.810000] cfg80211: (2402000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 3000 mBm), (N/A)
2021:03:12-10:59:50 A4004ECA1C61124 kernel: [ 35.820000] cfg80211: (5170000 KHz - 5250000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 1700 mBm), (N/A)
2021:03:12-10:59:50 A4004ECA1C61124 kernel: [ 35.830000] cfg80211: (5250000 KHz - 5330000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2400 mBm), (0 s)
2021:03:12-10:59:50 A4004ECA1C61124 kernel: [ 35.840000] cfg80211: (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, 2400 mBm), (0 s)
2021:03:12-10:59:50 A4004ECA1C61124 kernel: [ 35.850000] cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 3000 mBm), (N/A)
2021:03:12-10:59:50 A4004ECA1C61124 kernel: [ 36.160000] device vxlan.101 entered promiscuous mode
2021:03:12-10:59:50 A4004ECA1C61124 kernel: [ 36.160000] device vxlan entered promiscuous mode
2021:03:12-10:59:50 A4004ECA1C61124 kernel: [ 36.190000] br-vxlan101: port 1(vxlan.101) entered forwarding state
2021:03:12-10:59:50 A4004ECA1C61124 kernel: [ 36.200000] br-vxlan101: port 1(vxlan.101) entered forwarding state
2021:03:12-10:59:50 A4004ECA1C61124 add_radio_mapping.sh: AP15C detected: Using on-the-fly ACS procedure
2021:03:12-10:59:50 A4004ECA1C61124 netifd: Interface 'vxlan' is enabled
2021:03:12-10:59:50 A4004ECA1C61124 netifd: Network device 'vxlan' link is up
2021:03:12-10:59:50 A4004ECA1C61124 netifd: Interface 'vxlan' has link connectivity
2021:03:12-10:59:50 A4004ECA1C61124 netifd: Interface 'vxlan' is setting up now
2021:03:12-10:59:50 A4004ECA1C61124 netifd: Interface 'vxlan' is now up
2021:03:12-10:59:50 A4004ECA1C61124 netifd: VLAN 'vxlan.101' link is up
2021:03:12-10:59:50 A4004ECA1C61124 netifd: Interface 'vxlan101' is enabled
2021:03:12-10:59:50 A4004ECA1C61124 netifd: Bridge 'br-vxlan101' link is up
2021:03:12-10:59:50 A4004ECA1C61124 netifd: Interface 'vxlan101' has link connectivity
2021:03:12-10:59:50 A4004ECA1C61124 netifd: Interface 'vxlan101' is setting up now
2020:09:07-00:41:48 box awed[8407]: [A4004ECA1C61124] ll_read: dead socket: Interrupted system call
2020:09:07-00:41:48 box awed[8407]: [A4004ECA1C61124] disconnected. Close socket and kill process.
2021:03:12-10:59:52 A4004ECA1C61124 astaro-cfg.sh: Configuration is not valid in UCI, retrying...
2021:03:12-10:59:52 A4004ECA1C61124 kernel: [ 38.200000] br-vxlan101: port 1(vxlan.101) entered forwarding state
2021:03:12-10:59:53 A4004ECA1C61124 add_radio_mapping.sh: AP15C detected: Using on-the-fly ACS procedure
2021:03:12-10:59:55 A4004ECA1C61124 astaro-cfg.sh: Configuration is not valid in UCI, retrying...
2021:03:12-10:59:56 A4004ECA1C61124 add_radio_mapping.sh: AP15C detected: Using on-the-fly ACS procedure
2021:03:12-10:59:57 A4004ECA1C61124 astaro-cfg.sh: Configuration is not valid in UCI, retrying...
2021:03:12-10:59:59 A4004ECA1C61124 add_radio_mapping.sh: AP15C detected: Using on-the-fly ACS procedure
2021:03:12-11:00:00 A4004ECA1C61124 astaro-cfg.sh: Configuration is not valid in UCI, retrying...
2021:03:12-11:00:00 A4004ECA1C61124 astaro-cfg.sh: Maximum retry of astaro-cfg reached, exiting...
2021:03:12-11:00:00 A4004ECA1C61124 aweclient[874]: aweclient.c (1883) A signal received during select.
2020:09:07-00:42:30 A4004ECA1C61124 kernel: [ 80.400000] random: nonblocking pool is initialized


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

     

    which firmware version are you running for your UTM? 

    Did you select the specific ssid / wlan inner your AP configuration?

    How long did you wait after the AP was connected / powered on? Sometimes it needs "long" time to wait until it becomes really active state.

     

    Regards, Andy.

Reply
  • Hello,

     

    which firmware version are you running for your UTM? 

    Did you select the specific ssid / wlan inner your AP configuration?

    How long did you wait after the AP was connected / powered on? Sometimes it needs "long" time to wait until it becomes really active state.

     

    Regards, Andy.

Children
No Data