The above answer is great and helped me to save a lot of time with my setup, but I chose to make a few changes I thought I'll share.
The setup is this: I have a Denon amplituner that has an Ethernet jack, but no wifi; it also doesn't have Spotify. Since it accepts HDMI input, I chose to use Volumio on a Raspberry Pi 1B - audio via HDMI, Raspberry gets WiFi ...
I tried the solutions above with some success but nothing as good as I wanted. I found ComitUp as being another method of doing this. It was a lot easier.
https://davesteele.github.io/comitup/ (Thanks to Dave!)
Comitup is a software package that provides a service to establish Wifi networking on a headless computer (that is, one with no video, keyboard, ...
So, RPI is a computer and yes, you can configure your RPI to be an access point (and basically serve it's own wifi network devices can connect to). This may be a good start. It would not let your RPI wifi users access internet (unless you have another adapter that connects to network to bridge it) but it would work if you wanted them to connect to this wifi ...
I've solved it, it was a very simple problem. In /etc/default/hostapd I had changed DAEMON_OPTS instead of DAEMON_CONF. When I corrected this and had the configuration file specified in DAEMON_CONF everything started up and worked as expected.
Just replying to myself following some testing.
Escaping the network name appears to work: R\xC3\xA9seau de MP1
In my local setup using hexdump -C I see the encoding is UTF8 (probably a side effect of using a UTF8 based terminal)
Also looking at the docs, for the network block, I see:
# ssid: SSID (mandatory); network name in one of the optional formats:
I don't know what a pifi access point is but it is not necessary to switch anything. You can have an access point on the Raspberry Pi and also be connected with a WiFi client connection to your internet router. How to do it you can look at Access point as WiFi router/repeater, optional with bridge.
If you like to simplify the setup you can purchase an ...
Some years later I have found new possibilities using systemd-networkd to create a WiFi router/repeater. The built-in WiFi device of a Raspberry Pi is capable to create an access point together with a client connection simultaneously as uplink to another WiFi internet router. How to do it you can look at Access point as WiFi router/repeater, optional with ...
As a side note, seeing WiFi networks but being unable to connect is one of the symptoms I've got after switching from Rapsbian Buster repo to regular Debian Buster repo and upgrading. That's obviously not the OP's case, but other people finding this question might find it useful.
Note that there's no easy way to undo an arbitrary upgrade involving many ...
Please do not touch /etc/network/interfaces if you do not know what you are doing. Please be aware the line in it:
# Please note that this file is written to be used with dhcpcd
To setup WiFi just create a file wpa_supplicant.conf in /boot, something like this, but with your settings:
rpi ~$ cat /boot/wpa_supplicant.conf
Some years later the development has go on. Here are some up to date answers to the old questions:
A comment on this blog says that RTL8188CUS does not allow monitor mode. How can I be certain that the next cheap wifi dongle I buy for a RPI will work in monitor mode?
With iw list you may get something like this from my USB/wifi dongle:
rpi ~$ iw ...
There's project on GitHub that answers this problem without recompiling the kernel, https://github.com/TheN00bBuilder/rtl8188monitor
From the readme
Check the directory with the RTL8192CU drivers in them by typing sudo ls /lib/modules/$(uname -r)/kernel/drivers/net/wireless/realtek.
If it returns with an error or cannot find the driver (and it ...
I found wpa_supplicant to be super confusing to work with until I figured out how to see its debug messages by running it manually.
sudo killall wpa_supplicant
sudo wpa_supplicant -c/etc/wpa_supplicant/wpa_supplicant.conf -iwlan0
(Add a -d onto the end to make it verbose.)
Until I figured this out, it was complete voodoo. Once you get the config file ...
With the setup you have used it is right that the wired interface has gone. It is simply not configured because it is not used. To use it in addition to the access point the best way is to bridge it with interface wlan0. How to do it you can look at Using an additional WiFi dongle to create WAP and switch.
There's (2) parts to your question, so I'll answer each in turn:
How does an Access Point Work?
Since I actually wrote "pi-ap"- a Github repo which automates the configuration of a Pi into a WiFi Access Point- I'm in a good position to detail the inner workings of an AP.
In a nutshell:
An AP- in this case your Pi- has a radio in it through which it ...
Use "pi-ap"- a Github repo which automates the configuration of a Pi 3 (or Pi 4) into a WiFi AP. Really, REALLY simple to use. Just edit variables.sh and change some default values, and then sudo ./install.sh will get you a working Pi Access Point in about 3.5 minutes while you drink your tea.
Only need a Pi 3B+ or a Pi 4, an Ethernet cable and a router ...
Try "pi-ap": It automates configuration of a Pi 3B+ or Pi 4 running either Stretch or Buster into a WiFi Access Point. The following link provides an overview of the solution, benefits and a download link to the Github repo:
Automate Configuration of Pi Access Point
You only need to edit a few default values in a centralized variables file and execute ...
I hit a similar issue - see here:
The solution was to run the following two sed commands:
sed -i 's/^dkms build/ARCH=arm dkms build/' dkms-install.sh
sed -i 's/^MAKE="/MAKE="ARCH=arm\ /' dkms.conf
After that, I was able to run:
$ sudo ./dkms-install.sh
About to run dkms install steps...
A client that knows the SSID will connect even if the SSID is hidden. So there is no need to hide it after the client connects, just run with it hidden all the time.
You can manually add a new client just by entering the SSID into the wpa_supplicant.conf file along with the password. You should also be able to do it with what ever GUI tools are available, ...
What Jake said worked for me, HOWEVER, the latest version of Raspbian is 32bit instead of 64bit. Because of this, the lines starting in SED did not work. To have this done correctly:
sudo nano Makefile
(search for, or scroll down until you see 'arm')
Make sure that the y (yes) is on CONFIG_PLATFORM_ARM_RPI instead of CONFIG_PLATFORM_ARM64_RPI. Those three ...
You can make the RPi 0 W an Access Point so that any device using WiFi, e.g. your smart phone, can connect to it. You can also connect the RasPi to your local WiFi internet router so all devices that are connected to the RasPis Access Point can also get into internet.
This way you are using the RasPi as WiFi repeater. How to do it you can look at Access ...
Now is even easier!
As per last update on the post https://www.raspberrypi.org/forums/viewtopic.php?f=28&t=62371 already mentioned, MrEngman made a beautiful script, you just need to download and execute it
sudo wget http://downloads.fars-robotics.net/wifi-drivers/install-wifi -O /usr/bin/install-wifi
sudo chmod +x /usr/bin/install-wifi
As far as I understand you want to handle an error condition in a python script that is started by a service. If a wifi connection fails you want to reconnect it. You try to manage it with service management but manage services within a service is not a good idea because dependencies and other conditions are handled by different services at the same time and ...
The problem is that when the services terminate, it terminates the child process also. This is the reason why the wifi again goes back to the disconnected state.
When we use wpa_supplicant, there will be a background process running to load the configuration file and it is /sbin/wpa_supplicant -s -B -P /run/wpa_supplicant.wlan0.pid -i wlan0 -D nl80211,wext -...
You are asking how to bridge eth0 with the uplink connection wlan1. This is not an easy task because bridging a client connection can only be done with WDS mode and must be supported by the hardware. The built-in device of the Raspberry Pi does not support it. For further information about this issue you can look at Raspberry Pi WiFi to Ethernet Bridge for ...
Here's a way I used that should work on any Pi- or any Debian Based distro on a Pi- to PERSISTENTLY disable Power Management as a systemd service.
Just copy the below bash script into a file, chmod 700 it and sudo ./fileName will setup a service that ensures Power Management stays down across reboots. Tested and known to work correctly on Raspbian Buster:
This question is predicated on the false premise that lower rates are more reliable
Lowering baud rate can only be achieved by selecting a mode (b, g, n) supported by the router and most do not even support the legacy modes by default.
Spread-spectrum systems transmit at a constant bit rate (usually 20/40MHz for 2.4GHz WiFi). The spreading function ...
You can use the iw command to set the bitrate. With calling its help you will find:
dev <devname> set bitrates [legacy-<2.4|5> <legacy rate in Mbps>*] [ht-mcs-<2.4|5> <MCS index>*] [vht-mcs-<2.4|5> <NSS:MCSx,MCSy... | NSS:MCSx-MCSy>*] [sgi-2.4|lgi-2.4] [sgi-5|lgi-5]
For example to limit the bitrate to 12 Mbps on ...
This problem can be reduced to make the RasPi a router with an WiFi uplink to the local hotspot/router and connect to a local wired network. It is no problem to use the wired and wireless connection at the same time because you asked it. If you mean to have all devices on the same subnet 192.168.1.0/24 then it isn't possible. For this you have to use a ...
Seems you are mixing up two authentication key management protocols. There are mainly two methods used:
WPA-PSK uses a Pre Shared Key defined with option psk= in /etc/wpa_supplicant/wpa_supplicant.conf. This is simple and therefore mostly used in home networking.
WPA-EAP means Extensible Authentication Protocol and is often used by enterprises or ...
I'm sorry that I disturbed the members of the forum.
I found the solution!
It much easier than I thought:
Android Phone > Serial > Self built antenna with an Arduino > RFM95W > Raspberry Pi
I haven't found any important differences between the wifi devices on RPi 3B, RPi 3B+ (yes, that supports 5 GHz) and RPi 4B. All my wifi setups where upstream compatible.
You are using Debian ifupdown. It may be possible that this old style networking get more and more out of the focus from the developers with newer versions of the operating system. In ...
I use the first solution (goobering), and it didn't work.
After search on the Internet, I found these might be help. All you need to do is install crda and set the wifi region.
RPI 3 doesn't see my wifi
If you use wpa_supplicant, you have to change country in /etc/wpa_supplicant/...