|Configuring Wireless Connectivity within Backtrack 4 r2|
|Version||version 4 r2|
|UNIX / Linux - Debian / Ubuntu|
|Wednesday, 16 February 2011 13:04|
This article aims to explain the various steps required in configuring Wireless connectivity within Backtrack 4 r2. It is also worth mentioning that as Backtrack is based upon Ubuntu/Debian you may find steps and solutions within this article useful when faced with other Ubuntu/Debian based wireless issues.
1. Install wicd
First you will need to install wicd and remove the standard network-manager (if installed). wicd is an open source wired and wireless network manager for Linux which we will use later to configure your wireless connection.
sudo apt-get update
2. Determine Wireless Card
Next you will need to determine the make and model of your wireless card within your system. This is achieved by running the following command :
root@bt:~# lspci | grep Network
3. Download Drivers
I found the best source for Linux wireless drivers could be found here : http://linuxwireless.org/en/users/Download/stable/
Based on my wireless card being a Atheros AR9285 the ath9k drivers were selected.
4. Confirm MODULE LOAD
Once your system has rebooted confirm that the driver has been loaded by running the following command.
root@bt:~# lshw -C network -network
You can also check to see if the module (driver) is loaded by running the command - lsmod | grep ath9k
5. Configure WiFi Connection
Next you will need to configure your connection, adding your settings such as keys, encryption etc etc. To access the Wicd Network Manager go to "K Menu" --> Select "Internet" and click on "Wicd Network Manager".
Once you have configured your settings you should have the required wireless connectivity within Backtrack.
The main issue I faced when configuring the above was that after adding my wireless key and then trying to connect I would get the message
Unable To Get IP Address
If I then configured a static IP address I received the message,
Connection failed: Could not contact the wireless access point
To resolve this I removed the following file and rebooted.
sudo rm /etc/udev/rules.d/70-persistent-net.rules
- Incapsula (Review) - How to Protect and Secure your website in 10 minutes
- Window wont show when using Cisco VPN Client 5.x / Windows 7
- How to Fix Unreadable Directory Listings within the Shell
- Python - List Comprehensions
- Python - What does 'if __name__ == "__main__"' mean ?
- Python - Decorators
- BIGIP F5 LTM - Action on Service Down
- Brocade ADX - How do I bind multiple ports to a single healthcheck ?
- MySQL - How to reset a forgotten Root password
- Django - How can I pass a string from a URL to a view ?
- Vyatta - Unable to log into GUI : "Username or password is incorrect"
- Cisco ASA - How do VPN Filters work ?
- How do I use AJAX along side Django ?
- Outlook 2010 - The 'Delete Conversation' Shortcut
- How do I import a python module from another folder ?
- How do I configure Django to serve my Robots.txt file ?
- Brocade ADX - The Dynamic Weighted Predictor
- How to serve multiple domains from within a single Django project
- Vyatta - How do I secure management access ?
- Vyatta - How to configure an IPSEC site to site VPN
- Proxy ARP – SPLAT
- Check Point Commands
- IPSO - Commands
- ASA 8.3 - Auto NAT Examples
- vSphere - Creating User and Group Permissions
- Configuring Wireless Connectivity within Backtrack 4 r2
- Juniper Netscreen Commands
- Configuring Windows 2008 R2 as an NTP Server
- How to set the Time / Date and Timezone in CentOS
- PEMU - Free Cisco PIX Firewall Emulator / Simulator
- Juniper Netscreen - NAT Explained
- How do I install snmpwalk / snmpget using Yum ?
- Troubleshooting a Netscreen Site 2 Site VPN
- Netscreen - NSRP
- Check Point Logging Troubleshooting Guide
- How do I configure IPv6 in Windows XP ?
- Check Point - How to Reset SIC
- Endpoint Connect Installation / Troubleshooting Guide
- VI shows the error Terminal too wide within Solaris
- ESX Convertor - The session is not authenticated