Hi folks,
I am just playing around with a Pi Zero W (Pi OS lite, current Buster),
it works nicely as a Wifi client.
But I want it to be a Wifi AP (WPA), so other clients (laptops,
tablets...) can log into the Pi to SSH and FTP.
Hi folks,
I am just playing around with a Pi Zero W (Pi OS lite, current Buster),
it works nicely as a Wifi client.
But I want it to be a Wifi AP (WPA), so other clients (laptops,
tablets...) can log into the Pi to SSH and FTP.
On Mon, 16 Aug 2021 17:38:08 +0200
Wolfgang Mahringer <yeti201@gmx.at> wrote:
Hi folks,
I am just playing around with a Pi Zero W (Pi OS lite, current Buster),
it works nicely as a Wifi client.
But I want it to be a Wifi AP (WPA), so other clients (laptops,
tablets...) can log into the Pi to SSH and FTP.
You don't need it to be an access point in order to do that as long
as the clients and Pi are on the same network or at least not firewalled apart. Some access points isolate their clients so that they can't reach
each other but this can usually be turned off.
Hi folks,
I am just playing around with a Pi Zero W (Pi OS lite, current Buster),
it works nicely as a Wifi client.
But I want it to be a Wifi AP (WPA), so other clients (laptops,
tablets...) can log into the Pi to SSH and FTP.
There are several tutorials on the net, but they seem to not work
somehow on the current OS.
I also want to be able to turn the AP off while it is instructed to do
some stuff, and on again when it is done.
Any pointers that really work?
Cheers,
Wolfgang
all the other posters can't fathom a situation where there is no
router and the other devices must connect directly to the Pi.
But I want it to be a Wifi AP (WPA), so other clients (laptops,
tablets...) can log into the Pi to SSH and FTP.
"A. Dumas" wrote:
all the other posters can't fathom a situation where there is no
router and the other devices must connect directly to the Pi.
I'm one of them. What is the difference? I presume it's fixed addresses instead of DHCP, but what else? That can't be all, can it?
"A. Dumas" wrote:
all the other posters can't fathom a situation where there is no router
and the other devices must connect directly to the Pi.
I'm one of them. What is the difference? I presume it's fixed addresses instead of DHCP, but what else? That can't be all, can it?
Danke
Axel
Apparently all the other posters can't fathom a situation where there is
no router and the other devices must connect directly to the Pi.
Axel Berger <Spam@Berger-Odenthal.De> wrote:
"A. Dumas" wrote:
all the other posters can't fathom a situation where there is no
router and the other devices must connect directly to the Pi.
I'm one of them. What is the difference? I presume it's fixed addresses
instead of DHCP, but what else? That can't be all, can it?
Somewhere where there is no router. Idk, maybe the back of the garden?
There doesn't have to be a follow up network connection from the Zero, it
can be the endpoint. Perhaps it is just there to collect data from a few wireless devices.
Wtf, people.
On Mon, 16 Aug 2021 20:42:42 -0000 (UTC)
A. Dumas <alexandre@dumas.fr.invalid> wrote:
Apparently all the other posters can't fathom a situation where there is
no router and the other devices must connect directly to the Pi.
Sure we can, but the OP already said it was working as a client so there's an AP around.
On Mon, 16 Aug 2021 20:42:42 -0000 (UTC)
A. Dumas <alexandre@dumas.fr.invalid> wrote:
Apparently all the other posters can't fathom a situation where there is
no router and the other devices must connect directly to the Pi.
Sure we can, but the OP already said it was working as a client so there's an AP around.
Hi folks,
I am just playing around with a Pi Zero W (Pi OS lite, current Buster),
it works nicely as a Wifi client.
But I want it to be a Wifi AP (WPA), so other clients (laptops,
tablets...) can log into the Pi to SSH and FTP.
There are several tutorials on the net, but they seem to not work
somehow on the current OS.
I also want to be able to turn the AP off while it is instructed to do
some stuff, and on again when it is done.
Any pointers that really work?
Cheers,
Wolfgang
IF THERE IS NO ROUTER, WHAT IS THE PI CONNECTING TO?
Or is it absolutely standalone ?
1st result from a google search "raspberry pi as wifi access point" https://thepi.io/how-to-use-your-raspberry-pi-as-a-wireless-access-point/
To be able to install packets or update the Pi's OS, I plan to use
network bridging (Pi uses the connected laptop to share its internet connection).
But whatever, none of us came up with a helpful response yet to make the AP mode work. Router or not, it's an interesting problem by itself especially since, reportedly, it seems to have stopped working with the old howtos. Maybe it's another achievement of systemd.
Hi folks,
Thanks for the answers. Many of you seem to not know that the Pi Zero W
has no ethernet ports, so that is no option here.
OK so just to be clear the aim is to have a stand alone Pi Zero W reachable over WiFi for incoming ssh and ftp connections with nothing else reachable over that WiFi link. Further this arrangement is out of reach of any AP and there are multiple clients for the Pi so the Pi needs to be an
AP.
For that purpose the guide that Alister pointed you at should do
fine, hostapd and dnsmasq are the primary ingredients. You can just ignore the bits about routing out via the ethernet (from enabling IP forwarding onwards) because you're not doing that.
1st result from a google search "raspberry pi as wifi access point" https://thepi.io/how-to-use-your-raspberry-pi-as-a-wireless-access-point/
Hi folks,
Am 17.08.2021 um 00:20 schrieb alister:
1st result from a google search "raspberry pi as wifi access point"
https://thepi.io/how-to-use-your-raspberry-pi-as-a-wireless-access-point/
This tutorial does not work either (like several others I have tried).
It is about creating an AP on the Pi, which is in turn connected to the internet via ethernet. That's exactly what I /don't/ want to achieve.
I've done everything but steps 6, 7 and 8, since they are about IP
forwarding and brisging.
More ideas anyone?
Cheers,
Wolfgang
Wolfgang Mahringer wrote:
Ahem A Rivet's Shot wrote:
OK so just to be clear the aim is to have a stand alone Pi Zero W >>> reachable over WiFi for incoming ssh and ftp connections with nothing
else
reachable over that WiFi link. Further this arrangement is out of
reach of
any AP and there are multiple clients for the Pi so the Pi needs to
be an
AP.
That's exactly what I want to do, correct!
can a Pi do ad-hoc wifi?
can a Pi do ad-hoc wifi?
and the Pi is still logging into my router.
Ahem A Rivet's Shot wrote:
OK so just to be clear the aim is to have a stand alone Pi Zero W
reachable over WiFi for incoming ssh and ftp connections with nothing
else
reachable over that WiFi link. Further this arrangement is out of
reach of
any AP and there are multiple clients for the Pi so the Pi needs to be an
AP.
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.
Hi,
Am 17.08.2021 um 11:44 schrieb Ahem A Rivet's Shot:
OK so just to be clear the aim is to have a stand alone Pi Zero W
reachable over WiFi for incoming ssh and ftp connections with nothing
else
reachable over that WiFi link. Further this arrangement is out of
reach of
any AP and there are multiple clients for the Pi so the Pi needs to be an
AP.
That's exactly what I want to do, correct!
For that purpose the guide that Alister pointed you at should do
fine, hostapd and dnsmasq are the primary ingredients. You can just
ignore
the bits about routing out via the ethernet (from enabling IP forwarding
onwards) because you're not doing that.
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
But my Pi zero should work standalone, only sometimes (hours between) >somebody will connect to the Pi, so the client and the Pi are a private >network. There is /no/ router involved.
But whatever, none of us came up with a helpful response yet to make the AP >mode work. Router or not, it's an interesting problem by itself especially >since, reportedly, it seems to have stopped working with the old howtos. >Maybe it's another achievement of systemd.
Hi folks,point/
Am 17.08.2021 um 00:20 schrieb alister:
1st result from a google search "raspberry pi as wifi access point"
https://thepi.io/how-to-use-your-raspberry-pi-as-a-wireless-access-
This tutorial does not work either (like several others I have tried).
It is about creating an AP on the Pi, which is in turn connected to the internet via ethernet. That's exactly what I /don't/ want to achieve.
I've done everything but steps 6, 7 and 8, since they are about IP
forwarding and brisging.
More ideas anyone?
Cheers,
Wolfgang
surely simply not connecting the ethernet would cure the routing to the internet problem?
surely simply not connecting the ethernet would cure the routing to the internet problem?
On Tue, 17 Aug 2021 17:59:18 -0000 (UTC)
alister <alister.ware@ntlworld.com> wrote:
surely simply not connecting the ethernet would cure the routing to the
internet problem?
Yep, especially since there isn't one to connect anyway.
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.
Hi folks,
I am just playing around with a Pi Zero W (Pi OS lite, current Buster),
it works nicely as a Wifi client.
But I want it to be a Wifi AP (WPA), so other clients (laptops,
tablets...) can log into the Pi to SSH and FTP.
There are several tutorials on the net, but they seem to not work
somehow on the current OS.
I also want to be able to turn the AP off while it is instructed to do
some stuff, and on again when it is done.
Any pointers that really work?
Cheers,
Wolfgang
Am 17.08.2021 um 16:52 schrieb Dennis Lee Bieber:
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.
That sounds great.
Which one of the images offered on
http://www.pistar.uk/downloads/
would you suggest for Pi Zero W 1.1?
Hi folks,
I finally got it to work. This time I used this tutorial: https://www.elektronik-kompendium.de/sites/raspberry-pi/2002171.htm
(German)
These were the pitfalls I think I fell into:
- 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:
Hi folks,
I am just playing around with a Pi Zero W (Pi OS lite, current
Buster), it works nicely as a Wifi client.
But I want it to be a Wifi AP (WPA), so other clients (laptops,
tablets...) can log into the Pi to SSH and FTP.
There are several tutorials on the net, but they seem to not work
somehow on the current OS.
I also want to be able to turn the AP off while it is instructed to do
some stuff, and on again when it is done.
Any pointers that really work?
Cheers,
Wolfgang
On Tue, 17 Aug 2021 17:59:18 -0000 (UTC) alister
<alister.ware@ntlworld.com> wrote:
surely simply not connecting the ethernet would cure the routing to the
internet problem?
Yep, especially since there isn't one to connect anyway.
Why? The wifi link already encodes traffic. The pi is off grid.
On 18.8.21 17.49, Wolfgang Mahringer wrote:
Hi folks,
I finally got it to work. This time I used this tutorial:
https://www.elektronik-kompendium.de/sites/raspberry-pi/2002171.htm
(German)
These were the pitfalls I think I fell into:
- 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:
Hi folks,
I am just playing around with a Pi Zero W (Pi OS lite, current
Buster), it works nicely as a Wifi client.
But I want it to be a Wifi AP (WPA), so other clients (laptops,
tablets...) can log into the Pi to SSH and FTP.
There are several tutorials on the net, but they seem to not work
somehow on the current OS.
I also want to be able to turn the AP off while it is instructed to
do some stuff, and on again when it is done.
Any pointers that really work?
Cheers,
Wolfgang
Just a side note: If you have SSH working to the Pi, you should
not need FTP. Please use SFTP instead.
On Wed, 18 Aug 2021 21:04:03 +0100, The Natural Philosopher wrote:
Why? The wifi link already encodes traffic. The pi is off grid.
Agreed. The benefit of using SSH transfers is having no more software to install because bog-standard sshd acts as a client to ssh, scp, sftp and
(if you happen to have it installed), gftp
The Natural Philosopher wrote:
ftp is in some ways nicer
Huh? I'm struggling to think of a protocol causes more grief than FTP, since NAT came along at least.
The Natural Philosopher wrote:
ftp is in some ways nicer
Huh? I'm struggling to think of a protocol causes more grief than FTP, since NAT came along at least.
On 19.8.21 11.22, Andy Burns wrote:
The Natural Philosopher wrote:
ftp is in some ways nicer
Huh? I'm struggling to think of a protocol causes more grief than
FTP, since NAT came along at least.
FTP is kind of obsolete. It belongs to the era of XDMCP and Telnet.
ftp is in some ways nicer
On 19/08/2021 09:22, Andy Burns wrote:
The Natural Philosopher wrote:
ftp is in some ways nicer
Huh? I'm struggling to think of a protocol causes more grief than
FTP, since NAT came along at least.
I meant from the users perspective
it works nicely as a Wifi client.[...]
Wolfgang Mahringer <yeti201@gmx.at> wrote:
But I want it to be a Wifi AP (WPA), so other clients (laptops,
tablets...) can log into the Pi to SSH and FTP.
Apparently all the other posters can't fathom a situation where there
is no router and the other devices must connect directly to the Pi.
Sorry, I don't have a solution for you because I never tried to use a
Pi as an AP.
The Natural Philosopher <tnp@invalid.invalid> writes:
On 19/08/2021 09:22, Andy Burns wrote:
The Natural Philosopher wrote:
ftp is in some ways nicer
Huh? I'm struggling to think of a protocol causes more grief than
FTP, since NAT came along at least.
I meant from the users perspective
Number of times I’ve had an SFTP transfer corrupted by line ending conversion 0. Number of times for FTP, too many to count. Completely
horrible protocol from any angle.
The Natural Philosopher wrote:
ftp is in some ways nicer
Huh? I'm struggling to think of a protocol causes more grief than FTP, since NAT came along at least.
The Natural Philosopher wrote:
ftp is in some ways nicer
Huh? I'm struggling to think of a protocol causes more grief than FTP, since NAT came along at least.
Richard Kettlewell wrote:
The Natural Philosopher <tnp@invalid.invalid> writes:
On 19/08/2021 09:22, Andy Burns wrote:
The Natural Philosopher wrote:
ftp is in some ways nicer
Huh? I'm struggling to think of a protocol causes more grief than
FTP, since NAT came along at least.
I meant from the users perspective
Number of times I’ve had an SFTP transfer corrupted by line ending
conversion 0. Number of times for FTP, too many to count. Completely
horrible protocol from any angle.
it has binary mode. dont use it in any other,
The Natural Philosopher <tnp@invalid.invalid> writes:
Richard Kettlewell wrote:
The Natural Philosopher <tnp@invalid.invalid> writes:
On 19/08/2021 09:22, Andy Burns wrote:
The Natural Philosopher wrote:
ftp is in some ways nicer
Huh? I'm struggling to think of a protocol causes more grief than
FTP, since NAT came along at least.
I meant from the users perspective
Number of times I’ve had an SFTP transfer corrupted by line ending
conversion 0. Number of times for FTP, too many to count. Completely
horrible protocol from any angle.
it has binary mode. dont use it in any other,
Sure, but historically the default was text mode, so in practice
corruption was pretty common.
Today I don’t use it at all.
$ ftp whatever
-bash: ftp: command not found
On 19/08/2021 09:22, Andy Burns wrote:+1
The Natural Philosopher wrote:
ftp is in some ways nicer
Huh? I'm struggling to think of a protocol causes more grief than
FTP, since NAT came along at least.
SIP/RTP
UPnp
Lots of VOIP are harder to do over NAT than FTP is.
This is why many mobile--- SoupGate-Win32 v1.05
VOIP applications need TUN/STUN servers and whatnot. At the very least there are well known solutions for deploying FTP whereas setting certain VOIP services requires you to read three tonnes of additional manuals. Specially if
they have some P2P or WebRTC component.
On the Mac I had to
open 2020-02-13-raspbian-buster-lite.img
touch /Volumes/boot/ssh
in order to be able to slogin into the pi. I haven't tried to set up an
ftp server.
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 371 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 174:58:40 |
| Calls: | 7,915 |
| Files: | 12,983 |
| Messages: | 5,797,724 |