Jump to content


Active Members
  • Posts

  • Joined

  • Last visited

  • Days Won


Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

mda1125's Achievements


Newbie (1/14)

  1. I thought I would test out the 2 VPN services I'm subscribed to at this time. I wanted to see raw tests, tests with VPN enabled and more importantly, the possibility of a DNS leak. I'll admit while I understand the concept of a DNS leak, I used 3 different web sites to test which are listed at the bottom. No links included as this isn't a pitch for either service except raw links to the speed test I used and the 3 DNS leak websites. Happy to know if those don't work and if there are better actual methods to test for a DNS leak. Speed Test: http://speedtest.xfinity.com/ Comcast Speed Test: No VPN Location: San Jose, CA Download: 240.6 Upload: 12.6 Latency: 14ms Let Software Pick the Server: Comcast Speed Test: NordVPN Location: New Castle, DE Download: 44.6 Upload: 11.8 Latency: 93ms Comcast Speed Test: IPVanish Location: San Jose, CA Download: 67.9 Upload: 11.5 Latency: 19ms Let's Pick a Country: Costa Rica Comcast Speed Test: IPVanish Location: Augusta, GA Download: 62.3 Upload: 9.3 Latency: 198ms Comcast Speed Test: NordVPN Location: Foxboro, MA Download: 46.0 Upload: 10.0 Latency: 233ms DNS Leak Tests: https://www.dnsleaktest.com/ https://ipleak.net/ http://dnsleak.com/ NordVPN never showed DNS leaks on the 3 sites listed above. IPVanish frequently shows a Comcast DNS server(s) in the mix.
  2. Let it run for about 20 minutes and saw 7 WiFi clients, 6 DHCP and 338 log files. Most of the logs were empty but a few weren't. The net-creds.log was empty. But it appears to be working full force on the Nano.
  3. Deleted everything in the module folder. Copied over the latest update. Totally seems to be working now! I can see refreshes happening and 3 log files created. It keeps running. Thank you!
  4. If I had to guess... I'd say it's the bleeding edge module has something wrong because launching from the Terminal in my case, does seem to work. After it throws some errors, I start to see Broadcasts and Responses to various SSIDs around me. And in the Mana Module inside the Pineapple Management.. I do see 2 log files being written. It's really caught up on this line: /sd/usr/sbin/launch-mana: line 285: /pineapple/modules/ManaToolkit/log/Net-Creds/net-creds.log: No such file or directory I've created the directory and "touched" the file. However, that directory does disappear? I've made it several times, navigated to it, seen the file. But it somehow gets deleted and when I start up again, this error comes back. Running the commands to create this directory and file does seem to fix the issue.
  5. Thanks @Zylla Installed the Mana-Toolkit using the script (installed fine) Created a directory as outlined in the DEV branch of the module Created the softlink Copied over the files using Filezilla to the directory on the SD Here's where it gets odd... I can see the module. I can see the dependencies are installed (the click to install went to the SD card without error). But when I click on start... it starts and then stops within a few seconds. If I run it from the terminal instead.. I see this output ___________________________________________ Mana Toolkit - Pineapple Edition! Device seems to be: ONLINE. RTNETLINK answers: File exists Configuration file: /sd/etc/mana-toolkit/hostapd-mana.conf dnsmasq: cannot read /sd/etc/mana-toolkit/dnsmasq-dhcpd.conf: No such file or directory /sd/usr/sbin/launch-mana: line 233: /sd/usr/sbin/ip: No such file or directory /sd/usr/sbin/launch-mana: line 240: /sd/usr/sbin/ip: No such file or directory /sd/usr/sbin/launch-mana: line 252: cd: /sd/usr/share/mana-toolkit/sslstrip-hsts/sslstrip2/: No such file or directory /sd/usr/sbin/launch-mana: line 255: cd: /sd/usr/share/mana-toolkit/sslstrip-hsts/dns2proxy/: No such file or directory /sd/usr/sbin/launch-mana: line 257: cd: OLDPWD not set /sd/usr/sbin/launch-mana: line 285: /pineapple/modules/ManaToolkit/log/Net-Creds/net-creds.log: No such file or directory Exiting! (Error code: 4) hostapd-mana was not launched correctly. Mana Toolkit has been shutdown. __________________________________________ The interesting thing is .. last night the errors were only about the Net-Creds.log file which last time was solved simply by porting over the module. This time, it persisted. I created the directory and the net-creds.log showed up when I tried to start it again. Blank but it was there. Now it looks like the entire Mana-Toolkit doesn't launch but the files are there when I navigate around them. If I wait a bit and launch it again.. here's the error I see which is exactly what it was doing last night. root@Pineapple:/sd/usr/share/mana-toolkit# launch-mana Mana Toolkit - Pineapple Edition! Device seems to be: ONLINE. RTNETLINK answers: File exists Configuration file: /sd/etc/mana-toolkit/hostapd-mana.conf Using interface wlan1 with hwaddr 00:c0:ca:91:82:c5 and ssid "MANA" wlan1: interface state UNINITIALIZED->ENABLED wlan1: AP-ENABLED RTNETLINK answers: Invalid argument /sd/usr/sbin/launch-mana: line 285: /pineapple/modules/ManaToolkit/log/Net-Creds/net-creds.log: No such file or directory hostapd-mana is running with pid: 3016 DHCP Server is running with pid: 3031 SSLstrip+ is running with pid: 3098 DNS2Proxy is running with pid: 3100 Exiting! (Error code: 6) SSLsplit was not launched correctly. Mana Toolkit has been shutdown. root@Pineapple:/sd/usr/share/mana-toolkit# It I keep launching it from the Terminal.. It does work after around 5 tries. However, the module interface is left looking like the attached screenshot.
  6. Just installed the 2.9 (3.0) development version. Love it. The targeted portal seems really cool. By default does it capture credentials? I'll have to take a peek at the default.php and see what's happening since I'll be copying that for the default of my target rules. +10 to this module. Really a lot of hard work and effort. You developers of these things amaze me. I'm taking a beginning fundamentals of programming and trying python. Mad props to you people.
  7. I followed the instructions you mentioned in this thread about either touching the file or installing the Mana Module... once I installed the module, this error went away and the toolkit launches. It also works from the Pineapple interface using the module as well.
  8. I've had much better luck using this module lately by: ensuring there's enough space a good quality signal prior to capture (35% signal quality is terrible) I shoot for 60% (green indicator) 200 IVS .. if I get a capture quickly, I just let it run for another 100 IVS. In the past, I've stopped when it says WPA Handshake = YES and found that I missed just a single EPOL message. By allowing it to go a few IVS past the success, I've seen my overall success rate increase Love the PIneapple thus far but it's gotta be in close proximity. A poor signal to begin with just leads to endless captures and frustrating deauth attempts. Need to be in the green for signal quality to really be effective. Not that it hasn't happened to me in maybe 45% signal quality but it's more rare and more time consuming.
  9. @diabolic It's by far my favorite use of the Nano... discrete and you can grab the WPA Handshake and work it offline. Everything else (URLSnarf, SSL, etc.. ) is somewhat intrusive. But this.. it's just brilliant! What has worked for me is installing it to the SD card so there's never a question of space and to go for a Capture that is higher than 50% Quality. Even then (last attempt) it failed to grab Message 3 of 4 for the EPOL but it was close. Like the theads says.. aircrack-ng is the fastest method and works on the Pineapple. Although I think it's much more flawless when a handshake is captured via my laptop than the Nano (both programs saying a handshake was captured).
  10. No luck over here.. about the same error. It finished.. with errors about not finding directories and such. Could very well be the SD card stuff everybody has mentioned in this thread. Although the card is fine anywhere else and I can get into it via ssh and whatever else. Launch-Mana.. started to see some progress! But ultimately failed hostapd-mana is running with pid: 3234 DHCP Server is running with pid: 3248 SSLstrip+ is running with pid: 3315 DNS2Proxy is running with pid: 3317 Exiting! (Error code: 6) SSLsplit was not launched correctly. Mana Toolkit has been shutdown.
  11. @Zylla Okay.. factory reset, format SD card.. rooted into Pineapple.. running this script now
  12. Seems like you connected Wlan2 to a phony SSID your Pineapple is broadcasting. That IP looks super similar to what the Pineapple gives out. Look in the client list and see if your device is connected to itself.
  13. Question: Could you use the Certbot ACME client to install and automate the addition of an SSL Certificate for the Wifi Pineapple? I know there is a Paper module but that seems to be more for the creation of local certificates for other uses. I didn't see the ability to import some signed cert. Given there is root access to this device, it seems in theory it might work to do so assuming the Private key wasn't encrypted so as not to disrupt the boot-up sequence. I did a quick search, found nothing. Maybe the real question is why would you want to do this?
  14. Interested in this as the Mana for the Pineapple seems to be worth exploring!
  15. Google Fi .. I think that would work except it would eat up my data given I'm not passing thru the Open Wifi of the public place. I can only guess it had something to do with Google Wifi Assistant at this point. I did connect to another secure network via the phone, used the tethering option and that appeared to work quite well. Something about walking into this place and my phone using the Google assistant to auto-establish some connection was different. When left, it did as well. It's not in my saved list. I'll have to test out your idea. Pretty sure that would work but I didn't want to serve my my own data plan. Appreciate the additional insight. Worth testing.
  • Create New...