Hot answers tagged wifi
How about iwgetid? The iwgetid(8) man page says: iwgetid is used to find out the NWID, ESSID or AP/Cell Address of the wireless network that is currently used.
You usually have a button or switch on your wifi adapter which can be used to forcibly stop the signal. There is nothing you can do in software to change that, only observe it (but note that there are some drivers which do not observe it correctly, and always generate one result); you need to press the button or flip the switch.
Debian 3.2.60-1+deb7u3 x86_64 GNU/Linux 867Mbps 802.11ac Intel 7260 card, Dual band 5GHz + 2.4GHz Wireless 2x2 AC + Bluetooth4.0 Your kernel is too old. http://wireless.kernel.org/en/users/Drivers/iwlwifi says "Intel® Wireless 7260 (3.10)", so you'll need at least Linux 3.10. Set up Debian backports, and install a newer kernel: aptitude -t ...
Turning network interfaces down does not in general cause TCP connections to terminate. That's the way TCP/IP is designed. The idea is that links that go down should not cause the upper layers to give up on connections because the problem might be transient and go away quickly, or routing protocols may promptly install alternate routes and heal the network ...
According to this kernel.org page on wireless drivers; yes you have the right driver! Whether or not a newer version (than what your distro supplies) would be better or not will depend... I have had newer versions of drivers work better but I have also had newer version work worse... So the best answer to that question IMO is another question: "Does it work ...
According to your link the filename of the driver should be mt7601Usta.ko (.ko is the extension for kernel modules). Kernel modules are usually installed in /lib/modules/$(uname -r), so use find /lib/modules/$(uname -r) -name mt7601Usta.ko then sudo rm to delete it if you're sure it is the right module (or mv to move it out from the modules tree so it won't ...
NOTE: I'm on Fedora 20 but the issue would be the same here, only the pathing and Linux kernel version numbers are different. When I downloaded and attempted to run the install script, bash ./install.sh I noticed this error message as well. make: *** /lib/modules/3.16.3-200.fc20.x86_64/build: No such file or directory. Stop. The script isn't equipped ...
I found a fix to the compilation errors in another driver on this website: http://www.arnelborja.com/compiling-rt2870-wifi-driver-in-fedora/ below is the patch content: --- include/os/rt_linux.h 2013-09-12 13:27:14.000000000 +0800 +++ include/os/rt_linux.h.patched 2014-03-23 11:45:03.907628847 +0800 @@ -279,8 +279,8 @@ typedef struct file* RTMP_OS_FD; ...
After the commands above, restarting the hostapd did the trick. sudo service hostapd restart Now the internal wifi works as an access point and the usb dongle is connected to another access point providing internet connection.
This is what you need to do, as using 4 accounts will cost you extra, cannot be used at the same time, and may be illegal in your AUP anyway. Disconnect All Computers from the Internet. Remove All PPPoE Connection Software from all computers. Find the Ethernet Cable that came with your Router. Disconnect the DSL Cable from the DSL Port Disconnect the Power ...
It doesn't sound like 'bridging' is what you're looking for, it sounds like you want your Pi to act as an access point and share the internet it sees on wlan0 via a new SSID on wlan1. See this guide for details on how to set that up: http://www.maketecheasier.com/set-up-raspberry-pi-as-wireless-access-point/
Only top voted, non community-wiki answers of a minimum length are eligible