Skip to content
Bill Zimmerman edited this page Apr 21, 2019 · 17 revisions

This has been written to address some frequently encountered issues among users of RaspAP.

My custom rc.local/networking configuration/wpa configuration is gone!

Currently, RaspAP generates a few of its own files so that it starts with a known configuration. Your custom configurations haven't been lost however, they've been moved to the backups directory in /etc/raspap/backups.

Feel free to SSH in to restore those files to their rightful position, however, you may need to ensure that the RaspAP modifications are applied to your own custom configurations.

How do I remove RaspAP?

We have provided an uninstall script to remove RaspAP cleanly, and also restore any backups of your configuration that were created when RaspAP was installed. The uninstall script is located in installers/uninstall.sh.

What are the steps to upgrade RaspAP?

Upgrading your current install to a specific release is very straightforward. For example, to upgrade to release version 1.5, enter the following in the RaspAP install folder (default location is /var/www/html):

sudo git fetch --tags
sudo git checkout tags/1.5

A tag is a pointer that isn't connected to the main development tree that git knows about. As a result, git will reply that you're in a 'detached HEAD' state. This isn't a big deal, it just means that you have a specific version of the code that isn't connected to the git tree.

Alternatively, if you want the latest bleeding edge commits from the master branch, use the following:

sudo git checkout master
sudo git pull origin master

Whichever method you choose (specific release or latest updates), your RaspAP configuration won't be changed.

RaspAP control panel works but there is no WiFi after reboot.

This problem is often caused when another program tries to re-configure hostapd at startup. It may also occur when your RPi is configured as both a WiFi client and access point. To address this, RaspAP has added a systemd init service to bring up networking services in a predictable order and timing after the Linux kernel is booted. You can check the status of this service with:

sudo systemctl status raspap.service

The raspap.service is optionally installed and enabled by the Quick Installer. It is also included in the manual setup steps.

Do I need the RaspAP service to run at boot?

If you are using your RPi as a client on a WiFi network (also known as managed mode) and hosting an access point simultaneously, the raspap.service will ensure that your hotspot is active after a reboot. It does this by detecting WiFi client AP mode, adding the uap0 interface and starting up networking services in a specific order.

If your RPi is configured with wired ethernet (eth0) or you haven't experienced problems with the AP starting on boot, you can disable the RaspAP daemon like so:

sudo systemctl disable raspap.service

How do I integrate RaspAP with Pi-hole?

Pi-hole® is a popular RPi-based project that blocks ads network-wide by creating a DNS sinkhole. There have been several discussions around integrating RaspAP with Pi-hole, with the end goal of hosting a complete AP and ad-blocker on a single device. This is possible with a few modifications, essentially giving permission to Pi-Hole to manage dnsmasq leases.

Follow these steps in the order below:

  1. Install RaspAP
  2. Install Pi-Hole
  3. sudo touch /var/lib/misc/dnsmasq.leases
  4. sudo chown pihole:pihole /var/lib/misc/dnsmasq.leases
  5. Reboot manually or sudo reboot

(source)

Please note: Pi-hole integration is not officially supported by this project. Therefore, bug reports will not be addressed.

Can I configure RaspAP to work with a captive portal?

Yes, the nodogsplash project works just fine with RaspAP and is recommended over other methods. No configuration changes are needed with raspap-webgui, however you will need to modify some default settings in the nodogsplash config.

The nodogsplash GatewayInterface should be set to the interface RaspAP runs on (wlan0 is used by the Quick Installer). You will also need to change the GateWayAddress to 10.3.141.1.

sudo nano /etc/nodogsplash/nodogsplash.conf

# Default: NONE
#
# GatewayInterface is not autodetected, has no default, and must be set here.
# Set GatewayInterface to the interface on your router
# that is to be managed by Nodogsplash.
# Typically br-lan for the wired and wireless lan.
#
GatewayInterface wlan0
# Parameter: GatewayAddress
# Default: Discovered from GatewayInterface
#
# This should be autodetected on an OpenWRT system, but if not:
# Set GatewayAddress to the IP address of the router on
# the GatewayInterface.  This is the address that the Nodogsplash
# server listens on.
#
GatewayAddress 10.3.141.1

Give the nodogsplash service a kick:

sudo systemctl restart nodogsplash

...and verify that the service is running:

sudo systemctl status nodogsplash

   Loaded: loaded (/lib/systemd/system/nodogsplash.service; enabled; vendor preset: enabled)
   Active: active (running) since Sat 2019-03-02 07:55:11 UTC; 11min ago
  Process: 3404 ExecStart=/usr/bin/nodogsplash -d 5 $OPTIONS (code=exited, status=0/SUCCESS)
 Main PID: 3405 (nodogsplash)
   CGroup: /system.slice/nodogsplash.service
           └─3405 /usr/bin/nodogsplash -d 5

Point your browser to http://10.3.141.1 and you should see the default nodogsplash page.

image

Why can't I access wireless mode 'N' (802.11n)?

On the Configure hotspot > Security tab, be sure to select CCMP for the Encryption Type. Save the settings and restart the hotspot. The wireless mode should be reported on clients as 802.11b/g/n.

RaspAP:
  PHY Mode:		802.11n
  Channel:		1
  Network Type:		Infrastructure
  Security:		WPA2 Personal
  Signal / Noise:	-49 dBm / -86 dBm
  Transmit Rate:	73

If using TKIP for encryption with WPA, you will be restricted to 54 Mb/s. This is because the IEEE 802.11n draft prohibits using high throughput with WEP or TKIP ciphers.

How do I prepare the SD card to connect to WiFi in headless mode?

Since May 2016, Raspbian has been able to copy wifi details from /boot/wpa_supplicant.conf into /etc/wpa_supplicant/wpa_supplicant.conf to automatically configure wireless network access.

An example wpa_supplicant.conf file is shown below. Replace the fields with your settings:

ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev
update_config=1
country=your_ISO-3166_two-letter_country_code

network={
    ssid="my_SSID"
    psk="my_PSK"
    key_mgmt=WPA-PSK
}

Can I use wlan0 and wlan1 rather than eth0 for my AP?

The short answer is yes. In this scenario, you may wish to use the built-in wlan0 interface with a USB wlan1 connection, rather than wired ethernet (eth0). This is partly supported by RaspAP, although you will need to make two small updates.

Change the following setting in includes/config.php to wlan1:

define('RASPI_WIFI_CLIENT_INTERFACE', 'wlan1')

...add the following to /etc/dhcpcd.conf:

nohook wpa_supplicant

...and finally restart hostapd.

You can’t perform that action at this time.