Updated FAQs (markdown)

FAQs.md

@@ -3,7 +3,8 @@ This has been written to address some frequently encountered issues among users
 * [My custom rc.local/networking configuration/wpa configuration is gone!](#custom)
 * [How do I remove RaspAP?](#uninstall)
 * [What are the steps to upgrade RaspAP?](#upgrade)
-* [RaspAP control panel works but there is no WiFi after reboot](#nowifi)
+* [RaspAP control panel works but there is no WiFi after reboot.](#nowifi)
+* [Do I need the RaspAP service to run at boot?](#raspap-service)
 * [How do I integrate RaspAP with Pi-hole?](#pihole)
 * [Can I configure RaspAP to work with a captive portal?](#captive)
 * [Why can't I access wireless mode 'N' (802.11n)?](#wireless-mode)
@@ -35,34 +36,23 @@ sudo git pull origin master
 ```
 Whichever method you choose (specific release or latest updates), your RaspAP configuration won't be changed.
 
-### <a name="nowifi"></a>RaspAP control panel works but there is no WiFi after reboot
+### <a name="nowifi"></a>RaspAP control panel works but there is no WiFi after reboot.
-The problem is often caused when another program tries to re-configure hostapd at startup (pi-hole is an example). What you need to do is create a shell script that tries to ping a device IP on your network. If it fails then you should stop/start hostapd.
+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:
 
-```bash
-#!/bin/bash
-
-Blue='\033[0;34m'
-Green='\033[0;32m'
-
-if ping -c 1 10.3.141.254 &> /dev/null
-then
- echo -e "${Green}Wifi Works Fine"
-else
- echo -e "${blue}Restarting Wifi"
- service hostapd stop; service hostapd start
-fi
 ```
-save the file as `netfix` then follow these steps
+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.
+ 
+### <a name="raspap-service"></a>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:
 
-```bash
-sudo chmod +x netfix
-sudo crontab -e
 ```
-add the following line at the end of the file
+sudo systemctl disable raspap.service
-```bash
-@reboot /home/pi/netfix
 ```
-**note:** replace `10.3.141.254` with a device IP on your network. (other than 10.3.141.1). The only downside of this method is that no matter the device is offline or unreachable, this script will execute at startup. But it's not that noticeable.
 
 ### <a name="pihole"></a>How do I integrate RaspAP with Pi-hole?
 [Pi-hole®](https://github.com/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.