[>] HowTo Make a valid Thread.
NOTE: This will be a quick example that will show you how a thread should look like.
In this thread I will be a user which is having trouble getting his wireless card working so I decide to make a thread asking for help.
Step 1: Searching
NOTE: Before opening a thread make sure you read our Wiki, FAQ and do a bit of searching on the internet, in most cases the time you wait for your thread to be moderated + the time for someone to respond to it is a lot grater than the time it will take you to find a solution by searching.
Now wheather you realize it or not most of your issues can be found by doing some simple searching, so in our case we will check:
- The Backtrack Wiki
- The Aircrack-ng website
- Google
We are going to pretend that we could not find any useful information here and move on with creating our thread.
Step 2: Creating an appropriate thread
* The Thread Title:
If we take a look at the Forum Rules we can see the following:
Quote:
Use sensible descriptive titles in your posts.
This means you will have to correctly choose a thread title in order to give the readers a clue about what that thread might contain. So do not choose titles similar to: "Help!!!", "Wireless not working", "Need Assistance!", etc.
* Introduction:
The first thing of your thread should contain a short write-up describing your problem.
* Necessary details:
After a description of your problem you need to provide the necessary details so that people will be able to assist you.
By necessary details I refer to:
- Backtrack version (KDE/GNOME, Arhitecture)
- Backtrack installation (VM, HDD, USB)
- Basic output of commands (ifconfig, iwconfig, lspci, lsusb, dmesg, etc.)
- An error message (if any)
- Links to the same problem (if any)
- Solutions tried and their result
WARNING: OPENING A THREAD THAT DOES NOT CONTAIN THE NECESSARY INFORMATION MENTIONED ABOVE WILL NO LONGER BE APPROVED!!!
Let's see how this thread should look like.
Re: [>] HowTo Make a valid Thread.
Thread title: USB WiFi Card (zd1211rw) SIOCSIFFLAGS error.
Introduction:
Hello, I have a HDD install of 32 bit Backtrack 5 with GNOME as a WM. Recently I bought a SMCWUSB-G 802.11bg which uses the zd1211rw chipset and I am having some trouble getting it to run properly on Backtrack 5 (This adapter however was tested on Backtrack 3/4 and was confirmed as working).
Details:
Here is the output of some basic commands:
iwconfig
Code:
root@bt:~# iwconfig
lo no wireless extensions.
eth0 no wireless extensions.
wlan0 IEEE 802.11bg ESSID:off/any
Mode:Managed Access Point: Not-Associated Tx-Power=0 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off
ifconfig
Code:
root@bt:~# ifconfig wlan0 up
ioctl(SIOCSIFFLAGS) failed: No such file or directory
airmon-ng / airodump-ng
Code:
root@bt:/home# airmon-ng start wlan0
Found 2 processes that could cause trouble.
If airodump-ng, aireplay-ng or airtun-ng stops working after
a short period of time, you may want to kill (some of) them!
PID Name
885 dhclient3
1527 dhclient3
Process with PID 1527 (dhclient3) is running on interface wlan0
Interface Chipset Driver
wlan0 Zydas zd1211rw - [phy0]SIOCSIFFLAGS: No such file or directory
(monitor mode enabled on mon0)
root@bt:/home# airodump-ng mon0
ioctl(SIOCSIFFLAGS) failed: No such file or directory
dmesg | tail
Code:
[ 877.911195] device mon0 entered promiscuous mode
[ 880.650405] usb 1-1: Could not load firmware file zd1211/zd1211b_ub. Error number -2
[ 880.650413] zd1211rw 1-1:1.0: couldn't load firmware. Error number -2
[ 959.639458] usb 1-1: Could not load firmware file zd1211/zd1211b_ub. Error number -2
[ 959.639469] zd1211rw 1-1:1.0: couldn't load firmware. Error number -2
[ 965.210303] usb 1-1: Could not load firmware file zd1211/zd1211b_ub. Error number -2
[ 965.210310] zd1211rw 1-1:1.0: couldn't load firmware. Error number -2
[ 965.210322] device mon0 entered promiscuous mode
[ 968.347700] usb 1-1: Could not load firmware file zd1211/zd1211b_ub. Error number -2
[ 968.347716] zd1211rw 1-1:1.0: couldn't load firmware. Error number -2
I have found similar issues here: (pretend they are not on this forum)
http://www.backtrack-linux.org/forum...ory-error.html
http://www.backtrack-linux.org/forum...esnt-work.html
