2 wifi radio running concurrent

Installing and Using OpenWrt
1

Hi guys,

I can't get 2 wifi radio running concurrent.
My hardware is a iNet GL-AR150 Router. That’s a Atheros AR9330 SoC plattform.
I tried an Atheros AR9271 USB adapter and an Alfa AWUS036NHA (RTL8187vB) USB adapter as
second wifi radio.
This is my /etc/config/wireless:

config wifi-device 'radio0'
        option type 'mac80211'
        option channel '11'
        option path 'platform/ar933x_wmac'
        option htmode 'HT20'
        option hwmode '11n'
        option txpower '18'
        option country 'NZ'
        option disabled '0'

config wifi-iface 'default_radio0'
        option device 'radio0'
        option network 'lan'
        option mode 'ap'
        option ssid 'INTERNET'
        option encryption 'none'

config wifi-device 'radio1'
        option type 'mac80211'
        option channel '6'
        option path 'platform/ehci-platform/usb1/1-1/1-1:1.0'
        option htmode 'HT20'
        option hwmode '11n'
        option txpower '20'
        option country 'NZ'
        option disabled '0'

config wifi-iface 'default_radio1'
        option device 'radio1'
        option network 'lan'
        option mode 'ap'
        option ssid 'LEDE'
        option encryption 'none'

The radio0 is broadcasting, radio1 is not.
Same result with the AWUS036NHA (start-up log too ?)
The Atheros AR9271 USB adapter worked with Windows 7.

USB driver problem ?
What do I wrong ?

What I get in the log:

[    0.831020] mtd: device 4 (rootfs) set to be root filesystem
[    0.835350] 1 squashfs-split partitions found on MTD device rootfs
[    0.841405] 0x0000003d0000-0x000000ff0000 : "rootfs_data"
[    0.849155] 0x000000ff0000-0x000001000000 : "art"
[    0.871895] libphy: ag71xx_mdio: probed
[    1.464125] ag71xx ag71xx.0: connected to PHY at ag71xx-mdio.1:04 [uid=004dd041, driver=Generic PHY]
[    1.472858] eth0: Atheros AG71xx at 0xb9000000, irq 4, mode:MII
[    2.063888] ag71xx-mdio.1: Found an AR7240/AR9330 built-in switch
[    2.095954] eth1: Atheros AG71xx at 0xba000000, irq 5, mode:GMII
[    2.103319] NET: Registered protocol family 10
[    2.111364] NET: Registered protocol family 17
[    2.114549] bridge: automatic filtering via arp/ip/ip6tables has been deprecated. Update your scripts to load br_netfilter if you need this.
[    2.127145] 8021q: 802.1Q VLAN Support v1.8
[    2.138316] VFS: Mounted root (squashfs filesystem) readonly on device 31:4.
[    2.146420] Freeing unused kernel memory: 312K
[    3.406826] init: Console is alive
[    3.409072] init: - watchdog -
[    4.586230] kmodloader: loading kernel modules from /etc/modules-boot.d/*
[    4.695420] usbcore: registered new interface driver usbfs
[    4.699575] usbcore: registered new interface driver hub
[    4.704976] usbcore: registered new device driver usb
[    4.716905] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    4.724098] ehci-platform: EHCI generic platform driver
[    4.728009] ehci-platform ehci-platform: EHCI Host Controller
[    4.733741] ehci-platform ehci-platform: new USB bus registered, assigned bus number 1
[    4.743663] ehci-platform ehci-platform: irq 3, io mem 0x1b000000
[    4.762463] ehci-platform ehci-platform: USB 2.0 started, EHCI 1.00
[    4.768556] hub 1-0:1.0: USB hub found
[    4.771558] hub 1-0:1.0: 1 port detected
[    4.776210] kmodloader: done loading kernel modules from /etc/modules-boot.d/*
[    4.792777] init: - preinit -
[    5.388082] usb 1-1: new high-speed USB device number 2 using ehci-platform
[    5.513310] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[    5.567510] random: procd: uninitialized urandom read (4 bytes read, 9 bits of entropy available)
Press the [f] key and hit [enter] to enter failsafe mode
Press the [1], [2], [3] or [4] key and hit [enter] to select the debug level
[    8.807380] jffs2: notice: (372) jffs2_build_xattr_subsystem: complete building xattr subsystem, 0 of xdatum (0 unchecked, 0 orphan) and 0 of xref (0 dead, 0 orphan) found.
[    8.824642] mount_root: switching to jffs2 overlay
[    8.838333] urandom-seed: Seeding with /etc/urandom.seed
[    9.152142] procd: - early -
[    9.153907] procd: - watchdog -
[    9.843755] procd: - watchdog -
[    9.845820] procd: - ubus -
[    9.974911] random: ubusd: uninitialized urandom read (4 bytes read, 16 bits of entropy available)
[    9.984476] random: ubusd: uninitialized urandom read (4 bytes read, 17 bits of entropy available)
[    9.992761] random: ubusd: uninitialized urandom read (4 bytes read, 17 bits of entropy available)
[   10.001008] random: ubusd: uninitialized urandom read (4 bytes read, 17 bits of entropy available)
[   10.010480] random: ubusd: uninitialized urandom read (4 bytes read, 17 bits of entropy available)
[   10.019011] random: ubusd: uninitialized urandom read (4 bytes read, 17 bits of entropy available)
[   10.028251] random: ubusd: uninitialized urandom read (4 bytes read, 17 bits of entropy available)
[   10.037081] random: ubusd: uninitialized urandom read (4 bytes read, 17 bits of entropy available)
[   10.046239] procd: - init -
Please press Enter to activate this console.
[   10.699693] kmodloader: loading kernel modules from /etc/modules.d/*
[   10.785597] SCSI subsystem initialized
[   10.826832] ip6_tables: (C) 2000-2006 Netfilter Core Team
[   10.847633] Loading modules backported from Linux version wt-2017-01-31-0-ge882dff19e7f
[   10.854278] Backport generated by backports.git backports-20160324-13-g24da7d3c
[   10.865882] ip_tables: (C) 2000-2006 Netfilter Core Team
[   10.881255] nf_conntrack version 0.5.0 (947 buckets, 3788 max)
[   10.934061] usbcore: registered new interface driver usb-storage
[   10.963318] xt_time: kernel timezone is -0000
[   11.058995] PPP generic driver version 2.4.2
[   11.065390] NET: Registered protocol family 24
[   11.085520] usbcore: registered new interface driver rtl8187
[   11.178936] usb 1-1: ath9k_htc: Firmware ath9k_htc/htc_9271-1.4.0.fw requested
[   11.184960] usbcore: registered new interface driver ath9k_htc
[   11.251372] ieee80211 phy0: Atheros AR9330 Rev:1 mem=0xb8100000, irq=2
[   11.414949] kmodloader: done loading kernel modules from /etc/modules.d/*
[   11.912595] usb 1-1: ath9k_htc: Transferred FW: ath9k_htc/htc_9271-1.4.0.fw, size: 51008
[   12.204708] ath9k_htc 1-1:1.0: ath9k_htc: HTC initialized with 33 credits
[   12.839141] ath9k_htc 1-1:1.0: ath9k_htc: FW Version: 1.4
[   12.843169] ath9k_htc 1-1:1.0: FW RMW support: On
[   12.870624] ieee80211 phy1: Atheros AR9271 Rev:1
[   13.196623] random: jshn: uninitialized urandom read (4 bytes read, 29 bits of entropy available)
[   22.668465] device eth1 entered promiscuous mode
[   22.689923] br-lan: port 1(eth1) entered forwarding state
[   22.694027] br-lan: port 1(eth1) entered forwarding state
[   22.762122] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   23.633182] br-lan: port 1(eth1) entered disabled state
[   27.261662] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[   27.421611] IPv6: ADDRCONF(NETDEV_UP): wlan1: link is not ready
[   27.427011] device wlan0 entered promiscuous mode
[   27.469600] device wlan1 entered promiscuous mode
[   27.473087] br-lan: port 3(wlan1) entered forwarding state
[   27.478378] br-lan: port 3(wlan1) entered forwarding state
[   28.262495] br-lan: port 3(wlan1) entered disabled state
[   32.487750] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[   32.492994] br-lan: port 2(wlan0) entered forwarding state
[   32.498191] br-lan: port 2(wlan0) entered forwarding state
[   32.703164] IPv6: ADDRCONF(NETDEV_CHANGE): wlan1: link becomes ready
[   32.708342] br-lan: port 3(wlan1) entered forwarding state
[   32.713707] br-lan: port 3(wlan1) entered forwarding state
[   33.050894] usb 1-1: USB disconnect, device number 2
[   33.163129] ath: phy1: RX failed to go idle in 10 ms RXSM=0x2000000
[   33.273481] ath: phy1: RX failed to go idle in 10 ms RXSM=0x2000000
[   33.381860] ath: phy1: RX failed to go idle in 10 ms RXSM=0x2000000
[   33.387271] br-lan: port 3(wlan1) entered disabled state
[   33.400982] device wlan1 left promiscuous mode
[   33.404106] br-lan: port 3(wlan1) entered disabled state
[   33.417082] usb 1-1: ath9k_htc: USB layer deinitialized
[   33.712452] usb 1-1: new high-speed USB device number 3 using ehci-platform
[   33.885724] usb 1-1: ath9k_htc: Firmware ath9k_htc/htc_9271-1.4.0.fw requested
[   34.173432] usb 1-1: ath9k_htc: Transferred FW: ath9k_htc/htc_9271-1.4.0.fw, size: 51008
[   34.424444] ath9k_htc 1-1:1.0: ath9k_htc: HTC initialized with 33 credits
[   34.492441] br-lan: port 2(wlan0) entered forwarding state
[   34.667312] ath9k_htc 1-1:1.0: ath9k_htc: FW Version: 1.4
[   34.671303] ath9k_htc 1-1:1.0: FW RMW support: On
[   34.687055] ieee80211 phy2: Atheros AR9271 Rev:1
[   34.877949] IPv6: ADDRCONF(NETDEV_UP): wlan1: link is not ready
[   41.027522] random: nonblocking pool is initialized


BusyBox v1.25.1 () built-in shell (ash)

     _________
    /        /\      _    ___ ___  ___
   /  LE    /  \    | |  | __|   \| __|
  /    DE  /    \   | |__| _|| |) | _|
 /________/  LE  \  |____|___|___/|___|                      lede-project.org
 \        \   DE /
  \    LE  \    /  -----------------------------------------------------------
   \  DE    \  /    Reboot (17.01.4, r3560-79f57e422d)
    \________\/    -----------------------------------------------------------

root@LEDE:/#
3

At 33 seconds the USB device disconnects, then reconnects and the driver loads again. Does it do that over and over? That is often from a lack of DC power.

4

Thanks for the quick reply.
No, it doesn't this over and over.
The Atheros AR9271 USB adapter uses 5.03 Volt / 0.077 A = 0.387 Watt with no connection.
Max. 120 mA spikes at init. All inside the USB specs.
I will check corelation if no other thing comes up.
Thank you for your input.

5

I am having exactly the same problem, using an ALFA AP121U with and ALFA AR9271.
Can somebody confirm that its a lack of power or please give another advice ?

thanks !!

6

You can do it yourself.
What happens if you use a powered USB to connect to the router?

7

Instead of using a powered hub, I took a Y - USB cable with a second adapter and it works!

1 Like
8

Hello djesys,

pretty please point us to the source of this Y - USB cable.
I also want to buy one of these.
Thank you.

9

Given that you can buy a powered hub from a decent manufacturer right now for under $12 (Under a minute of searching, might be cheaper ones out there), I'd strongly recommend that over the potential of back-feeding, introducing ground loops, noise, and a host of other reasons why a "Y" is not a standard piece of kit.

(Note, I have not tried this specific hub. First one that came up on my Amazon search.)

10

An average of 4.3 out of 5 rating from 10,231 reviews is a pretty good indicator.

For the price, you can't go wrong.

11

Hi got an ar150,

been able to have both an 8gb usb storage key and TP-Link TL-WN722N working with a powered usb hub

see below

https://www.amazon.com/Anker-4-Port-Macbook-Surface-Notebook/dp/B00XMD7KPU/ref=sr_1_5?s=electronics&ie=UTF8&qid=1539853304&sr=1-5&keywords=usb+hub.

SORRY WRONG ONE BELOW RIGHT ONE

second radio was for AP while onboard radio was for relayd protocol see https://openwrt.org/docs/guide-user/network/wifi/connect_client_wifi

In a setting were I compiled pineapplenano firmware on ar150 was not able to have a second TP-Link TL-WN722N working as third antenna , I don't remember if the third one works in normal openwrt set up.

Not sure about this working but I am sure I 've seen a green light while connecting one TP-Link TL-WN722N directlky to ar150 usb port in openwrt.

Bests P.

12

Edit: Post above edited to refer to the powered version of the Anker hub.

While I've found that Anker hub originally linked and visually very similar to be a good one for certain applications (I use several myself), it is not a powered hub. (The hub presently linked is powered.)

As such, it An unpowered hub can't provide more power to the attached devices than the host can provide. Some of the problems above appeared to be that the host device was not able to supply enough power to the attached devices. Both wireless adapters and spinning-disk drives are power hungry devices. Although they are "within the specs" for USB, many hosts don't have enough power available to support them.

2 Likes
13

Sorry wrong one

I was talking about the powered version !!

My mistake and for the same price the sabrent looks better because of the power switches,

one thing I would consider is the distance between the ports. Sometimes you need to use a usb cable to

avoid contacts between the dongle usb key etc etc

Sorry again

Bests

P.

14

USB cable that comes with ALFA is bad - too long. just replace it with 50cm UGREEN cable it will work fine.