In my case, it turned out to be an easy fix.
apt install php-sqlite3
a2enmod proxy_fcgi setenvif
systemctl restart apache2
I am running Buster on PHP 7.3. on a Raspberry Pi 2 Model B Rev 1.
Hope this helps others too.
My problem was a combination of two factors:
using SFTP instead of Samba share. Using Samba massively increases the speed, as detailed in @MichaelHarvey's answer
the PSU that I used did not deliver enough current: the RPi was "throttled":
/opt/vc/bin/vcgencmd get_throttled # throttled=0x50005: under voltage, currently throttled!
Now that I ...
You are trying to use WiFi-Direct so you do not have to worry about security. WiFi-Direct uses WPA2 encryption by default.
You are using old style Debian networking managed with /etc/network/interfaces. This is deprecated on the Raspberry Pi OS based on Buster since years. I haven't used it for a long time so I cannot help much with it. I'm afraid you are ...
I have an Rpi4 8GB with a WD Elements 2TB USB3 external HDD (USB3 powered from the Pi) and a Seagate Backup Plus USB 3TB (with its own power supply), both shared by the Pi using Samba and I can get 100 Mbyte/sec each way from either on my LAN, maxing out the Gigabit Ethernet. SFTP is slow because of encryption/decryption. Also, if the drives are formatted ...
With the built-in wifi-device of a Raspberry Pi it is possible to create an access point together with an uplink client connection. This can be done with creating a virtual interface ap0 (or what name do you like) from the physical interface wlan0. Because the virtual interface ap0 depends on wlan0 it is a bit sophisticated to manage its initialization in ...
Andyroo gave a robust answer regarding ethernet hardware, but I don't think the issue lies there. I've used a variety of ethernet cables of different cats, many being over 10 years old as well, and never ran into any issues with them.
Especially because you mention that it connects just fine to your laptop via that cable. It does not appear to be an issue ...
Raspbian is using a thing called mDNS, which allows you to access your raspberry pi by a hostname raspberrypi.local.
So, you don't need to search for an IP address anymore, just connect like so:
Yet another option is to use Pulseaudio (especially if you already have it on your PC), configuring the Pi as a network sink. In the simplest case, you set up module-native-protocol-tcp on the Pulse server on your Pi, and set the $PULSE_SERVER variable on your PC to the IP address of the Pi.
If everything is set up correctly, you'll have another output ...
This might be a bit late but I have recently used 4G in combination with my Raspberry Pi. The usecase I had is somewhat different but should have the same steps to setup the 4G connection (I used a webserver on my Pi to have endpoints I could access from my PC).
First off, what I used:
A Raspberry Pi LTE Hat (in my case equipped with the SIM7600E)
There is a standard UPnP/DLNA that makes it easy to setup what you want, including bonus points for controlling it with your Android smartphone.
You can install a media server on your PC and a media renderer on the Raspberry Pi. Before doing it you must have the audio working on the RasPi, means you should be able to play local stored test songs with simple ...
Gigabit Ethernet is supported on the Pi 4 (though the max throughput speed CANNOT be reached on the Pi)as as such it needs a cable with all eight pins connected:
I think you will have a cat-5 or cat-5e cable that will not have the correct lines for the Pi.
You maybe able to get this to work by setting the switch port to force a lower speed but this may not ...
You can easily rename your network interfaces with:
ip link set wlan1 down
ip link set wlan1 name wlan0
ip link set wlan0 up
that is, assuming that you don't have any lingering wlan0 on your Pi.
In the boot messages, you can find some more information. On virtual machines with "predictable" network names, I use the following code in the ...
There are three things to consider:
Storage of the music.
The music files have to be available to the Pi. This means setting up up a share on the Pc so the Pi can access the files and having them in the correct format.
Connection to the stereo.
The Pi has very basic audio capabilities and I would look to one of the many many HATs that are available ...
There have been instances where RPi's mount.cifs seems to behave oddly. Try adding vers=1.0 after guest; i.e.
sudo mount -v -t cifs //WinMachine/tv /home/pi/SHARED/TV -o guest,vers=1.0
You may also wish to peruse man mount.cifs; esp the section vers=arg.
Let us know how that works.
It seems that this answer by @frank-yellin solved the problem.
If your router supports APSD / WMM (look on the wireless configuration page), turn it off. On my tomato router, I had to turn it off separately for both bands.
1.Use the simplest hostapd.conf file available from here: https://wiki.gentoo.org/wiki/Hostapd
2.Check to make sure you dont have conflicting wifi credentials in wpa_supplicant file.
sudo nano /etc/wpa_supplicant/wpa_supplicant.conf
Comment out any lines showing another wifi network. Mine only has:
As @leanne said in the comments, you can use this command to keep network-manager (needed for some features) but disable MAC Address Randomization:
printf "[connection]\nwifi.mac-address-randomization=1\n\n[device]\nwifi.scan-rand-mac-address=no\n" | sudo tee /etc/NetworkManager/conf.d/100-disable-wifi-mac-randomization.conf
As noted in a comment you are also agreed with using systemd-networkd. Here in short a configuration I have just tested, based on Setting up a Raspberry Pi as an access point - the easy way.
Switch over to systemd-networkd
Just follow to Use systemd-networkd for general networking. You can use section "♦ Quick Step". Then come back here.
The built-in WiFi device on a Raspberry Pi is limited to create only one access point. To have a second access point for a guest network you need an additional USB/WiFi dongle. All other access issues are then only routing settings.
To have a wired connection to the additional guest network you also need a second USB dongle with an ethernet RJ45 port of ...
I have inadvertently solved my own problem and I am very ashamed to say I don't know exactly what did it. I did a number of things at the same time and my pi now boots and connects to the new network just fine. Sincerest apologies for not being able to pinpoint the issue.
In /etc/network/interfaces, I changed iface wlan0 inet dhcp to iface wlan0 inet manual....
You are conflating/confusing two distinct concepts that might both be referred to as "opening a port".
Opening a port "in a firewall" means configuring the firewall to allow traffic to/from that port, but the port is actually not in the firewall, meaning, it is not something that is created or controlled by the firewall.
An internet ...
I do not understand what you are trying. As far as I understand you want to have a persistent group owner (GO) to which different devices can connect with the same password. This is already given with your configuration in /etc/wpa_supplicant/wpa_supplicant.conf. That looks good.
On WiFi-Direct the pin entry method is mandatory and default. There is no need ...
I had this issue also, and it was related to my routers AP Isolation setting in the wireless WAN area. Even though it was off, turning it on and back off fixed my issue. AP Isolation is for allowing separation of "guests" to access the internet without exposing the rest of your internal subnet.