UPD. Found the Plex web interface and successfully configured it)

I applied chmod -R 777 to the folder with movies (actually I did it in order to get Transmission access to this folder). How I can check what plex does actually see? The webconfig section has nothing related to this.

I closed those ports dedicated to my local pc and did port forwarding instead (with help of the 1-to-1 NAT app). Canyouseeme.org informs that the corresponding port is open, the uTorrent indicator is green, however whenever I run test it fails. I think it is a problem of uTorrent since Deluge works fine.

By the way why did you choose ClearOS as a server OS and what distribution do you have on your pc? I'm considering to move to Linux completely and now wondering which distribution to choose.

I've little idea about plex, but I know permissions can be a problem. Mine are all owned by root:allusers and have permissions of 777. Does plex see the disk, but not the files on it, or does it not even see the disk?

If a port is being mapped by miniupnpd you should see it in the UPNP chain of the firewall. Also in the firewall there is a big difference between the INPUT chain and the FORWARD chain. The INPUT chain is for traffic from the internet (or LAN) destined for the ClearOS box while the FORWARD chain is for traffic from the internet (or LAN) destined for somewhere the other side of your ClearOS box. I noticed that you have opened the incoming ports, which is incorrect. They should have been forwarded to to PC instead.

UPD2. The corresponding port on my Mac is open Although I didn't configure it in the router, so I believe it is utilizing the miniupnpd service.

UPD. This port is allowed by the firewall

The last few remarks.

1) Plex doesn't see my external hdd. Here is the "ls -la" output:

[root@gateway ~]# ls -la /mnt/udata/

total 20

drwxrwxr-x   5 flexshares allusers 4096 Dec 27 22:29 .

drwxr-xr-x.  3 root       root     4096 Dec 27 22:19 ..

drwxrwxrwx   7 myksok     allusers 4096 Dec 26 20:11 backup

drwxrwxrwx   2         48 allusers 4096 Sep 10 23:24 ftp

drwxrwxrwx  12 myksok     allusers 4096 Dec 31 08:45 p2p

All movies are in p2p folder. The user is transimssion or 300 (?), group is always "allusers"

2) uTorrent on my local machine is experiencing problem with port forwarding. I installed 1to1 NAT app and mapped my external IP address to the local one. Since it didn't help I installed miniupnpd in order to employ UPnP port forwarding. Unfortunately it didn't work as well. Here is the output of "iptables -L -n -v":

[root@gateway ~]# iptables -L -n -v

Chain INPUT (policy DROP 841 packets, 73425 bytes)

 pkts bytes target     prot opt in     out     source               destination

  669  181K DROP       all  --  *      *       0.0.0.0/0            0.0.0.0/0            state INVALID

    0     0 REJECT     tcp  --  *      *       0.0.0.0/0            0.0.0.0/0            tcp flags:0x12/0x12 state NEW r

eject-with tcp-reset

   26  1774 DROP       tcp  --  *      *       0.0.0.0/0            0.0.0.0/0            tcp flags:!0x17/0x02 state NEW

    0     0 DROP       all  --  enp3s0 *       127.0.0.0/8          0.0.0.0/0

    0     0 DROP       all  --  enp3s0 *       169.254.0.0/16       0.0.0.0/0

 3355  844K ACCEPT     all  --  lo     *       0.0.0.0/0            0.0.0.0/0

    0     0 ACCEPT     all  --  pptp+  *       0.0.0.0/0            0.0.0.0/0

    0     0 ACCEPT     all  --  tun+   *       0.0.0.0/0            0.0.0.0/0

 9648 2073K ACCEPT     all  --  enp4s0 *       0.0.0.0/0            0.0.0.0/0

  534 27741 ACCEPT     all  --  wlp2s0 *       0.0.0.0/0            0.0.0.0/0

   21   609 ACCEPT     icmp --  enp3s0 *       0.0.0.0/0            0.0.0.0/0            icmptype 0

  183 19111 ACCEPT     icmp --  enp3s0 *       0.0.0.0/0            0.0.0.0/0            icmptype 3

    9   612 ACCEPT     icmp --  enp3s0 *       0.0.0.0/0            0.0.0.0/0            icmptype 8

    5   377 ACCEPT     icmp --  enp3s0 *       0.0.0.0/0            0.0.0.0/0            icmptype 11

  194 71057 ACCEPT     udp  --  enp3s0 *       0.0.0.0/0            0.0.0.0/0            udp spt:67 dpt:68

    0     0 ACCEPT     tcp  --  enp3s0 *       0.0.0.0/0            0.0.0.0/0            tcp spt:67 dpt:68

2230K 4422M ACCEPT     tcp  --  *      *       0.0.0.0/0            x.x.x.x        tcp dpt:33709

1673K 2380M ACCEPT     udp  --  *      *       0.0.0.0/0            x.x.x.x        udp dpt:33709

    0     0 ACCEPT     udp  --  *      *       0.0.0.0/0            x.x.x.x        udp dpt:1194

    0     0 ACCEPT     tcp  --  *      *       0.0.0.0/0            x.x.x.x        tcp dpt:29144

   36  1828 ACCEPT     udp  --  *      *       0.0.0.0/0            x.x.x.x        udp dpt:29144

    0     0 ACCEPT     tcp  --  *      *       0.0.0.0/0            x.x.x.x        tcp dpt:81

  543  165K ACCEPT     udp  --  enp3s0 *       0.0.0.0/0            0.0.0.0/0            udp dpts:1024:65535 state RELAT

ED,ESTABLISHED

1614K 3247M ACCEPT     tcp  --  enp3s0 *       0.0.0.0/0            0.0.0.0/0            tcp dpts:1024:65535 state RELAT

ED,ESTABLISHED



Chain FORWARD (policy DROP 4 packets, 366 bytes)

 pkts bytes target     prot opt in     out     source               destination

    0     0 ACCEPT     icmp --  enp3s0 *       0.0.0.0/0            192.168.10.26        icmptype 0

 1105  113K ACCEPT     icmp --  enp3s0 *       0.0.0.0/0            192.168.10.26        icmptype 3

    0     0 ACCEPT     icmp --  enp3s0 *       0.0.0.0/0            192.168.10.26        icmptype 8

   44  3285 ACCEPT     icmp --  enp3s0 *       0.0.0.0/0            192.168.10.26        icmptype 11

    0     0 DROP       icmp --  enp3s0 *       0.0.0.0/0            192.168.10.26

47331 8032K ACCEPT     tcp  --  enp3s0 *       0.0.0.0/0            192.168.10.26        tcp dpt:29144

58359 7727K ACCEPT     udp  --  enp3s0 *       0.0.0.0/0            192.168.10.26        udp dpt:29144

24797   25M MINIUPNPD  all  --  enp3s0 !enp3s0  0.0.0.0/0            0.0.0.0/0

 130K   86M ACCEPT     all  --  *      *       0.0.0.0/0            0.0.0.0/0            state RELATED,ESTABLISHED

16434 1337K ACCEPT     all  --  enp4s0 *       0.0.0.0/0            0.0.0.0/0

  431 22394 ACCEPT     all  --  wlp2s0 *       0.0.0.0/0            0.0.0.0/0

    0     0 ACCEPT     all  --  pptp+  *       0.0.0.0/0            0.0.0.0/0

    0     0 ACCEPT     all  --  tun+   *       0.0.0.0/0            0.0.0.0/0



Chain OUTPUT (policy DROP 0 packets, 0 bytes)

 pkts bytes target     prot opt in     out     source               destination

 3372  845K ACCEPT     all  --  *      lo      0.0.0.0/0            0.0.0.0/0

    0     0 ACCEPT     all  --  *      pptp+   0.0.0.0/0            0.0.0.0/0

    0     0 ACCEPT     all  --  *      tun+    0.0.0.0/0            0.0.0.0/0

 6429 1408K ACCEPT     all  --  *      enp4s0  0.0.0.0/0            0.0.0.0/0

  587 47663 ACCEPT     all  --  *      wlp2s0  0.0.0.0/0            0.0.0.0/0

  275 74367 ACCEPT     icmp --  *      enp3s0  0.0.0.0/0            0.0.0.0/0

    0     0 ACCEPT     udp  --  *      enp3s0  0.0.0.0/0            0.0.0.0/0            udp spt:68 dpt:67

    0     0 ACCEPT     tcp  --  *      enp3s0  0.0.0.0/0            0.0.0.0/0            tcp spt:68 dpt:67

1153K  102M ACCEPT     tcp  --  *      enp3s0  x.x.x.x        0.0.0.0/0            tcp spt:33709

 817K   58M ACCEPT     udp  --  *      enp3s0  x.x.x.x       0.0.0.0/0            udp spt:33709

    0     0 ACCEPT     udp  --  *      enp3s0  x.x.x.x        0.0.0.0/0            udp spt:1194

    0     0 ACCEPT     tcp  --  *      enp3s0  x.x.x.x        0.0.0.0/0            tcp spt:29144

    0     0 ACCEPT     udp  --  *      enp3s0  x.x.x.x        0.0.0.0/0            udp spt:29144

    0     0 ACCEPT     tcp  --  *      enp3s0  x.x.x.x        0.0.0.0/0            tcp spt:81

 843K   59M ACCEPT     all  --  *      enp3s0  0.0.0.0/0            0.0.0.0/0



Chain DROP-lan (0 references)

 pkts bytes target     prot opt in     out     source               destination

    0     0 DROP       all  --  *      *       0.0.0.0/0            0.0.0.0/0



Chain MINIUPNPD (1 references)

 pkts bytes target     prot opt in     out     source               destination

and "iptables -t nat -L -n -v"

[root@gateway ~]# iptables -t nat -L -n -v

Chain PREROUTING (policy ACCEPT 14926 packets, 1621K bytes)

 pkts bytes target     prot opt in     out     source               destination

 3214  203K DNAT       tcp  --  *      *       0.0.0.0/0            x.x.x.x        tcp dpt:29144to:192.168.10.26

 3848  342K DNAT       udp  --  *      *       0.0.0.0/0            x.x.x.x        udp dpt:29144to:192.168.10.26

  974 76139 MINIUPNPD  all  --  enp3s0 *       0.0.0.0/0            0.0.0.0/0



Chain INPUT (policy ACCEPT 2567 packets, 437K bytes)

 pkts bytes target     prot opt in     out     source               destination



Chain OUTPUT (policy ACCEPT 3235 packets, 280K bytes)

 pkts bytes target     prot opt in     out     source               destination



Chain POSTROUTING (policy ACCEPT 7413 packets, 618K bytes)

 pkts bytes target     prot opt in     out     source               destination

    0     0 ACCEPT     all  --  *      tun+    0.0.0.0/0            0.0.0.0/0

11385 1057K SNAT       all  --  *      *       192.168.10.26        0.0.0.0/0            to:x.x.x.x

    0     0 SNAT       tcp  --  *      *       192.168.10.0/25      192.168.10.26        tcp dpt:29144to:192.168.10.1

    0     0 SNAT       tcp  --  *      *       192.168.20.0/26      192.168.10.26        tcp dpt:29144to:192.168.20.1

    0     0 SNAT       udp  --  *      *       192.168.10.0/25      192.168.10.26        udp dpt:29144to:192.168.10.1

    0     0 SNAT       udp  --  *      *       192.168.20.0/26      192.168.10.26        udp dpt:29144to:192.168.20.1

 2888  207K MASQUERADE  all  --  *      enp3s0  0.0.0.0/0            0.0.0.0/0



Chain MINIUPNPD (1 references)

 pkts bytes target     prot opt in     out     source               destination

Here I replaced my real WAN IP by "x.x.x.x". My local PC has an IP 192.168.10.26 and port we are looking for is 29144

I'm afraid I can't recommend any books or courses. I'm entirely self-taught, firstly from following this forum where I started about 11 years ago in the old ClarkConnect days. The internet has also been my friend where there is a fantastic amount of information available. If I've wanted to do something I've just researched it, often building on other peoples ideas. Just about the only manual I've printed is the bash manual when I wanted to learn how to script something. My programming is also self-taught so has no style and is hopelessly badly documented.

After another firmware crash (could not fetch firmware file..) I replaced the Compex card by my old well tested Intel 7260. Nevertheless, during testing I couldn't get it working in bridge mode with the second LAN. I'm thinking that it might be new system updates that I had to install during setting up the OS. Since my PC and TV connected by wire it is not crucial (I've never accessed any of my PCs from a mobile device, there was no need). What is crucial that this time OpenVPN works perfectly out-of-the-box!

And the last and the most important conclusion out of my efforts to build my own x86 router is that I need to learn Linux. It is really great and powerful OS. It is off topic here but, nevertheless, if you Nick (or any bode else who is following this post) have any suggestion about books and online courses (by the way there is one in edX prepared by the Linux Foundation) they are much welcomed.

Mikhail Sokolovskyy wrote:

That is exactly what I've been doing all the time. I'm enabling this repo only when installing app-wireless.
Tried to create manually all necessary files for wireless: hostapd.conf and ifcfg-wlan. Still there is information missing in the IP settings section (wireless field) It seems that the system cannot read properly hostapd.conf file or some module is missing

Those dependencies are not pulled in when I install app-wireless. I wonder if you have to complete your installation first, installing packages like Windows Networking and choosing your Directory Server before you try to install app-wireless so it does not bring in more than necessary from clearos-updates-testing. The only packages I get are app-wireless, app-wireless-core, hostapd, app-events and app-events-core.

No idea why the webconfig is not loading fully.

Here is a screenshot

That is exactly what I've been doing all the time. I'm enabling this repo only when installing app-wireless.
Tried to create manually all necessary files for wireless: hostapd.conf and ifcfg-wlan. Still there is information missing in the IP settings section (wireless field) It seems that the system cannot read properly hostapd.conf file or some module is missing

The --enablerepo= bit should only be done to install app-wireless which is what that command does. Don't permanently enable app-wireless and don't use it with every yum command.

Very simple. I've been using this recipe since the beginning. As I understand there is no official support for wireless by default.

How do you have clearos-updates-testing enabled. It is better not to. Also, from experience, try not to use --ship-broken. It can leave you in limbo-land.

Nope, it didn't help, unfortunately. So I decided to reinstall my old Intel 7260 NIC. Because some network problem, I did a fresh install of the OS. Now got stuck in the wireless app instalation. Here is the error:

Error: Package: samba-libs-4.4.4-9.v7.1.x86_64 (clearos-updates-testing)

           Requires: libpytalloc-util.so.2(PYTALLOC_UTIL_2.1.6)(64bit)

Error: Package: samba-libs-4.4.4-9.v7.1.x86_64 (clearos-updates-testing)

           Requires: krb5-libs >= 1.14

           Installed: krb5-libs-1.13.2-12.el7_2.x86_64 (@clearos-centos-updates)

               krb5-libs = 1.13.2-12.el7_2

           Available: krb5-libs-1.13.2-10.el7.i686 (clearos-centos)

               krb5-libs = 1.13.2-10.el7

Error: Package: samba-python-4.4.4-9.v7.1.x86_64 (clearos-updates-testing)

           Requires: libpytalloc-util.so.2(PYTALLOC_UTIL_2.1.6)(64bit)

 You could try using --skip-broken to work around the problem

 You could try running: rpm -Va --nofiles --nodigest

Have tried using "--skip-broken"with no luck. While installing samba I'm getting the same error. Any ideas?

I believe wpa_supplicant is for when the NIC is running as a client and not server (AP) so the last comment is irrelevant.

I'd try removing the MODE, ESSID and KEY lines from ifcfg-wlp2s0 file as they should be covered by hostapd. Beyond looking at the logs, I've no idea where to look or what to do next.

After some "tinkering" was able to get the internet access... but only for the wired part of my network. The wireless NIC got stuck deactivated. Manual restart with "service hostapd restart" fails. Here is probably a recipe on how to fix the problem. At the end of the post it is written "When the client side interface is included in a bridge, add -b <bridge_interface> when running wpa_supplicant" But it seems that ClearOS doesn't support wpa_supplicant out-of-the-box.

Your subnet choice looks OK. Did you also make the change to /etc/clearos/network.conf to make LANIF="br0" (now missing from the howto )? You may also be able to make the change from the Webconfig in the IP Settings.

I remember about your advice and keep clear of 192.168.0.0/24 and 192.168.1.0/24.

My first LAN interface (WAN) obtains its address automatically from the ISP router. It is 192.168.1.20 where subnet is 255.255.255.0.
My second LAN interface has static address 192.168.10.1 with DHCP server releasing IP addresses in 255.255.255.128 subnet.
Similarly, my wireless adapter has address 192.168.20.1 with DHCP server working on 255.255.255.192 subnet.

Everything works fine until I configure a bridge. I've already posted its configuration. For convenience I' ll do it again:

DEVICE=br0

TYPE="Bridge"

ONBOOT="yes"

USERCTL="no"

BOOTPROTO="static"

IPADDR="192.168.10.1"

NETMASK="255.255.255.128"

GATEWAY="192.168.10.1"



DEVICE=enp4s0

TYPE="Ethernet"

ONBOOT="yes"

USERCTL="no"

# BOOTPROTO="static"

# IPADDR="192.168.10.1"

# NETMASK="255.255.255.128"

BRIDGE=br0



DEVICE=wlp2s0

TYPE="Wireless"

ONBOOT="yes"

USERCTL="no"

# BOOTPROTO="static"

# IPADDR="192.168.20.1"

# NETMASK="255.255.255.192"

BRIDGE=br0

MODE="managed"

ESSID="ClearOS"

KEY="123456789"

So basically there is only one network with IP address 192.168.10.1/25 which I believe doesn't have to interfere with the WAN 192.168.1.20/24.

Mikhail Sokolovskyy wrote:
Will concentrate on the bridging issue. Can you give an example of a not overlapping subnet mask to 255.255.255.0?

You have not really given enough information. What is the base address or an address in each range? Plug in your IP address and network mask into something like the Supernet Calculator and look at your CIDR address range. So, for example 192.168.10.1/255.255.255.0 has a range of 192.168.10.0 - 192.168.10.255. 192.168.10.10/255.255.255.128 has a range of 192.168.10.0 - 192.168.10.127 so one range is a subset of the other, but 192.168.11.1/255.255.255.128 would have a range of 192.168.11.0-192.168.11.127 so would not overlap either of the previous 2 ranges.

Generally for home stuff people seem to stick to /24 subnets (255.255.255.0), but you don't have to. In that case you need to make sure the third set of digits (octet) is different for each interface.

According to the RFC's, you should be able to use subnets anywhere in the following address spaces: 10.0.0.0/8, 172.16.0.0/12 and 192.168.0.0/16. As I said above, keep clear of 192.168.0.0/24 and 192.168.1.0/24. Also avoid 10.8.0.0/24, 10.8.10.0/24 (both used by ClearOS OpenVPN but it can be changed) and 192.168.100.0/24 (cable modems?). Others may have other subnets they recommend to avoid.

When you do chose a subnet, remember you cannot use the first and last address in the range so router LAN NIC's are typically .1 or .254 in a /24 subnet, but again, they don't have to be.

After a few hours of googling and testing have figured out that such solution:

ExecStart=/usr/bin/hostapd /etc/hostapd/hostapd.conf /etc/hostapd/hostapd2.conf

(taken from here) doesn't work. Even when I keep only second interface (USB dongle). When I start second interface manually I'm losing the first one.

Will concentrate on the bridging issue. Can you give an example of a not overlapping subnet mask to 255.255.255.0?

Nick Howitt wrote:
You could start the second instance from /etc/rc.d/rc.local (perhaps putting a "&" at the end of the line)

From the hostapd README:

Host AP configuration for IEEE 802.1X
-------------------------------------

The user space daemon has its own configuration file that can be used to
define AP options. Distribution package contains an example
configuration file (hostapd/hostapd.conf) that can be used as a basis
for configuration. It includes examples of all supported configuration
options and short description of each option. hostapd should be started
with full path to the configuration file as the command line argument,
e.g., './hostapd /etc/hostapd.conf'. If you have more that one wireless
LAN card, you can use one hostapd process for multiple interfaces by
giving a list of configuration files (one per interface) in the command
line.

The start up file is /usr/lib/systemd/system/hostapd.service where you can probably change the ExecStart line.

You could start the second instance from /etc/rc.d/rc.local (perhaps putting a "&" at the end of the line)

A kernel update should not mess things up. That is one of the benefits of kmod drivers. Otherwise add a line "exclude=kernel*" to the end of /etc/yum.conf.

Subnets 255.255.255.0 (/24) and 255.255.255.128 (/25) overlap so that is no good for different interfaces (and keep clear of 192.168.0.0/24 and 192.168.1.0/24 if you can)

Finally, with a help of scientific trial and error method have managed to configure a working hostapd script! (Was inspired by this discussion). For anyone who may be interested in it I'm posting it here:

#

# 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=wlp2s0

driver=nl80211

hw_mode=a

channel=36

max_num_sta=128

auth_algs=1

ssid=ClearOS

macaddr_acl=0

ignore_broadcast_ssid=0



### DFS

country_code=US

ieee80211d=1

ieee80211h=1



### IEEE 802.11n

ieee80211n=1

ht_capab=[HT40+][LDPC][SHORT-GI-20][SHORT-GI-40][TX-STBC][RX-STBC1][DSSS_CCK-40]



### IEEE 802.11ac

ieee80211ac=1

#vht_oper_chwidth=1

vht_capab=[MAX-MPDU-11454][RXLDPC][SHORT-GI-80][TX-STBC-2BY1][RX-STBC-1]

#vht_oper_centr_freq_seg0_idx=62



# WPA

wpa=2

wpa_key_mgmt=WPA-PSK

wpa_passphrase=123456789

wpa_pairwise=TKIP

rsn_pairwise=CCMP

These two lines which are commented in the ac section were crucial for the wireless. Also the system doesn't work on every allowed channel from "iw list".
Although I managed to run my wireless NIC, it happened after another reinstall of the OS, which I guess is not a good solution for solving problems. This time even after installing all the necessary software the kernel has not been updated and the wireless driver initiates correctly. Here is the output:

[root@gateway install]# dmesg | grep ath10k

[   18.686060] ath10k_pci 0000:02:00.0: irq 92 for MSI/MSI-X

[   18.686097] ath10k_pci 0000:02:00.0: pci irq msi interrupts 1 irq_mode 0 reset_mode 0

[   19.963223] ath10k_pci 0000:02:00.0: qca988x hw2.0 (0x4100016c, 0x043202ff) fw 10.2.4.45 api 4 htt 2.1 wmi 5 cal o

tp max_sta 128

[   19.963231] ath10k_pci 0000:02:00.0: debug 0 debugfs 0 tracing 0 dfs 0 testmode 0

[63852.216116] ath10k_pci 0000:02:00.0: could not get mac80211 beacon

[63852.318522] ath10k_pci 0000:02:00.0: could not get mac80211 beacon

[63852.420920] ath10k_pci 0000:02:00.0: could not get mac80211 beacon

[63852.523318] ath10k_pci 0000:02:00.0: could not get mac80211 beacon

[63852.625726] ath10k_pci 0000:02:00.0: could not get mac80211 beacon

[63852.728118] ath10k_pci 0000:02:00.0: could not get mac80211 beacon

[63852.830527] ath10k_pci 0000:02:00.0: could not get mac80211 beacon

[63852.932975] ath10k_pci 0000:02:00.0: could not get mac80211 beacon

[63853.035336] ath10k_pci 0000:02:00.0: could not get mac80211 beacon

[63853.137749] ath10k_pci 0000:02:00.0: could not get mac80211 beacon

[65862.187239] ath10k_warn: 3 callbacks suppressed

[65862.187259] ath10k_pci 0000:02:00.0: SWBA overrun on vdev 0, skipped old beacon

[65862.289654] ath10k_pci 0000:02:00.0: SWBA overrun on vdev 0, skipped old beacon

[65862.391956] ath10k_pci 0000:02:00.0: SWBA overrun on vdev 0, skipped old beacon

[65862.494414] ath10k_pci 0000:02:00.0: SWBA overrun on vdev 0, skipped old beacon

[65862.596823] ath10k_pci 0000:02:00.0: SWBA overrun on vdev 0, skipped old beacon

[65862.699209] ath10k_pci 0000:02:00.0: SWBA overrun on vdev 0, skipped old beacon

[65862.801618] ath10k_pci 0000:02:00.0: SWBA overrun on vdev 0, skipped old beacon

[65862.904014] ath10k_pci 0000:02:00.0: SWBA overrun on vdev 0, skipped old beacon

[65863.006416] ath10k_pci 0000:02:00.0: SWBA overrun on vdev 0, skipped old beacon

[65863.108826] ath10k_pci 0000:02:00.0: SWBA overrun on vdev 0, skipped old beacon

[66031.967049] ath10k_warn: 19 callbacks suppressed

[66031.967070] ath10k_pci 0000:02:00.0: could not get mac80211 beacon

[66272.915585] ath10k_pci 0000:02:00.0: SWBA overrun on vdev 0, skipped old beacon

[66273.018012] ath10k_pci 0000:02:00.0: SWBA overrun on vdev 0, skipped old beacon

[66273.120406] ath10k_pci 0000:02:00.0: SWBA overrun on vdev 0, skipped old beacon

[66273.222811] ath10k_pci 0000:02:00.0: SWBA overrun on vdev 0, skipped old beacon

[66273.325198] ath10k_pci 0000:02:00.0: SWBA overrun on vdev 0, skipped old beacon

[66273.427599] ath10k_pci 0000:02:00.0: SWBA overrun on vdev 0, skipped old beacon

[66273.530007] ath10k_pci 0000:02:00.0: SWBA overrun on vdev 0, skipped old beacon

[66273.632397] ath10k_pci 0000:02:00.0: SWBA overrun on vdev 0, skipped old beacon

[66273.734797] ath10k_pci 0000:02:00.0: SWBA overrun on vdev 0, skipped old beacon

I believe this card doesn't support operation on both WiFi 2G and 5G simultaneously. I've already connected my old TP link wireless usb dongle and easily run another 2G network. The only few things left are

1) How to run automatically second hostapd.conf file? As of now I do it manually.
2) Bridging still doesn't work. Maybe i is because my x86 router connected to the ISP router and hence has local IP address. Nevertheless I double checked the subnets and ensured that they are different (x86 router is in 255.255.255.0 subnet and the bridge interface is in 255.255.255.128).
3) How to prevent any changes in the kernel in order to avoid problems with the Atheros card?

P.S. OpenVPN works fine out-of-the-box)

Finally had time to read the links - interesting - thanks...

As for other sources, no idea if the implementation of the QCA9880 chipset is the same as for the Compex :-
https://www.amazon.com/AIRETOS-AEX-QCA9880-NX-802-11ac-Extended-Temperature/dp/B00OJPJVV6?tag=viglink21162-20
for http://www.airetos.com/products/aex-qca9880-nx/
and
https://www.amazon.com/MikroTik-R11e-5HacT-802-11ac-Triple-Chain-miniPCI/dp/B01F9HSTE2
for https://routerboard.com/R11e-5HacT

As for operation on both WiFi 2G and 5G simultaneously - I believe the device has to have two radios - one radio cannot handle both at the same time. How many radios does your card have?

Actually this is my second wireless NIC. The first one was Intel 7260 which was pretty much straightforward to run in 2.4 GHz mode but I couldn't find any information on how to force it to work in ac mode. After a month of testing it proved itself as a reliable and stable card. But I was striving to make an ac wifi router. I followed Nicks link where a guy named Sergey, could manage to build his own router based on this Compex card under Gentoo OS (in the comments section you can also find another article on this matterm where the OS is Ubuntu). Unfortunately I couldn't find any other wireless NIC with ac support which are freely available through ebay or other well known markets.

Been following this discussion. Reason for asking the manufacturer? From what I can glean from the 'Net - the Compex WLE900VX is actually designed to be used in a Compex Board with CompexWRT firmware. Looking in the Compex Forums, they are not interested in support other than use in their own custom designed products. I see reported problems with this card even with users of the 4.4 Linux kernel.

Over the years have tried various USB/PCI wireless devices. While they could often be made to work, were never reliable enough to be really satisfactory. The investment in time was never repaid by the outcome. Currently use either a wireless router and ignore the WAN port (turn off DHCP), or use VLAN/Interface Grouping on an ADSL2+ modem to separate the wireless and one ethernet port from the rest so the pair can be connected to my internal LAN.

Anyway - good luck with your project. If you really want to go this route, perhaps one thing to consider would be to investigate which wireless card provides the best Linux support for your purpose with the kernel version you have - purchase it and sell your card?

Here is the output:

[root@gateway ~]# ethtool -i wlp2s0

driver: ath10k_pci

version: 3.10.0-327.36.3.v7.x86_64

firmware-version: 999.999.0.636

bus-info: 0000:02:00.0

supports-statistics: yes

supports-test: no

supports-eeprom-access: no

supports-register-dump: no

supports-priv-flags: no

I believe the solution is simple since I am able to run the NIC once. But then, some of my actions are causing failure. So the idea is to understand what went wrong.

I really can't help any more as I don't have the hardware. All you can do is search the internet or try the Compex forums (the drivers is a backport from the 4.1 kernel).

Can you do any of this to check your firmware level which may help you get the right firmware from the github zip file?

No I did something similar at the very end, when all possible ideas have finished. All the time I'm using the driver you compiled and shared with me. In the corresponding folder there are board.bin, firmware-2.bin and firmware-4.bin (firmware-3.bin is absent) files with some notice text file. I tried then to dump a few different firmware's from the github link you posted, but with no success. I believe there is some relation between firmware and kernel versions. I simply can not find appropriate documentation.

You've triggered my memory of an issue on the ElRepo mailing list here. Following it through, I think you end up here on github. I think you then download the firmware file and take the ones you want (the latest firmware-3.bin and firmware-4.bin files and dump them into /usr/lib/firmware/ath10k/QCA988X/hw2.0/ and remove the last bit from the file name. What I find odd is that I already have the firmware-4.bin file. Do you? Anyway, it can't harm to rey the latest one, but keep the original one just in case.

Yes, the card manufacturer is Compex. Here is what I've found after some testing.

1) Crda allows me to play with frequency regulations.

iw reg set

starts to work and I can see allowed bands in the 5GHz range. At the end I managed to run ac mode on my router, by picking the right channel.... until something happened and after next reboot I got this message:

[    2.160484] ath10k_pci 0000:02:00.0: could not fetch firmware file 'ath10k/QCA988X/hw2.0/firmware-4.bin': -2

[    2.160510] ath10k_pci 0000:02:00.0: could not fetch firmware file 'ath10k/QCA988X/hw2.0/firmware-3.bin': -2

Also I've noticed that a new entry has appeared in the grub menu. I believe the kernel has been somehow updated ("uname -r" leads to the following output "3.10.0-327.36.3.v7.x86_64" now). Nevertheless if I choose the old entry I'm still getting this message.
At the same time I am able to run this card in g mode but not in ac anymore

2) Finally no need to tinker before access to the Internet! Probably an additional line "PROMISC="yes"" which I added to the network scripts did the job.

3) Still have no idea what is wrong with bridging interfaces. I've done it accordingly to this article and my previous experience but with no success unfortunately I'm getting correct IP settings on my PC connected to the second NIC but can't access even the router, not saying about Internet.

Who is the manufacturer of your Atheros WLE900VX card Compex?

Installed the drivers. Here is the output:

Kernel driver in use: r8168

Still need to tinker in order to get Internet access. Installing crda didn't help. Will continue googling.
It is strange since I configured once a working system with 5GHz support. But after installation of few packages the system crushed

Anyway thank you for your advices!

Mikhail Sokolovskyy wrote:

Regarding ac mode:

[root@gateway ~]# dmesg | grep cfg80211

[   18.624647] cfg80211: Calling CRDA to update world regulatory domain

[   20.091040] cfg80211: Calling CRDA to update world regulatory domain

[   21.768834] cfg80211: Calling CRDA to update world regulatory domain

[   24.953135] cfg80211: Calling CRDA to update world regulatory domain

[   28.104682] cfg80211: Calling CRDA to update world regulatory domain

[   29.610436] cfg80211: Calling CRDA to update world regulatory domain

[   31.256629] cfg80211: Calling CRDA to update world regulatory domain

[   34.408560] cfg80211: Calling CRDA to update world regulatory domain

[   37.560487] cfg80211: Calling CRDA to update world regulatory domain

[   40.712664] cfg80211: Calling CRDA to update world regulatory domain

[   43.864487] cfg80211: Calling CRDA to update world regulatory domain

[   47.016873] cfg80211: Calling CRDA to update world regulatory domain

[   50.170259] cfg80211: Calling CRDA to update world regulatory domain

[   53.429707] cfg80211: Calling CRDA to update world regulatory domain

[   56.578921] cfg80211: Calling CRDA to update world regulatory domain

[   59.194857] cfg80211: Calling CRDA to update world regulatory domain

[   59.732417] cfg80211: Calling CRDA to update world regulatory domain

[   62.885936] cfg80211: Calling CRDA to update world regulatory domain

[   66.039571] cfg80211: Calling CRDA to update world regulatory domain

[   69.193107] cfg80211: Calling CRDA to update world regulatory domain

[   72.346609] cfg80211: Calling CRDA to update world regulatory domain

[   75.500131] cfg80211: Calling CRDA to update world regulatory domain

[   78.653630] cfg80211: Calling CRDA to update world regulatory domain

[   81.807147] cfg80211: Calling CRDA to update world regulatory domain

[   84.960677] cfg80211: Calling CRDA to update world regulatory domain

[   88.114234] cfg80211: Calling CRDA to update world regulatory domain

[   91.267674] cfg80211: Exceeded CRDA call max attempts. Not calling CRDA

Maybe you have any idea where to dig further

Perhaps "yum install crda" but all I am doing is googling your error messages. Can you try googling as well as this is beyond my knowledge. (I found this link, but only the crda package is immediately available).

This is getting messy and pushing my knowledge. It looks like hostapd is trying to start before the interface has started and fails. Somewhere in /usr/lib/systemd/system/ there is probably a file hostapd.service which may need some tinkering. This is a search I did and there are a number of solutions here. I am not keen on anything which waits for a specific interface as it is too easy to forget you've changed it, and if you move the card to another slot you'll have to remember to change it.

I think you have hostapd config errors - it does not like a channel you're choosing, but in your file you seem to only choose a channel for g, not n or ac.

You also have a side issue with your main NICs. It looks like you're running an rtl8111/8168 card with the r8169 driver. This is the default set up but not good. You can check with an "lspci -k | grep Eth -A 3". Please can you download and install both the kmod-r8168 and kmod-r8169 drivers from my server then reboot.

Regarding ac mode:

[root@gateway ~]# dmesg | grep cfg80211

[   18.624647] cfg80211: Calling CRDA to update world regulatory domain

[   20.091040] cfg80211: Calling CRDA to update world regulatory domain

[   21.768834] cfg80211: Calling CRDA to update world regulatory domain

[   24.953135] cfg80211: Calling CRDA to update world regulatory domain

[   28.104682] cfg80211: Calling CRDA to update world regulatory domain

[   29.610436] cfg80211: Calling CRDA to update world regulatory domain

[   31.256629] cfg80211: Calling CRDA to update world regulatory domain

[   34.408560] cfg80211: Calling CRDA to update world regulatory domain

[   37.560487] cfg80211: Calling CRDA to update world regulatory domain

[   40.712664] cfg80211: Calling CRDA to update world regulatory domain

[   43.864487] cfg80211: Calling CRDA to update world regulatory domain

[   47.016873] cfg80211: Calling CRDA to update world regulatory domain

[   50.170259] cfg80211: Calling CRDA to update world regulatory domain

[   53.429707] cfg80211: Calling CRDA to update world regulatory domain

[   56.578921] cfg80211: Calling CRDA to update world regulatory domain

[   59.194857] cfg80211: Calling CRDA to update world regulatory domain

[   59.732417] cfg80211: Calling CRDA to update world regulatory domain

[   62.885936] cfg80211: Calling CRDA to update world regulatory domain

[   66.039571] cfg80211: Calling CRDA to update world regulatory domain

[   69.193107] cfg80211: Calling CRDA to update world regulatory domain

[   72.346609] cfg80211: Calling CRDA to update world regulatory domain

[   75.500131] cfg80211: Calling CRDA to update world regulatory domain

[   78.653630] cfg80211: Calling CRDA to update world regulatory domain

[   81.807147] cfg80211: Calling CRDA to update world regulatory domain

[   84.960677] cfg80211: Calling CRDA to update world regulatory domain

[   88.114234] cfg80211: Calling CRDA to update world regulatory domain

[   91.267674] cfg80211: Exceeded CRDA call max attempts. Not calling CRDA

Maybe you have any idea where to dig further

This is a part of dmesg messages:

[   18.707780] cfg80211: Calling CRDA to update world regulatory domain

[   18.743984] ath: module verification failed: signature and/or required key missing - tainting kernel

[   18.745168] snd_hda_intel 0000:00:1b.0: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915])

[   18.745566] alg: No test for crc32 (crc32-pclmul)

[   18.753193] ath10k_pci 0000:02:00.0: irq 92 for MSI/MSI-X

[   18.753210] ath10k_pci 0000:02:00.0: pci irq msi interrupts 1 irq_mode 0 reset_mode 0





[    1.961977] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded

[    1.961991] r8169 0000:03:00.0: can't disable ASPM; OS doesn't have ASPM control

[    1.962381] r8169 0000:03:00.0: irq 88 for MSI/MSI-X

[    1.962525] ahci 0000:00:13.0: irq 89 for MSI/MSI-X

[    1.962644] r8169 0000:03:00.0 eth0: RTL8168evl/8111evl at 0xffffc9000060e000, 00:e0:b4:17:72:08, XID 0c900800 IRQ 88

[    1.962649] r8169 0000:03:00.0 eth0: jumbo features [frames: 9200 bytes, tx checksumming: ko]

[    1.962676] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded

[    1.962686] r8169 0000:04:00.0: can't disable ASPM; OS doesn't have ASPM control

[    1.963044] r8169 0000:04:00.0: irq 90 for MSI/MSI-X

[    1.963285] r8169 0000:04:00.0 eth1: RTL8168evl/8111evl at 0xffffc90000622000, 00:e0:b4:17:72:09, XID 0c900800 IRQ 90

[    1.963289] r8169 0000:04:00.0 eth1: jumbo features [frames: 9200 bytes, tx checksumming: ko]

During the system start hostapd service seems to fail:

Dec 15 22:03:54 gateway hostapd: nl80211: Driver does not support authentication/association or connect commands

Dec 15 22:03:54 gateway hostapd: nl80211: deinit ifname=wlp2s0 disabled_11b_rates=0

Dec 15 22:03:54 gateway hostapd: Could not read interface wlp2s0 flags: No such device

Dec 15 22:03:54 gateway hostapd: nl80211 driver initialization failed.

Dec 15 22:03:54 gateway hostapd: wlp2s0: interface state UNINITIALIZED->DISABLED

Dec 15 22:03:54 gateway hostapd: wlp2s0: AP-DISABLED

Dec 15 22:03:54 gateway hostapd: hostapd_free_hapd_data: Interface wlp2s0 wasn't started



Dec 15 22:03:54 gateway systemd: hostapd.service: control process exited, code=exited status=1

Dec 15 22:03:54 gateway systemd: Failed to start Hostapd IEEE 802.11 AP, IEEE 802.1X/WPA/WPA2/EAP/RADIUS Authenticator.

Dec 15 22:03:54 gateway systemd: Unit hostapd.service entered failed state.

Dec 15 22:03:54 gateway systemd: hostapd.service failed.

Sill I'm not sure how this service is related to my ethernet NICs. It supposed to control wireless networks.
Ethernet interfaces seems to start:

Dec 15 22:03:58 gateway kernel: IPv6: ADDRCONF(NETDEV_CHANGE): enp4s0: link becomes ready

Dec 15 22:03:58 gateway dnsmasq-dhcp[617]: DHCPREQUEST(enp4s0) 192.168.10.58 08:62:66:2d:6f:65

Dec 15 22:03:58 gateway dnsmasq-dhcp[617]: DHCPACK(enp4s0) 192.168.10.58 08:62:66:2d:6f:65 DESKTOP-FU0R907

Dec 15 22:03:58 gateway network: Bringing up interface enp4s0:  [  OK  ]

Dec 15 22:03:58 gateway network: Bringing up interface wlp2s0:  key must be [d:]index:data where

Dec 15 22:03:58 gateway network: 'd:'     means default (transmit) key

Dec 15 22:03:58 gateway network: 'index:' is a single digit (0-3)

Dec 15 22:03:58 gateway network: 'data'   must be 5 or 13 ascii chars

Dec 15 22:03:58 gateway network: or 10 or 26 hex digits

Dec 15 22:03:58 gateway network: for example: d:2:6162636465 is the same as d:2:abcde

Dec 15 22:03:59 gateway kernel: IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready

Dec 15 22:03:59 gateway kernel: cfg80211: Calling CRDA to update world regulatory domain

But then:

Dec 15 22:04:02 gateway kernel: device enp4s0 entered promiscuous mode

Dec 15 22:04:02 gateway kernel: device wlp2s0 entered promiscuous mode

And in a moment:

Dec 15 22:04:04 gateway kernel: device wlp2s0 left promiscuous mode

Dec 15 22:04:04 gateway kernel: cfg80211: Calling CRDA to update world regulatory domain

Dec 15 22:04:04 gateway hostapd: wlp2s0: interface state UNINITIALIZED->COUNTRY_UPDATE

Dec 15 22:04:04 gateway systemd: Started Hostapd IEEE 802.11 AP, IEEE 802.1X/WPA/WPA2/EAP/RADIUS Authenticator.

And at the end:

Dec 15 22:04:05 gateway kernel: r8169 0000:03:00.0 enp3s0: link down

Dec 15 22:04:05 gateway kernel: r8169 0000:03:00.0 enp3s0: link down

Dec 15 22:04:05 gateway kernel: IPv6: ADDRCONF(NETDEV_UP): enp3s0: link is not ready

Dec 15 22:04:06 gateway kernel: cfg80211: Calling CRDA to update world regulatory domain

Dec 15 22:04:07 gateway systemd: Created slice user-0.slice.

Dec 15 22:04:07 gateway systemd: Starting user-0.slice.

Dec 15 22:04:07 gateway systemd: Started Session 2 of user root.

Dec 15 22:04:07 gateway systemd-logind: New session 2 of user root.

Dec 15 22:04:07 gateway systemd: Starting Session 2 of user root.

Dec 15 22:04:07 gateway kernel: r8169 0000:03:00.0 enp3s0: link up

Dec 15 22:04:07 gateway kernel: IPv6: ADDRCONF(NETDEV_CHANGE): enp3s0: link becomes ready

Dec 15 22:04:08 gateway dhclient[1738]: DHCPREQUEST on enp3s0 to 255.255.255.255 port 67 (xid=0x3f05e42e)

Dec 15 22:04:09 gateway dhclient[1738]: DHCPACK from 192.168.1.1 (xid=0x3f05e42e)

Dec 15 22:04:09 gateway kernel: cfg80211: Calling CRDA to update world regulatory domain

Dec 15 22:04:09 gateway hostapd: wlp2s0: IEEE 802.11 Configured channel (6) not found from the channel list of current mode (2) IEEE 802.11a

Dec 15 22:04:09 gateway hostapd: wlp2s0: IEEE 802.11 Hardware does not support configured channel

Dec 15 22:04:10 gateway kernel: IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready

Dec 15 22:04:11 gateway NET[1809]: /usr/sbin/dhclient-script : updated /etc/resolv-peerdns.conf

Dec 15 22:04:11 gateway nscd: 554 monitoring file `/etc/resolv.conf` (5)

Dec 15 22:04:11 gateway nscd: 554 monitoring directory `/etc` (2)

Dec 15 22:04:11 gateway dhclient[1738]: bound to 192.168.1.20 -- renewal in 1353 seconds.

Dec 15 22:04:12 gateway kernel: cfg80211: Calling CRDA to update world regulatory domain

Dec 15 22:04:13 gateway dnsmasq[617]: reading /etc/resolv-peerdns.conf

Dec 15 22:04:13 gateway dnsmasq[617]: using nameserver 213.57.22.5#53

Dec 15 22:04:13 gateway dnsmasq[617]: using nameserver 213.57.2.5#53

Dec 15 22:04:15 gateway kernel: cfg80211: Calling CRDA to update world regulatory domain

Dec 15 22:04:18 gateway kernel: cfg80211: Calling CRDA to update world regulatory domain

Dec 15 22:04:21 gateway kernel: hpet1: lost 9599 rtc interrupts

Dec 15 22:04:21 gateway kernel: cfg80211: Calling CRDA to update world regulatory domain

Dec 15 22:04:22 gateway kernel: hpet1: lost 9600 rtc interrupts

Dec 15 22:04:22 gateway kernel: hpet1: lost 9600 rtc interrupts

Mikhail Sokolovskyy wrote:

Have tried your firmware.

I'm just compiling the sources. I don't have the hardware to test.

For your tinkering, again it is hard to diagnose without the hardware. I did ask if hostapd runs after you reboot but before you tinker. You also need to look at the logs - probably /var/log/messages and /var/log/system but perhaps also /var/log/dmesg and the boot log.