Yes, there is a better way.
You can edit /boot/config.txt and add this two lines:
After reboot, WiFi & Bluetooth will be fully disabled.
More info on: https://github.com/raspberrypi/firmware/blob/master/boot/overlays/README
Literally the very next thing I tried worked. I spent the last 5 hours working on this so I'll go ahead and share what I did to fix.
First, I sourced my drivers from the following github repo.
sudo git clone https://github.com/gnab/rtl8812au.git
modified the Makefile
sudo nano Makefile
CONFIG_PLATFORM_I386_PC = n
CONFIG_PLATFORM_ARM_RPI = ...
Credit to pogo-pope on Reddit for the answer:
replace: KERNEL!="ath*|msh*|ra*|sta*|ctc*|lcs*|hsi*", \
Shutdown your Pi, remove the USB dongle you intend to call wlan1. Boot
up and plug the wlan1 dongle back ...
I know this question asks for instructions on Arch Linux, but since I have been struggling for several days with the exact same issue on Raspbian Wheezy I thought it might be helpful if I shared my solution anyway.
Basically, I ended up creating a solution where my Raspberry Pi (RPi) tries to connect to one of its known wireless networks, and if that do not ...
Problem solved!!! I will explain here the steps I took:
I bought a good 2A charger, which at the beginning helped to see the blue light of the dongle. However it didn't yet connect. So googling and googling I came across this page
he gives a solution so that the dongle gets detected always. If you do exactly ...
You can install any VNC server app on your Android, such as VMLite VNC Server. On the RPi you can use a VNC viewer, such as SSVNC (sudo apt-get install ssvnc) or xtightvncviewer (sudo apt-get install xtightvncviewer) to connect to your Android VNC server and take control of your Android desktop. This does require you to have access to the RPi - so it doesn't ...
You don't have to change to dhcp.
cat /etc/resolve.conf should show you which dns servers are currently configured.
As dastaan said, you can just type ping google.com to see if you are resolving basic addresses. You can also use nslookup google.com
To add a dns server w/o changing your permanent setup, just add the entries to /etc/resolv.conf. This ...
Usually via DHCP you get also the names of the DNS servers to use so that you Debian/Raspbian can automatically configure them in order to resolve hostnames into IP addresses (and vice versa).
When you go static you need to specify it. On recent Debian/Ubuntu, this is done like follow, and I believe that this would be similar on Raspbian.
Add an extra line ...
I suggest using Bluetooth Low Energy (BLE). You can get a dongle (pay attention that it is a BLE and not regular Bluetooth dongle).
As name already says - it is low energy.
Then I would setup an ad hoc network over Bluetooth connection. I have written a blog post about that.
You can use ssh with IP address set up by DHCP.
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 ...
Assuming you don't have any network equipment other that the WIFI dongle that you could unplug, you could simply write
SUBSYSTEM=="net", ACTION=="remove", RUN+="/path/to/command"
into a file named /etc/udev/rules.d/my_custom.rules. Note that you need to specify the full path to your command, since it will be executed directly, without using a shell.
Per the comments below your question, that's just not how USB works. Your desktop is enjoying a variety of advantages over the Pi - a USB 3.0 adapter, superior bandwidth on its internal buses, faster CPU, etc. etc. etc. It's not entirely realistic to expect similar performance from a Pi.
The Netgear adapter you've spec'd may well not work as expected in ...
Wireless keyboards could operate by using radio frequency (RF) or infrared (IR). RF techniques range from 27 MHz to up to 2.4 GHz (according to wikipedia). With Bluetooth being a widely used technology. While both WiFi and Bluetooth share the 2.4 GHz band they differ both in technical aspects as well as in their objective.
So in short: Your (presumed) ...
it shows me a bunch of wi fi networks...so it must be working right?
Yep, you would not be able to scan for wifi networks without a working wifi adapter.
service networking stop
wpa_supplicant -B -c /etc/wpa_supplicant/wpa_supplicant.conf -i wlan0
dhclient -v wlan0
Wait ~5 seconds between the last two commands; you'll see a bit of ...
I second the power comment. I too have had "working" Pi configurations that suddenly started showing problems after months. In my case I was running edimax wifi and shairport for apple airplay support. The bandwidth was always marginal, but it worked. One day the wifi died, and I ultimately determined that a better wall wart solved the problem and ...
If an adapter doesn't show up in lsusb that usually means that it needs firmware file(s) and your dmesg output proves that:
[ 140.213122] r8188eu 1-1.2:1.0: Direct firmware load for rtlwifi/rtl8188eufw.bin failed with error -2
[ 140.213169] r8188eu 1-1.2:1.0: Firmware rtlwifi/rtl8188eufw.bin not available
Installing the firmware-realtek package should ...
You will need to allocate the extra resource for a server software to send these details to your chosen solution. It is unclear what you want to be sending over, just text data? Or image data too?
For Images, video streams, you can use a normal WiFi dongle, during debug mode plug it in and start your server. A simple Python web server that can push the data ...
If you are using a low power source like laptop USB port or external battery try to connect it to electricity using a 5V charger.
Try the following:
I do a static config for eth0 bcz its easier for me to get the IP address but u also have to configure your wired device into the same subnet
$ nano /etc/network/interfaces
iface lo inet loopback
Most Realtek Wi-Fi dongles do work on the pi, i had the same problem with a different Realtek dongle when i first tried to use it. You should start by getting an internet connection with a network cable and making sure it is up to date by using the commands :
sudo apt-get update
Once that has run you run:
sudo apt-get upgrade
After a reboot then you ...
If you configure the WiFi connection via /etc/wpa_supplicant/wpa_supplicant.conf, it should automatically connect - example file contents:
#Set wifi network name and password here
# Protocol type can be: RSN (for WP2) and WPA (for WPA1)
If you are sure your adapter works fine, try running the command
sudo ifconfig wlan0 up
When you do this, all the available wifi networks should show up when you click the wifi signal button at the top right of the screen. You should then be able to click any of them and type in your password.
Edit: Try running the command sudo iw dev wlan0 scan since you ...
Atheros based wifi adapter - TP-LINK TL-WN722N, would definitely solve your purpose of making wifi adapter work in dual mode. The driver should work out of the box on raspian or should be little effort to figure out and install the driver. You would however need other settings to being up vlan interface, etc.
To build this module from source, I did the following on my RPI2.
Install build tools:
# apt install build-essential bc git wget
Get kernel source code
# cd /usr/src
# git clone --depth 1 https://github.com/raspberrypi/linux.git
# ln -s linux $(uname -r)
# ln -s /usr/src/linux /lib/modules/$(uname -r)/build
Prepare linux build headers
# cd linux
# wget ...
I've found that most of my chargers don't provide enough power to my PI3, even if the "under-voltage" icon doesn't show up. This causes the Wifi and Bluetooth to be disabled in an otherwise working system. An original Apple iPad charger did the trick.
I don't know if you have solved your problem after 2 years without an accepted answer but here is a solution for someone coming to this by google.
The problem is that you need to bridge the wired interface eth0 with the client wlan0 uplink to the internet router but this isn't supported by the on-board WiFi device of a Raspberry Pi 3B. So you have to use ...
I suppose you have completely setup and running Building a 'Packet squirrel" using Raspberry Pi you have linked in your question. It is using systemd-networkd. If you want to extend it with WiFi you also have to use systemd-networkd, in particular to use *.network configuration files. So try this and add setup wpa_supplicant in addition to the existing ...
Make sure to boot the Pi with the usb dongle attached.
Edit /etc/network/interfaces and add the following to the bottom:
iface wlan0 inet dhcp
wpa-ssid "your network name"
wpa-psk "your password"
If you want to give it a static ip then just do:
iface wlan0 inet static
address 192.168.0.XX #static ip address
I had a TP-LINK 723N, which is basically the same thing as the 725N V2. Raspbian did not support it out of the box. I had to download and install drivers; specifically the 8188eu.ko. I used this forum post to get mine working.