search

f1linux / pi-ap

Raspberry Pi wireless Access Point: This repo automates the config of hostapd, dnsmasq, dhcpcd & wpa_supplicant to transform a Pi into an AP. Requires: a Pi, Ethernet cable & DHCP-enabled port on a broadband router or a switch connected to this router. For other interesting & practical Pi solutions, my Stack page is: https://raspberrypi.stackexchange.com/users/97613/f1linux
GNU General Public License v3.0
83 stars 17 forks source link

pi-ap Bug Report : Script No Longer Enables AP mode #5

Open dazz100 opened 4 years ago

dazz100 commented 4 years ago

Script No Longer Enables AP mode because of rfkill

Firstly, thank you for making this script available. It is clear you have spent a lot of time and applied a high level of expertise to produce this script. Being able to run a script in a few minutes is a much better solution than transcribing a series of instructions. Well done.

OK so During installation, I get the following error message:

Job for hostapd.service failed because the control process exited with error code.

As a result, the wifi does not run in AP mode.

Also, just a small point, Raspbian Lite does not have git installed by default.

I did the installation with a new virgin install of Raspbian Buster Lite. No other applications were installed. I burned a fresh install of Buster and then installed pi-ap without making any changes to the OS or the pi-ap scripts or variables.

After installation, AP mode was not enabled.

Did AP EVER work correctly before fault?

Never tried it before.

Bug CONSISTENTLY reproducible?

yes

If "yes", provide detailed steps to reproduce bug: Just run the unmodified pi-ap scripts/variables on a fresh install of Buster.

Error Messages/Screenshots

Additional context

The reason I found your script was because my own, much simpler script, shows the same problem. I get the same error message at the same stage in installation.

Proposed Fixes IF you have any suggested fixes, please describe them here.

Yes. Add the following commands to the script.

echo "Unblock and enable wifi "
rfkill unblock wlan
echo " Check that wifi is unblocked. "
rfkill list wlan

AP Client: Please provide details about the client used to connect to the AP:

The RPi clients can't connect to the RPi server AP.

dazz100 commented 4 years ago

Hi I also found a problem with dnsmasq in the logs.

May 03 09:02:54 raspberrypi dnsmasq[1349]: Too few arguments.
May 03 09:02:54 raspberrypi systemd[1]: Started dnsmasq - A lightweight DHCP and caching DNS server.
May 03 09:11:59 raspberrypi systemd[1]: Stopping dnsmasq - A lightweight DHCP and caching DNS server...
May 03 09:11:59 raspberrypi dnsmasq[1641]: Too few arguments.

I think I have found the solution to the problem of too few arguments at this post:

https://www.raspberrypi.org/forums/viewtopic.php?t=199037

It is not a problem and can be ignored.

Piehti commented 4 years ago

Unfortunatly, the AP wont show up on any device after the initial reboot. ~Any ideas or alternate (WORKING!!!!) tutorials to finally get my RasPi back to AP? :/~

~Where exactly did you put the rfkill?~

Got it working. Thanks for the RFKILL hint.