First we need to change over completely to systemd (which might be the future anyway), as Ingo has explained here:
apt update && apt -y full-upgrade
systemctl mask networking.service dhcpcd.service
sudo mv /etc/network/interfaces /etc/network/interfaces~
sed -i '1i resolvconf=NO' /etc/resolvconf.conf
systemctl enable systemd-networkd.service ...
I only had a glance at the tutorial you have linked, tldr;
So I don't know where exactly do you went wrong. And it is difficult to follow your description. You described something and a bit later you changed a subnet and after that defining static ip addresses. And that all may impact dhcpcd, hostapd and dnsmasq and all must play together with different ...
There are many quirks with creating the virtual interface ap0. You have to follow exactly a sequence, otherwise it won't work. If other applications bind to the wifi port it cannot be set.
create a virtual interface ap0 for the access point
start access point daemon hostapd using interface ap0
start wpa_supplicant for wifi client using interface wlan0
You have configured a bridge with slave interfaces eth0 and wlan0. Everything looks good.
You only have one (virtual) interface br0 with an ip address 192.168.1.90. Don't be confused by eth0 and wlan0. As slaves of the bridge they have lost their normal IP characteristics and only work on the OSI data link layer with MAC addresses. The normal interface of ...
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
AFAIK the WiFi adapter on RPi 3 is not on USB bus but on SDIO bus, same as the SD card. Therefore the earliest dmesg message proving its presence is
mmc1: new high speed SDIO card at address 0001
One of the possible failure messages is
mmc1: error -110 whilst initialising SDIO card
If you get this message, or there is no mention of mmc1 at all, this ...
It's weird. Sounds like HDMI signals conflicting with Wifi signals, however, change the cable to another one (better, if it has a shield it'd be better.) and add an external wifi dongle.
If you change the cable, maybe you would realize that it's ok with "1920 x 1080" and it's not with "1280 x 720".
The list below can help you.
With setting up an Access point as WiFi router/repeater, optional with bridge I run into the same problem with the common channel of ap0 and wlan0 and could not get it to run with wpa_supplicant for the access point. So I decided to use hostapd. It is able to follow the channel for ap0 from wlan0 automagically. You may have a look at Step 2: install hostapd ...
From the hostapd.conf file :
# Maximum number of stations allowed in station table. New stations will be
# rejected after the station table is full. IEEE 802.11 has a limit of 2007
# different association IDs, so this number should not be larger than that.
# (default: 2007)
Prevent dhcpcd from configuring an interface in How to set up networking/WiFi shows how to stop dhcpcd configuring an interface.
NOTE Predictable Network Interface Names is recommended if multiple WiFi interfaces are in use.
Turns out I can simply access my webserver through the wlan0 interface with a little configuration on the access point. I don't quite remember what it was exactly as I tried multiple things, but I believe the solution was to remove denyinterfaces wlan from /etc/dhcpcd.conf. Then you use ifconfig to find out what ip address wlan0 uses, and you use it to ...
I would say ifplugd is the right daemon to solve your problem. But the Debian package for it uses old style ifupdown managed with /etc/network/interfaces. Since Raspbian Stretch dhcpcd is used for networking instead of ifupdown so support for ifplugd is also "deprecated". I think to use a complete outdated Raspbian version Jessie only for this issue is not a ...
You can create a bash script with this code content and create a systemd unit file where you call the bash file in ExecStart, enabling the unit at boot and using systemctl start yourunit and systemctl stop yourunit commands whenever. See the commented lines :
# Configure the variables
# check ETHIF link every 5 ...
It is unclear what WiFi configuration do you use but wpa_supplicant has the ability to configure itself and find some necessary options. It will store these settings for next use in /etc/wpa_supplicant/wpa_supplicant.conf, the one that you try to edit. This is what the option
allows. Set it to update_config=0 and wpa_supplicant will never ...
I've a doubt in your question here. Only changes are disappeared or the whole content gets disappeared? If the whole content is disappeared, it is a common problem which might be solved by setting the wifi-country and region correctly or by setting following things correctly:
The objective is receiving the data from the Ground module to air module and decoding it without a controller board such as PX4 or Navio.
Start with loopback test on the RPi4. Connect the Tx pin of the RPi4 to the Rx pin of the RPi4 with a jumper wire.
Install cutecom/minicom/putty on RPi4 to test the loopback. I used minicom to do the loopback test. The ...
"In normal circumstances there is NEVER a need to run rpi-update as it always gets you to the leading edge firmware and kernel and because that may be a testing version it could leave your RPi unbootable". https://www.raspberrypi.org/forums/viewtopic.php?p=916911#p916911
Even the rpi-update documentation now warns "Even on Raspbian you should only use this ...
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 ...
You are mixing up different networking systems. As far as I can see it is old style Debian ifupdown managed in /etc/network/interfaces and Raspbian default networking dhcpcd. From the log I see a DHCPREQUEST from dhclient so I assume that you also use isc-dhcp-client in addition to dhcpcd. If so you have two dhcp clients running on your RasPi. This cannot ...
Raspberry Pi 4 Model B uses the CYW43455 wireless chip, just like the Pi 3B+. The specifications indicate that it provides single-stream 11ac. There are no visible ports for external antennas.
If you require something different, you could get a better USB wireless adapter (RTL8812AU-based, for example), but that might be cost prohibitive.
After reading up on the concepts discussed in Ingo's replies I realised my (admittedly stupid) mistake! I had the device configured as a bridge, meaning that the the Pi itself wasn't assigning IP address's to the connected devices, simply providing an interface between the connected devices and the router!
The solution involved a combinational approach of ...
You analysis shows that the PI is fast enough to transmit and receive the data.
The only conclusion left is that whatever you do in MATLAB is too slow. While the PI is not bad, it is no match for a somewhat recent PC.
So you may want to write the control program in a more efficient language, like C, or you can try to identify the parts that need the most ...
You can make the RasPi a router that routes data between the wired and wireless interfaces. But I don't believe that the old RasPi with the limitations of USB for ethernet will be strong enough to ensure an uninterruptible video stream. You can try it. How to setup a router you can look at Can a Raspberry Pi Zero W be turned into an USB WiFi dongle to any ...
If you like to use systemd-networkd you can create two instances of wpa_supplicant that each can be managed independent from the other. Here in short I would do it.
First switch over to systemd-networkd:
# disable classic networking
rpi ~$ sudo -Es
rpi ~# systemctl mask networking.service
rpi ~# systemctl mask dhcpcd.service
rpi ~# mv /etc/network/...
Use different wpa_supplicant files in How to set up networking/WiFi
describes how to setup networking to use different wpa_supplicant files for each interface.
Your etc/network/interfaces should work (only because it causes dhcpcd to disable itself) and can be configured to use multiple wpa_supplicant files, however this uses old Debian networking, which is ...
I found the issue.
The following line was missing in wpa_supplicant.conf.
The whole file must looks like this.
Just for testing your network environment please flash a new image Raspbian Stretch Lite 2019-04-08 and boot it in your RasPi. Then create your wpa_supplicant.conf in the /boot/ directory, not in /etc/wpa_supplicant/. It should look like this:
rpi ~$ cat /boot/wpa_supplicant.conf
You have 2 options, (1) Disable onboard WiFi or (2) Use networkmanager instead of ifupdown.
(1) is explained already as another answer by @Ingo
(2) You can install networkmanager using apt install networkmanager
You can follow https://askubuntu.com/questions/377687/how-do-i-connect-to-a-wifi-network-using-nmcli to connect to network.
You can follow ...
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 ...