No wireless internet connection

[maverik35]

Hi..Can you type : lsmod and see what modules is the kernel loading? Look for the ieee802.11(r8187) or the mac802.11(rtl8187) only if the chipset is realtek 8187L...You have to look at your wifi card, Identify the vendor and check the chipset..If it is a USB device, it will be recognized as "wlanx", if it is internal device such as miniPCI, PCI, etc, it will be recognized as "ethx".
Once you know what type of chipset and type of device (USB, ethernet), see if it has compatibility with the aircrack-ng suite, already installed in BT5....
If you get a "No such device", it is because is not there or it is damaged..In your case, you could possibly be using an internal device. According to your post and I qute:
I type iwconfig and show this:
lo no wireless extensions.

eth1 no wireless extensions.
It tells you that you have the eth1 as device, it is an internal device...Not USB device (external usb)

I quote:
type lsusb and show this
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

It tells you that you have 2 usb "ports"...But not meanning you have a device connected...If you had a USB device such as, per say, alfa 500, it would say something like this:
Bus 001 Device 002: ID 103:788 Alfa Network Corp. USB Adapter
Bus 003 Device 002: ID 413e:900 Dell Computer Corp. BC02 Bluetooth USB Adapter (If you have a bluetooth device attached)
etc..

Hope it helps you and best of luck.

[Pathos]

What is displayed when you run rfkill list in terminal?

[Feniks]

When I type ''rfkill list'' show me
Wireles lan
soft blocked: no
hard blocked: yes.

Edit:

Hi..Can you type : lsmod and see what modules is the kernel loading? Look for the ieee802.11(r8187) or the mac802.11(rtl8187) only if the chipset is realtek 8187L...You have to look at your wifi card, Identify the vendor and check the chipset..If it is a USB device, it will be recognized as "wlanx", if it is internal device such as miniPCI, PCI, etc, it will be recognized as "ethx".
Once you know what type of chipset and type of device (USB, ethernet), see if it has compatibility with the aircrack-ng suite, already installed in BT5....
If you get a "No such device", it is because is not there or it is damaged..In your case, you could possibly be using an internal device. According to your post and I qute:
I type iwconfig and show this:
lo no wireless extensions.

eth1 no wireless extensions.
It tells you that you have the eth1 as device, it is an internal device...Not USB device (external usb)

I quote:
type lsusb and show this
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

It tells you that you have 2 usb "ports"...But not meanning you have a device connected...If you had a USB device such as, per say, alfa 500, it would say something like this:
Bus 001 Device 002: ID 103:788 Alfa Network Corp. USB Adapter
Bus 003 Device 002: ID 413e:900 Dell Computer Corp. BC02 Bluetooth USB Adapter (If you have a bluetooth device attached)
etc..

Hope it helps you and best of luck.

Hi..Can you type : lsmod and see what modules is the kernel loading? Look for the ieee802.11(r8187) or the mac802.11(rtl8187) only if the chipset is realtek 8187L...You have to look at your wifi card, Identify the vendor and check the chipset..If it is a USB device, it will be recognized as "wlanx", if it is internal device such as miniPCI, PCI, etc, it will be recognized as "ethx".
Once you know what type of chipset and type of device (USB, ethernet), see if it has compatibility with the aircrack-ng suite, already installed in BT5....
If you get a "No such device", it is because is not there or it is damaged..In your case, you could possibly be using an internal device. According to your post and I qute:
I type iwconfig and show this:
lo no wireless extensions.

eth1 no wireless extensions.
It tells you that you have the eth1 as device, it is an internal device...Not USB device (external usb)

I quote:
type lsusb and show this
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

It tells you that you have 2 usb "ports"...But not meanning you have a device connected...If you had a USB device such as, per say, alfa 500, it would say something like this:
Bus 001 Device 002: ID 103:788 Alfa Network Corp. USB Adapter
Bus 003 Device 002: ID 413e:900 Dell Computer Corp. BC02 Bluetooth USB Adapter (If you have a bluetooth device attached)
etc..

Hope it helps you and best of luck.

Here's what you told me to type could you explain what this means
airmon-ng


Interface Chipset Driver

wlan1 Realtek RTL8187L rtl8187 - [phy0]

root@bt:~# airmon-ng start wlan1


Found 1 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
813 dhclient3


Interface Chipset Driver

wlan1 Realtek RTL8187L rtl8187 - [phy0]SIOCSIFFLAGS: Unknown error 132

(monitor mode enabled on mon0)

root@bt:~# airodump-ng mono0
Interface mono0:
ioctl(SIOCGIFINDEX) failed: No such device
root@bt:~# airodump-ng mon0
ioctl(SIOCSIFFLAGS) failed: Unknown error 132
root@bt:~# lsusb
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 1b75:8187
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

I would not bother you but I have just one more question. Since I no longer know what to do on website BackTrack I found this dmesg| tail -20 and I type this in
terminal and show me :
root@bt:~# dmesg| tail -20
[ 8922.495145] cfg80211: Updating information on frequency 2452 MHz for a 20 MHz width channel with regulatory rule:
[ 8922.495149] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (300 mBi, 2000 mBm)
[ 8922.495152] cfg80211: Updating information on frequency 2457 MHz for a 20 MHz width channel with regulatory rule:
[ 8922.495157] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (300 mBi, 2000 mBm)
[ 8922.495160] cfg80211: Updating information on frequency 2462 MHz for a 20 MHz width channel with regulatory rule:
[ 8922.512454] cfg80211: 2402000 KHz - 2472000 KHz @ KHz), (300 mBi, 2000 mBm)
[ 8922.512502] cfg80211: Updating information on frequency 2467 MHz for a 20 MHz width channel with regulatory rule:
[ 8922.512507] cfg80211: 2457000 KHz - 2482000 KHz @ KHz), (300 mBi, 2000 mBm)
[ 8922.512518] cfg80211: Updating information on frequency 2472 MHz for a 20 MHz width channel with regulatory rule:
[ 8922.512523] cfg80211: 2457000 KHz - 2482000 KHz @ KHz), (300 mBi, 2000 mBm)
[ 8922.512527] cfg80211: Updating information on frequency 2484 MHz for a 20 MHz width channel with regulatory rule:
[ 8922.512531] cfg80211: 2474000 KHz - 2494000 KHz @ KHz), (300 mBi, 2000 mBm)
[ 8922.516318] ieee80211 phy1: Selected rate control algorithm 'minstrel_ht'
[ 8922.518182] ieee80211 phy1: hwaddr 00:4f:78:01:89:bb, RTL8187vB (default) V1 + rtl8225z2, rfkill mask 2
[ 8922.732031] rtl8187: Customer ID is 0xFF
[ 8922.732675] Registered led device: rtl8187-phy1::radio
[ 8922.732822] Registered led device: rtl8187-phy1::tx
[ 8922.732957] Registered led device: rtl8187-phy1::rx
[ 8922.738623] rtl8187: wireless switch is off
[ 8923.415184] udev: renamed network interface wlan0 to wlan1

Does this have anything to do with my problem??
Sorry and thanks. )

[maverik35]

Are you making sure you are starting the networking services before running anything involving wifi card?
xx@xx>/etc/init.d/wicd start (for BT5 or any Linux using Wicd manager)
xx@xx>/etc/init.d/networking start (for any linux distro using Networking Manager)

After that, you can start using aircrack suite..But not before.....Then type xx@xx>lsmod
Please, post the results of lsmod, so we can see if OS loaded the driver...Then retype xx@xx>lsusb
Here is my "lsusb" output:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 002: ID 413c:8000 Dell Computer Corp. BC02 Bluetooth USB Adapter
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 1d57:0008
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
As you can see, I have device 001: ID 413c is my bluetooth
device 002: ID 1d57 is my wireless mouse
The rest is unused usb ports (nothing connected to them)
In your case your OS found device: Bus 001 Device 002: ID 1b75:8187 So it is something connected, but by no means can assure you that correct drivers are being loaded or that Networking services are being started..So make sure first to start "networking services", then check what driver was loaded by typing "lsmod |grep -i ieee", this way you'll know if drivers from ieee stack were loaded, or type "lsmod |grep -i mac802" if drivers from mac stack were loaded. This way we can see what type of drivers we are working with..
I had an experience with realtek chipset 8187b and OS loaded the r8187 driver, which is the driver for rtl8187L, and is not the right driver to work with..That is why 8187B are not supported by aircrack..
According to your dmesg output, the kernel:
ieee80211 phy1: hwaddr 00:4f:78:01:89:bb, RTL8187vB (default) V1 + rtl8225z2, rfkill mask 2
It is showing a RTL8187vB, I want to belive it is a rtl8187B and it is not supported by aircrack-ng suite yet....Make sure you have the RTL8187L chipset, go to the vendors page and be sure the type of chipset, this is very important.
Best of lucks.

[Feniks]

Are you making sure you are starting the networking services before running anything involving wifi card?
xx@xx>/etc/init.d/wicd start (for BT5 or any Linux using Wicd manager)
xx@xx>/etc/init.d/networking start (for any linux distro using Networking Manager)

After that, you can start using aircrack suite..But not before.....Then type xx@xx>lsmod
Please, post the results of lsmod, so we can see if OS loaded the driver...Then retype xx@xx>lsusb
Here is my "lsusb" output:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 002: ID 413c:8000 Dell Computer Corp. BC02 Bluetooth USB Adapter
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 1d57:0008
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
As you can see, I have device 001: ID 413c is my bluetooth
device 002: ID 1d57 is my wireless mouse
The rest is unused usb ports (nothing connected to them)
In your case your OS found device: Bus 001 Device 002: ID 1b75:8187 So it is something connected, but by no means can assure you that correct drivers are being loaded or that Networking services are being started..So make sure first to start "networking services", then check what driver was loaded by typing "lsmod |grep -i ieee", this way you'll know if drivers from ieee stack were loaded, or type "lsmod |grep -i mac802" if drivers from mac stack were loaded. This way we can see what type of drivers we are working with..
I had an experience with realtek chipset 8187b and OS loaded the r8187 driver, which is the driver for rtl8187L, and is not the right driver to work with..That is why 8187B are not supported by aircrack..
According to your dmesg output, the kernel:
ieee80211 phy1: hwaddr 00:4f:78:01:89:bb, RTL8187vB (default) V1 + rtl8225z2, rfkill mask 2
It is showing a RTL8187vB, I want to belive it is a rtl8187B and it is not supported by aircrack-ng suite yet....Make sure you have the RTL8187L chipset, go to the vendors page and be sure the type of chipset, this is very important.
Best of lucks.

Thanks I made now maverick and now everything works properly. But now I have another problem. I tried to crack my wireless network and appears a new problem a problem with the ''handshake''. I pass all procedure and everything is as it should but when I get to ''aireplay-ng....''
show me this:

Sending 64 directed Deauth STMA[] [ 0 |64 ACKs]
Sending 64 directed Deauth STMA[] [ 1 |63 ACKs]
Sending 64 directed Deauth STMA[] [ 0 |64 ACKs]
Sending 64 directed Deauth STMA[] [ 0 |63 ACKs]
Sending 64 directed Deauth STMA[] [ 0|63 ACKs]
Sending 64 directed Deauth STMA[] [ 0 |64 ACKs]

and

Encryption
WPA (0 handshake)

Choosing first network as target.

No valid WPA handshakes found.


what does that mean and what to do?? I apologize but you are the only answer.

[Sys7emR00t]

Feniks, are you able to connect to the internet? From wicd, I mean.

Take a look here, http://www.aircrack-ng.org/doku.php?...no_such_device for the airmon-ng problems. I understand how frustrating configuring Backtrack can be sometimes, just keep googling and things should come together. It's odd that you're having this problem because the RTL8187 chipset is known to work well with Backtrack. Have you tried another box?

[Feniks]

Yes I can connect on the net over WICD.
but I found on the WIKI page a kind of injection for ''no valid handshake'' but now I can not find. It was a kind of tutorial and when I click it redirected me to a post on the forum here. but now I do not know how to get to it.

[darcstar]

The VMware versions cannot support additional interfaces, however you should be able to use your wireless card if you name it 'eht0'. VMware will support a hard wired connection and should allow you to connect through that interface. To find your wireless interface info go to 'device manager' in windows. hope you manage to get it working.

[shadowzero]

Yes I can connect on the net over WICD.
but I found on the WIKI page a kind of injection for ''no valid handshake'' but now I can not find. It was a kind of tutorial and when I click it redirected me to a post on the forum here. but now I do not know how to get to it.

This is probably what you're looking for: http://www.aircrack-ng.org/doku.php?id=cracking_wpa
I suggest reading up on the tutorials there. If it is your wireless network and you just want to test if you can capture the handshake and crack it, then you don't need to deauth the clients. Just have another device connect to the AP and aireplay-ng should be able to capture the handshake and it should notify you when it's captured the handshake. However, I've noticed that sometimes it doesn't, so you can manually check if the handshake was captured using either cowpatty or running aircrack-ng against the capture file. So if aireplay-ng is writing to out-01.cap then: cowpatty -c -r out-01.cap will tell you if the handshake has been captured.

[cbrobertson]

sorry about the (very) delayed response,

lsusb is
Bus 004 Device 001: ID ld6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID ld6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID ld6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID ld6b:0002 Linux Foundation 2.0 root hub

ifconfig shows:

eth0
Link encap: Ethernet HWaddr 00:0b:db:dc:31:40
UP BROADCAST MULTICAST MTU:1500 Metric:l
RX/TX packets, errors, dropped, etc all 0 except txqueuelen:1000
RX and TX bytes 0.0
Interrupt :ll

lo
Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:44 errors, dropped, overruns, frame:0
TX packets:44 errors, dropped, overruns, carrier, collisions, txqueuelen:0
RX/TX bytes 2849 (2.8KB)

It's a native installation, and lacking internet connectivity on computer in question (and after numerous google/ask.com searches, I was unable to figure out how to ascertain chipset.