jman012

Well the Pineapple got bricked after trying to upgrade it (because the connection was lost again). After buying the serial connector to flash it manually, everything is working again! I guess the problem was more low-level stuff that required an entire reflashing, not just an upgrade of firmware. But it's all fixed, able to install infusions, have users connect to it, and run the modules, etc.

Just tried this. Killed the network manager and made sure wicd was closed while running the wp4 script and still no dice. After only a couple minutes of being connected over ssh, was disconnected again with the pineapple becoming unreachable. Am only able to run a couple commands before this keeps happening. I have no clue what is causing the issue as now I've tried it on two different computers, one running kali and one running just ubuntu and it's happening on both machines. Seems like no matter what i do, even quitting all network managers isn't stopping this problem. What I don't understand is why the connection jsut randomly breaks after a certain amount of time. And why would restarting the pineapple and re-running wp4 fix the problem yet just rerunning wp4 doesn't. What would even cause that? It just doesn't make sense to me....

So, I had a revelation! I've found out that the Pineapple is not the source of the problem here. I was intrigued at how the Pineapple had its lights still on after "freezing". Well I tried connecting another device to it through it's SSID and sure enough it connected, and pinging it works fine. So this means that the problem is the connection from my computer (where I run the wp4.sh to give internet) and the Pineapple. My computer is an Asus EEE laptop running the latest (1.0.3) version of Kali Linux, and I think the problem is with the Network Manager. This explains my problems because leaving the Pineapple idle doesn't disrupt the connection, it only does after SSH and Web activity where Network Manager might be ruining the connection. wp4.sh runs fine initially since I get a connection at first, but again, re-running it doesn't seem to help. The Ethernet cord to the Pineapple is in the correct port. Anyways so I tried disabling the Network Manager and manually connecting to internet (tethered iPhone) which worked fine. But again, after running wp4.sh after a few minutes the connection was once again disrupted. Any new ideas into this?

Sorry to bump this, but do you have any idea as to what the problem could be?

It's literally about 5 minutes. I just timed it right now and it was about 4:55 or so (+- maybe 5-10 seconds since i looked away while it was pinging). It's pretty constant but I've seen it sometimes take a minute or two longer and in other cases when I'm downloading a package like randomroll (with nothing else major running at the same time), it will crash as well. However, as I said, all the LEDs remain on. PWR, USB are on and LAN and WLAN are blinking. It's plugged into the wall through the adapter it came with. I don't think it's overheating as feeling the outside everything seems cool and fine, however I haven't taken it out of the case to check specific parts. I can do this later Hakshop! Got it around the holidays when the sales were going on. Played with it for a while but hadn't touched it in a couple months. Just got it and my alfas out of my laptop bag to setup with my new laptop to start using it again now that I have more time and ran into this problem. No problem! I know how hard it is to diagnose problems when not given enough information so I made sure to get everything I possibly could. Please let me know if there's anything else I can get for you to help figure out the problem. I don't recall problems like this when I first got it. I would sometimes have the pineapple reboot (indicated by the led's turning off) because of what I think was probably overusage of memory, but not like this where it apparently is freezing yet not rebooting. It's very odd which is why I posted here - I have no clue how to solve this. Thanks so much for your reply! I hope we can figure this issue out so I can go back to being able to use the pineapple!

As I said, I'm having a problem where, after the Pineapple has been on for only several minutes, it crashes/freezes. This is after running the wp4.sh script with default settings: internet sharing, pinging, ssh, and the web interface all work fine. When it crashes/freezes the Wlan, Lan, WPS, and Power lights on the device are still on and everything, but pinging gives no results, and it is impossible to SSH into it, or access the web interface. This usually requires a reboot to fix, when after yet another few minutes it'll crash/freeze. When I leave it alone for a bit it seems to take longer to crash. After the crash, re-running the wp4.sh script does not fix the matter. For instance, one time it stayed up for quite a while, until we tried installing something through the web interface (randomroll), and at about 90% of the way through it crashed/froze. Has anyone else encountered this problem and is there any solution? Even after reflashin with a fresh install the problem persisted so I'm not sure what else to do. Thanks Pineapple Hardware Version (ex: Mark III, Mark IV, etc.): Mark IV Pineapple Software Version (ex: 2.5.0, 2.6.4): 2.8.1 OS used to connect to the pineapple: Kali Linux Network layout of how your setup is connected (including IP information): laptop connected to pineapple through ethernet and connected to the internet through wireless router. Using the wp4.sh script to create connection and internet sharing between the laptop and pineapple. All network settings default and this does work when the pineapple is initially turned on. Am able to connect to it through both ssh and the web interface for a few minutes before it crashes/freezes All the tools/options that are running on the pineapple when the issue happened: Fresh flashed pineapple with nothing extra added in at all Ping results from computer to pineapple: For the first 5 or so minutes the pineapple responds to ping requests and everything fine. Can access it through web and ssh. After a few minutes however it stops responding everywhere. No ping back with an error of "Destination Host Unreachable" and web and ssh are both down as well. The entire thing seems to completely freeze. Is the problem repeatable (Yes/No): Yes, every time I start up the pineapple it crashes after 5 minutes. Have to reboot to regain access and then it happens again Steps taken which created the problem: Just leave it sitting there for about 5 minutes Error Messages: -- Log file information(use spoiler tags for large logs): Here are the most recent logfiles from the pineapple right after a fresh flash of 2.8.1 in case there's anything useful in there: Anything else that was attempted to 'fix' the problem: Reflashed the pineapple over ssh to new firmware 2.8.1 - - no success

This sounds like a great idea, it might start off slow but people can share their experiences with their use of the Ubertooth and fix problems. And more episodes on it would be amazing as well, it looks like it has so much potential.

I figured out that using dnsspoof with ip addresses and not DNS names seems to work, and that successfully goes around the nscd stuff. Through this thread, http://forums.hak5.org/index.php?/topic/28146-urlsnarf-module-simultaneously-with-sslstrip-module/, it turns out that sslstrip is the culprit. I turned off ssltrip and sure enough, urlsnarf worked perfectly. But as you said there, sslstrip shouldn't be hogging a port to cause the problem, so it must be something else.

I too am having this problem, I refer to this thread I made: http://forums.hak5.org/index.php?/topic/28422-i-have-some-problems-with-urlsnarf-dnsspoof-and-slow-internet/ I just tried keeping sslstrip turned off and sure enough, urlsnarf worked perfectly. I don't really know why ssltrip would interfere if what vector said is true.

Hello all! So first of all urlsnarf doesn't seem to output any logs from client's traffic.Sometimes urlsnarf would output random traffic, but there doesn't seem to be a pattern that I can see. Is there something urlsnarf specifically looks for, or checks for? Maybe I don't know what it specifically does. Second, dnsspoof is spotty in how it works. Sometimes it will correctly re-direct traffic, but other times it won't. It's a little hard to explain, here is a ping output: xandermbp:~ alexander$ ping www.reddit.com PING a659.b.akamai.net (165.254.26.73): 56 data bytes 64 bytes from 165.254.26.73: icmp_seq=0 ttl=48 time=73.265 ms 92 bytes from pineapple.lan (172.16.42.1): Redirect Host(New addr: 172.16.42.42) Vr HL TOS Len ID Flg off TTL Pro cks Src Dst 4 5 00 0054 25bb 0 0000 3f 01 bec7 172.16.42.207 165.254.26.73 64 bytes from 165.254.26.73: icmp_seq=1 ttl=48 time=71.029 ms 64 bytes from 165.254.26.73: icmp_seq=2 ttl=48 time=101.353 ms 64 bytes from 165.254.26.73: icmp_seq=3 ttl=48 time=83.039 ms 64 bytes from 165.254.26.73: icmp_seq=4 ttl=48 time=85.661 ms 64 bytes from 165.254.26.73: icmp_seq=5 ttl=48 time=77.908 ms 64 bytes from 165.254.26.73: icmp_seq=6 ttl=48 time=72.256 ms 64 bytes from 165.254.26.73: icmp_seq=7 ttl=48 time=70.567 ms ^C --- a659.b.akamai.net ping statistics --- 8 packets transmitted, 8 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 70.567/79.385/101.353/9.832 ms xandermbp:~ alexander$ ping google.com PING google.com (74.125.224.228): 56 data bytes 64 bytes from 74.125.224.228: icmp_seq=0 ttl=51 time=32.533 ms 92 bytes from pineapple.lan (172.16.42.1): Redirect Host(New addr: 172.16.42.42) Vr HL TOS Len ID Flg off TTL Pro cks Src Dst 4 5 00 0054 22d5 0 0000 3f 01 5693 172.16.42.207 74.125.224.228 64 bytes from 74.125.224.228: icmp_seq=1 ttl=51 time=19.402 ms 64 bytes from 74.125.224.228: icmp_seq=2 ttl=51 time=22.356 ms 64 bytes from 74.125.224.228: icmp_seq=3 ttl=51 time=19.230 ms 64 bytes from 74.125.224.228: icmp_seq=4 ttl=51 time=20.175 ms 64 bytes from 74.125.224.228: icmp_seq=5 ttl=51 time=20.814 ms 64 bytes from 74.125.224.228: icmp_seq=6 ttl=51 time=19.545 ms 64 bytes from 74.125.224.228: icmp_seq=7 ttl=51 time=24.446 ms 64 bytes from 74.125.224.228: icmp_seq=8 ttl=51 time=23.360 ms 64 bytes from 74.125.224.228: icmp_seq=9 ttl=51 time=22.641 ms 64 bytes from 74.125.224.228: icmp_seq=10 ttl=51 time=25.756 ms ^C --- google.com ping statistics --- 11 packets transmitted, 11 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 19.230/22.751/32.533/3.722 ms [/CODE] It seems, for the pings, that the pineapple did something but it was still pinging google's and reddit's address. And lastly, the pineapple sometimes seems to be a bottleneck for clients connected to it. Both testing at home and especially at a local coffee shop, clients connected through the pineapple had significantly slower and choppier connections. Right now it's setup connected to my eee pc which is sharing its wifi connection over ethernet to the pineapple. Usually all that is running is karma, urlsnarf, and sslstrip By the way, my Pineapple is a Mark IV, 8GB USB with the swap space correctly made (I followed Darren's tutorial and used the flash script()). Also it is indeed plugged into the wall, so there shouldn't be a power issue.