Frank ...
Firstly thx for yr additional improvements (add haveged and to hostapd.conf).
After many hours spent on this, here are my conclusions about an AP (not using NAT) on an
RPi2 ...
I’ve got an AP working using a generic dongle with a Ralink chipset RT RT5370 and have successfully changed the SSID name & Pass phrase and the AP’s ip address.
But I have failed to get the same result with an Edimax dongle which uses a Realtek chipset. The Rune Network UI shows wlan0 connected to my selected AP ip address with my selected SSID name. My wifi discovery program (InSSIDer) shows Rune_AP (my selected name) to be broadcasting on channel 7. However I cannot connect to Rune_AP from my Windows 10 laptop or from my Nexus Android tablet.
My debug report is ...
http://pastebin.com/tuNekrZcAlso running the command below gave the following ...
[root@runeaudio ~]# /usr/sbin/hostapd /etc/hostapd/hostapd.conf
Configuration file: /etc/hostapd/hostapd.conf
Could not set channel for kernel driver
Interface initialization failed
wlan0: interface state UNINITIALIZED->DISABLED
wlan0: AP-DISABLED
wlan0: Unable to setup interface.
wlan0: interface state DISABLED->DISABLED
wlan0: AP-DISABLED
hostapd_free_hapd_data: Interface wlan0 wasn't started
nl80211: deinit ifname=wlan0 disabled_11b_rates=0
[root@runeaudio ~]#
I don’t know whether the above is helpful?
I am mindful that several months ago when building an RPi just as an AP that online tutorials needed to provide a modified version of hostapd which solved Edimax/Realtek driver problems (ref AdaFruit & Dave Conroy).
The following link is informative ....
https://github.com/oblique/create_ap/blob/master/howto/realtek.mdCould yr success with Edimax be related to the RPi3 built in wifi or yr choice of ip address (192.168.1.1) which is commonly used by routers? I’m clutching at straws for understanding yr success and my failure.
Thx