Jump to content


Pineapple Moderators
  • Posts

  • Joined

  • Last visited

  • Days Won


Profile Information

  • Gender
  • Location
    The Nebakanezer
  • Interests
    Networking, Programming, Learning, Observing, and Drumming

Recent Profile Visitors

16,384 profile views

newbi3's Achievements


Newbie (1/14)

  1. I was watching your video on how to make a custom portal and I must have typed a dot or something wrong lol I simple could not see it good. Is there anyway you can shoot me the two lines of code you used in both those files. when I review the portal it looks great but when I input info in the field I get nothing.

  2. when you get a chance can you give us a work flow. I have downloaded the portals and they are cool , but when i activate one, then get on and connect with my phone the first thing I see is the portal pop up. if I enter info I do see it in log which is awesome. I thought and maybe I am wrong, but the evil portal only pops up when someone tries to login to say Face Book?

  3. For your usecase it sounds like you want a Basic Portal which will show the same captive portal page to everyone always. Targeted Portals allow you to change the page that is returned to the user based on different conditions that you set in the rules editor. For example, you may have a target that you know might connect to 2 different SSIDs based (lets say `Corporate Wifi` and `Coffee Shop`) and based on this you want to show a page that relates to the SSID. You would create two rules in the targeted rule editor for SSIDs and route them to two different destinations (we'll call them corporate.php and coffee.php). Now when a client connects to the Pineapple thinking its `Corporate Wifi` they will be shown the `corporate.php` page. If the connect thinking its `Coffee Shop` they will be shown the `coffee.php` page.
  4. This should be fixed in the 1.0.1 Beta 4 firmware. Sorry about that.
  5. Would you mind sharing the portal with me? You can DM it to me. I never actually tested portals from the previous pineapple so something might be broken. I'll try to help you migrate it so I can write some documentation on what to do going forward.
  6. Did you create this portal new on the mk7 or is it from an older version created on the nano/tetra? I'll take a deeper look into this weekend. Which version of the firmware are you on? Also can you please include the output of the module log file? You can find it at /tmp/modules/evilportal.log
  7. This should now be fixed in firmware version 1.0.1 Beta 3 and newer. If anyone has issues going forward please report it.
  8. I'm assuming this is a custom made portal since you are submitting credentials. My guess is the portal's backend code isn't handling the authorization flow correctly.
  9. The goal of the Evil Portal module is to provide a captive portal platform with a few bells and whistles, not necessarily to create pre-made templates for every use case. If this is something you need I highly encourage you to build it. If there are any specific questions you have about how to do something with Evil Portal I'm happy to help.
  10. This module isn't really meant to be left running while you're not looking at it. If you need to do a packet capture that records the data it collects I recommend using tcpdump.
  11. Hello, we are looking into this and will have a fix asap. Have you tried the temporary solution in this thread?
  12. The modules are typically developed by 3rd party developers. Developers need to port over the modules from the Nano/Tetra to the Mk7. This will take some time since developers have to get the hardware and then start writing code. Feel free to create any modules you want to as well! https://docs.hak5.org/hc/en-us/sections/360008923634-Development More documentation and tutorials are in the works from what I hear.
  • Create New...