RPi + Runeaudio +Wifi as Accesspoint

[johnbanks]

Frank/Dror ...
Thanks for your inputs.
I'm away from home for a few days so will try again on my return.
Once I get it running on an RPi2, I'll try on my RPi3 and will report back.
Frank - I don't think you should be despondent.
Your solution will be particularly popular when the next image is released and it can be installed just by wireless.
There must be many users like me who do not have a wired LAN connection where their Rune & hifi speakers are located.
Regards

[Mat]

[hondagx35]

[dror]

Hi,
Some more impressions/issues
First, after changing the AP configuration - for example, I tried to turn off the NaT and to turn off the AP (using the commands you post of course), then executing a reboot via ssh - the pi is not responsive. You need to unplug the power cord and replug for the reboot and the changes take effect.
Turning them on and reboot worked for me though

Second, the NaT off configuration is not working as expected. My android connects to the AP, and as expected there is an examination mark ("!") near the wifi sign indicating there is no internet access. The problem is - you can't access the UI no matter what I put into as the web address. Moreover, network diagnostic utility I use - "Fing" - can't analyse the network. You do get an IP though .

Third but probably an off topic (please tell me if so, I will open a new thread) -with the great working NaTed configuration, the DLNA renderer is not visible through my Android - But - I do see the Airplay renderer, and the DLNA renderer IS visible to my PC on the network.

Thanks,
Dror

[hondagx35]

[hondagx35]

[JERKBALL]

[hondagx35]

[johnbanks]

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 ...

Also 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 ....

Could 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

[hondagx35]