Jump to content

Search the Community

Showing results for tags 'issues'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Talk
    • Everything Else
    • Gaming
    • Questions
    • Business and Enterprise IT
    • Security
    • Hacks & Mods
    • Applications & Coding
    • Trading Post
  • WiFi Pineapple
    • WiFi Pineapple TETRA
    • WiFi Pineapple NANO
    • WiFi Pineapple Mark V
    • WiFi Pineapple Mark IV
    • Pineapple Modules
    • WiFi Pineapples Mark I, II, III
  • Hak5 Gear
    • Hak5 Cloud C²
    • Plunder Bug
    • Bash Bunny
    • Signal Owl
    • USB Rubber Ducky
    • Packet Squirrel
    • LAN Turtle
    • Screen Crab
    • Shark Jack
    • Key Croc
  • O.MG (Mischief Gadgets)
    • O.MG Cable
    • O.MG DemonSeed EDU
  • Hak5 Shows
  • Community
    • Forums and Wiki
    • #Hak5
  • Projects
    • SDR - Software Defined Radio
    • Community Projects
    • Interceptor
    • USB Hacks
    • USB Multipass
    • Pandora Timeshifting

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests


Enter a five letter word.

Found 10 results

  1. Battery Tester/CPU Stress For the SharkJack I keep seeing people talk about how the battery lasts less then 10 minutes, etc etc etc.. I made a script to test and prove the Battery Drains incredibly fast under load. Further more... The Script.. (NOTE: This Script should be ran on the SharkJack itself!) battery-tester.sh #!/bin/bash # Title : Battery Tester/CPU Stress # Author : REDD of Private-Locker # Version : 1.1 # Description : The script uses a simple log system to pull the # batteries status, date, and time into a log file for Hak5 # to help diagnose the issues. Also uses "sha256sum" to verify # a null file leaving it to stress the CPU. # # Log File : /root/battery.log # Set to YES to stress the CPU during Battery Test. MAX_LOAD=YES STRESS="sha256sum" # Time in seconds to report in log. (20 mins = 1200) TIME=600 # Initial Script Variables - DO NOT CHANGE UNDER_LOAD=0 DATE_NOW=$(date +'%r') START_TIME=$(date) CPU_USAGE=$(grep 'cpu ' /proc/stat | awk '{usage=($2+$4)*100/($2+$4+$5)} END {print usage "%"}') BATTERY_STATUS=$(BATTERY) LOG_FILE="/root/battery.log" function DISPLAY_TIME () { MINS=$((TIME / 60)) SECS=$((TIME % 60)) if [ "$TIME" -ge "60" ]; then printf "$MINS minutes and $SECS seconds" else printf "$SECS seconds" fi } TOTAL_TIME=$(DISPLAY_TIME "$TIME") if [ ! -f "$LOG_FILE" ]; then touch "$LOG_FILE" fi if [ -f "$LOG_FILE" ]; then echo -e "" >> "$LOG_FILE" echo -e " Battery Test Date: $START_TIME" >> "$LOG_FILE" echo -e "==================================================" >> "$LOG_FILE" echo -e "" >> "$LOG_FILE" echo -e "" echo -e " Battery Test Date: $START_TIME" echo -e "\n Battery Test running for $TOTAL_TIME." echo -e " Battery Test running for $TOTAL_TIME." >> "$LOG_FILE" echo -e " Battery Status: $BATTERY_STATUS" echo -e " Battery Status: $BATTERY_STATUS" >> "$LOG_FILE" echo -e "" if [ "$MAX_LOAD" == "YES" ]; then echo -e "\n\n -> LOAD created by $STRESS." echo -e " -> LOAD created by $STRESS." >> "$LOG_FILE" echo -e "" >> "$LOG_FILE" echo -e "==================================================" >> "$LOG_FILE" echo -e "" >> "$LOG_FILE" fi echo -e "" >> "$LOG_FILE" fi echo -e "[${DATE_NOW}] -> LOAD: $MAX_LOAD - CPU Load: ${CPU_USAGE} [Battery Status: ${BATTERY_STATUS}]" >> "$LOG_FILE" for ((i=0; i<=TIME; i++)); do if [ "$MAX_LOAD" == "YES" ]; then if [ "$UNDER_LOAD" == "0" ]; then UNDER_LOAD=1 $STRESS /dev/zero & fi fi DATE_NOW=$(date +'%r') CPU_USAGE=$(grep 'cpu ' /proc/stat | awk '{usage=($2+$4)*100/($2+$4+$5)} END {print usage "%"}') BATTERY_STATUS=$(BATTERY) printf "[%s%s] -> LOAD: %s - CPU Load: %s [Battery Status: %s]\r" $DATE_NOW $MAX_LOAD $CPU_USAGE $BATTERY_STATUS echo -e "[${DATE_NOW}] -> LOAD: $MAX_LOAD - CPU Load: ${CPU_USAGE} [Battery Status: ${BATTERY_STATUS}]" >> "$LOG_FILE" sleep 1; done if [ "$UNDER_LOAD" == "1" ]; then killall -9 $STRESS fi echo -e "" >> "$LOG_FILE" echo -e "==================================================" >> "$LOG_FILE" echo -e "" >> "$LOG_FILE" # Blank line for running in Terminal. printf " \n" printf "Finished.\n" Output Example: Battery Test Date: Tue Jan 28 13:47:30 UTC 2020 ================================================== Battery Test running for 10 seconds. Battery Status: full [01:47:30 PM] -> LOAD: NO - CPU Load: 18.0325% [Battery Status: full] [01:47:30 PM] -> LOAD: NO - CPU Load: 18.0437% [Battery Status: full] [01:47:31 PM] -> LOAD: NO - CPU Load: 18.0428% [Battery Status: full] [01:47:32 PM] -> LOAD: NO - CPU Load: 18.0432% [Battery Status: full] [01:47:33 PM] -> LOAD: NO - CPU Load: 18.0469% [Battery Status: full] [01:47:34 PM] -> LOAD: NO - CPU Load: 18.0515% [Battery Status: full] [01:47:35 PM] -> LOAD: NO - CPU Load: 18.0556% [Battery Status: full] [01:47:37 PM] -> LOAD: NO - CPU Load: 18.0596% [Battery Status: full] [01:47:38 PM] -> LOAD: NO - CPU Load: 18.0641% [Battery Status: full] [01:47:39 PM] -> LOAD: NO - CPU Load: 18.0678% [Battery Status: full] [01:47:40 PM] -> LOAD: NO - CPU Load: 18.0718% [Battery Status: full] [01:47:41 PM] -> LOAD: NO - CPU Load: 18.0759% [Battery Status: full] ================================================== I really hope this helps everyone else in their troubles in finding out if their Battery is just defective or it's just "Under Load" that makes it so short.
  2. Hello everyone, I've been playing around with a freshly acquired Wifi Pineapple Tetra. I upgraded, did a few factory resets and frimware reset too I there a two problems that need to be fixed. The first one apparead with the firmware upgrade from 2.4.something to the latest 2.6.2. : The live scan results don't print. We need to do a scan, stop it and load the scan file to output the results. I have seen this issue a few times on the forums but no admin/dev here made any answer or fix. WE NEED TO FIX THIS. This feature is important for the field pentesting. The second one is linked to wlan1mon. When I enable the PineAp, wlan1 goes into monitor mode and becomes wlan1mon. When PineAP gets disabled, the reverse operation is not done, making the red LED to keep blinking even though the PineAP is stopped. Any admin or dev here could take a look at this please ?
  3. Hi, I got internet connection working, ssh'd in. Did apt-get update, then apt-get upgrade. Now Im unable to get any result of GET TARGET_IP I did the firmware reset, but am still having issues LED R SOLID ATTACKMODE ECM_ETHERNET LOOTDIR='/root/udisk/loot/IP' mkdir -p $LOOTDIR GET TARGET_IP echo "IP: $TARGET_IP" >> $LOOTDIR/IP.log LED G SOLID Running the above now gives me a file without the Target IP within. Any Ideas?
  4. I Read The Instructions for How to do this on the WifiPineapple Website, But I don't Understand the Step Where Your Supposed To Power On The Device But Not Connect it to your pc... Any Help?
  5. I have been running the payload to install the tools for the bashbunny but it is not working. It doesn't turn on the led at first and then it flashes a white light and it boots normally. After it boots there is no tools folder and the install.sh file doesn't change to INSTALLED. Is there anyway I can fix this or is there another way to install the tools?
  6. My Wifi Pineapple Nano Tactical Elite edtion just arrived and I have some problems with it. The Wifi dongle wich it came with disconnect's after around 5 minutes, my system logs gives the following: Tue Jun 6 15:53:31 2017 kern.info kernel: [ 394.880000] wlan2: authenticate with e4:f4:c6:XX:XX:XX Tue Jun 6 15:53:31 2017 kern.info kernel: [ 394.940000] wlan2: send auth to e4:f4:c6:XX:XX:XX (try 1/3) Tue Jun 6 15:53:31 2017 kern.info kernel: [ 394.950000] wlan2: authenticated Tue Jun 6 15:53:31 2017 kern.info kernel: [ 394.960000] wlan2: associate with e4:f4:c6:XX:XX:XX (try 1/3) Tue Jun 6 15:53:31 2017 kern.info kernel: [ 394.960000] wlan2: RX AssocResp from e4:f4:c6:XX:XX:XX (capab=0x1411 status=0 aid=2) Tue Jun 6 15:53:31 2017 kern.info kernel: [ 395.000000] wlan2: associated Tue Jun 6 15:53:32 2017 daemon.notice netifd: Network device 'wlan2' link is up Tue Jun 6 15:53:32 2017 daemon.notice netifd: Interface 'wan' has link connectivity Tue Jun 6 15:53:32 2017 daemon.notice netifd: Interface 'wan' is setting up now Tue Jun 6 15:53:32 2017 kern.info kernel: [ 395.120000] wlan2: deauthenticating from e4:f4:c6:XX:XX:XX by local choice (Reason: 3=DEAUTH_LEAVING) Tue Jun 6 15:53:32 2017 daemon.notice netifd: Network device 'wlan2' link is down Tue Jun 6 15:53:32 2017 daemon.notice netifd: Interface 'wan' has link connectivity loss And when the dongle is working then for some reason my SD-Card is not showing up, I am using a Sandisk 16GB Micro SD Ultra. Greetings, Nathan102
  7. Hello, I just received my WifiPineapple Elite edition in the mail today and i am having issues setting it up. I run my Kali 2.0 through virtualbox and it is setup with a bridged connection. I've added the WP to the list of USB devices in the VM settings. I run the wp6 and do the guided setup, confirm my default address as 10.0.2.1, confirm eth0 is my internet connection, then confirm that eth1 is the pineapple. I look at my network connection and it shows both eth0 and eth1 are connected. My ip to eth0 is given as 10.0.2.100 and eth1 is 172.16.42.42. When i select "connect using saved settings" in the wp6 script, it says it is "detecting wifi pineapple" and just hangs there, throwing periods for dayzzz! I cant ping 172.16.42.1 either. Anybody know whats going on? Thank you.
  8. I mean Not getting stuck while scanning wifi networks. With clients not losing connectivity all the time SD Card reads all the time Broadcast SSID Pool all the time not just a few minutes Or it's just me?? I already reset, format, reboot many times, checked all the instructions, I'm pretty sure is not an user problem I wished i read the post from this forum before i bought the nano elite, it seems like many users have the same problem, so far is just an expensive brick.
  9. Good Morning all, I have upgraded to the new Codename Buffalo Bulldozer release and have been running into some issues using PineAP. With the settings as Allow Associations, Log Probes, Log Associations, PineAP Daemon: Enabled, Capture SSIDs to Pool, Beacon Response and Beacon Response Interval set to Aggressive I have not been able to get clients to connect as before with the previous release, before these settings would work flawlessly and any device not connected to wifi but beaconing would be added to the SSID Pool and connected as a client. Now I am unable to get any automatic associations, matter of fact for the last two days I have been working with the new firmware I have yet to get any ( I have three devices set up probing right next to the Pineapple). It doesn't even seem to be reading the Probes but sporadically and even then its two at max. Just wondering if anyone else is having these issues? Also the Save active config as default dose not seem to be working as before, with the same settings annotated above every time I start up the NANO PineAP is Disabled... The previous version fired right up into the settings I needed. Thanks in advance for the support Oh and not to pile too much into one post but I have had the Recon hang at 100% again, I hope these issues are user error lol since the release directly addressed this issue.
  10. Good evening, I own a wifi pineapple nano and ever since the firmware upgrade it has been acting funny I wiped it 3 days ago and it was working fine yesterday. Today it won't even stay on at all I plug it up and lights up then turns right back off. Also after not even having it for 3 months the antennae broke on it the black part came off and after continuous attmpts to make it stay on the wite finally ended up breaking. Please help I would like to be assured that the $200 I spent wasn't a waste of money......
×
×
  • Create New...