When I booted my Dell Studio XPS laptop yesterday I received an error regarding the Wireless Configuration application. I first rebooted to see if it was just a fluke however I received the same error again. Below I describe the error in more detail as well as how to resolve the error by disabling a service that likely is not necessary.
I recently ordered one of the newer Asus routers just to stay up on the wifi world and I decided on the RT-N16. I normally like open-wrt firmware however its still listed as a work in progress for this router. This left me with 2 options, Tomato firmware and DD-WRT firmware. For the first run I decided on DD-WRT. Below I will outline the relatively simply steps to get up and running with dd-wrt on the n16
Recently I was working on a Dell Latitude D630 laptop computer that came into the computer shop and needed to have Windows XP reinstalled on it. After reinstalling Windows XP Professional on the Latitude D630 and attempting to reinstall all of the drivers needed there was still a device that did not have the proper drivers installed. The device displayed under Other Devices as USB Device with a yellow exclamation mark next to it. The article below describes the USB Device driver error as well as how to resolve the problem on a Dell Latitude D630.
First of I would like to say that none of these hacks and files are my own work. This stuff was done by all the amazing phone developers over at XDA Developers. I am am simply writing a few posts on rooting the HTC Evo since most of the information was all spread out over the forums and I had a hard time gathering it all together in a organized manner.
The WiFi chip in the HTC Evo supports Wireless N technology, which allows for faster throughput on your WiFi connection. To use this you need a Wireless N capable AP or router. For some reason HTC decided to disable the wireless n capability of this chip but this can be fixed. I am going to assume that the reason this was disabled was battery life but I am not really sure to be honest. Anyway the hack used to be more complicated but some of the nice folks over at XDA packages up a zip file which makes this hack a breeze.
Trying to capture a 4-way TKIP handshake without help can involve sitting and watching traffic for hours and hours, waiting for a client to connect to a network. By using a tool called aircrack-ng we can forcefully deauthenticate a client who is connected to the network and force them to reconnect back up. During the process of re-exchanging the encrypted WPA key, you will capture a handshake. In order to forcefully capture a 4-way handshake, you will need to deauthenticate a client computer that is actively using services, forcing it to exchange the WPA key and in turn capturing the handshake that can be decrypted.