RPi 3B only has one antenna on board, so yes, it will be shared. Sharing is managed by the adapter firmware which is closed-source. Even if done right, it will not be as good as separate antennas.
You can get a USB dongle for either WiFi or BT (and use that instead of the built-in adapter) to get two separate antennas.
What you have purchased isn't only an antenna to replace the built-in antenna (I don't believe that's possible), it is a complete new WiFi transmitter/receiver that can be used in addition to the built-in WiFi. If you do not need the built-in WiFi so just don't configure/use it. You can also completely disable it by adding this option to /boot/config.txt:
I suppose you are using Raspbian. With my RasPis I have found that they tend to connect first to the 2.4 GHz band if both bands available. So first you should check if the 5 GHz band is seen by your RasPi. Execute this command.
rpi ~$ sudo iw wlan0 scan | grep -A5 'freq: 5'
It should give you at least one (ore more) outputs like this:
I see three possibilities as to what's happening here.
Somebody got unauthorized login access to your PI and used it to make attacks. I suggest checking for rootkits and the like.
Somebody is using the wifi to make attacks. It probably looks your PI because you probably are doing NAT. It could actually be an authorized user's compromised laptop. I ...
You can set a special SSID (WiFi network) to the wpa_supplicant.conf:
Add these details of your SSID to that config file like:
You can find more about it here.
I do not want to edit wpa_supplicant.conf every time it discover
Recover the /etc/network/interfaces by adding these lines:
# interfaces(5) file used by ifup(8) and ifdown(8)
# Please note that this file is written to be used with dhcpcd
# For static IP, consult /etc/dhcpcd.conf and 'man dhcpcd.conf'
# Include files from /etc/network/interfaces.d:
Then try to connect to your ...
One possible problem may be the DHCP client. It will always get an ip address and network configuration (DNS server, gateway, default route etc.) on boot up. When the lease has expired the DHCP client may have a problem to renew it. If it cannot renew its ip addres then it will configure a link-local ip address 169.254.197.68/16 which does not fit to you ...
Developer of RaspAP here. The project does not lock the file system or interfere with other services. I installed mosquitto after RaspAP, enabled the service and rebooted. Confirmed it's active and listening on port 1883:
sudo netstat -ltnp | grep -w ':1883'
tcp6 0 0 :::1883 LISTEN 405/mosquitto
Check the output of mount -l and ...
There is a high correlation between Questions which state "I have setup a static IP lease" and XXX doesn't work.
You have listed lots of files, but not provided any information which would enable anyone to answer.
What did YOU do? - in particular HOW did you set "a static IP lease".
I recommend you remove the attempt to set "static IP addresses" and let ...
To be able to setup Wifi on Raspberry Pi 4 B+ 4GB on Ubuntu server 18 TLS, you first need to get the name of the wifi card by showing physical components using the following command:
$ sudo lshw
in my case it was wlan0
Then navigate to /etc/netplan/ using the cd command the hit Enter
$ cd /etc/netplan/
use the command lsto list the files and ...
At least your PI was able to get an IP address (192.168.1.51 as per your screenshot). So the radio link is working although it may not be perfect. Looks more like a routing issue than a hardware issue. If you type ifconfig you should see the same address now or you still have an issue. What is your /etc/network/interfaces file like ?
One thing: your output ...
With iw dev wlan0 info you show that you are using:
channel 13 (2472 MHz), width: 20 MHz, center1: 2472 MHz
I remember that I had problems some times ago with connections using channels above 11. Since then I only use channels up to 11. I'm unsure if it also an issue for you because you have a link shown with iw dev wlan0 link but maybe there is a problem ...
I recommend trying to verify hardware is working: DHCP requires communication between the wifi adapter and the router, otherwise it can not be assigned an IP address. If you can confirm the wifi's MAC address was received by the router, then the wifi's transmit side is working.
If you had a second Zero-W with functional wifi, you could transfer the SD ...
For making remote ssh connection on raspberry pi 3B (os raspbian), it
need to close wifi connection. (to use only wired connection instead)
You can do it by ifplugd package with filling the /etc/network/interfaces out. Follow this link to do that. You can be enabled to disable wireless networks automatically when a wired cabled plugged.
But the ...
You don't tell us what error messages you get but you can try to restrict the connection to specific frequencies. In /etc/wpa_supplicant/wpa_supplicant.conf add a line with frequencies you want to use, for example (but use your own settings for country=, ssid= and psk=):
According to the commands output you have given about the configuration, bonding looks good so far. That all interfaces have the same mac address is due to bonding and will not confuse the fritz box router. Quite contrary it ensures that it does not sense the change of an interface on the fly because the mac address doesn't change. That's the trick of ...
I have configured my raspberry pi to something like you said.
I will be able to view live feed through Mobile app or in a browser
The motion is here for you. It has a web interface that you can see the camera's stream in real-time.
How to Make Raspberry Pi Webcam Server and Stream Live Video || Motion + Webcam + Raspberry Pi
When the Raspberry ...
This is my answer based on how I've read your situation:
If your ethernet port got blocked by your IT sysadmin because it was being used for brute forcing SSH/some other malicious behaviour, then it's likely one of your WiFi users started to abuse your service.
It's not out of the realms of possibility that somebody complained they were getting excess / ...
I do not have the ralink rt2870 USB/WiFi adapter but here are some general ideas I have tested with the built-in WiFi device that you should also verify with your adapter. How to set the txpower on a RPi 3B+ I have shown at Restrict WiFi range of Pi 3b+. It also works on a RPi 4B.
If I do not have a valid /etc/wpa_supplicant/wpa_supplicant.conf file, I get ...
"pi-ap" automates configuration of your Pi into a wireless AP. You can use the "pi-ap" scripts which are tested and proven to produce a working Pi wireless Access Point for comparative analysis with your own (broken) config. They're just a pile of bash scripts called in turn by the install.sh script. Things not obvious are well commented:
I encountered the same problem:
RPi3B and Geekworm X850 mSATA SSD Extension Board V 3.1 an a Sunbow mSATA 32GB:
Everything works as expected.
RPi3B+ and Geekworm X850 mSATA SSD Extension Board V 3.1 an a Sunbow mSATA 32GB:
No Wifi regardless of the booting device (SD or SSD) unless the SSD has no power connection (via USB or external). Powering up the ...
O help, just found out here what went wrong.
I've been having trouble with this too.
The answer was inside this command:
sudo wpa_supplicant -c/etc/wpa_supplicant/wpa_supplicant.conf -iwlan0 -d
I had placed the ssid and psk names between ' 'signs like ssid='my-network-ssid'
Changing it to "my-network-ssid" made it work right away.
And besides: raspi-...
Or if you want to disable WiFi at boot, in your /boot/ (or /boot/firmware/ ) "config.txt" file add or uncomment the line "dtoverlay=pi3-disable-wifi" Note that this may be simply "dtoverlay=disable-wifi" in newer configurations.
To reenable wifi, comment out the line with a leading hash (octothorpe) symbol. (a "#")
[ I use 'mcedit' as my preferred editor. ...