8 replies
by cyberghost_1 Accepted solution
by markp24 Accepted solution
Have you tried this command in a terminal as root?
/etc/init.d/wicd start
or
/etc/init.d/networking start
if not check this post out
http://www.backtrack-linux.org/forums/backtrack-howtos/209-how-start-networking-backtrack.html
and this video
http://revision3.com/hak5/thereisapoint
by markp24 Accepted solution
by cyberghost_1 Accepted solution
by spitfire_sysop Accepted solution
I think it would be more trouble than it is worth. Plus BT is a live CD so why on earth would you run it virtualized? There are certain features that need special drivers for direct hardware access. This will be unreasonable to accomodate through an extra virtualized hardware abstraction layer.
I'm not saying it's impossible but it may not be possible without writing your own drivers.
by m.a.s. matrix Accepted solution
There are several reasons to run BT using virtualization. One is pen testing multiple platforms. It's much easier to accomplish without having to have several different physical systems.
As to your question about wireless....VMWare only picks up my USB wireless and if you are running the same set up, you can airmon-ng to see your wireless USB. My setting is bridged. Now, for your built in wireless, BT and VMware can use it but it shows up as a wired network. You have to set your settings for network in VMware to NAT and once in BT run 'start networking' from the cli. After that, you can verify that your "wired" network is up and running by typing 'ifconfig' and look for eth0. This will be your wireless networking showing up as a wired network.
by cyberghost_1 Accepted solution
by seanferd Accepted solution
This discussion is closed to new replies.
Trending Software posts
Sort by Trending