[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:network_services:running_an_access_point_from_a_slackware_box [2016/10/21 07:44 (UTC)] – [4.7.1 Wired Clients] louigi600howtos:network_services:running_an_access_point_from_a_slackware_box [2022/11/13 04:21 (UTC)] – [5.5 Virtual AP] louigi600
Line 1: Line 1:
 ====== Setting up a WiFi Access Point on your Slackware Box ====== ====== Setting up a WiFi Access Point on your Slackware Box ======
 You should read this, regardless of whether you are a Slackware enthusiast or not, because you will find most of it applicable to other distributions too.  You should read this, regardless of whether you are a Slackware enthusiast or not, because you will find most of it applicable to other distributions too. 
 +I have recently reused most of this on a debian/DietPI based NanoPi R1S H3 just because it was fester for me to get something functional like that rather than tinkering with uboot and kernel to get slackwareARM running on it. 
 ====== 1 Preamble ====== ====== 1 Preamble ======
 There are endless reasons for wanting to run an AP from a standard Linux environment as opposed to the crippled ones that come in most AP appliances, we're not here to discuss them all but if you're reading this you've found your own motivation for doing it. There are endless reasons for wanting to run an AP from a standard Linux environment as opposed to the crippled ones that come in most AP appliances, we're not here to discuss them all but if you're reading this you've found your own motivation for doing it.
Line 15: Line 16:
 Look at the section  Look at the section 
      
-   software interface modes:+   Supported interface modes:
                  * AP/VLAN                  * AP/VLAN
                  * monitor                  * monitor
-AP need to be amongst the software interface modes.+AP needs to be among the Supported interface modes. 
 + 
 +Ok there is still some Wireless NICs that support hardware master mode but that's 3 against all the rest I'm not going to bother going into any detail with those 3 exceptions, google is your friend if you want to insist in the hardware master mode way.  
 + 
 + 
 +Should you want to have Virtual Access Poits (more than one AP on a single physical wireless NIC) you will want to look at the section "valid interface combinations". 
 +Here's the output from two cards : 
 + 
 +  [root@nuc8i5 ~]# for Phy in $(iw dev |grep ^phy); do   echo "$Phy";   iw $Phy info | grep  "valid interface combinations" -A 2; done 
 +  phy#1 
 +        valid interface combinations: 
 +                 * #{ AP, mesh point } <= 8, 
 +                   total <= 8, #channels <= 1 
 +  phy#0 
 +        valid interface combinations: 
 +                 * #{ managed } <= 1, #{ AP, P2P-client, P2P-GO } <= 1, #{ P2P-device } <= 1, 
 +                   total <= 3, #channels <= 2 
 +  [root@nuc8i5 ~]# 
 +   
 +The first one would allow more than on vAP (up to a maximum of 8) but they all got to be on the same channel. 
 +The second one would allow for one AP and one managed client to be used at the same time even of different channels but the total number of live APs need to be no more than one.
  
 ====== 3 Software Requirements ====== ====== 3 Software Requirements ======
Line 71: Line 92:
   * rp-pppoe (*)   * rp-pppoe (*)
  
-(*) only if you want your AP to actually manage your internet connection. +(*) only if you want your AP to actually manage your internet connection trough some sort of point PPP modem. 
  
  
 ===== 3.3 Other Software ===== ===== 3.3 Other Software =====
   * hostapd   * hostapd
 +  * miniupnpd (only required if you have appliances that require upnp)
  
-Hostapd is not shipped with Slackware packages and is the only extra software you need for a basic setup.+Neither of these are included in the slackare installation packages, only hostap is mandatory to gae basic AP functionality. 
 To obtain hostapd you could either download a binary version from some reliable source or compile it from sources. You might be slightly better off compiling from sources, so that you get e fairly recent version, but it's up to you. Just don't try using really old hostapd versions like 0.6.7 on 2.6+ kernels: hostapd has followed the kernel wireless stack drivers and transitioned from only supporting FullMAC devices to supporting SoftMAC on almost all devices trough nl80211. Nowadays the combination of both hardware and driver supporting FullMAC is hard to come by (Prism2/2.5/3, and Atheros ar521x) all the others need to go the SoftMAC way so I suggest ignoring the 2 that could still go the FullMAC way and just go for SoftMAC for all, allowing you to use almost any WiFi card for creating an AP. If you like you can read more about [[http://wireless.kernel.org/en/developers/Documentation/mac80211 |  mac80211 here]]. To obtain hostapd you could either download a binary version from some reliable source or compile it from sources. You might be slightly better off compiling from sources, so that you get e fairly recent version, but it's up to you. Just don't try using really old hostapd versions like 0.6.7 on 2.6+ kernels: hostapd has followed the kernel wireless stack drivers and transitioned from only supporting FullMAC devices to supporting SoftMAC on almost all devices trough nl80211. Nowadays the combination of both hardware and driver supporting FullMAC is hard to come by (Prism2/2.5/3, and Atheros ar521x) all the others need to go the SoftMAC way so I suggest ignoring the 2 that could still go the FullMAC way and just go for SoftMAC for all, allowing you to use almost any WiFi card for creating an AP. If you like you can read more about [[http://wireless.kernel.org/en/developers/Documentation/mac80211 |  mac80211 here]].
  
-Hostapd sources can be downloaded from [[http://w1.fi/hostapd/ | here]], you should be looking at recent stable version (2.5 last time this article was edited) and avoid the development/old branches.+Hostapd sources can be downloaded from [[http://w1.fi/hostapd/ | here]], you should be looking at the most recent stable version (2.9 last time this article was edited) and avoid the development/old branches.
 Compiling hostapd is really simple: Compiling hostapd is really simple:
   - extract the sources   - extract the sources
Line 87: Line 109:
   - edit the defconfig file and enable any optional features you need (default is fine for a simple setup)   - edit the defconfig file and enable any optional features you need (default is fine for a simple setup)
   - copy the defconfig file to .config   - copy the defconfig file to .config
 +  - make a softlink for netlink includes (cd /usr/include; ln -s libnl3/netlink .)
   - make   - make
   - make install (or optionally just put in /usr/local/bin just the hostapd binary)   - make install (or optionally just put in /usr/local/bin just the hostapd binary)
Line 95: Line 118:
 If your AP also acts a router it's probably going to be exposed to malware and even if you do your best to keep malicious users out of your work they might still find a way in. If your router is exposed to internet you might want to consider some sort of file integrity tool that would alert you if files have been tampered with. File integrity checking could be a whole article so I'm not going to go into any detail beyond advising to read more about it on security oriented communities like [[http://www.securityfocus.com|security focus]] or maybe just do a google search on "file integrity tool".   If your AP also acts a router it's probably going to be exposed to malware and even if you do your best to keep malicious users out of your work they might still find a way in. If your router is exposed to internet you might want to consider some sort of file integrity tool that would alert you if files have been tampered with. File integrity checking could be a whole article so I'm not going to go into any detail beyond advising to read more about it on security oriented communities like [[http://www.securityfocus.com|security focus]] or maybe just do a google search on "file integrity tool".  
 ====== 4 Configuring ====== ====== 4 Configuring ======
-Now let's have a look at how to configure everything to that it will work right.+Now let's have a look at how to configure everything so that it will work right.
  
 ===== 4.1 Hostapd ===== ===== 4.1 Hostapd =====
Line 114: Line 137:
   * hw_mode=g  #to keep it simple don't attempt n mode right away even if your hardware supports it   * hw_mode=g  #to keep it simple don't attempt n mode right away even if your hardware supports it
   * channel=6  #or whatever other channel you prefer   * channel=6  #or whatever other channel you prefer
 +  * ieee80211d=1
 +  * country_code=IT
 +  * ieee80211n=1
 +  * auth_algs=1
   * macaddr_acl=1 # see notes below    * macaddr_acl=1 # see notes below 
   * # 0 = accept unless in deny list (iptables mac filtering and optionally have a ban list)   * # 0 = accept unless in deny list (iptables mac filtering and optionally have a ban list)
Line 121: Line 148:
   * wpa=2   * wpa=2
   * wpa_psk_file=/etc/hostapd/wlan0.wpa_psk   * wpa_psk_file=/etc/hostapd/wlan0.wpa_psk
-  * wpa_key_mgmt=WPA-PSK WPA-PSK-SHA256 +  * wpa_key_mgmt=WPA-PSK 
-  * wpa_pairwise=TKIP +
   * rsn_pairwise=CCMP   * rsn_pairwise=CCMP
   * wpa_group_rekey=600   * wpa_group_rekey=600
Line 177: Line 203:
  
   * interface=br0   * interface=br0
 +  * bogus-priv
 +  * local=/local/
 +  * domain=local
   * except-interface=lo   * except-interface=lo
-  * bind-interfaces 
   * listen-address=192.168.0.1   * listen-address=192.168.0.1
   * dhcp-range=192.168.0.2,192.168.0.254,24h   * dhcp-range=192.168.0.2,192.168.0.254,24h
   * dhcp-leasefile=/run/dnsmasq/dnsmasq.leases   * dhcp-leasefile=/run/dnsmasq/dnsmasq.leases
   * conf-dir=/etc/dnsmasq.d   * conf-dir=/etc/dnsmasq.d
 +The options local and domain allow dnsmasq to tell clients they belong to a domain and in return serve as authoritative for that domain. Some distributions that use NetworkManager will not get local resolution to work unless yo define these 2 options.
  
 The options except-interface bind-interfaces and listen-address are particularly useful if you want to run more then one instance of dnsmasq. The options except-interface bind-interfaces and listen-address are particularly useful if you want to run more then one instance of dnsmasq.
Line 192: Line 221:
 Now is a good time to configure your firwall protection. Now is a good time to configure your firwall protection.
 Supposing that the box will be routing packages thought it I'll show some rules that you might find helpfull. Supposing that the box will be routing packages thought it I'll show some rules that you might find helpfull.
 +
 +Newer kernels nswitched to nftables but you can still use iptables to manipulate the kernel netfilter tables.
 +Actually if you want to move to using nftables but you are not familiar with the syntax you can save the kernel netfilter tables in netfilter format like this:
 +
 +  nft list ruleset > nftables.conf
 +
 +Personally I'm still struggling with nft syntax so I will keep the rest of this chapter in iptabls syntax: you can convert, like I showed above, after you are done.
 + 
 This is the output of iptables-save, you can edit it to make the changes you require and then pipe your edited file to iptables-restore. This is the output of iptables-save, you can edit it to make the changes you require and then pipe your edited file to iptables-restore.
 The iptables-save/iptables-restore is a handy way of keeping configuration for easy firewall activation and editing. The iptables-save/iptables-restore is a handy way of keeping configuration for easy firewall activation and editing.
Line 396: Line 433:
  
 It should then be possible to restart rc.inet1 (or just rc.inet1 wlan0_down and rc.inet1 wlan0_up) and the client should associate. It should then be possible to restart rc.inet1 (or just rc.inet1 wlan0_down and rc.inet1 wlan0_up) and the client should associate.
 +
 +There's also the command line alternative with wpa_cli in this example we'll assume that your client is totally unconfigured and wpa_supplicant is not running. We're going to do everything on the command line:
 +
 +  # wpa_supplicant -B -W -Dwext -i wlan0 -c /etc/wpa_supplicant.conf
 +  # wpa_cli
 +  wpa_cli v2.4
 +  Copyright (c) 2004-2015, Jouni Malinen <j@w1.fi> and contributors
 +  
 +  This software may be distributed under the terms of the BSD license.
 +  See README for more details.
 +  
 +  Selected interface 'wlan0'
 +  
 +  Interactive mode
 +  
 +  > scan
 +  OK
 +  <3>WPS-AP-AVAILABLE 
 +  > scan_results
 +  bssid / frequency / signal level / flags / ssid
 +  02:0c:42:f9:73:23       2412    -58     [WPA-PSK-CCMP][WPA2-PSK-CCMP][ESS]
 +  a4:51:6f:95:37:b6       2462    -58     [WPA2-PSK-CCMP][WPS][ESS]       Windows Phone0377
 +  00:0c:42:f9:73:23       2412    -62     [ESS]   Insecure-WiFi  
 +  >  add_network
 +  0
 +  > set_network 0 ssid "Windows Phone0377"
 +  OK
 +  > set_network 0 psk "passwordforcrappywindowsphone"
 +  OK
 +  > enable_network 0OK
 +  OK 
 +  <2>Trying to authenticate with a4:51:6f:95:37:b6 (SSID='Windows Phone0377' freq=2437 MHz)
 +  <2>Trying to associate with a4:51:6f:95:37:b6 (SSID='Windows Phone0377' freq=2437 MHz)
 +  <2>Associated with a4:51:6f:95:37:b6
 +  <2>WPA: Key negotiation completed with a4:51:6f:95:37:b6 [PTK=CCMP GTK=CCMP]
 +  <2>CTRL-EVENT-CONNECTED - Connection to a4:51:6f:95:37:b6 completed (reauth) [id=0 id_str=]
 +  > save_config
 +  OK
 +  > quit
 +  #
 +  
 +If all went right and your wpa_supplicant.conf file had 
 +  update_config=1
 +in it the above snippet would have saved the new network to wpa_supplicant.conf and associated you with it.
 +
 +Remember that if you're associating with an non secured AP you need to use this:
 +  > set_network 0 ssid "Insecure-WiFi"
 +  OK
 +  > set_network 0 key_mgmt NONE
 +  OK
 +  >
 +
  
 ==== 4.7.3 Other Linux Distributions Wireless Clients ==== ==== 4.7.3 Other Linux Distributions Wireless Clients ====
-I've tried various other flavor distributions ... most don't use wpa_gui for associating to AP but  some sort of other tool that generally pops up when you click on the icon that notifies the presence of an Access Point. After a few headaches I found that best association success is achieved by forcing setup for hidden AP even if the AP I'm configuring has not the hidden essid.+I've tried various other flavor distributions ... most don't use wpa_gui for associating to AP but  some sort of other tool that generally pops up when you click on the icon that notifies the presence of an Access Point. After a few headaches I found that best association success is achieved by forcing setup for hidden AP even if the AP I'm configuring has not the hidden essid. You can always use wpa_cli on the command line if it's shipped with whatever distro you prefer.
  
  
Line 453: Line 542:
 You can dump dnsmasq's lease file to see the dhcp leases You can dump dnsmasq's lease file to see the dhcp leases
  
-  root@router:~# cat /run/dnsmasq/dnsmasq.leases +  root@router:~# cat /run/dnsmasq/br0.leases 
   1411875361 00:01:02:03:04:05 192.168.0.3 b3bo *   1411875361 00:01:02:03:04:05 192.168.0.3 b3bo *
   1411874427 0a:0b:0c:0d:0e:0f 192.168.0.4 printsrv *   1411874427 0a:0b:0c:0d:0e:0f 192.168.0.4 printsrv *
Line 507: Line 596:
 Please note the above script only works on 2.6 kernels or above. This probably also applies to socklist. Please note the above script only works on 2.6 kernels or above. This probably also applies to socklist.
  
-====== 6 Wrapping It Up ======+===== 5.5 Virtual AP ===== 
 +If your wireless NIC supports it you might like to run multiple virtual APs. As mentioned in Chapter 2 to be able to do this  
 +you will need the "valid interface combinations" sections to have #AP to be greater than one and if you optionally want them to live on separate channels you will need #channels to be greater than 1. 
 +If this is the case then you can add virtual AP like this 
 + 
 +  iw phy0 interface add vap0 type __ap 
 +or 
 +  iw wlan0 interface add vap0 type __ap 
 +   
 +this will create a new virtual AP, arbitrarily called vap0 on which you will need to activate a separate instance of hostapd as explained in Chapter 4. 
 +Incidentally the type can be any of of these (as long as your wireless NIC supports them): 
 + 
 +  * monitor 
 +  * managed  
 +  * wds 
 +  * mesh  
 +  * ibss  
 +  * __ap 
 + 
 + 
 +if you subsequentlt want to remove the virtual AP toy can terminate the hostapd running on it, optionally put the nick in down state and then tell iw you want to delete the virtual device: 
 + 
 +  iw vap0 del 
 +   
 + 
 +====== 6 Remote Administration ====== 
 +I'm not advocating that allowing remote administration from your WAN connection is a good thing but there are times where it may be necessary so here are some tips for minimizing the risk of having your router suffering brute force attacks or other bad things happen to it. 
 + 
 +I'm an old fashioned system administrator so for me remote administration is done via ssh, if you've added a nice web administration tool to your AP/Router keep in mind that running apache just for the sake of having remote web administration will expose you to a whole lot of security issues that need to be addressed and maintained over time.  
 + 
 +  - use non standard ports 
 +  - disallow password authentication 
 +  - minimize your attack surfaces 
 +Let me give you a little reasoning for the list. 
 + 
 +===== 6.1 Use Non Standard Ports ===== 
 +Whatever is your remote administration tool of choice it's a good idea not to leave access to it from WAN on it's well known port, making it less obvious that you run such a service. If you do this there's a good chance that your AP/Router will never get unwanted attention.  
 + 
 +===== 6.2 Disallow Password Authentication ===== 
 +Allowing password authentication is a welcome for brute force attacks so avoid it wherever possible (ie for ssh administrations only allow authentication with keys). If you're doing web based remote administration you could send in a key via get and then set a cookie or something like that along with password protected htaccess. 
 + 
 +===== 6.3 Minimize Your Attack Surfaces ===== 
 +Your AP/Router should expose to the WAN connection nothing more then what is really needed. Scanning your own AP/Router and closing or disabling unnecessary services to WAN is something you should allays do so that you minimize the attack surfaces should you ever get unwanted attention. 
 + 
 +==== 6.3.1 Avoid Running Remote Administration 24x7 ==== 
 +If you can have remote administration active only when you need it you're not leaving the attack surface available all the time but then you need an easy way to turn it on when you're away from home. 
 +I've two means of doing so: 
 +  * If any family member is home it can be temporarily activated by pressing a specific button on the router itself (it's the second button under the blue led in the images below). 
 +  * If nobody is home I've modified a 200 line minimal web server (nweb) to listen to requests on a non standard port and temporarily allow remote administration if a specific url is requested. 
 + 
 +Whichever way the temporary remote admin is enabled it also get's automatically turned off after some time (should you ever forget to turn it off once you're done). 
 + 
 +Nweb is a really basic webserver that only servers static html images and a few archive formats, it does not even allow directory listing. Besides that I have it parse and enable before serving the page ... so if you don't physically have the page that enables the remote administration a 403 is returned anyway leaving no clue as to waht was done in response to that request. 
 + 
 +If you're interested in nweb you can get it by googling "nweb tiny web server". You should hit github with something like nweb23.c with some 204 lines of C code. It should be easy for you to modify the source to match your needs. 
 +  
 + 
 + 
 +====== 7 Wrapping It Up ======
 Now that you've done the configuration maybe next time you want to start the AP you want to do it surely more efficiently. Now that you've done the configuration maybe next time you want to start the AP you want to do it surely more efficiently.
  
-===== 6.1 Simple Starter Script =====+===== 7.1 Simple Starter Script =====
 Just put a few commands in a script to start it up really quickly: Just put a few commands in a script to start it up really quickly:
  
Line 529: Line 676:
 If you want a neater solution totally integrated in the init scripts read on. If you want a neater solution totally integrated in the init scripts read on.
  
-===== 6.2 Modifying Slackware Init Scripts  =====+===== 7.2 Modifying Slackware Init Scripts  =====
 I've not yet done this but I can suggest a possible way of doing it. I've not yet done this but I can suggest a possible way of doing it.
  
Line 564: Line 711:
  
  
-===== 6.3 Automating AP Startup For USB WiFi Dongles =====+===== 7.3 Automating AP Startup For USB WiFi Dongles =====
 Udev is very powerful and can do a variety of actions upon detecting certain events, like the appearance of a NIC. In fact it already does that and renames interfaces according to MAC address (have a look at /etc/udev/rules.d/70-persistent-net.rules and see how your interfaces get the same name even if you remove the modules and reinsert them in the wrong order). Udev is very powerful and can do a variety of actions upon detecting certain events, like the appearance of a NIC. In fact it already does that and renames interfaces according to MAC address (have a look at /etc/udev/rules.d/70-persistent-net.rules and see how your interfaces get the same name even if you remove the modules and reinsert them in the wrong order).
 Apart from renaming NICs and creating device files it can also execute commands or external helper scripts ... this is particularly handy if, for example, you wish that upon plugging a USB Ethernet dongle it automatically assigns an address via DHCP. Apart from renaming NICs and creating device files it can also execute commands or external helper scripts ... this is particularly handy if, for example, you wish that upon plugging a USB Ethernet dongle it automatically assigns an address via DHCP.
Line 683: Line 830:
 I used to devote 2 usb dongle for this: one that would be left inserted most of the time and has random generated WAP-PSK (only for family use) and one that would get temporarily plugged in for guests with a much simple WPA-PSK to aid them accessing my home network.  I used to devote 2 usb dongle for this: one that would be left inserted most of the time and has random generated WAP-PSK (only for family use) and one that would get temporarily plugged in for guests with a much simple WPA-PSK to aid them accessing my home network. 
  
-==== 6.3.1 Automation With Custom Scripts ====+==== 7.3.1 Automation With Custom Scripts ====
 Over the years trying to maintain modified rc scripts functional across updates that involved the rc scripts themselves became cumbersome so I started moving away from modifying the stock scripts and started developing my own stuff. Don't get me wrong I still use and appreciate the stock stuff for my desktop systems.  Over the years trying to maintain modified rc scripts functional across updates that involved the rc scripts themselves became cumbersome so I started moving away from modifying the stock scripts and started developing my own stuff. Don't get me wrong I still use and appreciate the stock stuff for my desktop systems. 
 The idea behind my own scripts is based on udev detecting the interfaces (even at boot time). The basic idea is still the same: upon detection udev executes nethelper.sh script that looks for and executes /etc/rc.d/network/<NIC> start. This is not for everyone because it requires manually writing the /etc/rc.d/network/<NIC> script but I think most have the basic knowledge and maybe with a little help most can manage. The idea behind my own scripts is based on udev detecting the interfaces (even at boot time). The basic idea is still the same: upon detection udev executes nethelper.sh script that looks for and executes /etc/rc.d/network/<NIC> start. This is not for everyone because it requires manually writing the /etc/rc.d/network/<NIC> script but I think most have the basic knowledge and maybe with a little help most can manage.
Line 822: Line 969:
 If you've gone so far you might want a neater way to deal with unplugging dongles as anything udev could possibly do would be too late. One possible approach is to use gpio pins with buttons attached to them and a script that monitors the button status and takes appropriate action when each button is pressed. I've done this on mi RPi2 with 5 buttons and 5 leds indicating whether the button press has been caught by the monitor script: one shuts down the RPI2 while the other 4 are for deactivating whatever is in the respective usb port to prepare it for unplugging. If you've gone so far you might want a neater way to deal with unplugging dongles as anything udev could possibly do would be too late. One possible approach is to use gpio pins with buttons attached to them and a script that monitors the button status and takes appropriate action when each button is pressed. I've done this on mi RPi2 with 5 buttons and 5 leds indicating whether the button press has been caught by the monitor script: one shuts down the RPI2 while the other 4 are for deactivating whatever is in the respective usb port to prepare it for unplugging.
 Here's a [[http://i246.photobucket.com/albums/gg113/louigi600/ARM/IMG_20160109_084509_zpshwu4p9x9.jpg|picture]] of such a setup while the script for handling it is [[http://www.linuxquestions.org/questions/slackware-arm-108/initiating-shutdown-from-a-button-press-4175494505/page3.html#post5476882|here]]. Here's a [[http://i246.photobucket.com/albums/gg113/louigi600/ARM/IMG_20160109_084509_zpshwu4p9x9.jpg|picture]] of such a setup while the script for handling it is [[http://www.linuxquestions.org/questions/slackware-arm-108/initiating-shutdown-from-a-button-press-4175494505/page3.html#post5476882|here]].
-====== 7 Setting up on an Embedded Device ======+====== 8 Setting up on an Embedded Device ======
 Supposing you want all this but you don't want to leave a laptop or desktop on all the time you might want to put in on an embedded ARM system that will only use a fraction of the power required to run an X86 laptop/desktop of any sort. (intel Curie might kick in with a 2.2W x86 SOC when the segfault bug is sorted out). Supposing you want all this but you don't want to leave a laptop or desktop on all the time you might want to put in on an embedded ARM system that will only use a fraction of the power required to run an X86 laptop/desktop of any sort. (intel Curie might kick in with a 2.2W x86 SOC when the segfault bug is sorted out).
 Well the official ARM Slackware port userland runs on almost any ARM device out in the market today. There is a number of machines that are officially supported from the ARM port and a god deal of [[http://docs.slackware.com/howtos:hardware:arm:start | community supported efforts]] for the platforms that are not officially supported. Well the official ARM Slackware port userland runs on almost any ARM device out in the market today. There is a number of machines that are officially supported from the ARM port and a god deal of [[http://docs.slackware.com/howtos:hardware:arm:start | community supported efforts]] for the platforms that are not officially supported.
Line 849: Line 996:
   * save the random-seed to unused sector on flash when shutting down (rc.0 ... well it's a link to rc.6) and load it back to /dev/urandom from rc.S when system comes up again   * save the random-seed to unused sector on flash when shutting down (rc.0 ... well it's a link to rc.6) and load it back to /dev/urandom from rc.S when system comes up again
  
-You could optionally have fstab specify that root should be mounted ro like this:+You could optionally have fstab specify that root should be mounted ro like this: (example below is relative to when I was using ubifs on the DocStar)
  
-/dev/ubi0_0      /               ubifs  ro                 0       1+  /dev/ubi0_0      /               ubifs  ro                 0       1
  
-You will also haveto make some links in various places so that they end up writing in /run that has been mounted tmpfs. I do that manually just once with / mounted rw and then remount it ro.+You will also have to make some links in various places so that they end up writing in /run that has been mounted tmpfs. I do that manually just once with / mounted rw and then remount it ro.
  
 If you're interested in actually making such changes to the init scripts I've shared how I go about it on [[http://www.linuxquestions.org/questions/slackware-arm-108/anyone-else-interested-in-running-some-of-their-arm-devices-with-root-mounted-read-only-4175590642/ | Linux Questions]]. If you're interested in actually making such changes to the init scripts I've shared how I go about it on [[http://www.linuxquestions.org/questions/slackware-arm-108/anyone-else-interested-in-running-some-of-their-arm-devices-with-root-mounted-read-only-4175590642/ | Linux Questions]].
-====== 8 Unexpected Trouble Sources ======+====== 9 Unexpected Trouble Sources ======
 When you start doing your own stuff you may run into problems that are hard to debug because the cause is pretty much unexpected. When you start doing your own stuff you may run into problems that are hard to debug because the cause is pretty much unexpected.
  
Line 867: Line 1014:
 Obviously there may be innumerable other trouble source you may run into (some of which you have no control ... like when your ISP makes clumsy NAT for you) but if you're doing your own stuff be prepared to put up and debug them. Obviously there may be innumerable other trouble source you may run into (some of which you have no control ... like when your ISP makes clumsy NAT for you) but if you're doing your own stuff be prepared to put up and debug them.
  
-====== 9 Conclusions ======+====== 10 Conclusions ======
 You have set up an AP with entry level security and the most common options available in the low end appliances but you have gained: You have set up an AP with entry level security and the most common options available in the low end appliances but you have gained:
   * ability to easily keep your AP software up-to date    * ability to easily keep your AP software up-to date 
Line 884: Line 1031:
 I'm not going to miss my old low end AP, are you ? I'm not going to miss my old low end AP, are you ?
 I replaced it with home-brew stuff from which this article is derived. I replaced it with home-brew stuff from which this article is derived.
-Over the years I've done several remakes adding some new features. The last upgrade was 8 programmable buttons with indicator leds to carry out arbitrary functions.+Over the years I've done several remakes adding some new features. The last upgrade was using a Friendlyelec NanoPi R1S with integrated wifi and 2 ethernet nics requiring no extra usb dongles. 
 + 
 +Gen 5 (Friendlyelec NanoPI R1S) 
 + 
 +{{howtos:network_services:g5_nanopi.jpeg| NanoPi R1S}} 
 + 
 +The original case has 2 issues: cappy internal antenna and tendency to overheat ... so I 3d-printed my own [[https://www.thingiverse.com/thing:5408048|case]]. 
 + 
 +{{howtos:network_services:nanopi_r1s_diy_case.jpg| DIY Case}} 
 + 
 +Gen 4 (RPi2 with display) 
 + 
 +{{howtos:network_services:g4_rpi.jpeg| RPi2 with shoft buttons}} 
 + 
 + 
 +Gen 3 (RPi2 with buttons and leds) 
 + 
 +{{howtos:network_services:g3_rpi.jpg| RPi2 with hardware buttons}} 
 + 
 +Gen 2 (RPi2 in aluminum Sandwich) 
 + 
 +{{howtos:network_services:g2_rpi.jpg| RPi2}} 
 + 
 +Gen 1 (Seagate DocStar in aluminum Sandwich)
  
-{{http://i246.photobucket.com/albums/gg113/louigi600/ARM/piwrap_zpshjjyflm8.jpg}} +{{howtos:network_services:g1_seagate_docstar.jpg| Seagate DocStart}}
-{{http://i246.photobucket.com/albums/gg113/louigi600/ARM/RPi2_2_zpsytug1dvq.jpg}} +
-{{http://i246.photobucket.com/albums/gg113/louigi600/ARM/Seagate_wrapStar_zpsf6047f16.jpg}}+
  
  

Trace: • sycamorex • mfillpot • cross_compiling_the_linux_kernel • roaming_profiles • install_fonts • setup_apache_php_mysql • development_refguide_di • tracking_updates • installing_tor_using_a_slackbuild_script

howtos:network_services:running_an_access_point_from_a_slackware_box ()