Page 11 of 12

Re: RPi + Runeaudio +Wifi as Accesspoint

PostPosted: 25 Oct 2016, 09:19
by dror
Hi
Noticed (a while a go) that updating Rune revertes the refresh_nics, so one needs to repaste the lines.

Re: RPi + Runeaudio +Wifi as Accesspoint

PostPosted: 14 Nov 2016, 23:02
by BorGreiner
Followed the instructions. Got it working but... Inbuilt WIFI that identifies itself as Cisco00068 has internet, my other dongle (that I can also connect to) has no internet access. I'd prefer vice versa, as dongle has better range.

Can some help me out here?

Re: RPi + Runeaudio +Wifi as Accesspoint

PostPosted: 22 Jan 2017, 01:05
by rlsten
I have been unable to get this to work using a Raspberry Pi 3 internal wifi. I started with a fresh installation of the latest image, and then followed Frank's how to from page 2. The results of redis-cli hgetall AccessPoint were:

Code: Select all
1) "enabled"
2) "1"
3) "enable-NAT"
4) "1"
5) "ip-address"
6) "192.168.12.1"
7) "broadcast"
8) "255.255.255.0"
9) "ssid"
10) "RuneAudioAP"
11) "passphrase"
12) "RuneAudio"
13) "dhcp-range"
14) "192.168.12.2,192.168.12.254,24h"
15) "dhcp-option"
16) "option:dns-server,192.168.12.1"


The results of /usr/sbin/hostapd /etc/hostapd/hostapd.conf were:

Code: Select all
Configuration file: /etc/hostapd/hostapd.conf
Failed to initate interface mon.wlan0: -95 (Operation not supported)
wlan0: Could not connect to kernel driver
Using interface wlan0 with hwaddr b8:27:eb:87:8c:51 and ssid "RuneAudioAP
wlan0: interface state UNINITIALIZED->ENABLED
wlan0: AP-ENABLED


When I tried to access the Pi from my Android phone, the RuneAudioAP was visible, but it was unable to obtain an IP address.

When I tried an iPad Pro, it seemed to be connected, but with no internet access; however, there was a continuous spinning and not a check mark for a connection, and the IP address was nowhere near the dhcp range.

Of course I could not connect to Rune at 198.168.12.1.

When I tried the connection I had the /usr/sbin etc. command still running and got the following output:

Code: Select all
wlan0: STA [i]MAC ADDRESS OF MY IPAD[/i] IEEE 802.11:associated
wlan0: AP-STA-CONNECTED STA [i]MAC ADDRESS OF MY IPAD[/i]
wlan0: STA [i]MAC ADDRESS OF MY IPAD[/i] RADIUS: starting accounting session 9FD30F51A234569D5
wlan0: STA [i]MAC ADDRESS OF MY IPAD[/i] WPA: pairwise key handshake completed (RSN)


And then it froze.

Any ideas what I am doing wrong?

Thanks,
Rod

Re: RPi + Runeaudio +Wifi as Accesspoint

PostPosted: 14 Apr 2017, 05:11
by rjm121012
This might not be the correct place to post, but I am interested in a variation of using the RPi as an WiFi AP.
I would like to ONLY CONTROL Runeaudio on a RPi-3 wirelessly using the RPi-3 imbedded Bluetooth.
I DO NOT want to stream audio wirelessly to or from the RPi. Audio is stored locally on USB and output to USB DAC.
I would think that Bluetooth would be ideal for this because it should be low bandwidth to just send play, pause, stop and skip commands to the RPi. Any thoughts on the feasibility of doing this? I am a RF hardware engineer and am not good with software.

Re: RPi + Runeaudio +Wifi as Accesspoint

PostPosted: 14 Apr 2017, 14:29
by hondagx35
Hi rjm121012,

maybe this is what you are searching.

Frank

Re: RPi + Runeaudio +Wifi as Accesspoint

PostPosted: 16 Apr 2017, 08:08
by rjm121012
I hadn't considered that method.
What I was looking for was to still use the RuneUI client on IOS and Android devices, but just change the communication from WiFi to Bluetooth.
For command only. No audio streaming.

Re: RPi + Runeaudio +Wifi as Accesspoint

PostPosted: 27 May 2017, 23:17
by imsai
I had been working on a media server for my vehicle, and originally used a Pi1 with some success. Around the time I was getting frustrated with the limited MPD interface apps, and the audio quality, and was experimenting with USB sound modules, I ran across RuneAudio. I decided to switch to a Pi3, and give it a go.
RuneAudio is responsive, works from the start. I'm impressed, and will be donating.

My setup is now a Pi3 with a battery pack. The battery will be replaced with a Mausberry car switch module soon, and the USB audio card will be replaced with a Hifiberry soon.

Future version will hopefully have a 3G dongle for internet access on the road.

I realize the focus is to create a good audio product, not a Swiss army knife software.

So we are respectfully requesting the AP to NAT over an additional WIFI connection with a wifi dongle or a 3G dongle. I haven't been able to make this work yet. Will have to research more. Streaming internet radio would become an option, as well as rsyncing a music directory.

Re: RPi + Runeaudio +Wifi as Accesspoint

PostPosted: 28 May 2017, 10:59
by hondagx35
Hi imsai,

the AP to NAT over an additional WIFI connection with a wifi dongle or a 3G dongle

This shouldn't be too hard to implement.

First, use my latest image it has AP and NAT functionality implemented.
Second, you have to get your 3g dongle up and running, see here.
You have to use the netctl approach because it is the network manager used on Rune.
Last, you have to point the NAT to your 3g connection.

NB: Never use "pacman -Syu" on an Rune image, because it will mess up your installation.

Frank

Re: RPi + Runeaudio +Wifi as Accesspoint

PostPosted: 28 Aug 2021, 16:11
by crisvanhamer
Hi Everyone,

I'm trying to use Runeaudio with pi 3, but actuelly I can't use the ethernet of my router, but i want to use the wifi.
Can I set up the wifi (ssid and password) during (of after) the sd flashing ?

Thanks among us apk!!

Re: RPi + Runeaudio +Wifi as Accesspoint

PostPosted: 31 Aug 2021, 16:40
by surfninja
Chris,
i'd suggest looking at https://www.runeaudio.com/forum/runeaudio-r-e6-t7141.html. I'm running wireless on a zero.