|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
- BigIP F5 LTM - Application Visibility and Reporting (aka Analytics)
- TCL - What is the difference between the eq and == operators ?
- Cisco ASA - How to Permit/Deny Traffic based on Domain Name (FQDN)
- How do I install g++ via Yum ?
- How do I install node.js in Centos ?
- Brocade ADX - The CSW Pseudo Stack
- Vyatta - How to Configure a Remote Access VPN
- Brocade ADX - How do I show the CPU usage for the MP (Management Processor) ?
- Vyatta - How do I configure NAT ?
- HTTP - What does 'Transfer-Encoding : Chunked' mean?
- Cisco ASA - SCP causes orphaned ssh_init processes
- F5 LTM (Deep Dive) - Using 'persist uie add' with the 'node' command in an iRule causes the F5 to send a RST
- VMware - vCetntre/vSphere shows virtual machine as 'Unknown VM' and inaccessible
- Brocade ADX - How to tune/configure the TCP stack
- Configuring a Hairpin VPN with Double NAT on a Cisco ASA running 8.0
- UNIX - What is a sticky bit ?
- Cisco ASA - Slow Memory Leak (CSCuh48577)
- F5 LTM - What is Auto Last Hop
- ADX - What is the order of priority for healthchecks ?
- Cisco ASA - ERROR: Capture doesn't support access-list containing mixed policies
- Check Point Commands
- Proxy ARP – SPLAT
- IPSO - Commands
- ASA 8.3 - Auto NAT Examples
- How to set the Time / Date and Timezone in CentOS
- vSphere - Creating User and Group Permissions
- Configuring Windows 2008 R2 as an NTP Server
- Juniper Netscreen Commands
- Configuring Wireless Connectivity within Backtrack 4 r2
- How do I install snmpwalk / snmpget using Yum ?
- Juniper Netscreen - NAT Explained
- VI shows the error Terminal too wide within Solaris
- PEMU - Free Cisco PIX Firewall Emulator / Simulator
- Troubleshooting a Netscreen Site 2 Site VPN
- Check Point Logging Troubleshooting Guide
- Check Point - How to Reset SIC
- Netscreen - NSRP
- How do I configure IPv6 in Windows XP ?
- Endpoint Connect Installation / Troubleshooting Guide
- Cisco ASA 8.3 - No NAT / NAT Exemption