| Configuring Wireless Connectivity within Backtrack 4 r2 |
| Vendor | Offensive Security |
| Platform | BackTrack |
| Version | version 4 r2 |
| UNIX / Linux - Debian / Ubuntu |
| Wednesday, 16 February 2011 13:04 |
INTRODUCTIONThis 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. MY SETUP
STEPS1. Install wicdFirst 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 CardNext 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 DriversI found the best source for Linux wireless drivers could be found here : http://linuxwireless.org/en/users/Download/stable/ 3.1 DOWNLOAD wget http://www.orbit-lab.org/kernel/compat-wireless-2.6-stable/v2.6.38/compat-wireless-2.6.38-rc4-1.tar.bz2 3.2 COMPILE Based on my wireless card being a Atheros AR9285 the ath9k drivers were selected. bunzip compat-wireless-2.6.38-rc4-1.tar.bz2 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 ConnectionNext 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. ISSUESThe 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 RESOULTION To resolve this I removed the following file and rebooted. sudo rm /etc/udev/rules.d/70-persistent-net.rules |
Latest Articles
- F5 LTM VE 10.2.x - Interfaces not recognised
- Cisco ASA - Security Levels / NAT Control
- F5 LTM - OneConnect
- Django - CSRF verification failed. Request aborted.
- F5 LTM VE - Unable to attach to PCI device 02:01.00 for Interface 1.1
- F5 LTM - Connection Management
- Brocade ADX - FTP
- PKI - Chain of Trust
- Juniper SRX - Site to Site VPN using a Dynamic IP address
- F5 LTM - How do I perform software installations ?
- Juniper SRX - NAT
- Juniper SRX - How to configure a route based VPN
- Juniper SRX - Dynamic VPN
- Juniper SRX - How to configure a policy based VPN
- Brocade ADX - NAT
- Brocade ADX - CSW nested rules
- How do I upgrade a Juniper SRX Series gateway
- Cisco ASA - How do I capture ARP`s ?
- Juniper SRX - Configuring Source NAT with pool
- Running a packet capture on a Juniper SRX
Popular
- Proxy ARP – SPLAT
- Check Point Commands
- IPSO - Commands
- ASA 8.3 - How to configure NAT
- vSphere - Creating User and Group Permissions
- PEMU - Free Cisco PIX Firewall Emulator / Simulator
- Configuring Wireless Connectivity within Backtrack 4 r2
- Juniper Netscreen Commands
- Juniper Netscreen - NAT Explained
- How do I install snmpwalk / snmpget using Yum ?
- Netscreen - NSRP
- ESX Convertor - The session is not authenticated
- Troubleshooting a Netscreen Site 2 Site VPN
- ESX - ViClient Cannot connect to host
- Endpoint Connect Installation / Troubleshooting Guide
- Check Point - How to Reset SIC
- ESXi - Connecting to a named pipe
- Netscreen - Routing Basics / Virtual Routers / PBR
- Check Point Logging Troubleshooting Guide
- Configuring Windows 2008 R2 as an NTP Server
