1
0
mirror of https://github.com/billz/raspap-webgui.git synced 2023-10-10 13:37:24 +02:00

typo

Bill Zimmerman 2020-08-18 13:44:58 +02:00
parent 3538a7f7d4
commit a6df451dbe

@ -26,10 +26,10 @@ The second valid interface combination indicates that both a `managed` and `AP`
There are many scenarios in which AP-STA mode might be useful. These are some of the more popular ones:
1. A device that connects to a wireless AP but needs an admin interface to configure the network and/or other services.
2. A a hub for Internet of Things devices, while also creating a bridge between them and the internet.
2. A hub for Internet of Things devices, while also creating a bridge between them and the internet.
3. A guest interface to your home wireless network.
Security is an important consideration with IoT and it can be beneficial to keep your devices on a separate network for safetys sake. No one wants a random internet user turning your lights on and off.
Security is an important consideration with IoT and it can be beneficial to keep your devices on a separate network, for safetys sake. No one wants a random internet user turning your lights on and off.
### How does AP-STA work?
In this configuration, we create a virtual network interface (here `uap0`) and use it instead of `wlan0` on the AP side. This virtual interface is used by several of the services needed to operate a software access point. RaspAP manages these configurations in the background for you. Relevant sections are displayed below as examples.
@ -53,7 +53,6 @@ interface=uap0
# RaspAP uap0 configuration
interface=lo,uap0 # Use interfaces lo and uap0
bind-interfaces # Bind to the interfaces
server=8.8.8.8 # Forward DNS requests to Google DNS
domain-needed # Don't forward short names
bogus-priv # Never forward addresses in the non-routed address spaces
```
@ -65,7 +64,7 @@ iw dev wlan0 interface add uap0 type __ap
ifconfig uap0 up
```
With the virtual `uap0` interface added to the `wlan0` physical device, we can then start up `hostapd`. It is important that the virtual interface is brought up first, otherwise it will fail with the message "could not configure driver mode". We also need to be sure that the interface is not managed by `systemd-networkd`, so this service should be disabled. These steps are handled by the RaspAP daemon `raspapd.service`.
After the virtual `uap0` interface is added to the `wlan0` physical device, we can then start up `hostapd`. It is important that the virtual interface is brought up first, otherwise it will fail with the message "could not configure driver mode". We also need to be sure that the interface is not managed by `systemd-networkd`, so this service should be disabled. These steps are handled by the [RaspAP daemon](https://github.com/billz/raspap-webgui/wiki/FAQs#raspap-service).
With a basic understanding of AP-STA mode, we can proceed with the installation.