You are trying to use a internal wireless device within a VB? (Virtual Box)
If so, may I direct you to this link: http://www.backtrack-linux.org/forum...rking-bt4.html
I have done as much reading as I can, but haven't found anything to help me yet.
I have a Dell Inspiron 1520, card is a Dell Wireless 1395 WLAN mini card.
My card works great in Ubuntu. Of course all I have to do is click "Auto eth0"
I am using VirtualBox for V.M.s
I have run the following: (as root)
/etc/init.d/networking start
/etc/init.d/wicd start (seems to be the same as /usr/bin/start-network)
/usr/bin/wicd-client
My settings in wicd client, preferences, general list eth0 was wired and wireless.
I have been trying to read up on this and figure it out for about a week now.
Someone help me understand how this works?
Iwconfig lists lo, eth0, and eth1 all as "no wireless extensions"
My wicd manager says no wireless networks found.
I have been reading up for a week.
My wireless works fine in Ubuntu.
Virtualbox V.M.
Have done basics, start networking, start wicd and client.
Last edited by Archangel-Amael; 03-06-2010 at 10:42 PM.
You are trying to use a internal wireless device within a VB? (Virtual Box)
If so, may I direct you to this link: http://www.backtrack-linux.org/forum...rking-bt4.html
Last edited by micole; 03-09-2010 at 01:46 AM. Reason: VB = Virtual Box
Common Knowledge: Username, "root". Password, "toor". "startx" gives you a GUI, and "fix-vesa" will fix BT if you have no GUI. Start networking with "/etc/init.d/networking start" and check your IP settings with "ifconfig -a". "dhclient" will automatically use DHCP for your IP. Google is your friend.
The only thing I got out of that was lspci.
That command appears to give the same results in both backtrack and ubuntu.
Ubuntu also does not recognize anything with iwconfig.
lo, eth0 no wireless extensions.
However, it does recognize eth0 with ifconfig.
I am having trouble believing that just because I am using a V.B. it will not work, as it works great in Ubuntu.
And if that is the case, why does it not work?
NEVERMIND.
I got it, works great!
Last edited by Archangel-Amael; 03-07-2010 at 02:56 PM.
While using a VB or a VM (Virtualbox or a Virtualmachine) The onboard PCI cards are "converted" into a virtual ethernet adapter. So your internal wireless now look like they are just regular wired connections. This has been discussed over the forums more then once, and I even think it is in the FAQ... let me go check... Yep right here http://www.backtrack-linux.org/forum...irtualbox.html.
I would either go set it up in a non-VB machine, or buy a USB wireless adapter.
Hope this helps. If not, respond, pm, message, or get on the IRC.
Common Knowledge: Username, "root". Password, "toor". "startx" gives you a GUI, and "fix-vesa" will fix BT if you have no GUI. Start networking with "/etc/init.d/networking start" and check your IP settings with "ifconfig -a". "dhclient" will automatically use DHCP for your IP. Google is your friend.
I got it figured out. Had something configured wrong.
Sees it as a wired connection, was not aware of that. That may be a problem...
Common Knowledge: Username, "root". Password, "toor". "startx" gives you a GUI, and "fix-vesa" will fix BT if you have no GUI. Start networking with "/etc/init.d/networking start" and check your IP settings with "ifconfig -a". "dhclient" will automatically use DHCP for your IP. Google is your friend.
Here are two images for you to read:
REMOVED
and:
REMOVED
Sorry, I won't post the banners again
Last edited by micole; 03-08-2010 at 05:05 AM. Reason: we don't need stuff like that
Common Knowledge: Username, "root". Password, "toor". "startx" gives you a GUI, and "fix-vesa" will fix BT if you have no GUI. Start networking with "/etc/init.d/networking start" and check your IP settings with "ifconfig -a". "dhclient" will automatically use DHCP for your IP. Google is your friend.