Jump to content

Search the Community

Showing results for tags 'slow'.

  • 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
  • Hak5 Gear
    • Hak5 Cloud C²
    • WiFi Pineapple Mark VII
    • USB Rubber Ducky
    • Bash Bunny
    • Key Croc
    • Packet Squirrel
    • Shark Jack
    • Signal Owl
    • LAN Turtle
    • Screen Crab
    • Plunder Bug
  • O.MG (Mischief Gadgets)
    • O.MG Cable
    • O.MG DemonSeed EDU
  • WiFi Pineapple (previous generations)
    • WiFi Pineapple TETRA
    • WiFi Pineapple NANO
    • WiFi Pineapple Mark V
    • WiFi Pineapple Mark IV
    • Pineapple Modules
    • WiFi Pineapples Mark I, II, III
  • 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 5 results

  1. Dug the Nano out of a drawer and though I could have some fun with it again. Updated to firmware 2.7.0 from -I can't remember- , but last time I used it was late 2018. The CPU usage (measure through the status module) was averaging 100%. Navigating to any menu takes a minimum of 20 seconds from clicking on it to actually being able to use anything. After a few minutes menus wont even work at all and I end up just unplugging the thing as the whole web page is unresponsive and the shut down button doesn't work. Also am having a hard time getting the recon to work. Will click start and wait indefinably (record was 15 minutes) for anything to show up. Usually going to the dashboard then back works. Haven't been out yet so no open networks to test and see if clients will connect or not but the open SSID just decides to disappear after a few minutes after booting, can't connect to it and doesn't show up as an available SSID when searching for wifi on my phone. I've factory reset the thing twice with nothing to help. I don't know if its just a nasty firmware release or the device somehow broke while sitting in my underwear drawer for 2 years.
  2. On our devices it is possible to run Python code, but even a simple "Hello World" Python script can take up 6-8 seconds to run, at worst! Investigations seems to show that all Python modules are kept in .py source code, and is compiled in memory on each run. (To save space i guess) Due to having alot of modules and that we're using small embedded devices, this causes delays in even the simplest of Python-related code! Example: Alot of the python scripts on my Mana Toolkit is slow, and causes the CPU-usage to sky-rocket. So what can we do do 'fix' this? Open a SSH terminal to your Pineapple and issue this command: python -m compileall This causes python to pre-compile all your python modules to .pyc-files. Which is located at: /usr/lib/python2.77 This fix is relative straight-forward on the TETRA. On the NANO we're better of moving that directory to the SD-card and issue a sym-link from that directory to: /usr/lib/python2.7 before we run the commmand. (Saves internal storage) For example like this: mv /usr/lib/python2.7 /sd/usr/lib/python2.7 ln -s /sd/usr/lib/python2.7 /usr/lib/python2.7 python -m compileall You can also pre-compile the python files within the directory you're inside by using the same command, but adding a dot at the end, like this: python -m compileall . This was a huge improvement for me. Hope it can be of usage for you guys :)
  3. I purchased a Pineapple NANO with the included RaLink RT5370 tertiary radio. I've connected the radio and confirmed it's recognized as wlan2 and I'm able to connect to my home wireless access point with it. However, when I enable PineAP and connect to an SSID on the Pineapple using a test client, the test client is only able to access the internet briefly before it stops working completely. If I SSH into the Pineapple and ping an external address (eg. 8.8.8.8), the ping times will begin around 40-50 ms but will quickly start increasing until they hit 30000 ms or higher and I start dropping pings. However, if I ping the Pineapple's default gateway (my home wireless access point), ping response times are reasonable and do not increase. I have tested this by powering the NANO with both the included Y-cable and the Anker PowerCore Slim 5000 battery and I get the same results with both power sources. It seems like a routing or iptables issue but I haven't made any customizations to the default Pineapple config. Does anyone have any experience getting client mode to work on a NANO using a tertiary radio (wlan2) in addition to PineAP? Thanks in advance!
  4. I bought a Mark V sometime last year and stopped using it shortly after because of how slow it was. If I remember correctly it was stuck around 25/kbps and I'm wondering if this was done on purpose. Has there been any software or hardware updates which fixes that?
  5. Loading the web interface is slow and doesnt always load properly, ssh is incredibly slow (i get a better connection to a server internationally then i get to the pineapple). Is this the case for most people? I did a ping test over the Ethernet cable, i send 1000 icmp packets and lost 245. The interesting thing is that the response rate of the ones that make it are always <1ms. My load average is 0.08 0.008 0.006. The firmware being used is 'Stablesaurus' 1.0.4 I ran these test before installing anything, its a clean install. Ping statistics for 172.16.42.1: Packets: Sent = 1000, Received = 755, Lost = 245 (24% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms Though if connected though wifi Pinging 172.16.42.1 with 32 bytes of data: Reply from 172.16.42.1: bytes=32 time=1ms TTL=64 Reply from 172.16.42.1: bytes=32 time=2ms TTL=64 Reply from 172.16.42.1: bytes=32 time=1ms TTL=64 Reply from 172.16.42.1: bytes=32 time=4ms TTL=64 Reply from 172.16.42.1: bytes=32 time=1ms TTL=64 Reply from 172.16.42.1: bytes=32 time=1ms TTL=64 Reply from 172.16.42.1: bytes=32 time=1ms TTL=64 Reply from 172.16.42.1: bytes=32 time=1ms TTL=64 Reply from 172.16.42.1: bytes=32 time=1ms TTL=64 Reply from 172.16.42.1: bytes=32 time=1ms TTL=64 Ping statistics for 172.16.42.1: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 1ms, Maximum = 4ms, Average = 1ms it works as expected.
×
×
  • Create New...