LinuxDad

I had many similar issues attempting to keep everything in the native WindBlows (sorry, freudian slip) environment. I finally restored to using vmware (in this case vmplayer-free) and a copy of Backtrack to implement the configuration using the wp4.sh script. I was immediately able to connect (I think that there are some additional server/service issues in WindBlows that you do not get in Windows 7 without get the server edition), and have complete control of the networking information needed to use the Pineapple. An added plus is the ability to use Backtrack along with the Pineapple. That's a Win-Win.

Sure, awaiting the new version.

I am also receiving the SSH Connection status, just after restarting the Pineapple. It appears that autossh is starting or attempting to start the connection: 00:01:00 Pineapple kern.info kernel: [ 60.790000] br-lan: port 1(eth0) entered forwarding state 00:00:59 Pineapple user.info autossh[2008]: starting ssh (count 5) 00:00:59 Pineapple user.info autossh[2008]: starting ssh (count 4) 00:00:59 Pineapple user.info autossh[2008]: starting ssh (count 3) 00:00:59 Pineapple user.info autossh[2008]: starting ssh (count 2) 00:00:59 Pineapple user.info autossh[2008]: starting ssh (count 1) 00:00:59 Pineapple user.info autossh[2008]: ssh exited with error status 1; restarting ssh 00:00:59 Pineapple user.info autossh[2008]: ssh exited with error status 1; restarting ssh 00:00:59 Pineapple user.info autossh[2008]: ssh exited with error status 1; restarting ssh 00:00:59 Pineapple user.info autossh[2008]: ssh exited with error status 1; restarting ssh 00:00:59 Pineapple user.info autossh[2008]: ssh exited with error status 1; restarting ssh 00:00:59 Pineapple user.info autossh[2008]: ssh child pid is 2020 00:00:59 Pineapple user.info autossh[2008]: ssh child pid is 2019 00:00:59 Pineapple user.info autossh[2008]: ssh child pid is 2012 00:00:59 Pineapple user.info autossh[2008]: ssh child pid is 2011 00:00:59 Pineapple user.info autossh[2008]: ssh child pid is 2010 00:00:59 Pineapple daemon.notice netifd: wan (2004): udhcpc (v1.19.4) st Then I see it doing the following: 00:01:10 Pineapple authpriv.warn dropbear[2336]: Failed listening on '22': Error listening: Address already in use 00:01:10 Pineapple authpriv.info dropbear[2336]: Premature exit: No listening ports available. 00:01:09 Pineapple user.info autossh[2008]: starting ssh (count 7) 00:01:09 Pineapple user.info autossh[2008]: ssh exited with error status 1; restarting ssh 00:01:09 Pineapple user.info autossh[2008]: ssh child pid is 2253 And lastly, these seemed relevent as well: 15:37:10 Pineapple user.info autossh[2008]: starting ssh (count 8) 15:37:10 Pineapple user.info autossh[2008]: ssh exited with error status 1; restarting ssh 15:37:10 Pineapple user.info autossh[2008]: ssh child pid is 2432 00:01:13 Pineapple user.info sysinit: sh: write error: Invalid argument 00:01:13 Pineapple user.info sysinit: sh: write error: Invalid argument Hope that helps.

Nice, this is a great test for WIPS devices in the secure network boundaries. Thank you for posting this.

Nice packaging. Security through obscurity? I love the Camera bag idea, but why broadcast the antenna outside of the bag? does the fabric attenuate the signal that much?

OK, I found the RandomRoll module in the Pineapple Bar. I think that what I really want is the Man in the Middle module.

I can Beta Test for you.

I am not able to download the files from: http://www.mediafire.com/file/ccyejfyph17993t/web.zip are they still available?

I will now!

I resolved this problem by using a Linux Based VM to route the Wireless traffic through the PC. The Pineapple worked well when connected directly to a netowkr, but attempting to permit the pineapple to connect to the internet via the Laptop (running Windows 7), simpley does not work. The reason for this is that Microsoft has removed the routing capabilities on the Windows 7 personal platforms, requiring a license to a server based version in order to perform the same functionality that was possible on Windows XP. The short answer is to install the VMWare player, and run either backtrack, or your favorite version of Linux to configure the interfaces, and then use the wp4.sh script. Hope that helps future Pineapple users.

Is there a guide for the opkg command, the resources that are available, and the ability to install updates to the USB device? I think that we can put something together for the Wiki if we can get the information together.

The Link on the top of the Jasager Forum indicated that the Wiki is on: http://forums.hak5.org/index.php?/forum-49/announcement-7-wifi-pineapple-wiki-page/ however the page indicates that this has moved to: http://cloud.wifipineapple.com/wiki/doku.php Thank you.

Thanks, I would like to see this as well.

Hey Whistlemaster, where do I find these modules or scripts?

I have the 2.7.0 version of the Pineapple firmware. I have installed sitesurvey, opkgmanager, sslstrip, status and Network manager. My goal was to test the sslstrip module. So I fired up the Pineapple, and connected to the SSID, but I got nowhere. My Pineapple is directly connected to the network via a switch to port eth1. Two questions here: 1. Normally if I'm in the field, the pineapple will route through my laptop, correct? (I'm guessing via eth0). 2. Do I need to enamle ICS via the Network Monitor in order to connect to the Internet via the Pineapple's SSID? I enabled the ICS from wlan0 to eth1, and confirmed the following iptables rules: root@Pineapple:~# iptables -nL Chain INPUT (policy ACCEPT) target prot opt source destination Chain FORWARD (policy ACCEPT) target prot opt source destination ACCEPT all -- 172.16.42.0 0.0.0.0/0 state NEW ACCEPT all -- 0.0.0.0/0 0.0.0.0/0 state RELATED,ESTABLISHED Chain OUTPUT (policy ACCEPT) target prot opt source destination The routing table also supports the use of the Default Gateway. root@Pineapple:~# netstat -rn Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 eth1 172.16.42.0 0.0.0.0 255.255.255.0 U 0 0 0 br-lan 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1 Unfortunately, my SSH Connection from my Laptop hangs up, as well as the web connections to websites are not working. What am I missing?

I second the use of step by step instruction. I am interested in getting my UI running better.faster but running with the GUI would be great! Thank you for the support Moriarty. Happy Holidays.

Thanks for the follow-up guys. First of all, this is not an external Wifi. It's the built in. Second of all, I flashed the firmware, and started over. This is not really solving the issue with the software not performing as expected, but it gets me back operational again. Thank you everyone for your updates and suggestions.

My Goal with the Network Manager was to secure the AP and make it require a PW. Does this activity interfere with with the Deauth activities? Thank you for the suggestion about reinstalling the 2.7.0 firmware. Thanks.

I have no ideas, do you?

I'm tracking down the issues with the Radio not starting on reboot. I removed the opkg_manager, and found that it did not clean up the /etc/rc.local file, so we need to edit the file as follows: #/usb/modules/networkmanager/autostart.sh Because of the error in the Log: 00:01:08 Pineapple user.info sysinit: /etc/rc.local: line 7: /usb/modules/networkmanager/autostart.sh: not found The next error I've found is the following: 00:01:08 Pineapple user.info sysinit: Failed to start hostapd for phy0 00:01:08 Pineapple user.info sysinit: Failed to connect to hostapd - wpa_ctrl_open: No such file or directory There is also the additional error, which should also be followed up on: 00:01:08 Pineapple user.info sysinit: sh: write error: Invalid argument 00:01:08 Pineapple user.info sysinit: sh: write error: Invalid argument Suggestions?

Hmm, is this relevant? 00:01:08 Pineapple user.info sysinit: sh: write error: Invalid argument 00:01:08 Pineapple user.info sysinit: sh: write error: Invalid argument 00:01:08 Pineapple user.info sysinit: setting up led WLAN 00:01:08 Pineapple user.info sysinit: setting up led WAN 00:01:08 Pineapple user.info sysinit: setting up led USB 00:01:08 Pineapple user.info sysinit: setting up led LAN 00:01:08 Pineapple user.info sysinit: Failed to start hostapd for phy0 00:01:08 Pineapple user.info sysinit: Failed to connect to hostapd - wpa_ctrl_open: No such file or directory 00:01:08 Pineapple user.info sysinit: /etc/rc.common: eval: line 1: can't create /sys/class/leds/alfa:blue:wan/mode: nonexistent directory 00:01:08 Pineapple user.info sysinit: /etc/rc.common: eval: line 1: can't create /sys/class/leds/alfa:blue:wan/device_name: nonexistent directory 00:01:08 Pineapple user.info sysinit: /etc/rc.common: eval: line 1: can't create /sys/class/leds/alfa:blue:lan/mode: nonexistent directory 00:01:08 Pineapple user.info sysinit: /etc/rc.common: eval: line 1: can't create /sys/class/leds/alfa:blue:lan/device_name: nonexistent directory

Following yesterday's forum postings, I installed the Network Monitor. I wanted to change some configuration settings on the Radio (I wanted a Password for the default SSID). I'm still not certain if doing so actually interferes with a Deauth attack or not yet, but I'll cross that bridge when I get there. My issue was that the Radio would not restart after removing the Network Monitor. This leaves me with two questions: 1. Do I need to configure Internet Sharing, and if so, how do I know whether the eth0 or eth1 will be connected for the out pathway (is there a way to specify that either ethernet is suitable?)? 2. After removing the Network Monitor module, I wanted to revert the operation back to what the Pineapple had before installing the module in the first place. However, after deinstalling the module, the radio would not turn on, I suspect that there were still remnants of the module still in place on the pineapple, thus preventing it from restarting. Suggestions? Comments? Did I miss an RTFM?

Just noticed the title about my member info, Hackling? Really? I teach Cyber Security to the Air Force, DISA, and other Govt agencies. THey just love it when I pull out the USB Rubber Ducky or the PineApple. But a Hackling? I think my skills are a level higher than Hackling.

Thank you. I guess the Modules will provide me with all of the rest of the configuration info. I appreciate your assistance.

Thanks, that's perfect. Now;s here's where it gets interesting. Can we Hide the SSID (don't Broadcast it), or create a Password for it, to restrict who has access to the AP?