[2024-feb-29] Sad news: Eric Layton aka Nocturnal Slacker aka vtel57 passed away on Feb 26th, shortly after hospitalization. He was one of our Wiki's most prominent admins. He will be missed.

Welcome to the Slackware Documentation Project

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
Next revisionBoth sides next revision
howtos:hardware:arm:raspberrypi3_wap [2018/08/26 20:55 (UTC)] – [Hardware Requirements] bifferoshowtos:hardware:arm:raspberrypi3_wap [2018/08/28 19:26 (UTC)] – [Adapter detection] bifferos
Line 8: Line 8:
  
   * A Raspberry Pi 3 running Slackware 14.2   * A Raspberry Pi 3 running Slackware 14.2
-  * A powered USB hub with 2A Power supply (to ensure the Wifi Dongle gets enough juice)+  * A powered USB hub with 2A Power supply (to ensure the Wifi adapter gets enough juice)
   * Alfa Network AWUS036NHA - USB WiFi Adapter with chipset ar9271l   * Alfa Network AWUS036NHA - USB WiFi Adapter with chipset ar9271l
   * Ethernet cable   * Ethernet cable
Line 44: Line 44:
  
 ===== Adapter detection ===== ===== Adapter detection =====
 +
 +<note>
 +I advise to not connect and disconnect the hub from the Pi while it's running.  Instead, power it up with hub connected (and powered) and then connect and disconnect the Wifi adapter as needed.
 +</note>
  
 Ensure that iwconfig shows two adapters wlan0 and wlan1.  wlan0 is the built-in one on the Pi.  If dmesg isn't showing the Alpha one has been plugged in, then just un-plug it and plug it in again.  Bring the Adapter up with: Ensure that iwconfig shows two adapters wlan0 and wlan1.  wlan0 is the built-in one on the Pi.  If dmesg isn't showing the Alpha one has been plugged in, then just un-plug it and plug it in again.  Bring the Adapter up with:
Line 77: Line 81:
 <code># Example of how to configure a bridge:</code> <code># Example of how to configure a bridge:</code>
  
-Ensure the following appears so a bridge will be created:+Ensure the following appears so a bridge will be created (adjust DHCP_HOSTNAME to suit):
  
 <code>IFNAME[0]="br0" <code>IFNAME[0]="br0"
Line 113: Line 117:
 auth_algs=1</code> auth_algs=1</code>
  
-What this does:  The interface wlan1, we've seen before.  The bridge br0 will get wlan1 interface added to it when hostapd has fired up.  The syslog logging lines ensure you get something in /var/log/messages to tell you what's going on.  The ssid, wpa and wpa_passphrase settings should be rather obvious, the hw_mode you can just leave as 'g' unless you know what you're doing, channel is set to something you didn't see when you ran 'iwlist wlan1 scanning' earlier on.+What this does:  The interface wlan1, we've seen before.  The bridge br0 will get wlan1 interface added to it when hostapd has fired up.  The syslog logging lines ensure you get something in /var/log/messages to tell you what's going on.  The ssid, wpa and wpa_passphrase settings should be rather obvious, the hw_mode you can just leave as 'g' unless you know what you're doing, channel is set to something you didn't see when you ran ''iwlist wlan1 scanning'' earlier on.
  
 That minimal config should get hostapd working fine, at least it did for me. That minimal config should get hostapd working fine, at least it did for me.
 howtos:hardware:arm:raspberrypi3_wap ()