Skip to content
This repository has been archived by the owner on Sep 30, 2021. It is now read-only.

Raspberry Pi 3A+ Cannot be AP and Station #388

Closed
frankgould opened this issue Mar 20, 2019 · 0 comments
Closed

Raspberry Pi 3A+ Cannot be AP and Station #388

frankgould opened this issue Mar 20, 2019 · 0 comments

Comments

@frankgould
Copy link

OS: Arch Linux ARM, 4.14

I'm trying to get two RPi 3A+ units to communicate with each other using sockets and to stream
video over the same SSID. When I use a RPi 3B with ethernet to setup/test, I have no problem but when running on the RPi3A+, I get the brmfmac warning below. Does this mean RPi3A+ is not supported due to the driver?

    echo "WARN: brmfmac driver doesn't work properly with virtual interfaces and" >&2
    echo "      it can cause kernel panic. For this reason we disallow virtual" >&2
    echo "      interfaces for your adapter." >&2
    echo "      For more info: https://github.com/oblique/create_ap/issues/203" >&2

On the RPi3B, I also to tried the suggestions by Oblique but it returned the command failed due to busy.

[root@remote ~]# iw dev wlan0 interface add ap0 type __ap
command failed: Device or resource busy (-16)

When I tried the command above on RPi3A+, it logged me out and back on the terminal window and the SSID appears in the scan results; however, it did not respond to ping. Below are the iw list combinations for the RPi3A+.

 valid interface combinations:
  * #{ managed } <= 1, #{ P2P-device } <= 1, #{ P2P-client, P2P-GO } <= 1,
    total <= 3, #channels <= 2
  * #{ managed } <= 1, #{ AP } <= 1, #{ P2P-client } <= 1, #{ P2P-device } <= 1,
    total <= 4, #channels <= 1
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant