Often with Backtrack3 the iso download gets schnerbed. So the BT3 disk boots partially on one try and completely on the next.
It's incredibly annoying, but with any ISO burn, if it doesn't work consistently, toss the disk, verify the checksum, and rebui;rn!
These cards have been tested to work in BT3:
http://backtrack.offensive-security.com/index.php?title=HCL:Wireless
Find your card and see the recommendations.
# dmesg
# ifconfig -a
You should see your card loaded, and you should see a device.
#lspci
Generally with BT3, your best bet is going to be using the Wireless tools in the menus, until you determine what is what.
Hey also, if you are on a shared wireless network check out the SMB4k - be careful not to get into trouble here.
Ethical hackers learn they do not impact the systems they study, (unless paid) and they DO NOT GO TO JAIL!
And USE THE SOURCE:
http://backtrack.offensive-security.com/index.php/ToolsObnosis | (503)754-4452
PLUG Linux Security Labs 2nd Saturday Each Month@Noon - 3PM
Date: Wed, 18 Mar 2009 22:36:03 -0400
Subject: rausb0 up
From:
bmike1@gmail.comTo:
PLUG-discuss@lists.plug.phoenix.az.us
it is strange. after I had downloaded backtrack3 and fired it up and the distro automaGICALY FOUND THE WIRELESS CARD AND i HAD WEB-ACCESS. the two subsequnt times I loaded it I didn't have web-access and that left me dum-founded. So I looked around and found that 'rausb0 up' is the comand I need to use but linux told me that that wasn't the device name. So please tell me, what is it that is assigned to an internal wireless card. How should I find out if you can't tell me.
You know.... I just looked at what I thought the device is called and just realived (DUHHHHH) it isn'r a USB device
--
:-)~MIKE~(-:
Windows Live™ Contacts: Organize your contact list.
Check it out.