Jump to content

[RELEASE][BETA] WiFi Pineapple Mark 7 2.0.0 Beta Firmware


Recommended Posts

On 5/9/2022 at 4:13 PM, dark_pyrro said:

Don't mind the daemon. The strange thing is that it uses that config file. That should have been resolved in later versions of the beta (and RC). I had my Pineapple reset (for the N:th time) and just recently installed the latest 2.0.0 RC and I didn't get that setting regarding the config file.

Stop the web server in the Evil Portal module.

Edit the /etc/config/nginx file and change "option uci_enable" from true to false.

Start the web server again and verify the preview of any portal available.

If you run the ps command I previously posted, you should see that it uses /etc/nginx/nginx.conf as the config file.

Please any ideas in getting a stable macchanger  macaddress using wlan2 connected to the Internet  and  getting macc address change for monitor mode 

 

Please help pleassssssssssseszzssezzz!

Link to comment
Share on other sites

On 4/20/2022 at 11:11 PM, techspecialist2019 said:

Hey guys I cant seem to connect to my pineapple mark 7 for the longest very frustrating. When I bought it a while ago it the directions were very vague and it wasn't set up right out of the box with AP enabled. then I tried to get it working with a USB to ethernet port and tried to enable the AP WiFi and it didn't work finally I hooked it up directly to my PC and i go to the GUI page was able to log in but still it wont connect or activate the WiFi I tried to reset it muliplitable time and still it wont connect either Ethernet nor WiFi enable Please help

Please any ideas in getting a stable macchanger  macaddress using wlan2 connected to the Internet  and  getting macc address change for monitor mode 

 

Please help pleassssssssssseszzssezzz!

Link to comment
Share on other sites

On 5/5/2022 at 3:11 PM, princesstoadstool said:

 

 

Just tried to update to RC2 and it failed.  Recovered. Flashed 1.0.1 or whatever it flashes by default, then changed to beta channel and tried again.   Failed again.

"A flash error was detected on your device."  any ideas? 

 

just tried a forth time after rebooting a few times beforehand. see if that made any difference. nope. 

 

is there a downloadable file which I can upload directly instead of downloading from the servers? at least i can verify the md5 etc that way

 

edit: ok i downloaded the latest version and tried to install it manually and i get the same red light/error.  so its just not installing for me.  at least over the top of 1.1.1

ok last try, tried to upgrade to RC2 straight from the recovery.  still same.   

 

will try RC1 instead if i knew what the filename was

Please any ideas in getting a stable macchanger  macaddress using wlan2 connected to the Internet  and  getting macc address change for monitor mode 

 

Please help pleassssssssssseszzssezzz!

Link to comment
Share on other sites

Posted (edited)

Bugs

- Anyone else experiencing an issue whereby the scan / handshake capture stops working? It's fairly random in my case but usually after ~5 mins they both disable and have to be manually re-enabled. No other changes made, it simply stops on it's own accord.

- After capturing a few handshakes, subsequent handshakes from other networks appear to be corrupted (E.g. They cannot be processed, read etc) When rebooted, the same handshake is captured successfully. I've had difficulty re-producing this but it's happened at least twice.

Feedback

- If you sort by signal strength, on each refresh, it undoes the sort order.

- Handshake captures can have random orders, perhaps the default should be by capture time.

- 'Once off' / single sweep recon as opposed to having to choose by time frame e.g. Once / 30 Seconds / 5 mins etc

- Handshakes should include column with SSID of network where applicable.

Edited by ironclaw
Link to comment
Share on other sites

  • 2 weeks later...
On 5/21/2022 at 9:26 PM, ironclaw said:

Bugs

- Anyone else experiencing an issue whereby the scan / handshake capture stops working? It's fairly random in my case but usually after ~5 mins they both disable and have to be manually re-enabled. No other changes made, it simply stops on it's own accord.

Put PineAP into "Passive" and that should stop happening.

Link to comment
Share on other sites

  • 3 weeks later...

RC3 is now available!

Coming up on the final refinements, RC3 has a handful of new fixes and changes on top of RC2, particularly a new take on the PineAP UI that should make it much more obvious what your Pineapple is up to.

  • Campaigns
    • Handle deleting the active campaign cleanly
  • PineAP
    • Handle resetting to 'any' type properly
    • New PineAP UI
    • Restored functionality of Evil WPA + Evil Enterprise at the same time
    • Ability to change MAC addresses on all PineAP access points (open, wpa, enterprise)
    • Significantly reduced background processor usage, again
    • Better performance in high-traffic areas
  • Networking
    • Handle disconnecting from client mode more cleanly
    • Fix client interfaces coming half-up with a blank SSID
  • System
    • Pre-compressed user interface files for much faster loading
    • Ability to flash a locally-uploaded firmware from the Settings UI
    • Start web shell in /root
    • Add additional health checks during setup
    • Add new basic health check / diagnostics page
    • Start linking documentation for each part of the UI
    • Ability to change MAC on Management AP
    • Tweak TLS client settings to attempt to address issues on some ISPs
  • UI
    • Reworked UI internals for future feature support
    • Reorganized WiFi settings to make more sense, management now in system settings
    • Server-side search and pagination for log viewing (significantly faster response)
    • Allow browser caching of images and fonts
    • Continue tweaking censor for recon scans to better anonymize data
    • Provide additional information about recon interfaces when selecting them in the UI
  • Like 2
Link to comment
Share on other sites

  • 2 weeks later...

I guess I'm the victim of my own success. I left a both-frequencies scan running for a week in continuous mode. Collected many, many, many SSIDs. log.db has 20k lines, recon.db had 52k lines. To the point where the UI was extremely sluggish. Collected 28 handshakes, so I can't complain I guess. What's the appropriate method to clearing out all this historical data and starting fresh, assuming that's what's making the UI sluggish? Just delete log.db and recon.db?

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

  • Recently Browsing   1 member

×
×
  • Create New...