Bridged AP mode
This wiki page has been sunsetted in favor of RaspAP Docs. You will find an updated page at:
By default RaspAP configures a routed AP as its hotspot, where your RPi creates a subnet and assigns IP addresses to its hotspot clients. If you would rather have your upstream router assign IP addresses, RaspAP lets you easily change the hotspot configuration to an alternative bridged AP. This is also useful if you want your RPi and its hotspot clients to be visible to other devices in your router's network.
In the RaspAP web interface, go to Hotspot > Advanced tab, then slide the Bridged AP mode toggle. Save settings then Restart hotspot.
Bridged AP mode has some limitations compared to RaspAP's default routed AP.
Hotspot > Advanced tab > Wifi Client AP mode is disabled. Your RPi cannot connect as a client to another Wifi network while simultaneously hosting its own bridged AP (hotspot).
DHCP Server page is disabled. In bridged AP mode, your upstream router is the DHCP server. Use your router's web interface to configure DHCP settings.
Clients connected to a bridged AP with OpenVPN enabled will not have their traffic routed through the VPN server. Your RPi itself will still have its own traffic routed through the VPN server.
In bridged AP mode, you will no longer be able to access RaspAP's web interface using the default 10.3.141.1 address. This is because your RPi no longer creates its own 10.3.141.0/24 subnet for its hotspot. Instead, access RaspAP's web interface by entering your RPi's hostname followed by .local. By default this will look like raspberrypi.local.
Some browsers have trouble resolving .local addresses. You might have to modify the address depending on your browser: http://raspberrypi.local or raspberrypi.local/.
If none of the above work, use your RPi's local IP address. Find it by checking your router's web interface or by entering the following command from your RPi terminal.
ifconfig br0 | grep 'inet ' | awk '{print $2}'
Contributed by @Taikuh
