diggler Posted January 16, 2012 Posted January 16, 2012 (edited) When manually connecting to an OPEN WiFi network using BT5R1 "dhclient wlan0" (as seen in Telot's script) (without using "NetworkManager Applet 0.8" or "Wicd Network Manager") for wlan0 I get an error. 1) Any ideas? I've searched all over and found different variations of what I'll post below but they all give me the same error: OPEN WiFi AP Cell 02 - Address: 00:10:D0:00:75:00 Channel:11 Frequency:2.462 GHz (Channel 11) Quality=44/70 Signal level=-66 dBm Encryption key:off ESSID:"TEST" Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s 9 Mb/s; 12 Mb/s; 18 Mb/s Bit Rates:24 Mb/s; 36 Mb/s; 48 Mb/s; 54 Mb/s Mode:Master Extra:tsf=000002a969051235 Extra: Last beacon: 90ms ago IE: Unknown: 000D574E315F4248355F534F555448 IE: Unknown: 010882848B960C121824 IE: Unknown: 03010B IE: Unknown: 0706555320010B1B IE: Unknown: 200100 IE: Unknown: 2A0100 IE: Unknown: 32043048606C IE: Unknown: DD0900037F01010000FF7F Configuring Wifi through wlan0 interface for netbook internet access root@bt:~/Desktop# ./wlan0.sh ifconfig wlan0 down ifconfig wlan0 up iwconfig wlan0 essid "TEST" iwconfig wlan0 channel 11 iwconfig wlan0 mode managed dhclient wlan0 ERROR Internet Systems Consortium DHCP Client V3.1.3 Copyright 2004-2009 Internet Systems Consortium. All rights reserved. For info, please visit https://www.isc.org/software/dhcp/ mon0: unknown hardware address type 803 mon0: unknown hardware address type 803 Listening on LPF/wlan0/00:35:d3:88:c9:18 Sending on LPF/wlan0/00:35:d3:88:c9:18 Sending on Socket/fallback DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 4 DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7 DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 13 DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 10 DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 10 DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 14 DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3 No DHCPOFFERS received. No working leases in persistent database - sleeping. My guess is that is has something to do with "DHCPDISCOVER" looking for "255.255.255.255" and not "255.255.254.0", or the error "mon0: unknown hardware address type 803" What it looks like if I connect successfully with NetworkManager Applet 0.8 with only one wifi adapter connected wlan0 Link encap:Ethernet HWaddr 00:11:d1:18:b1:11 inet addr:192.168.20.93 Bcast:192.168.21.255 Mask:255.255.254.0 inet6 addr: fe80::225:d3ff:fe88:c818/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:108579 errors:0 dropped:0 overruns:0 frame:0 TX packets:22183 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:54172944 (54.1 MB) TX bytes:2352640 (2.3 MB) 2) Is there a way to flush and restore "NetworkManager Applet 0.8" and "Wicd Network Manager" to default settings? I'm getting all sorts of "can't obtain IP address" errors. service network-manager stop /etc/init.d/wicd stop My hardware setup is: Laptop - Teo Pro Netbook (http://zareason.com/...ro-Netbook.html) Laptop built in wireless adapter - wlan0 ath9k[mac80211]-N/A Atheros Communicaitons Inc. AR9285 Wireless Network Adapter (PCI-Express) (rev 01) OS - BT5 R1 Linux bt 2.6.39.4 x86_64 GNU/LINUX Pineapple - AP51 MK3 v2.0.1 2nd external wireless adapter - wlan1 Alfa (from hakshop) rtl8187[mac80211]-N/A Realtek Semiconductor Corp. RTL8187 3) Could there be a conflict between the two WiFi NIC's because they're both trying to use the "mac80211" stack at the same time? Edited January 16, 2012 by diggler Quote
Mr-Protocol Posted January 16, 2012 Posted January 16, 2012 I dont see how this is pineapple related. use the wicd network manager is the gui way to manage connecting to wireless/lan. You cannot setup ICS with the pineapple by connecting it to WiFi. Quote
diggler Posted January 16, 2012 Author Posted January 16, 2012 1. My 2nd wireless adapter is used to deploy airdrop-ng for mass deauth. 2. I really dislike the GUI managers because when two wireless nic's are connected it auto connects both adapters to OPEN wifi networks. Even when /etc/init.d/interfaces remains commented. 3. I meant provide an internet source to the pineapple by first connecting the laptop itself to the internet I dont see how this is pineapple related. use the wicd network manager is the gui way to manage connecting to wireless/lan. You cannot setup ICS with the pineapple by connecting it to WiFi. Quote
Mr-Protocol Posted January 16, 2012 Posted January 16, 2012 not sure what you mean by auto connects both adapters to OPEN wifi networks. if you are trying to setup a pineapple ICS setup. Connect to the internet serving WiFi with wicd, and plug in the lan card to the pineapple with a cable and manually ifconfig the static ip to that. Setup ip forwarding and away you go. For deauthing, just the other interface or the pineapple itself. Quote
diggler Posted January 16, 2012 Author Posted January 16, 2012 (edited) BT5R1 is not supposed to connect to any internet connections on any wired or wireless adapters except the lo (loopback) by default - for privacy when beginning a pen test. When I boot my netbook (with both wifi adapters physically connected 1 internal / 1 physical connected to usb) it auto connects and both adapters join the nearby open wifi networks. It's a real pain the ass. I'd just like to get that behavior to stop. And I'd really like to know why dhclient wlan0 and iwconfig aren't working manually. Telot has the 'dhclient wlan0" grabbing an IP manually in his script but i can't get mine to do the same... not sure what you mean by auto connects both adapters to OPEN wifi networks. if you are trying to setup a pineapple ICS setup. Connect to the internet serving WiFi with wicd, and plug in the lan card to the pineapple with a cable and manually ifconfig the static ip to that. Setup ip forwarding and away you go. For deauthing, just the other interface or the pineapple itself. Edited January 16, 2012 by diggler Quote
Mr-Protocol Posted January 16, 2012 Posted January 16, 2012 If it was not supposed to connect to anything but loopback, you would have a worthless operating system. On BT4 it was setup to not have any interfaces try to DHCP and get on the network(on boot). That was changed in BT5. https://help.ubuntu.com/community/WifiDocs/WiFiHowTo Quote
barry99705 Posted January 17, 2012 Posted January 17, 2012 Take your adapter out of monitor mode. Quote
diggler Posted January 17, 2012 Author Posted January 17, 2012 I noticed that error with "mon0: unknown hardware address type 803" too but it was never put in monitor mode : / Take your adapter out of monitor mode. Quote
barry99705 Posted January 17, 2012 Posted January 17, 2012 I noticed that error with "mon0: unknown hardware address type 803" too but it was never put in monitor mode : / Did you run any of the scripts first? Pretty sure they start up monitor mode. Quote
barry99705 Posted January 21, 2012 Posted January 21, 2012 Just as an aside, I've seen BackTrack, and Ubuntu, run dhclient on all the network adapters, even if you specify a single one. Easiest way around this is to give all your devices a static address. Quote
diggler Posted January 21, 2012 Author Posted January 21, 2012 That's interesting... thanks, I'll definitely be giving that a try. Just as an aside, I've seen BackTrack, and Ubuntu, run dhclient on all the network adapters, even if you specify a single one. Easiest way around this is to give all your devices a static address. Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.