OK, I think I understand. The app is for any directly connected wireless NIC, so PCI or USB, as long as the drivers exist and as long as the NIC supports AP mode. There are a couple of good links about NICs and drivers here and here.

When I last looked, the app still needed manual configuration of the hostapd file.

To be honest a directly connected wireless NIC is possibly not the best configuration as the file server location is often not in the best place for general wireless coverage of your location. An ethernet-connected WAP is more flexible but has the disadvantage of needing cabling back to the server.

Nick Howitt wrote:

This is to run ClearOS as an AP, so on the LAN, and not to connect the ClearOS WAN by WiFi to an external AP.

My ap is on the lan. Its for the home ssid. It currently get its IP from clearos, then create 2.4 and 5 network.

I was just asking if its for a kind of wireless nic connected straight to clearos box through PCI or USB.

This is to run ClearOS as an AP, so on the LAN, and not to connect the ClearOS WAN by WiFi to an external AP.

This is for directly connected wireless interface ? I do have a Cisco AIR-CAP2602I AP at home... Can i do something with this app ?

I've been struggling to help a poster in this thread and in the end had to stick my antique USB NIC into the server I'm setting up and I've hit a few bugs. They appear to be similar to what the poster was seeing.

I'd like to add I don't have a full understanding of the hostapd.conf file so I am not 100% confident of the required configurations.

Working with Qualcomm Atheros AR9287 PCIe Half Mini 802.11 bgn and ClearOS 3.10.0-327.22.2 v7.x86_64.

Lots of joy if and when WPA2-PSK, Bridging and DHCP are working. Maybe in time, as you mentioned.


Thanks!

Yeah, bridge mode isn't working just yet unless you do manual things as you have. I'm working on that as well but will need some time.

Currently, using the UI only, you can set it up as its own network interface and gateway:

Hi Dave - a few early comments.
Using a Wireless PCI card based on the Qualcomm Atheros AR9227 PCI Wireless Adaptor.
ClearOS 7.2 Kernel 3.10.0-327.10.1.v7.x86_64

Initially was plagued with the following errors after initial install and using webconfig to setup wireless...

....

Jun  2 18:10:31 sandra hostapd: wlp0s12: AP-ENABLED

Jun  2 18:11:01 sandra hostapd: wlp0s12: STA 88:32:9b:25:55:e7 IEEE 802.11: authenticated

Jun  2 18:11:01 sandra hostapd: wlp0s12: STA 88:32:9b:25:55:e7 IEEE 802.11: associated (aid 1)

Jun  2 18:11:10 sandra hostapd: wlp0s12: STA 88:32:9b:25:55:e7 IEEE 802.11: deauthenticated due to local deauth request

Jun  2 18:11:22 sandra hostapd: wlp0s12: STA 88:32:9b:25:55:e7 IEEE 802.11: authenticated

Jun  2 18:11:22 sandra hostapd: wlp0s12: STA 88:32:9b:25:55:e7 IEEE 802.11: associated (aid 1)

Jun  2 18:11:31 sandra hostapd: wlp0s12: STA 88:32:9b:25:55:e7 IEEE 802.11: deauthenticated due to local deauth request

Jun  2 18:11:50 sandra hostapd: wlp0s12: STA 88:32:9b:25:55:e7 IEEE 802.11: authenticated

Jun  2 18:11:50 sandra hostapd: wlp0s12: STA 88:32:9b:25:55:e7 IEEE 802.11: associated (aid 1)

Jun  2 18:11:59 sandra hostapd: wlp0s12: STA 88:32:9b:25:55:e7 IEEE 802.11: deauthenticated due to local deauth request

...

[/code

and thousands of these

[code]

...

Jun  2 18:18:42 sandra kernel: ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040

Jun  2 18:18:42 sandra kernel: ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up

Jun  2 18:18:42 sandra kernel: ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040

Jun  2 18:18:42 sandra kernel: ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up

Jun  2 18:18:42 sandra kernel: ath: phy0: Failed to stop TX DMA, queues=0x100!

Jun  2 18:18:42 sandra kernel: ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040

Jun  2 18:18:42 sandra kernel: ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up

Jun  2 18:18:43 sandra kernel: ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040

Jun  2 18:18:43 sandra kernel: ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up

Jun  2 18:18:43 sandra kernel: ath: phy0: Failed to stop TX DMA, queues=0x100!

Jun  2 18:18:43 sandra kernel: ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040

Jun  2 18:18:43 sandra kernel: ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up

Jun  2 18:18:43 sandra kernel: ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040

Jun  2 18:18:43 sandra kernel: ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up

Jun  2 18:18:44 sandra kernel: ath: phy0: Failed to stop TX DMA, queues=0x100!

Jun  2 18:18:44 sandra kernel: ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040

Jun  2 18:18:44 sandra kernel: ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up

Jun  2 18:18:44 sandra kernel: ath: phy0: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040

Jun  2 18:18:44 sandra kernel: ath: phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up

Jun  2 18:18:44 sandra kernel: ath: phy0: Failed to stop TX DMA, queues=0x100!

...

So started looking at the config files... See that it was not setup to use a bridge - why is this? (#bridge=br0)
Abandoned the webconfig wireless app and setup like this manually after making sure the bridge-utils rpm was installed...

[root@sandra ~]# cat /etc/hostapd/hostapd.conf

#

# For more information, look here:

#

#	http://wireless.kernel.org/en/users/Documentation/hostapd

#



ctrl_interface=/var/run/hostapd

ctrl_interface_group=wheel



# General settings

bridge=br0

interface=wlp0s12

driver=nl80211

hw_mode=g

channel=4

auth_algs=1

ssid=guest

macaddr_acl=0

ignore_broadcast_ssid=0

ieee8021x=0

country_code=AU



wmm_enabled=1

ht_capab=[SHORT-GI-20][TX-STCB][RX-STBC1]

ap_max_inactivity=1800

skip_inactivity_poll=1



# logging

logger_syslog=-1

logger_syslog_level=2

logger_stdout=-1

logger_stdout_level=2

debug=0



# WPA

wpa=3

wpa_key_mgmt=WPA-PSK

wpa_passphrase=xxxxxxxxxxxxxxxxxxxxx

wpa_pairwise=TKIP

rsn_pairwise=CCMP

wpa_group_rekey=300

wpa_gmk_rekey=640

[root@sandra ~]# cat /etc/sysconfig/network-scripts/ifcfg-br0 

DEVICE="br0"

BOOTPROTO="dhcp"

NM_CONTROLLED="no"

ONBOOT="yes"

TYPE="Bridge"

[root@sandra ~]# cat /etc/sysconfig/network-scripts/ifcfg-enp0s10

DEVICE=enp0s10

TYPE="Ethernet"

ONBOOT="yes"

USERCTL="no"

BOOTPROTO="static"

IPADDR="192.168.1.38"

NETMASK="255.255.255.0"

GATEWAY="192.168.1.26"

BRIDGE=br0

So far rock solid with a Samsung Note 2 phone and laptop connected by WiFi, and each receiving an address. The laptop is accessed using remote desktop and web browsing on the phone have so far, touch wood, not triggered the initial failures. Just get a steady stream like this at five minute intervals...

...

Jun  2 19:34:18 sandra hostapd: wlp0s12: STA 70:77:81:31:96:ad WPA: group key handshake completed (RSN)

Jun  2 19:34:18 sandra hostapd: wlp0s12: STA 88:32:9b:25:55:e7 WPA: group key handshake completed (RSN)

Jun  2 19:39:18 sandra hostapd: wlp0s12: STA 70:77:81:31:96:ad WPA: group key handshake completed (RSN)

Jun  2 19:39:18 sandra hostapd: wlp0s12: STA 88:32:9b:25:55:e7 WPA: group key handshake completed (RSN)

Jun  2 19:44:18 sandra hostapd: wlp0s12: STA 70:77:81:31:96:ad WPA: group key handshake completed (RSN)

Jun  2 19:44:18 sandra hostapd: wlp0s12: STA 88:32:9b:25:55:e7 WPA: group key handshake completed (RSN)

Jun  2 19:49:18 sandra hostapd: wlp0s12: STA 70:77:81:31:96:ad WPA: group key handshake completed (RSN)

Jun  2 19:49:18 sandra hostapd: wlp0s12: STA 88:32:9b:25:55:e7 WPA: group key handshake completed (RSN)

Jun  2 19:54:18 sandra hostapd: wlp0s12: STA 70:77:81:31:96:ad WPA: group key handshake completed (RSN)

Jun  2 19:54:18 sandra hostapd: wlp0s12: STA 88:32:9b:25:55:e7 WPA: group key handshake completed (RSN)

...

UPDATE:
Hmm - the bandages didn't completely stop the bleeding. Finally broke out into
"DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x42000020 DMADBG_7=0x00006040
phy0: Could not stop RX, we could be confusing the DMA engine when we start RX up"
messages again - so will abandon this PCI card - it worked flawless as a wireless client

Another card is sitting here based on the RT2560F wireless chipset - will give that a whirl tomorrow if time permits...