Just from the installation with sudo apt install hostapd there is nothing configured for the service. hostapd has no default setup so it doesn't make sense to start the service without it. To avoid possible confusion I suppose the package manager has decided to mask the service on installation. Just disable it is not enough to be on the save side because a ...
I see that the man pages for hostapd are quite useless
I found a more useful page https://wiki.gentoo.org/wiki/Hostapd with the following example
802.11a/n/ac with WPA2-PSK and CCMP
A simple but secure AP for recent hardware:
interface=wlan0 # the interface used by the AP
You have to do three steps:
create a virtual interface ap0 for the access point
start access point daemon hostapd using interface ap0
start wpa_supplicant for wifi client using interface wlan0
You have to do it exactly in this order otherwise the setup will fail. I have seen many attempts to achieve this including restarting services in order with special ...
I was redirected here from the excellent thread of Ingo because I'm trying to make my RPi3 to act as WiFi extender.
Like you, I followed every steps and I noticed that a device connected to the extended WiFi network couldn't get any DNS address from the primary Wireless router.
Something draws my attention on Troubleshooting section. @Ingo explains that ...
I've resolved by myself, I have made a script in bash that restart the hostapd service with
service hostapd restart
and make it executable with
sudo chmod +x /location/file
and make the file executable without asking for password, adding in the file
[your_username] ALL= NOPASSWD: /location/of/file
You also asked: "Maybe you got even hints for a better solution in general." I prefer to use systemd-networkd because it has all in one. Using two USB/wifi dongle simplifies it a lot. So my hint is to look at Access point as WiFi repeater with additional WiFi-dongle. It does not fit exactly your needs but it should not be a big problem to adapt it to your ...
You have configured a bridge with slave interfaces eth0 and wlan0. Everything looks good.
You only have one (virtual) interface br0 with an ip address 192.168.1.90. Don't be confused by eth0 and wlan0. As slaves of the bridge they have lost their normal IP characteristics and only work on the OSI data link layer with MAC addresses. The normal interface of ...
After reading up on the concepts discussed in Ingo's replies I realised my (admittedly stupid) mistake! I had the device configured as a bridge, meaning that the the Pi itself wasn't assigning IP address's to the connected devices, simply providing an interface between the connected devices and the router!
The solution involved a combinational approach of ...
The important messages seem to be:
nl80211: Set mode ifindex 3 iftype 3 (AP)
nl80211: Failed to set interface 3 to mode 3: -95 (Operation not supported)
nl80211: Interface mode change to 3 from 0 failed
nl80211: Could not configure driver mode
For my interpretation hostapd tries to set the interface to mode 3 (AP) that is an access point (line 1). But the ...
Did you update your Pi?
If not run sudo apt-get update && upgrade, you Pi needs to update once in a while, it happends to me if I do not update it, and if that does not fix it run, sudo apt-get update --fix-missing
What is a IMX7 device? Is it a Raspberry Pi? The tutorial you have linked to is made for a Raspberry Pi with extensive using systemd-networkd and its dependency management. Look at the Details - General section. There are three steps that must always be done in a strict order.
I suppose connman (you don't gave a link) is one of the scripts that automated ...
To have the access point and the ethernet port using the same ip address range, means using the same subnet, you have to setup a bridge br0 and then add as members the interfaces eth0 and wlan0.
Because you are already use hostapd and dnsmasq you may have a look at Setting up a Raspberry Pi as an access point in a standalone network (NAT) how to do it with ...
This issue comes from kernel and hostapd service in raspbian jessie. In your logs in 385 line you can notice that 4-way handshake has never ending and it stoped on third step. It could be exception in pseudorandom generator.
You can use external WiFi dongle as a workaround now, or wait for a patch.
SSH is what you're looking for. If you connect your RPI ethernet port to your router you can use arp -a (linux, mac) to see all IP addresses on your network. You will likely see your pi as pi (192.168.1.15) or something along those lines.
Once you find the pi IP you can connect to the raspberry pi using the ssh command. When connecting to the ...
As far as I see you only want to setup a stand alone access point but there are some things mixed up. First you are using deprecated commands ifconfig and iwconfig. You should use its modern successors ip from iproute2 and iw.
Everywhere you are using sleeps. When nothing works a sleep mostly helps but it indicates that there is something wrong with service ...
Please take note that using /etc/rc.local has limitations due to Compatibility with SysV. Following the recommendation of the developers from systemd you should avoid using rc.local.
In addition your script is doing things that assumes that hostapd is up and running. That may or may not be possible because there is no dependency to start your script After=...
You need to check the sections IEEE 802.11n related configuration (IEEE 802.11n in the 2.4GHz band is available e.g. with the built-in Wifi chip of the Raspberry Pi 3B) and IEEE 802.11ac related configuration in case your wifi chip is capable of IEEE802.11ac (as is the built-in wifi chip of the Raspberry Pi 3B+).
The comments in the config file already give ...