Jump to content

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


Recommended Posts

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

Link to comment
Share on other sites

Since you aren't successful in your attempts (and this really should be an easy thing to accomplish), you need to be more detailed about what steps you are taking to try to get it to work. If not, it's nearly impossible to figure out where things might be wrong and try to help troubleshooting it all.

And, since you're posting this in the beta thread, what beta version of the firmware are you using?

Edited by dark_pyrro
  • Upvote 1
Link to comment
Share on other sites

After the pineapple update the devices scanning mode is acting up.

I left it scanning all night (continuous mode), and it seems it basically scanned for a few minutes, then stopped. Last update of anything is like 8h ago while my personal network and all the devices are still broadcasting.

I'll try and experiment a bit if I find a reason why it stopped (it could be that i've disabled the open wifi at the time the scanning stopped)

Link to comment
Share on other sites

WiFi Pineapple 2.0.0 RC1
 

The release candidate for the WiFi Pineapple 2.0.0 firmware is now available, in the Beta channel!

As always, you can grab the latest from the beta channel by going to 'Settings', 'Advanced' on the WiFi Pineapple, and setting your "Alternative Updates" to "Beta"!

This major release includes:

  • Campaigns
    • Revamped and expanded campaign system
    • Allow scheduling and launching campaigns directly from the UI
    • Include handshakes and enterprise credentials in campaign reports
    • Include WPA3, MFP, and other advanced encryption in campaign reports
    • Generate JSON data from campaigns
  • General
    • Updated to OpenWRT 21.02.1
    • Updated from kernel 4.14.180 to 5.4.154
    • Updated the Python Pineapple API
    • Updated HostAPd
    • Updated the OUI database
  • Logs
    • Logs moved to non-volatile storage by default in /root
  • Networking
    • Complete configuration UI for supported USB Ethernet devices
    • Allow setting device hostname in Settings...Advanced
  • Packages
    • Include OpenWRT 21.02 community feeds and Hak5 2.0.0 feeds
  • PineAPd
    • Enable PineAPd at all times
    • Clean up UI experience for configuring PineAP
    • Revamp WPA Enterprise UI for clarity
    • Always enable PineAP associations when WPA Enterprise Associations are enabled
    • Warn when campaigns are enabled which could interfere with settings
    • New capture methods for Handshakes
    • Changed the default location for Log and Recon databases to nonvolatile /root/
    • Added a README to the default handshakes location (/root/handshakes)
    • Improved the bring-up time for the Management, Open, and Evil WPA Access Points
  • Recon
    • Don't allow manual recon while there are scheduled campaigns
    • Properly respect DFS / UNII-2 / UNII-2e channels
    • Increase overall performance and stability of recon backend
    • Optimize recon and deauthentication performance
    • Reduce contention between Pineapple UI and PineAPd
    • Show relative times for detected networks even when the Pineapple system time is not set correctly, by comparing time offsets with the browser.
    • Use consistent interface naming for MK7AC module adapters (wlan3)
    • Add detection for WPA3 Access Points
    • Add detection for newer 802.11 authentication suites
    • Add a new tagged parameter view for Access Points
    • View the tagged parameters and their hexadecimal values for a given Access Point.
    • Add a column for MFP (Management Frame Protection) state
    • Simplified the Security column
    • Add a security summary dialog for Access Points
    • Implement an Auto Handshake Capture mode
    • When enabled, WPA Handshakes will be captured whenever they are seen, regardless of whether a handshake capture is running
    • Overhauled the Handshakes View
    • Handshake listings now show the Client MAC, and also show the messages that were captured
    • Improved the dynamic layout of the Recon page
    • Add an icon to table rows to further distinguish Clients from their associated Access Point
    • Show an informative message for Access Points or Clients with MFP enabled when trying to perform deauthentication attacks against them
  • Security
    • Allow restricting the management interface to wired and management networks only (under Settings...Advanced)
    • Network keys are now redacted from a generated debug log
  • Setup
    • Fix UI quirks in Firefox
    • Revamp the setup wizard to only require a physical button press when configuring via wireless.
    • Improved the dynamic layout of the Setup wizard
  • System
    • Go into an error state and communicate to the user when system is flashed improperly
  • UI
    • Extend login token timeout to handle NTP resetting the system time, you'll no longer be logged out as soon as the time jumps into the future.
    • Remove old 'News' link that didn't have new news
    • Display interface base names (wlanX) instead of multiple instances of the same interface (wlanX, wlanXmon) for recon

A big thanks to all those who have helped with beta testing!

  • Like 2
Link to comment
Share on other sites

Another minor update!  Thanks to some community help, we found a few bugs in the UI that could cause it to not update properly.

2.0.0 RC1a is now out, incorporating just one fix - fixing the UI pulling the wrong data and getting out of sync.

Enjoy!

Link to comment
Share on other sites

WiFi Pineapple 2.0.0 RC2

The second release candidate for the WiFi Pineapple Mark VII is now up in the beta channel!

RC2 hunts down some of the last problems with 2.0.0, and adds a few minor new features, too.

On top of RC1, the RC2 release contains:

  • C2
    • Enable CloudC2 UI bypass mode
    • Enable Ethernet configuration from CloudC2 mode
    • Add latest c2-client with updated encryption information
    • Add C2GETCONFIG tool
  • Networking
    • Fix bogus link-local addresses being added to all interfaces, disrupting ICS mode and other operation
  • UI
    • Fix an error when no campaigns are defined which could lead to the UI becoming confused in other panels.
    • Fix routes in the settings panel constantly growing
    • Sort network scan results in the settings panel by signal level
    • Improve censorship mode to blank more of the MAC address and all of the OUI string.
    • Censor interface MAC addresses on the networking setup page
    • Fix log filters
    • Fix deleting some SSIDs from the pool
  • System
    • Clean up and simplify pineapd launching
    • Clean up and simplify cc-client launching

Known Issues:

  • Encryption values displayed in the CloudC2 server will be incorrect until a future server release.
  • Like 1
Link to comment
Share on other sites

Posted (edited)
On 5/3/2022 at 8:10 PM, Dragorn said:

WiFi Pineapple 2.0.0 RC2

The second release candidate for the WiFi Pineapple Mark VII is now up in the beta channel!

RC2 hunts down some of the last problems with 2.0.0, and adds a few minor new features, too.

On top of RC1, the RC2 release contains:

  • C2
    • Enable CloudC2 UI bypass mode
    • Enable Ethernet configuration from CloudC2 mode
    • Add latest c2-client with updated encryption information
    • Add C2GETCONFIG tool
  • Networking
    • Fix bogus link-local addresses being added to all interfaces, disrupting ICS mode and other operation
  • UI
    • Fix an error when no campaigns are defined which could lead to the UI becoming confused in other panels.
    • Fix routes in the settings panel constantly growing
    • Sort network scan results in the settings panel by signal level
    • Improve censorship mode to blank more of the MAC address and all of the OUI string.
    • Censor interface MAC addresses on the networking setup page
    • Fix log filters
    • Fix deleting some SSIDs from the pool
  • System
    • Clean up and simplify pineapd launching
    • Clean up and simplify cc-client launching

Known Issues:

  • Encryption values displayed in the CloudC2 server will be incorrect until a future server release.

 

 

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

Edited by princesstoadstool
Link to comment
Share on other sites

10 hours ago, 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

You can't recover straight to the RC2 Betas.
https://docs.hak5.org/wifi-pineapple/faq/factory-reset-and-recovery

You have to download the recovery BIOS first.

  • Upvote 1
Link to comment
Share on other sites

13 hours ago, SKiZZ said:

You can't recover straight to the RC2 Betas.
https://docs.hak5.org/wifi-pineapple/faq/factory-reset-and-recovery

You have to download the recovery BIOS first.

yeah i know that, but once its in recovery it wants to download the latest proper image and i've done all that. I can get it all back up and running on 1.1.1 but cannot get it to RC2.   surprised noone has piped up from Hak5 on this matter.  Unless my device is faulty, surely it should work. right?

Link to comment
Share on other sites

On 5/6/2022 at 2:11 AM, princesstoadstool said:

Down here in New Zealand - we are having the same issue as below when trying to upgrade our 3 different Mk7 pineapples from 1.1.1 stable to the RC2 Beta release. Hoping for some Hak5 input?

Cheers
A

 

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

 

Link to comment
Share on other sites

If you want some Hak5 input, then create a support ticket. There's no guarantee that the forums will be monitored. It's a community for Hak5 device users. If having several Pineapples and none of them work (but has worked using 1.1.1) seems really strange. So strange that it's interesting to know more details in order to try to troubleshoot here on the forums. However, there's not much details to be shared if the updates are done/tried using the web UI. I really can't see what the issue might be since I haven't experienced the same myself. I've "traveled" to and from stable to beta countless times and haven't had a single problem doing so. I can't see that three devices would fail and therefore it's interesting to know if the stable to beta upgrades are made in some way that differs from "standard procedure".

Link to comment
Share on other sites

15 hours ago, dark_pyrro said:

If you want some Hak5 input, then create a support ticket. There's no guarantee that the forums will be monitored. It's a community for Hak5 device users. If having several Pineapples and none of them work (but has worked using 1.1.1) seems really strange. So strange that it's interesting to know more details in order to try to troubleshoot here on the forums. However, there's not much details to be shared if the updates are done/tried using the web UI. I really can't see what the issue might be since I haven't experienced the same myself. I've "traveled" to and from stable to beta countless times and haven't had a single problem doing so. I can't see that three devices would fail and therefore it's interesting to know if the stable to beta upgrades are made in some way that differs from "standard procedure".

Thanks for your excellent advice - perhaps our wording was wrong, our apologies. A support ticket has already been created - however, we don't have a response as yet from Hak5 so our intent was merely to confirm that we are having a similar beta upgrade issue as Princesstoadstool. We will wait to see if/when Hak5 respond and will post the advice here in case it helps others.

Link to comment
Share on other sites

Hello all I just upgraded to the Beta 2.0.0 with no problem BUT when checking that all modules were configured and working as in the 1.1.1 version Evil Portal is a no go? Works every time in the stable release(1.1.1.) and understand this is a BETA but any help would be appreciated. Server is up and running but when a portal is activated or active then selecting the preview button i get a broken image with as the portal is not being hosted properly with a message " The webpage at https://172.16.42.1/ might be temporarily down or it may have moved permanently to a new web address'' the permanent address is showing 172.16.42.42 but I am sure there is a config file I need to update for this beta version to get it working correctly I just need some guidance as to where or if there is a bigger issue with this beta version and evil portal. Thanks in advance.

Link to comment
Share on other sites

I'm on the latest beta and it works as it should. There was some issues with the first betas, but that is solved now (and was related to https, so not the same as described here). It seems as if nginx isn't playing ball in some way. Run

ps ax | grep [n]ginx

and verify that nginx is running (when you have started it in the Evil Portal web UI). Also note what config file that is used. It should be the one in /etc/nginx. Evil Portal should execute properly with the default configuration.

Link to comment
Share on other sites

Also good to know when troubleshooting is if you use some pre-made portals or if you created one (or several) of your own.

It can also be argued if this is really linked to the beta itself. Modules are maintained by their creators and usually detached from the Hak5 "core product". However, decisions made when releasing new versions of firmware might affect existing solutions (such as modules). One example is moving up to newer releases of the OS. In that case you are dependent on decisions made that is out of your control since you can't do anything about the fact that newer OpenWrt releases handles some things differently upstream (what's included in packages, how they are compiled, the settings that comes with them, etc.). It's just to adapt, take action and move on.

In any way, the Evil Portal module should work for you using the latest beta/RC.

Link to comment
Share on other sites

5 hours ago, dark_pyrro said:

Also good to know when troubleshooting is if you use some pre-made portals or if you created one (or several) of your own.

It can also be argued if this is really linked to the beta itself. Modules are maintained by their creators and usually detached from the Hak5 "core product". However, decisions made when releasing new versions of firmware might affect existing solutions (such as modules). One example is moving up to newer releases of the OS. In that case you are dependent on decisions made that is out of your control since you can't do anything about the fact that newer OpenWrt releases handles some things differently upstream (what's included in packages, how they are compiled, the settings that comes with them, etc.). It's just to adapt, take action and move on.

In any way, the Evil Portal module should work for you using the latest beta/RC.

pyrro thanks for the response and info Ill give it another go today and see if i can get it going. I do like all the new tweaks and information though in version 2.0.0 its slowly but surely getting there.

Link to comment
Share on other sites

 

6 hours ago, dark_pyrro said:

I'm on the latest beta and it works as it should. There was some issues with the first betas, but that is solved now (and was related to https, so not the same as described here). It seems as if nginx isn't playing ball in some way. Run

ps ax | grep [n]ginx

and verify that nginx is running (when you have started it in the Evil Portal web UI). Also note what config file that is used. It should be the one in /etc/nginx. Evil Portal should execute properly with the default configuration.

 

thank you for the command (server is on and running through the UI) when checking the process of nginx it does indeed look as if its not running and the daemon is turned off?

ps ax | grep [n]ginx

/usr/sbin/nginx -c /etc/nginx/uci.conf -g daemon off

I went to the uci.conf file and did not see where to turn it on again any guidance will help I am also researching my self as well. I love learning this stuff so again thanks for the help.

 

Link to comment
Share on other sites

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.

  • Like 1
Link to comment
Share on other sites

That worked but after you said you had reset your pineapple a lot I went a head and selected update and flashed the firmware again and PATIENTLY waited for it to install. Unplugged the PA then plugged back in and reconfigured everything signed in and REBOOTED AGAIN. Selected the newly named AP verified I had an IP address for the connected Wi-Fi then downloaded the EvilPortal module, installed its requested dependencies REBOOTED again for good measure signed back in and everything was working correctly as you mentioned your was doing and pulling the correct config file displaying my portals on any device that selected the open AP. I still walked away learning some new stuff with your help and for me thats what all this about! Thank you again 

Link to comment
Share on other sites

I just want to be clear about my comment about resetting the Pineapple. That's not something I do because the Pineapple isn't working as it should. It's because I go from beta to stable and back again for different reasons (or just follow the betas and RC:s as they progress which involves setting up the Pineapple from scratch every time there's a new release).

Link to comment
Share on other sites

I was running a demo at a recruiting event for HS students today and was not able to get any results from recon. I had evil portal running and even turning it off did not help. Anyone else getting this? It is scanning as it captured a handshake at some point, but would never show results.

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   0 members

    • No registered users viewing this page.
×
×
  • Create New...