Can't get AccessPoint working on RP3

mrcrowley

hondagx35 wroteHi mrcrowley,

Is Rune project dead ?
No, it absolutely isn't.

Ok. And what about Bluetooth control ??
This isn't something that is on top of our roadmap.
The next image will have the ability for an automatic wifi access point (AP).

What is the benefit for bluetooth over wifi?

Frank

I didn't know nothing about you are planning on WiFi direct. It's the same of Bluetooth.
If I know this I could save the money for the WiFi AP. [emoji30]

Inviato dal mio HTC One utilizzando Tapatalk

hondagx35

Hi mrcrowley,

I didn't know nothing about you are planning on WiFi direct.

please see here for more information.

Frank

mrcrowley

I see the link you gave me and try to apply, but I get this error:

 pacman -Sy --force raspberrypi-firmware-bootloader linux-raspberrypi              
:: Synchronizing package databases...                                                                 
 core is up to date                                                                                   
 extra                                                                                             2.3
 community                                                                                         4.0
 alarm is up to date                                                                                  
 aur is up to date                                                                                    
error: target not found: raspberrypi-firmware-bootloader

What I am doing wrong ???

Yatsushiro

The firmware & kernel update commands have changed recently, you shoud use

pacman -Sy --force raspberrypi-firmware raspberrypi-bootloader linux-raspberrypi

mrcrowley

Ok now it works, but I still can't get AP works.
I don't even see RuneAudioAP.

mrcrowley

After restart I can see RuneAudioAP, but now RuneAudio doesn't start at all anymore. Even with normal WiFi connection.
I can't even open ssh !!!
I fear that all is to format. I don't know if due to resizing partition, or to the AP procedure.
What can I try ??

hondagx35

Hi,

did you follow this step by step?

During the setup process you have to be connected via ethernet.

Frank

mrcrowley

Yes, via SSH.
But when I did

pacman -Sy --force raspberrypi-firmware-bootloader linux-raspberrypi

without success, I keep going on the others step.
After get to the final, I did

pacman -Sy --force raspberrypi-firmware raspberrypi-bootloader linux-raspberrypi

Moreover, when I did not see RuneAudioAP appear, I did change dns IP address in /etc/dnsmasq.conf, from 192.168.1.1 to the IP of my Rasp/Rune, and also in /var/www/command/refresh_nics.
Now I can not get access via SSH to these files to get to 192.168.1.1.

mrcrowley

No chance to get back working RaspPi ??
Only format and re-falsh all ??

mrcrowley

Anyone can help ???

hondagx35

Hi mrcrowley,

Anyone can help ???

Are you trying to connect via ethernet?

The only way to edit the files is to use a linux PC or the Pi itself.
Connect a monitor and keyboard and try to get access to the console.

Frank

mrcrowley

Yes. Connect via Ethernet not work. Rasp don' t answer.
I try to put the card with Rune into a pc with Linux, but I can not get access to the files. It seem because of permission problem.

Inviato dal mio HTC One utilizzando Tapatalk

mrcrowley

Ok I can access console directly on Raspy.
I try to get back dnsmasq.conf and refresh_nics to original IP address (192.168.1.1), but when I am trying to save the changes, nano doesn't let me save.
I try also to copy the files from the ones downloaded from here #97216 , but when I reboot, I find angain the old files with the wrong IP address.

What else can I do ???

hondagx35

Hi,

check the database entries in redis.

redis-cli hgetall AccessPoint

The settings can be changed like this:

redis-cli hset AccessPoint dhcp-option-dns 192.168.1.1

redis-cli hset AccessPoint dhcp-option-router 192.168.1.1

Frank

mrcrowley

Ok. Do it.
I see at the last entries the right ip number (192.168.1.1)
But at the first entries there are still the wrong ip number.
Is it okay, or they should be cancelled ?

Inviato dal mio HTC One utilizzando Tapatalk

mrcrowley

Ok. My Raspy has come back to work. Now I got SSH and access via WiFi.
EDIT: No, sorry. No Access with RuneAudioRemote via WiFi. Only with browser on pc-desktop via ethernet.
And still no RuneAudioAP visible !!

TommyBoy

the unit you are using to access the runeaudio webpage, needs to be on the SAME net.
phones change net to others, if stronger, so it can be a pain.

mrcrowley

So it was before trying to enable WiFi Access Point feature.
I only want to get back.

hondagx35

Hi mrcrowley,

So it was before trying to enable WiFi Access Point feature.

I have absolutely no idea what you are doing.
I followed my own how-to on a fresh installation and it works perfect.
Also connecting to the AP with the Rune Android app works like it should.

The only thing to consider is that the ethernet and AP should be on different IP ranges.
E.g. eth: 192.168.0.x AP:192.168.1.1

I only want to get back.

Why not disabling the AP feature?

Frank

mrcrowley

Then this is the problem.
My router is on 192.168.1.1
So I should set 192.168.1.2 (3,4,5,6,7,8, etc) in redis for AP ??? Or should I modified other files ??