Alfa Awus036H (RTL8187L) not work

PirateBox1.0.1 Raspberry Pi

Led green is ok but not AP present!

[root@alarmpi ~]# ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.1.113 netmask 255.255.255.0 broadcast 192.168.1.255
inet6 fe80::ba27:ebff:fe6d:8925 prefixlen 64 scopeid 0x20<link>
ether b8:27:eb:6d:89:25 txqueuelen 1000 (Ethernet)
RX packets 908 bytes 154518 (150.8 Ki
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 310 bytes 53650 (52.3 Ki
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 0 (Local Loopback)
RX packets 166 bytes 12670 (12.3 Ki
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 166 bytes 12670 (12.3 Ki
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

wlan0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 192.168.77.1 netmask 255.255.255.0 broadcast 192.168.77.255
ether 00:c0:ca:54:65:c0 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

---

[root@alarmpi ~]# iwconfig
wlan0 IEEE 802.11bg ESSIDff/any
Mode:Managed Access Point: Not-Associated Tx-Power=20 dBm
Retry long limit:7 RTS thrff Fragment thrff
Encryption keyff
Power Managementff

lo no wireless extensions.
eth0 no wireless extensions.
ifb0 no wireless extensions.
ifb1 no wireless extensions.

---

[root@alarmpi ~]# iw list
Wiphy phy0
max # scan SSIDs: 4
max scan IEs length: 2285 bytes
Coverage class: 0 (up to 0m)
Device supports RSN-IBSS.
Supported Ciphers:
* WEP40 (00-0f-ac:1)
* WEP104 (00-0f-ac:5)
* TKIP (00-0f-ac:2)
* CCMP (00-0f-ac:4)
Available Antennas: TX 0 RX 0
Supported interface modes:
* IBSS
* managed
* monitor
Band 1:
Bitrates (non-HT):
* 1.0 Mbps
* 2.0 Mbps
* 5.5 Mbps
* 11.0 Mbps
* 6.0 Mbps
* 9.0 Mbps
* 12.0 Mbps
* 18.0 Mbps
* 24.0 Mbps
* 36.0 Mbps
* 48.0 Mbps
* 54.0 Mbps
Frequencies:
* 2412 MHz [1] (20.0 dBm)
* 2417 MHz [2] (20.0 dBm)
* 2422 MHz [3] (20.0 dBm)
* 2427 MHz [4] (20.0 dBm)
* 2432 MHz [5] (20.0 dBm)
* 2437 MHz [6] (20.0 dBm)
* 2442 MHz [7] (20.0 dBm)
* 2447 MHz [8] (20.0 dBm)
* 2452 MHz [9] (20.0 dBm)
* 2457 MHz [10] (20.0 dBm)
* 2462 MHz [11] (20.0 dBm)
* 2467 MHz [12] (20.0 dBm) (no IR)
* 2472 MHz [13] (20.0 dBm) (no IR)
* 2484 MHz [14] (20.0 dBm) (no IR)
Supported commands:
* new_interface
* set_interface
* new_key
* start_ap
* new_station
* new_mpath
* set_mesh_config
* set_bss
* authenticate
* associate
* deauthenticate
* disassociate
* join_ibss
* join_mesh
* set_tx_bitrate_mask
* frame
* frame_wait_cancel
* set_wiphy_netns
* set_channel
* set_wds_peer
* probe_client
* set_noack_map
* register_beacons
* start_p2p_device
* set_mcast_rate
* testmode
* connect
* disconnect
Supported TX frame types:
* IBSS: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* managed: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* AP: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* AP/VLAN: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* mesh point: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* P2P-client: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* P2P-GO: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
* P2P-device: 0x00 0x10 0x20 0x30 0x40 0x50 0x60 0x70 0x80 0x90 0xa0 0xb0 0xc0 0xd0 0xe0 0xf0
Supported RX frame types:
* IBSS: 0x40 0xb0 0xc0 0xd0
* managed: 0x40 0xd0
* AP: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
* AP/VLAN: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
* mesh point: 0xb0 0xc0 0xd0
* P2P-client: 0x40 0xd0
* P2P-GO: 0x00 0x20 0x40 0xa0 0xb0 0xc0 0xd0
* P2P-device: 0x40 0xd0
software interface modes (can always be added):
* monitor
interface combinations are not supported
HT Capability overrides:
* MCS: ff ff ff ff ff ff ff ff ff ff
* maximum A-MSDU length
* supported channel width
* short GI for 40 MHz
* max A-MPDU length exponent
* min MPDU start spacing
Device supports TX status socket option.
Device supports HT-IBSS.
Device supports low priority scan.
Device supports scan flush.
Device supports AP scan.

hi,
did you change something on hostapd.conf ?
Did you add a powered usb hub? (some usb sticks need that)
and please post the output of

dmesg | tail -n 30

Matthias

---

This is only my signature.

Thanks for the reply.
I realized after that Awus036H requires additional power. I changed it with another model and is now working.

Hallo Matthias,

ich würde gerne mein Alfa WiFi Adapter in Betrieb nehmen. Leider kenne ich mich mit Linux nicht aus. Kannst du mir dabei helfen?

dmesg | tail -n 30

gibt mir folgenden Fehler aus:

[root@alarmpi ~]# dmesg | tail -n 30
[   16.960705] cfg80211: 2402000 KHz - 2472000 KHz @ 40000 KHz), (600 mBi, 2000 mBm)
[   16.960717] cfg80211: Updating information on frequency 2432 MHz with regulatory rule:
[   16.960731] cfg80211: 2402000 KHz - 2472000 KHz @ 40000 KHz), (600 mBi, 2000 mBm)
[   16.960743] cfg80211: Updating information on frequency 2437 MHz with regulatory rule:
[   16.960757] cfg80211: 2402000 KHz - 2472000 KHz @ 40000 KHz), (600 mBi, 2000 mBm)
[   16.960769] cfg80211: Updating information on frequency 2442 MHz with regulatory rule:
[   16.960783] cfg80211: 2402000 KHz - 2472000 KHz @ 40000 KHz), (600 mBi, 2000 mBm)
[   16.960796] cfg80211: Updating information on frequency 2447 MHz with regulatory rule:
[   16.960810] cfg80211: 2402000 KHz - 2472000 KHz @ 40000 KHz), (600 mBi, 2000 mBm)
[   16.960823] cfg80211: Updating information on frequency 2452 MHz with regulatory rule:
[   16.960838] cfg80211: 2402000 KHz - 2472000 KHz @ 40000 KHz), (600 mBi, 2000 mBm)
[   16.960850] cfg80211: Updating information on frequency 2457 MHz with regulatory rule:
[   16.960864] cfg80211: 2402000 KHz - 2472000 KHz @ 40000 KHz), (600 mBi, 2000 mBm)
[   16.960877] cfg80211: Updating information on frequency 2462 MHz with regulatory rule:
[   16.960891] cfg80211: 2402000 KHz - 2472000 KHz @ 40000 KHz), (600 mBi, 2000 mBm)
[   16.960903] cfg80211: Updating information on frequency 2467 MHz with regulatory rule:
[   16.960917] cfg80211: 2457000 KHz - 2482000 KHz @ 40000 KHz), (600 mBi, 2000 mBm)
[   16.960930] cfg80211: Updating information on frequency 2472 MHz with regulatory rule:
[   16.960945] cfg80211: 2457000 KHz - 2482000 KHz @ 40000 KHz), (600 mBi, 2000 mBm)
[   16.960957] cfg80211: Updating information on frequency 2484 MHz with regulatory rule:
[   16.960972] cfg80211: 2474000 KHz - 2494000 KHz @ 20000 KHz), (600 mBi, 2000 mBm)
[   17.091429] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
[   17.101819] ieee80211 phy0: hwaddr 00:c0:ca:7e:f0:72, RTL8187vB (default) V1 + rtl8225z2, rfkill mask 2
[   17.223666] rtl8187: Customer ID is 0xFF
[   17.280012] rtl8187: wireless switch is on
[   17.343856] usbcore: registered new interface driver rtl8187
[   21.053053] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[   23.447943] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready

Okey,
in der Hoffnung dem Alpha ein AP Modus beizubringen, habe ich nach folgende Anweisung ausprobiert ->r8187 Driver
Leider ohne Erfolg. Beim compilieren kommt zu Fehler -“RTL8187.ko konnte nicht gefunden werden “
und das wars schon. Auch weitere Versuche mit Original Realteck Treibern und allen Treibern die ich finden konnte, schlugen fehl Ich vermute das es keine aktuelle Treiber für den Realtek RTL8187L mehr geben wird . Komischerweise läuft Alpha im Access Pointe Mode im M$ Windows problemlos.
Kurz-gesagt : bin ich zum “Plan B” übergegangen und Alpha durch TP-Link TL-WN822N v.3 -> RTL8192cu
ersetzte. Dank Anleitung von WACOMalt aus >diesem Thread< läuft jetzt meine Piratenbox einigermaßen.