still not working, any help ?
i use bt3 on the eeepc 701.
i successfully extracted the wep 128 bit wep key from my own wlan but i cannot connect from the backtrack 3 system via console or wireless assistant gui.
my net: KEY FOUND! [ 37:31:30:37:33:32:32:38:35:33:36:36:xx ]..
bt # iwconfig ath0 mode managed
bt # iwconfig ath0 essid "my net"
bt # iwconfig ath0 key xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx open
bt # iwconfig
lo no wireless extensions.
eth0 no wireless extensions.
wifi0 no wireless extensions.
ath0 IEEE 802.11g ESSID:"my net" Nickname:""
Mode:Managed Frequency:2.437 GHz Access Point: 00:1C:4A:09:D8:5E
Bit Rate:36 Mb/s Tx-Power:17 dBm Sensitivity=1/1
Retry:off RTS thr:off Fragment thr:off
Encryption key:3731-3037-3332-3238-3533-3636-xx Security mode:open
Power Management:off
Link Quality=14/70 Signal level=-82 dBm Noise level=-96 dBm
Rx invalid nwid:1249 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
bt # dhclient ath0
Internet Systems Consortium DHCP Client V3.0.6
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
wifi0: unknown hardware address type 801
wifi0: unknown hardware address type 801
Listening on LPF/ath0/00:15:af:8c:f7:83
Sending on LPF/ath0/00:15:af:8c:f7:83
Sending on Socket/fallback
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 6
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 15
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 8
again iwconfig
bt sda1 # iwconfig
lo no wireless extensions.
eth0 no wireless extensions.
wifi0 no wireless extensions.
ath0 IEEE 802.11g ESSID:"mynet" Nickname:""
Mode:Managed Frequency:2.437 GHz Access Point: 00:1C:4A:09:D8:5E
Bit Rate:1 Mb/s Tx-Power:17 dBm Sensitivity=1/1
Retry:off RTS thr:off Fragment thr:off
Encryption key:3731-3037-3332-3238-3533-3636-xx Security mode:open
Power Management:off
Link Quality=16/70 Signal level=-79 dBm Noise level=-95 dBm
Rx invalid nwid:11788 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
so dhclient fails, dhcpcd fails and manual ip configuration fails either.
the wep key is correct.. i can connect from other systems via this wep key.
can anyone help me with this ?
still not working, any help ?
use windows ...
if it works in windows yer doing it wrong :P
use spoonwep just type it in the CLI of bt3 its idiot proof
killall -9 dhcpd
wlanconfig ath0 destroy
macchanger --mac 00:11:22:33:44:55 wifi0
wlanconfig ath0 create wlandev wifi0 wlanmode managed
ifconfig ath0 up
iwconfig ath0 essid "my net" key 37:31:30:37:33:32:32:38:35:33:36:36:xx
iwconfig ath0 ap 00:1C:4A:098:5E
dhcpcd -d -n ath0
in windows the connection works perfectly with the discovered WEP key.
i also should mention that there is NO macfilter enabled on the AP.
I tried your suggestion, no success:
bt ~ # killall -9 dhcpd
dhcpd: no process killed
bt ~ # wlanconfig ath0 destroy
bt ~ # macchanger --mac 00:11:22:33:44:55 wifi0
Current MAC: 00:15:af:8c:f7:83 (unknown)
Faked MAC: 00:11:22:33:44:55 (Cimsys Inc)
bt ~ # wlanconfig ath0 create wlandev wifi0 wlanmode managed
ath0
bt ~ # ifconfig ath0 up
bt ~ # iwconfig ath0 essid "xxx" key 37:31:30:37:33:32:32:38:35:33:36:36:xx
bt ~ # iwconfig
lo no wireless extensions.
eth0 no wireless extensions.
wifi0 no wireless extensions.
ath0 IEEE 802.11g ESSID:"xxx" Nickname:""
Mode:Managed Frequency:2.437 GHz Access Point: 00:1C:4A:09:D8:5E
Bit Rate:36 Mb/s Tx-Power:17 dBm Sensitivity=1/1
Retry:off RTS thr:off Fragment thr:off
Encryption key:3731-3037-3332-3238-3533-3636-xx Security mode:restricted
Power Management:off
Link Quality=11/70 Signal level=-85 dBm Noise level=-96 dBm
Rx invalid nwid:55 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
bt ~ # iwconfig ath0 ap 00:1C:4A:09:D8:5E
bt ~ # iwconfig
lo no wireless extensions.
eth0 no wireless extensions.
wifi0 no wireless extensions.
ath0 IEEE 802.11g ESSID:"xxx" Nickname:""
Mode:Managed Frequency:2.437 GHz Access Point: 00:1C:4A:09:D8:5E
Bit Rate:36 Mb/s Tx-Power:17 dBm Sensitivity=1/1
Retry:off RTS thr:off Fragment thr:off
Encryption key:3731-3037-3332-3238-3533-3636-xx Security mode:restricted
Power Management:off
Link Quality=21/70 Signal level=-75 dBm Noise level=-96 dBm
Rx invalid nwid:284 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
bt ~ # dhcpcd -d -n ath0
dhcpcd: MAC address = 06:11:22:33:44:55
nothing here...also dhclient wont do:
bt ~ # dhclient
Internet Systems Consortium DHCP Client V3.0.6
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved
wifi0: unknown hardware address type 801
wifi0: unknown hardware address type 801
Listening on LPF/ath0/06:11:22:33:44:55
Sending on LPF/ath0/06:11:22:33:44:55
Listening on LPF/wifi0/
Sending on LPF/wifi0/
Listening on LPF/eth0/00:1f:c6:4d:4f:24
Sending on LPF/eth0/00:1f:c6:4d:4f:24
Sending on Socket/fallback
DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 5
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6
DHCPDISCOVER on wifi0 to 255.255.255.255 port 67 interval 8
still no ip address....
This is the problem.bt ~ # dhcpcd -d -n ath0
dhcpcd: MAC address = 06:11:22:33:44:55
Change this line: wlanconfig ath0 create wlandev wifi0 wlanmode managed
To this: wlanconfig ath0 create wlandev wifi0 wlanmode sta -bssid
This should work for ya
Code:killall dhcpd wlanconfig ath0 destroy macchanger --mac 00:11:22:33:44:55 wifi0 wlanconfig ath0 create wlandev wifi0 wlanmode sta -bssid ifconfig ath0 up iwconfig ath0 essid "my net" key 37:31:30:37:33:32:32:38:35:33:36:36:xx iwconfig ath0 ap 00:1C:4A:09:D8:5E dhcpcd -d -n ath0
The only reason that I have really needed to use the -bssid option for is to successfully spoof the mac address without getting the "06".
Without having mac filtering enabled on the router, there is not really any point in doing other than testing if it works on your setup.
Besides that, OP is getting connected to AP, but just not getting IP address assigned.
So, either the AP is not running DHCP, or perhaps there is a limited range of IP's which already in use ?
(which would not appear to be the case as reportedly in windows no problem connecting)
You could try 'netdiscover' to see what that returns when associated with the AP ?