Jump to content

catohagen

Active Members
  • Posts

    35
  • Joined

  • Last visited

Everything posted by catohagen

  1. @sebkinne Not trying to be negative, sorry and apologies if anyone got that impression. I've also edited my post (#13) as the android 4.1.2 device today did connect to Jasager/karma with the SSID from the Nexus7 tablet i created yesterday, i moved the pineapple as I needed the outlet, and when the pineapple was plugged in and up, it picked it up and created the correct SSID.
  2. seems the fucks given here by developers are totally minimal :)
  3. just a follow up, Yesterday I fired up my old Sony Ericsson X10i from 2010, with android 2.3.3 (2.3.3 was released in early 2011) and Jasager/Karma worked instantly, faking a stored open ssid's from the phone and let phone connect to it before my homescreen was up, when boot was finished it was already connected to wifi with blue wifi icon at notification bar (ssid was open 'wireless'). Wifi Pineapple working as intended, working as advertised. Wanted to try get ICS on it, so I rooted the x10i, unlocked bootloader, installed a custom recovery and installed Cyanogenmod 10 (based on android 4.1.2, released mid 2012) Created a portable hotspot, an open ssid with my nexus 7 tablet, connected the new upgraded X10i to the nexus 7 tablet, then killed hotspot and the X10i should in theory send probe requests that Jasager/Karma should pick up, and make its fake SSID but the X10i didnt see any wifi network, rebooted a few times and still no open AP's. EDIT : Seems I spoke too soon about android 4.1.2 , saw today when I moved the pineapple to another outlet, that when loaded up karma had faked the open SSID i created on the Nexus 7, so indeed Jasager/Karma works with 4.1.2 devices
  4. There isnt any solution to this unless karma/jasager is updated(if its even possible) to take account for how 2012-13 devices scans or connects to a saved open wifi accesssspoint, i sense the lack of response to threads taking this issue up(there have been several, just like this with no solution), speaks for itself about the low possibility that this can or will be fixed. The wifi pineapple is a pretty cool device and all that, the writeup descriptions in the Hak5 Shop about how easy and simple Jasager / Karma works in 2008 to owning the network, isnt quite as true anymore as none of my 6-7 different phones/tables/ipad/iphones at home connected to anything unless tampered with. At a workplace nearby with 30 employees and god knows how many different phone brands/operating systems, getting 50-60 probe requests but not a single connect, and at this workplace there is no wifi available, so peoples phones where on mobile data and should look for known wifi's I wish i've read about/looked this up before buying my Pineapple, as basicly i'm left with a basic router with 'MITM' tools on, but what i really wanted was the Jasager/karma functionality. I hope future potentional buyers could get a heads up from the Hak5 shop about Jasager/Karma and how it may not say 'Hey Im your network!' to phones/tables sold for the last 2 years, as wifi probing clearly have changed since 2008 and got more secure. I would very much like to have the Pineapple / Jasager fixed so it works as it should, and would help to test/debug any new firmware or solutions, but looking at threads posted nearly 2 years ago with little helpful reply's on the subject tells me this is difficult to find a solution for. Atleast I would not bought it if i've known the main selling point of the device may not work as advertised.
  5. screenshots of adding 'scan_ssid=1' to two open saved ssid's in /data/misc/wifi/wpa_supplicant.conf and turning wifi off and on, and those two ssids shows up after.
  6. @newbi3 I reboot the pineapple and load up the ui after boot : KARMA: ENABLED KARMA: Probe Request from 1c:b0:94:xx:xx:xx for SSID 'dd-wrt_vap' KARMA: Probe Request from 1c:b0:94:xx:xx:xx for SSID 'dlink' KARMA: Probe Request from 20:02:af:xx:xx:xx for SSID 'leneogbaari' KARMA: Probe Request from 20:02:af:xx:xx:xx for SSID 'AIRPORT' KARMA: Probe Request from 20:02:af:xx:xx:xx for SSID 'WAGNERTRANSPORT 4' KARMA: Probe Request from 20:02:af:xx:xx:xx for SSID 'Sofitel-premium' KARMA: Probe Request from 20:02:af:xx:xx:xx for SSID 'Norwegian Internet Access' KARMA: Probe Request from 20:02:af:xx:xx:xx for SSID 'omg' KARMA: Probe Request from 20:02:af:xx:xx:xx for SSID 'Flybussen' KARMA: Probe Request from 20:02:af:xx:xx:xx for SSID 'GIGABYTE' KARMA: Probe Request from 1c:b0:94:xx:xx:xx for SSID 'Norled_kundenett' KARMA: Probe Request from 20:02:af:xx:xx:xx for SSID 'Coop-Guest' KARMA: Probe Request from 1c:b0:94:xx:xx:xx for SSID 'Stavanger TAXI' KARMA: Probe Request from 20:02:af:xx:xx:xx for SSID 'FERIEPARK' KARMA: Probe Request from 20:02:af:xx:xx:xx for SSID 'SAFE' KARMA: Probe Request from 20:02:af:xx:xx:xx for SSID 'Forsand' KARMA: Probe Request from 20:02:af:xx:xx:xx for SSID 'D35Broadband' there is probe requests to wpa password protected AP's and open AP's, without 'scan_ssid=1' on the open ones, none of these open AP's show up in the devices as fake as soon as I edit and add 'scan_ssid=1' to the wpa_supplicant.conf file on any open networks thats been saved there, disable and enable wifi, i get all of these open networks with full wifi bars. And I only see these probe requests once, if I reboot a device or turn on/off wifi on a device, one would assume new probes would be sent after a phone reboot or wifi off, but karma doesnt show new probes when phone is done rebooting. Rebooting the pineapple several times...will get those probes show up each time.
  7. Found a tiny small difference, going to /data/misc/wifi/wpa_supplicant.conf in my phone, i see this : network={ ssid="dd-wrt_G" psk="not_a_password" key_mgmt=WPA-PSK priority=95 } network={ ssid="Stavanger TAXI" key_mgmt=NONE } network={ ssid="NORLED_kundenett" key_mgmt=NONE } network={ ssid="LOLNET" scan_ssid=1 key_mgmt=NONE } there are 2 open AP's here i've been connected to before, the "NORLED_kundenett" one and "Stavanger TAXI", while i see these probes in karma.log, it never connects. Notice the extra line in the "LOLNET" ssid that I created/added on the phone, it got 'scan_ssid=1' and karma sees this and fakes the ssid instantly, while the other open ssid doesnt have this 'scan_ssid=1' line If i change the pineapple ssid to "NORLED_kundenett" the phone connects instantly. I edited my /data/misc/wifi/wpa_supplicant.conf on my android phone, and added 'scan_ssid=1' to my already saved open ssid's and karma picked up and faked all open ssid's. All those open AP's had full bars (This was on my HTC One with android 4) So Karma works as long as the devices sends out correct probes, but the updated changes on how wifi operates in new devices prevents karma from working properly. KARMA: ENABLED KARMA: Probe Request from 1c:b0:94:xx:xx:xx for SSID 'Norled_kundenett' KARMA: Probe Request from 1c:b0:94:xx:xx:xx for SSID 'Stavanger TAXI' KARMA: Probe Request from 1c:b0:94:xx:xx:xx for SSID 'LOLNET' KARMA: Probe Request from 1c:b0:94:xx:xx:xx for SSID 'Far_East_Verksgata_Guest_5G' KARMA: Checking SSID for start of association, pass through Norled_kundenett KARMA: Successful association of 1c:b0:94:xx:xx:xx KARMA: Checking SSID for start of association, pass through Stavanger TAXI KARMA: Successful association of 1c:b0:94:xx:xx:xx Station 1c:b0:94:xx:xx:xx (on wlan0) ip address: 172.16.42.206 host name: htc-one-x Karma SSID: 'Norled_kundenett' inactive time: 520 ms rx bytes: 16600 rx packets: 129 tx bytes: 16384 tx packets: 82 tx retries: 2 tx failed: 0 signal: -73 dBm signal avg: -72 dBm tx bitrate: 72.2 MBit/s MCS 7 short GI rx bitrate: 19.5 MBit/s MCS 2 authorized: yes authenticated: yes preamble: short WMM/WME: yes MFP: no TDLS peer: no
  8. After googling and reading more about the issue, several people have the same issue, so one can assume that wifi security have been upgraded or changed last few years, and the wifi pineapple and karma only worked flawless a few years ago(or on old devices used today) In the threads linked below, several places its a confirmed bug and the 2.8.1 release should have this fixed. https://forums.hak5.org/index.php?/topic/30113-clients-not-probingconnecting-to-karma-in-mk4-with-fw-281/?hl=karma https://forums.hak5.org/index.php?/topic/29973-karma-issues-with-android-fw-281-or-300/?hl=karma https://forums.hak5.org/index.php?/topic/29055-convert-probes-to-fake-networks/?hl=karma anyway, the same results and karma.logs i have here have been discussed and reported before and no solution nor fix have been given.
  9. yes, it works for AP's you create on the device but not for other real non-Karma AP's thats already been connected to and saved on the device. Reading the wiki and hak5 shows, the Pineapple should create fake AP's after probes after open AP's from devices and let those devices connect to the new created fake AP, if users need to create imaginary SSID's the whole concept goes away as my grandmother or any other noob have no idea how they can creating SSID's thats not visible in their list, if grandmother or a noob comes for a visit with their phones with saved free AP's from random cafe's or airports, the Pineapple and Karma should listen and get those SSID's from the probes and fake those AP's and get devices to connect ?
  10. Hi, I bought the Pineapple Mark iV pro, a few weeks ago, and just wanted to (bug)report/confirm what a few others have posted about Karma not working properly. I've reflashed 3.0.0 and 2.8.1 probably 4-5 times each and find that Karma is behaving the same, whatever I do on both those firmware versions....clients isnt automaticly connecting to saved open AP's I got a android phone and a few tablets and the kids got android phones, every device have multiple 'free wifi's picked up from cafe's and public places. I see from the karma log after a reset that it gets probes from 20-25 accesspoints thats stored in the phones and tablets around in the house, so I assumed if I disabled my home router or rebooted it, some devices should connect to the pineapple, but none does.....but if I have wifi enabled on any device but its not connected to any SSID, and I *create* a new on that device, it connects instantly. So my HTC One, deleted my home ap from list, and added a new open wifi accesspoint to connect to with name 'LOLNET' --> instant connect to LOLNET and apple ipad, deleted my home ap from list, not connected to any ap, created a new 'LOL' network, --> connected. I can enable my home wifi after this, go to the store and use mobile data there, drive home and see that the phone is connected to LOLNET, even when my real home wifi is enabled. Tried the same with multiple phones and only like this Karma works, even if all the phones and tablets have several and the also same open ap's saved in the list, either Karma doesnt create those SSID's or the phone never sees any of the previous saved open AP in devices around the house. I basicly have a very cool $114.99 device here, that doesnt work.
×
×
  • Create New...