You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I observed this bug on a clean install of the OS [x]
I have followed the project prerequisites [x]
I have searched this repository for existing issues [x]
I checked the FAQ and official documentation before creating this issue [x]
I have read and understand the issue reporting guidelines [x]
Bug description
Wi-Fi information on GUI shows nothing
Your environment
Operating System: RPI OS 32-bit Lite
Hardware and version: Raspberry Pi 4 Model B Rev 1.4
RaspAP version: RaspAP v2.9.2
Clean install of a compatible operating system? Yes
RaspAP Quick Install or Manual setup? Quick Install/Manual
Using default configuration? Yes
Simultaneous AP and managed mode? No
Onboard wireless chipset or external adapter? Onboard
Other software or services running with RaspAP? No
Steps to reproduce
My raspapd.service seems to be starting the uap0 interface on ExecStart, but I don't have it because I am using eth0 (Internet) and wlan0 for (hotspot).The scripts (/etc/raspap/hostapd/servicestart.sh)
seemed to be starting uap0 towards the end with Ifconfig up uap0. Why is it focusing on the interface I don't have? Could that be what's causing the problem?
Additional context
Wlan0 ip range is 10.3.141.0/24
The text was updated successfully, but these errors were encountered:
As the name suggests, the dashboard widget displays info about a configured wireless client - not your AP.
The raspapd.service only manipulates uap0 if AP-STA mode is enabled.
Checklist
Bug description
Wi-Fi information on GUI shows nothing
Your environment
Steps to reproduce
My raspapd.service seems to be starting the uap0 interface on ExecStart, but I don't have it because I am using eth0 (Internet) and wlan0 for (hotspot).The scripts (/etc/raspap/hostapd/servicestart.sh)
seemed to be starting uap0 towards the end with Ifconfig up uap0. Why is it focusing on the interface I don't have? Could that be what's causing the problem?
Additional context
Wlan0 ip range is 10.3.141.0/24
The text was updated successfully, but these errors were encountered: