Pi Zero W as access point, how to?

Hi,

Am 17.08.2021 um 11:44 schrieb Ahem A Rivet's Shot:

That's exactly what I want to do, correct!

Does not work unfortunately (see other post). Have moitted steps 6 to 8. The new Wifi network does not even appear, and the Pi is still logging into my router. Yes, I have rebooted, and there are no errors visible. dmesg also shows nothing obvious.

Cheers, Wolfgang

can a Pi do ad-hoc wifi?

That's a problem - you need to disable the client configuration. You can't be an AP and connect to an AP on the same radio, once you get the client configuration out of play the host configuration should work.

Can your clients 'see' at least the ssid? what does iwconfig say?

I would start with why that is happening

No reason why not.

Sounds like you still have the wlan bound as a wpa_supplicant

in /etc/dhcpd.conf you should have

interface wlan0 static ip_address=192.168.1.1/24 nohook wpa_supplicant

take a look at

which shows how to set up a router and what to leave out if you do not need access to the ethernet network

Peter

On Tue, 17 Aug 2021 07:05:58 -0000 (UTC), A. Dumas declaimed the following:

Pi-Star systems (minimal RaspOS, with a load of Amateur Radio stuff on board) are designed to open an AP IF they fail to connect to a normal router. The only purpose of the AP is to allow one to SSH/HTTP in to the device and configure the credentials needed by a local router.

Once it connects to a regular router, the AP is effectively disabled.

On Tue, 17 Aug 2021 10:05:30 +0200, Wolfgang Mahringer declaimed the following:

How many "random" clients do you expect? If you just mean one or two known laptops, it might be better to see if the laptop can be made the access point, and configure the wpa_supplicant file with connection credentials for each potential client. Though I'll have to admit I don't know if the R-Pi will periodically poll looking for an access point (Pi-Star systems don't -- if one moves out of range of an access point, one needs to reboot to get it to search for another).

point/

surely simply not connecting the ethernet would cure the routing to the internet problem?

On a Pi zeroW, what ethernet?

Yep, especially since there isn't one to connect anyway.

-- Steve O'Hara-Smith | Directable Mirror Arrays C:\>WIN | A better way to focus the sun The computer obeys and wins. | licences available see You lose and Bill collects. |

Nor does a Pi-Zero have an ethernet port...

Am 17.08.2021 um 16:52 schrieb Dennis Lee Bieber:

That sounds great. Which one of the images offered on

Cheers, Wolfgang

Hi folks,

I finally got it to work. This time I used this tutorial:

- WPA-PSK passphrase was too short (yeah I know)

- "nohook wpa_supplicant" in /etc/dhcpcd.conf was missing

- "RUN_DAEMON=yes" in /etc/default/hostapd was missing

Best parts were the checks: $ ip l to check if wlan0 is working properly $ dnsmasq --test -C /etc/dnsmasq.conf to check if DHCP server config is OK $ sudo hostapd -dd /etc/hostapd/hostapd.conf to check if hostapd is properly configured

All is well now, case closed. Thanks for all your help, guys. Wolfgang

Am 16.08.2021 um 17:38 schrieb Wolfgang Mahringer:

On Wed, 18 Aug 2021 11:59:00 +0200, Wolfgang Mahringer declaimed the following:

I don't think you'd actually want to use one of those images. As mentioned, they are quite heavily loaded with Amateur Radio stuff -- and on boot attempt to start up communications with a piggy-backed radio board, run a web server for configuration/status display, and set up the file system as READ-ONLY (log files go into a RAM disk -- the whole idea being to reduce SD card wear).

root 28249 1.5 0.7 51748 7456 ? S

Just a side note: If you have SSH working to the Pi, you should not need FTP. Please use SFTP instead.

I know but the article was a generic conf for all pies & the op complained he did not want the routing to the internet feature

I am almost tempted to try setting this up myself now