tertko

I am also wondering if i am the only one having this issue. For people here on the forums , if you can test the autostart of sslstrip and post some logs, please do.

as i already written twice, same happening when powering from the wall :)

its what i was thinking also, its something with the usb, but if it is , i guess pineapple would then power off/reboot, rather then die. i have 6 gigs free on usb, and 2 gigs of swap so nothing that could clog up the drive space. also, sometimes the pineapple dies with the sslstrip log being empty, as noone has connected to it. but even with only sslstrip running, when it was running "ok", i was never able to run it more then 24 hours straight. it always reboot itself or die. i will try to troubleshoot it and run something else beside sslstrip, and see how it goes. i wonder how much other people have their pineapple running without being rebooted or reseted. sadly, for me, it never went over 24 hours without a reboot . its why i still cant set it up somewhere outside, still playing with it indoors only

tried to add full path, the error i get after reboot is: 00:01:17 Pineapple user.info sysinit: env: can't execute 'python': No such file or directory i added also a "sleep 60" in the autostart script, but this doesnt work also

no problem, i will. i doubt its a path issue, as when i start the same script manually, it works. which is weird. if you need any more logs or something, lemme know

i only have running sslstrip. no hub, no nothing. just a usb stick plugged in where sslstrip and all other modules are installed i cant ssh, i cant access the page, wireless is off. basically, it just goes dead. usually when i run lots of modules, and its high load, the pineapple restart itself. but this is not the case, it just goes dead with the led being dimmed. not turned off completely. only the power led is turned on. nothing has changed in the setup i have, and this is what is weird, because i dont know what to look at or troubleshoot. during last 2 days, the pinneaple died at least 10 or more times a day and as im typing this, it happened again. dead. usually, before this started happening, i had pineapple rebooted itself maybe once a day. i havent installed anything new, am not running nothing new just sslstrip the only change i did was trying to run sslstrip automatically, but i am running into issues which i explained in other thread but i changed this after this started happening, as rebooting pineapple and running everything manually started getting on my nerves. so i wanted to automate that.

then it wouldnt die when powered from adapter in the wall

I have this issue happening from yesterday. Before, my pineapple was running usually at least a day before it restarted itself. From yesterday, it goes dead after around half an hour. It doesnt restart, but it just goes dead. PWR led is on, and other leds are dimmed. I need to power it off and on to restart it. Nothing has changed in my setup. Not sure what can it be. Power source is from laptop using the power cable. The same thing happens if i use the normal power adapter.

i have the similar issue. i usually have urlsnarf working for couple of minutes and then it stops, and sslstrip takes over and only sslstrip works. i think you cannot have both running simultaneously as sslstrip is forwarding everything to port 10000, and urlsnarf doesnt catch that at least this was the explanation that i found on this forum a while ago.

hi there im having issues when trying to autostart sslstrip this is from the log: 00:01:16 Pineapple user.info sysinit: /usb/modules/sslstrip/autostart.sh: line 7: sslstrip: not found now, if i run manually the same script over ssh when i login, everything works so i am not sure why i have this error tried searching the forums but didnt come up with nothing root@Pineapple:/usb/modules/sslstrip# sh autostart.sh sslstrip 0.6 by Moxie Marlinspike running... root@Pineapple:/usb/modules/sslstrip# cat autostart.sh #!/bin/sh MYPATH="$(dirname $0)/" MYTIME=`date +%s` iptables -t nat -A PREROUTING -p tcp --destination-port 80 -j REDIRECT --to-ports 10000 sslstrip -k -f -w ${MYPATH}log/output_${MYTIME}.log 2>&1 &

mind posting somewhere where you dont need a live account?

Yes, i know this :) Saved ssid are for open networks.Not encrypted. Like i said before. I see the probes for the saved ssids from my phone on karma. But it doesnt get connected. All ssids are for open networks. The second i change ssid in pineapple to any of the saved ssid from my phone(the same ones i get the probes in karma), it gets connected instantly. If i dont change the ssid from pineapple, i only see probes , over and over. Both htc and iphone behave the same.

Hi there. Now, i have an issue, which maybe isnt an issue at all, but i think it is :) The scenario: If the pineapple ssid isnt changed, it has a default pineapple:00... when i turn on wireless on my phone. It doesnt get connected to pineapple. If I change the ssid to a certain name i have connected before with my phone, it will connect automatically to pineapple. I turn off the wireless of the phone again, change the ssid of pineapple to something random, turn on back wireless on phone, the phone isnt connected automatically. Now, shouldnt the pineapple pick up the probe request and answer to anything? It is weird that the phone will connect automatically only when the pineapple has the ssid of one of the APs my phone remembered. If pineapple has default/different ssid, the phone doesnt connect. EDIT: I can do that also without powering the phone wireless in the middle. I have the phone with wireless on, scanning for network, and NOT connecting to pineapple with default/different SSID. When i change the SSID of pineapple to something my phone has in memory, it automatically connects. EDIT2: tried with iphone, same behaviour. i see iphone doing bunch of probe request, pineapple doing nothing. changed the ssid of the pineapple to one of the probe request from iphone, BAM. connected immediatly

in mountain lion you can only share net if your network is at 192.168.2.0 you cannot change that

done so while was waiting for the reply...the same