Jump to content

Search the Community

Showing results for tags 'LED'.

  • 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 18 results

  1. I did a reset of my bash bunny (doesn't boot 3 times, auto-reset) and now its LED doesnt accept states. I have done some testing and it looks like what used to be a constantly running service to blink the LED is now only running once then stopping. To elaborate, if I say "LED G SOLID" the LED will stay green solid, same if I say "LED G VERYFAST" but if I say "LED G IQUAD" it starts and stays off. (so my idea is that, the first instance of blink_led.sh closes early or it doesnt detect that I even passed a state at all) when in the remote shell if I use the "LED R VERYFAST" command two times in a row it echos "blink_led.sh: process not found" which seems to further indicate the process isnt running. I have already tried doing another reset and even updating the firmware completely and it hasnt seemed to work. Is this a known issue with solutions or is there an issue with my hardware? (tell me if I'm missing something here but I hope this is enough information, also by BB is like brand new, I got it last week and havent really used it aside from testing)
  2. Hello guys, I've tried everything and it seems that my USB Rubber Ducky just doesn't read any sd cards. By everything I mean: Tried 4 different SD Cards; Resetted the firmware using ducky-flasher; Changed the firmware from the original to Twin Duck; Tried different USB ports; Tried formatting the SD Cards (FAT/FAT32); Tried with empty SD Cards Tried with different inject.bin payloads; Tried with different Operating Systems; And finally, tried changing laptops. The Rubber Ducky is brand new, arrived a week or so ago and it worked great a few times while on the original firmware with simple payloads (fake update) in the sd card that came with it. Today, I decided to check it a little more, using ducky-flasher and following the instructions on github, I flashed the twin duck firmware and it worked once or twice but after checking the available payloads on github I tried again using it and it kept an always constant red led which I found out that means that it's not communicating with the SD Card. After trying a few thing on the list above, I discovered that the LED is always red with or without an SD Card (not sure if it's the default behavior for when there's no card present). What more can I do?
  3. Today I received my nano version of the wifi pineapple. As per instructions shown here: https://www.youtube.com/watch?v=CrHbEZd4t00 I've connected the device to my laptop and eagerly started waiting for the blue led to show up at no avail. The device also came in a skeptical condition with the casing falling apart - see the picture. I've tried connecting it to a total of 2 laptops and a desktop pc with the same results. However, with lsusb the machine finds it under the name Any ideas ideas on what may be wrong?
  4. Hi how do i get the police led sequence from the update flashes I want to implement this sequence into my payload, whats the code I need to write to get the sequence and how do I change the colours and the timing. Changing the colours and timing is just changing values but I don,t know how to recreate the police lighting. Thanks
  5. b0N3z

    TwoTone LED

    So I have tried a couple things and I only get a white LED from my arming mode payload. LED W B 500 <---- only shows solid white LED W B SINGLE <----- only blinks white I want the LED to blink blue and white similar to the update RED and BLUE but slower blinking. Anybody got some advice on this
  6. tl;dr- Add logic to the RD to monitor key lock values. Use this for functions like file transfer. Because I wanted to see if I could, I wrote a VBScript to transmit a file using the Scroll lock, Caps lock, and Num lock keys. As it turns out, if you record the data with a fast enough camera you can decode the bits and reproduce the transmitted file. Unfortunately, to make it feasible for a camera to pickup the LED fluctuations and and then for a human to interpret the blinks, the transfer rate is very slow. In fact, if you have the time and ability to use a camera to record the computer, you should really just take a picture of the screen. If only there was a technical means of monitoring these LED statuses that could increase the rate at which this could operate... (Note: In the above video, you have to view at 60fps and set the playback speed to 25% to even have a chance of decoding it manually) Fast forward a couple days and I saw another demonstration of the Rubber Ducky on Hak5. As I understand it, the RD interprets a compiled script and primarily acts as an output only HID. Because of this, payloads from the RD have only two ways of currently gathering information. One is to exfiltrate the data over a network connection (bad because it may be logged by a firewall or proxy), and the other is to switch to USB storage mode (bad because systems may monitor or block USB Mass Storage Devices). However, by utilizing Caps/Num/Scroll lock, payloads could potentially communicate any type of data back to the Rubber Ducky (without tripping any host system security/monitoring). I'm suggesting that some logic be added to the RD to monitor the Key Locks and use them as a way of receiving data. In the video demonstration demonstration, I used sendkeys to flip the status on the three LEDs. Every-other-bit is sent to Num Lock and Caps Lock with Num Lock being bit one, Caps Lock being bit two, and Scroll Lock always being the timing. For efficiency's sake, every transmission of two bits is indicate by alternating Scroll Lock. This means that with SL turns on, two bits were sent and when SL turns off, 2 more bits were sent. This timing is necessary to indicate to the interpreter (be it human or RD) that the other two bits are current (even if they haven't changed in value). The script currently lacks any intelligence- it just blindly sends the contents of a file. But, if the script were to know it was talking to the RD, it could wait for acknowledgements from the RD before sending a file. Furthermore, since this technique would allow two-way communications with the RD, we could incorporate useful file transfer features like CRCs and the inclusion of the file name. As I mentioned in the beginning, using this technique to visually send information via the LEDs is too slow to really be of any value. But, this same technique may have value when the thing observing the LED value changes is a Rubber Ducky. I estimate that this technique would allow binary data to be sent to the RD at around 1.5 kB/s. Granted, this is a far cry from USB Mass Storage Device speeds and network transfer speeds, but this method doesn't require a system to be on-line and wouldn't leave any trail on the host system*. Of course, in addition to file transfers, two-way communications with the RD can open up more possibilities. For instance, the RD could run a script on the host system to see what version of the OS is running and then send the OS version back to the RD. From there, the RD could send a different script based on the version. Granted, you could just put this logic in one payload file that is executed on the host, but there may be cases where you want to keep some secret sauce on the RD and never written to a host machine. The Duck Whisper *- Okay, some key-loggers might record the key presses. But if the system has a key-logger, it would have recorded the entire RD session anyway.
  7. I have a solid amber light on my mark 5 after installing the 2.4 bin file through the GUI on 192.168.1.1 after powering up while holding the button and continuing to hold for 10 earth seconds. really would like to get my pineapple running again.. -Jon
  8. pmurton

    LED Control

    I've only had the BB for a few days so please excuse me if I'm asking a stupid question. How do I turn off the LED? on ver 1.0 of the firmware it seems to have been LED with no parameter, but this does seem to be the case in ver 1.1. I can pick most of it up from other payloads, but is the any documentation on controlling the LED.
  9. When connecting my nano to my windows machine, the led turns on for about 3 seconds and turns off. The GUI is unreachable at 172.16.42.1:1471. When trying Darren's recovery method where you set a static ip in the 192.168.1.X range, I reconnect the nano while holding the reset button and get a solid LED, but when going to 192.168.1.1 I am redirected to the Asus web management of my router instead of the recovery page. Any help would be appreciated. Thanks :)
  10. Okay. So I just got my bash bunny today and the LED lights were working a when I got it (amber, yellow, purple, blue) But now the payloads "run" and the only led light that works is Green for when I plug it in arming mode. It will not turn other colors.
  11. Hi, So while digging around the NANO I discovered two LED devices labelled "ath9k-phy0" and "ath9k_htc-phy1". The first one isn't too interesting, but the latter, "ath9k_htc-phy1" is the device entry for a green LED on the NANO. Go ahead and look through the cutout for the female USB port, you should see it lit up. I think these LEDs were left in by accident by the manufacturer for the second radio. And while it is pretty useless because you can't see the LED easily, you can control it. If you'd like to mess with it, I recommend reading this and experimenting with different triggers. To enable a simple blinking of the LED, edit "/etc/config/system" and place the following underneath the existing led config block. config led option name 'wlan1' option sysfs 'ath9k_htc-phy1' option trigger 'timer' option delayon '5000' option delayoff '2000' Your config should then look a little like this: config system option hostname Pineapple option timezone UTC config led option name 'wlan0' option sysfs 'pineapple:blue:system' option trigger 'netdev' option dev 'wlan0' option mode 'link tx rx' config led option name 'wlan1' option sysfs 'ath9k_htc-phy1' option trigger 'timer' option delayon '5000' option delayoff '2000' config 'timeserver' 'ntp' list 'server' '0.openwrt.pool.ntp.org' list 'server' '1.openwrt.pool.ntp.org' list 'server' '2.openwrt.pool.ntp.org' list 'server' '3.openwrt.pool.ntp.org' option enable_server 0 -Foxtrot
  12. Hello! I have recently bought the basic version of the MK5 Wifi Pineapple. I'm new to The Pineapple and am having some confusion. The Wifi Pineapple works great when plugged into the PSU that came in the kit. When I try to use any other cable and wall adapter the green L.E.D. is dimly lit and it seems to not be getting enough power. I am using an iPad wall adapter and the output is 10w (5v * 2a). I run into the same issue with using a power bank, which is also 10w (5v * 2a port): USB cable and power bank: http://www.amazon.com/gp/product/B00MRD3UE6/ref=oh_aui_detailpage_o07_s00?ie=UTF8&psc=1 http://www.amazon.com/gp/product/B00304DZ7I/ref=oh_aui_detailpage_o07_s00?ie=UTF8&psc=1 Any help would be appreciated. Thank you!
  13. Hi! I've been trying to find some information on different status light combinations. Forums and wiki seem blank on that topic. The main reason is a flash that seems to be taking an awful long time and the status lights are: Constant green Flashing red, blue, amber, blue, red in that order. One topic described a constant green and a flashing blue as a wait for EULA confirmation. Any sources on this topic or a guess to what I described could mean?
  14. When I turn wlan0 on the blue led stay's on, is this intended? With wlan1 on there is no light ? I thought the blue on was an indicator of the flash process?
  15. Ok, when the duck is in it's case, you can't see the LED - meh. Anyway - does anyone know how to add another one? Is it possible to attach one to the connections at the bottom of the duck? Thanks.
  16. Hi since the upgrade to 2.0.0 i have some strange or diferent combinations in my leds. First i see red led with green led. Next to that i see green led and blue blinking (startup) When the startup finish i have always the blue, orange and green led (blue and orange blink each 4 seconds, or other times like 5 seconds, or 2 seconds, isnt a regular blinking) In the instructions have the solid red in the startup means md5sum mismach, or bad upgraded files... so i decided to flash it: 1. I follow this steps: https://wifipineapple.com/?flashing (yeah, the MD5 hash , its the same) 2. in the first reboot i still see the red led on the startup of the machine with the green led, before the normal combinations leds of the startup. 3. I get the SD and make in my computer a partition to SWAP, and other in EXT4 (maybe bad files on SD) 4. Flash it again, same issue 5. I upgrade to 2.0.2 and still same issue Now i can "use it" (not sure what can be go bad) but i feel that the pineapple go very very very very slow, and always i have 3 leds ON: blue, orange, green. Thanks for read
  17. LAN and WAN leds don't work. I know this is a known problem, but just wanted to register it here for the record :P
  18. I've had my Mark IV for about a week now, it's become slow to start, and now the only Led that stays on is the pwr one and the WPS just blinks, It functions but the leds just don't show when I have something in usb or any of the other plug ins. I currently have 2.6.3 running on it did they burn out or is this just a software issue?
×
×
  • Create New...