search

MkLHX / AP_STA_RPI_SAME_WIFI_CHIP

Configures simultaneous AP and Managed Mode Wifi on Raspberry Pi with the same wifi chip
https://mklhx.github.io/AP_STA_RPI_SAME_WIFI_CHIP/
GNU General Public License v3.0
38 stars 14 forks source link

Device or resource busy (-16) #27

Open eroom1966 opened 1 month ago

eroom1966 commented 1 month ago

Hi I would really like to get this working on my RPi3, but am facing a few issues.

Firstly I should say, my installation has gone through a few iterations where I have had to upgrade from earlier versions of raspbian, and hence I think it is possible I have a lot of history with starting up the network interfaces which are conflicting with this setup

Previously I had a a WiFi dongle in addition to the builtin Wifi, this allowed me to configure the builtin WiFi wlan0 as an access point, and the USB Wifi wlan1, as a station.

Having updated my installation to Buster, I have removed the WiFi dongle, and having run your script to setup AP + STA, I look at my interfaces, I see the following

$ ifconfig

eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.0.16  netmask 255.255.255.0  broadcast 192.168.0.255
        inet6 fe80::cb51:1b17:7a3b:a087  prefixlen 64  scopeid 0x20<link>
        ether b8:27:eb:6a:f7:b3  txqueuelen 1000  (Ethernet)
        RX packets 1207  bytes 325131 (317.5 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 1348  bytes 169157 (165.1 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 4536  bytes 387212 (378.1 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 4536  bytes 387212 (378.1 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wg0: flags=209<UP,POINTOPOINT,RUNNING,NOARP>  mtu 1420
        inet 10.200.0.44  netmask 255.255.255.255  destination 10.200.0.44
        unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00  txqueuelen 1000  (UNSPEC)
        RX packets 4  bytes 380 (380.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 5  bytes 468 (468.0 B)
        TX errors 3  dropped 0 overruns 0  carrier 0  collisions 0

wlan0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether b8:27:eb:3f:a2:e6  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

You can see the wlan0 interface above, also my eth0 and wg0 which is a wireguard interface to my private network Unfortunately I don't really know where to look next - any help greatly appreciated Happy to post any other diagnostics that can help me resolve my issue

github-actions[bot] commented 1 month ago

Message that will be displayed on users' first issue

eroom1966 commented 1 month ago

An update, after my system was up for a minute, I noticed a new interface appear

rename4: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether b8:27:eb:3f:a2:e6  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

and interestingly if I run "dmesg | grep rename" [ 11.503402] brcmfmac mmc1:0001:1 rename4: renamed from ap0