Tag Info

New answers tagged

0

Upgrading my kernel from 3.13 to 3.16 (http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.16-utopic/) and reinstalling the new driver from https://github.com/lwfinger/rtlwifi_new seems to have solved my problems. Don't forget to reboot. Note: Upgrading the kernel in itself did not help.


0

For update and upgrade your kali linux: apt-get update & then apt-get upgrade Next : Set network adapter to BRIGED MODE if in virtual Box.


1

You can configure sudo so that members of a group can run a command without a password. Use visudo to edit the sudoers file: # visudo Add something similar to: %mygroup ALL = (root) NOPASSWD: iwlist wlanX scan to the bottom of the file (where mygroup is the name of your group preceded with a percent symbol). You could also allow a single user to run ...


1

Install the pciutils package. Use the command lspci. Post the output of lspci in your question using the Edit Link, and I'll help you install the driver after we know what it is. Read this Beginner's Guide to Debian Read the Official Debian Manual on Aptitude, the Debian Package Manager. You might want to do this one first, even though you asked it last. ...


1

Why is this Ethernet here? I am using wifi, not an Ethernet. Because you're not capturing in monitor mode; on most operating systems, the only way to get 802.11 headers, rather than fake Ethernet headers, on a Wi-Fi capture is to capture in monitor mode. This includes Linux, OS X, and Windows (although WinPcap doesn't currently support monitor mode). ...


1

When I changed the line auto wlan0 to allow-hotplug wlan0 in my /etc/network/interfaces file, it just worked. The answers to this question helped me.


0

Try: sudo apt-get update sudo apt-get install linux-headers-`uname -r` dkms build-essential bcmwl-kernel-source reboot See: https://answers.launchpad.net/ubuntu/+source/gnome-nettool/+question/252499


0

Although searching on the internet will lead you to instructions like: reboot/reset your router, reinstall "this" or "that" driver version or make sure your ESSID is not configured to be hidden, the problem may be the channel. Having a look at the 2.4 GHz (802.11b/g/n) specification (my router can only use de 2.4 GHz band), it seems that countries apply ...


0

It looks like https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1354924 P.S. 14.10 is not LTS.


-1

Fundamentally, your problem here is that the bandwidth on your downstream connection (eth0) is higher than the bandwidth on your upstream connection (wlan0). To solve this, you need to throttle the speed on eth0 to something below the speeds of wlan0; I have used Wondershaper for this sort of thing.


2

It all depends on how you define idle. If you're thinking of idle as being no user input, then you could write a script that monitors the output of: xscreensaver-command -watch which, according to it's man page: -watch Prints a line each time the screensaver changes state: when the screen blanks, locks, unblanks, or when the running hack is changed. ...


1

You cant access your WiFi adapter card from Virtualbox. You can only use some option like Bridge, NAT, etc.


0

I had the same issue and this site worked for me http://www.kalilinux.net/community/threads/how-to-make-broadcom-bcm43142-wireless-card-work-in-kali.814/


2

Access points are the equivalent to ethernet switches; they relay packets from one physical segment to another. The difference is that on one side the segment happens to be wireless. Moving from one AP to another is like unplugging an ethernet cord from one port on the switch and into another very quickly. A broadcast packet goes out notifying the ...


2

Access Points are essentially just relays; when you go from AP to AP you are never leaving the network, so if you do not encounter a physical (layer 1) lack of service somewhere in the middle, you should loose little or no data during the process. This is because there's no layer 3 renegotiation; consecutive access points are generally on different channels ...


1

I have the same issue. Might be a bug. Quick workaround is to run sudo killall NetworkManager from the command line. It will respawn quickly and connect.



Top 50 recent answers are included