Search the Community

Ok so i wanted to upgrade to firmware 1.3. That didnt work well. The bunny starts to flash the LED red->blue. as intended. Then the LED shuts off. No LED. I tried to boot it 3 times to trigger recovery. It then starts the flash red -> blue. After some time it comes a green LED and then it starts the red -> blue blinking again. After that a green LED and then it goes dark again. If i unplug it and plugs it back in, the green LED is solid for a sec and then ...wait for it...... DARK again. What a fun bunny, i might carry it out in the woods and leave it there :..( It also gets burning hot. I cannot accsess the files either. Maybe there is a way i dont know about? Its this BB dead now? 100 dollars out the window i guess

Im having some issues updating the bash bunny to the most recent firmware. I am currently on the base firmware from when I have purchased the device and have run apt-get update && apt-get upgrade after getting internet with my linux machine. I then download the firmware .tar file from the downloads area and copy the file to the / directory of the bash bunny. I then safely eject the device in arming mode and plug it back in expecting to see a red blinking light. Unfortunately it does nothing and boots to the regular storage mode and nothing has changed. I have searched the forums for help but I can't seem to figure out why this is happening. Can someone help me out with this issue?

I'm trying to upgrade my firmware of this yard stick one. But I keep getting different errors. Now I have the bad address one. root@raspberrypi3:/home/pi/rfcat_170508# rfcat_bootloader /dev/RFCAT_BL_YS1 erase_all RC = 0 (OK) root@raspberrypi3:/home/pi/rfcat_170508# rfcat_bootloader /dev/RFCAT_BL_YS1 download firmware/CCBootloader/CCBootloader-rfcat-ys1.hex Writing :0600000002017B02140363 RC = 3 (Bad Address) Error downloading code!

UPGRADE TO THE LATEST FIRMWARE Download the latest version of the Bash Bunny firmware from https://bashbunny.com/downloads Verify that the SHA256 checksum of the downloaded firmware files matches the checksum listed at bashbunny.com Slide the Bash Bunny switch into Arming Mode (closest to the USB plug) and plug the Bash Bunny into your computer Copy the firmware upgrade file downloaded in step 1 to the root of the Bash Bunny flash drive. Safely eject the Bash Bunny flash drive (IMPORTANT) With the switch still in Arming Mode, plug the Bash Bunny back into your computer and wait 10 minutes. When the bunny is done flashing, it will pop up as an storage device. INSTALLING LANGUAGES i have opened a pull request on the official repo to add the languages to the /languages folder (.json provided/made by ducktoolkit.com) But for now you will have to manually add them (Atleast from what i understand since i cannot get the ducktoolkit install payload to work) Download the Ducktoolkit compressed file-> https://github.com/hak5/bashbunny-payloads/raw/53a9e7fb69677b0480b2005a590471f4feacd180/payloads/library/DuckyInstall/DuckToolkit-1.0.1.tar.gz Unzip all the .json language files from "\DuckToolkit-1.0.1\ducktoolkit\languages" inside the .tar.gz file to\languages on the BashBunny (Connected while in arming mode) Remove and re-attach the bash bunny, you can now use different keyboard languages INSTALLING "IMPACKET" AND OTHER DEPENDENCIES There are 2 tools folders on the bash bunny itself, one lives in /tools on the Linux file-system which you can see and access using SSH/ Serial access.The other one lives in the mounted drive which you see every-time you connected the bunny as an storage device. What we effectively are going to do is to download the latest impacket source from github, place it on the bash bunny flash-mounted tools folder. re-attach and re-boot the bunny , this will copy the folder into the linux file-system tools folder, where we will install the module. Clone or download -> https://github.com/CoreSecurity/impacket as an .zip file. Unzip the "impacket-master" folder inside the .zip file into the /tools folder while the bash bunny is connected as an storage device (in arm mode) Rename the "impacket-master" folder to "impacket" ( remove and re-attach /reboot the bash bunny on the system. If you go to the same /tools folder now, the "impacket" folder should be gone. Serial/SSH into the bunny so you get a shell. and execute the following commands, in this order "cd" | "cd .." | " cd /tools/impacket/" | "python setup.py install" ( "|" separate each command, dont type the " quotes) remove and re-attach the bash bunny, and you are all good ! :)

Hi Ya'll, This is my first post on the Hak Forums. So, I'm in a bit of a panic. I finally cracked open my launch day firmware versioned BashBunny. I grabbed the latest firmware from the site, dropped it into the root directory of the BashBunny, and safely ejected. Then I plugged it back in to my computer. The light went green, then almost immediately started flashing red. I thought everything was good, but then after a while, the LED changed to solid red. It's been like that for 30 minutes, and I'm very scared that somehow my new $100 tool got bricked for no reason. Please please someone help soon. I need to sleep, but I can't leave the Bunny powered at the same time. Thanks, -NR

Apparently I've tried to update to 1.1 incorrectly. It has a solid green on startup then it turns blank. After three times it goes into recovery mode I am assuming. Then once there it blinks red for a while. Then it turns blank again. I've waited ten minutes tried to replug it in assuming something went wrong it it was done. But it never blinks or goes solid green or blue after the red blinking. But just now It was blinking red then started to alternate red to blue. Now it's blank again, I will wait another fifteen minutes before I try anything else. What exactly is going on? I am assuming it's either trying to recover then flash. I moved the upgrade contents to the root file system. I don't know exactly what went wrong. Easier way to understand the problem: Plug In > Solid Green > Blank LED ........ Ten minutes has passed.... Replug In > Solid Green > Blank LED ....... Ten minutes has passed.... Replug In > Solid Green Blank LED ...... Ten minutes has passed.... Replug In > Blinking Red > Couple of Minutes Passed > Blinking Red . Blinking Blue . Blinking Red > Couple of Minutes Passed > Blinking Red > Couple of Minutes Passed > BLANK LED!!!! Ten minutes has passed... Replug In > Solid Green > Blank LED Every time it tries to recover then it will try to boot three times and try to recover again. It will never fully boot up nor will Kali recognize the file system or that it's plugged in.

So, I've made a payload to upgrade the bash bunny to allow for switching on the fly. I'm not posting it yet, because it seems that the PRs are piling up and don't want it lost in the shuffle. i currently have it so that it runs the payload on the switch you switch it to, but feel it could eventually be used to register commands to the script. Would anyone find this useful? Any ideas on other uses detecting the switches could do?

So after the latest episode of Hak5, you mentioned 1.1 was ready to ship. When will this be available, and is there a new feature list?? You guys are awesome for pumping this out so quickly. I'm super excited.

Hello I have built a usb rubber with at32uc3b1256. but it does not work. when I plug it in to my computer, I receive this error :"A request for the USB device descriptor failed". could anyone tell me, what I should do? thanks. I've used a 12 MHz crystal. this is the conf_clock file: /** * \file * * \brief Chip-specific system clock manager configuration * * Copyright (c) 2011 Atmel Corporation. All rights reserved. * * \asf_license_start * * Redistribution and use in source and binary forms, with or without * modification, are permitted provided that the following conditions are met: * * 1. Redistributions of source code must retain the above copyright notice, this * list of conditions and the following disclaimer. * * 2. Redistributions in binary form must reproduce the above copyright notice, * this list of conditions and the following disclaimer in the documentation * and/or other materials provided with the distribution. * * 3. The name of Atmel may not be used to endorse or promote products derived * from this software without specific prior written permission. * * 4. This software may only be redistributed and used in connection with an Atmel * AVR product. * * THIS SOFTWARE IS PROVIDED BY ATMEL "AS IS" AND ANY EXPRESS OR IMPLIED * WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF * MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT ARE * EXPRESSLY AND SPECIFICALLY DISCLAIMED. IN NO EVENT SHALL ATMEL BE LIABLE FOR * ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES * (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; * LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND * ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT * (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS * SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. * * \asf_license_stop * */ #ifndef CONF_CLOCK_H_INCLUDED #define CONF_CLOCK_H_INCLUDED // ===== System Clock Source Options //#define CONFIG_SYSCLK_SOURCE SYSCLK_SRC_RCSYS //#define CONFIG_SYSCLK_SOURCE SYSCLK_SRC_OSC0 #define CONFIG_SYSCLK_SOURCE SYSCLK_SRC_PLL0 // ===== PLL0 Options #define CONFIG_PLL0_SOURCE PLL_SRC_OSC0 //#define CONFIG_PLL0_SOURCE PLL_SRC_OSC1 #define CONFIG_PLL0_MUL 2 /* Fpll = (Fclk * PLL_mul) / PLL_div */ #define CONFIG_PLL0_DIV 2 /* Fpll = (Fclk * PLL_mul) / PLL_div */ // ===== PLL1 Options #define CONFIG_PLL1_SOURCE PLL_SRC_OSC0 //#define CONFIG_PLL1_SOURCE PLL_SRC_OSC1 #define CONFIG_PLL1_MUL 8 /* Fpll = (Fclk * PLL_mul) / PLL_div */ #define CONFIG_PLL1_DIV 2 /* Fpll = (Fclk * PLL_mul) / PLL_div */ // ===== System Clock Bus Division Options //#define CONFIG_SYSCLK_CPU_DIV 1 /* Fcpu = Fsys/(2 ^ CPU_div) */ //#define CONFIG_SYSCLK_PBA_DIV 1 /* Fpba = Fsys/(2 ^ PBA_div) */ //#define CONFIG_SYSCLK_PBB_DIV 1 /* Fpbb = Fsys/(2 ^ PBB_div) */ // ===== Peripheral Clock Management Options //#define CONFIG_SYSCLK_INIT_CPUMASK ((1 << SYSCLK_SYSTIMER) | (1 << SYSCLK_OCD)) //#define CONFIG_SYSCLK_INIT_PBAMASK (1 << SYSCLK_USART0) //#define CONFIG_SYSCLK_INIT_PBBMASK (1 << SYSCLK_HMATRIX) //#define CONFIG_SYSCLK_INIT_HSBMASK (1 << SYSCLK_MDMA_HSB) // ===== USB Clock Source Options //#define CONFIG_USBCLK_SOURCE USBCLK_SRC_OSC0 //#define CONFIG_USBCLK_SOURCE USBCLK_SRC_PLL0 #define CONFIG_USBCLK_SOURCE USBCLK_SRC_PLL1 #define CONFIG_USBCLK_DIV 1 /* Fusb = Fsys/(2 ^ USB_div) */ #endif /* CONF_CLOCK_H_INCLUDED */ and this is the conf_usb.h file: /** * \file * * \brief USB configuration file * * Copyright (c) 2009 Atmel Corporation. All rights reserved. * * \asf_license_start * * Redistribution and use in source and binary forms, with or without * modification, are permitted provided that the following conditions are met: * * 1. Redistributions of source code must retain the above copyright notice, this * list of conditions and the following disclaimer. * * 2. Redistributions in binary form must reproduce the above copyright notice, * this list of conditions and the following disclaimer in the documentation * and/or other materials provided with the distribution. * * 3. The name of Atmel may not be used to endorse or promote products derived * from this software without specific prior written permission. * * 4. This software may only be redistributed and used in connection with an Atmel * AVR product. * * THIS SOFTWARE IS PROVIDED BY ATMEL "AS IS" AND ANY EXPRESS OR IMPLIED * WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF * MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT ARE * EXPRESSLY AND SPECIFICALLY DISCLAIMED. IN NO EVENT SHALL ATMEL BE LIABLE FOR * ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES * (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; * LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND * ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT * (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS * SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. * * \asf_license_stop * */ #ifndef _CONF_USB_H_ #define _CONF_USB_H_ #include "compiler.h" /** * USB Device Configuration * @{ */ //! Device definition (mandatory) #define USB_DEVICE_VENDOR_ID USB_VID_ATMEL #define USB_DEVICE_PRODUCT_ID USB_PID_ATMEL_AVR_HIDKEYBOARD #define USB_DEVICE_MAJOR_VERSION 1 #define USB_DEVICE_MINOR_VERSION 0 #define USB_DEVICE_POWER 100 // Consumption on Vbus line (mA) #define USB_DEVICE_ATTR \ (USB_CONFIG_ATTR_REMOTE_WAKEUP|USB_CONFIG_ATTR_SELF_POWERED) // (USB_CONFIG_ATTR_REMOTE_WAKEUP|USB_CONFIG_ATTR_BUS_POWERED) // (USB_CONFIG_ATTR_SELF_POWERED) // (USB_CONFIG_ATTR_BUS_POWERED) //! USB Device string definitions (Optional) #define USB_DEVICE_MANUFACTURE_NAME "ALVAND" #define USB_DEVICE_PRODUCT_NAME "HAMEDAN" // #define USB_DEVICE_SERIAL_NAME "12...EF" /** * Device speeds support * @{ */ //! To define a Low speed device //#define USB_DEVICE_LOW_SPEED //! To authorize the High speed #if (UC3A3||UC3A4) //#define USB_DEVICE_HS_SUPPORT #endif //@} /** * USB Device Callbacks definitions (Optional) * @{ */ #define UDC_VBUS_EVENT(b_vbus_high) main_vbus_action(b_vbus_high) #define UDC_SOF_EVENT() main_sof_action() #define UDC_SUSPEND_EVENT() main_suspend_action() #define UDC_RESUME_EVENT() main_resume_action() //! Mandatory when USB_DEVICE_ATTR authorizes remote wakeup feature #define UDC_REMOTEWAKEUP_ENABLE() main_remotewakeup_enable() #define UDC_REMOTEWAKEUP_DISABLE() main_remotewakeup_disable() //! When a extra string descriptor must be supported //! other than manufacturer, product and serial string // #define UDC_GET_EXTRA_STRING() //@} //@} /** * USB Interface Configuration * @{ */ /** * Configuration of HID Keyboard interface * @{ */ //! Interface callback definition #define UDI_HID_KBD_ENABLE_EXT() main_kbd_enable() #define UDI_HID_KBD_DISABLE_EXT() main_kbd_disable() #define UDI_HID_KBD_CHANGE_LED(value) ui_kbd_led(value) //@} //@} /** * USB Device Driver Configuration * @{ */ //@} //! The includes of classes and other headers must be done at the end of this file to avoid compile error #include "udi_hid_kbd_conf.h" #include "main.h" #include "ui.h" #endif // _CONF_USB_H_ and this is my main.c file: /** * \file * * \brief Main functions for Keyboard example * * Copyright (c) 2009-2011 Atmel Corporation. All rights reserved. * * \asf_license_start * * Redistribution and use in source and binary forms, with or without * modification, are permitted provided that the following conditions are met: * * 1. Redistributions of source code must retain the above copyright notice, this * list of conditions and the following disclaimer. * * 2. Redistributions in binary form must reproduce the above copyright notice, * this list of conditions and the following disclaimer in the documentation * and/or other materials provided with the distribution. * * 3. The name of Atmel may not be used to endorse or promote products derived * from this software without specific prior written permission. * * 4. This software may only be redistributed and used in connection with an Atmel * AVR product. * * THIS SOFTWARE IS PROVIDED BY ATMEL "AS IS" AND ANY EXPRESS OR IMPLIED * WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF * MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT ARE * EXPRESSLY AND SPECIFICALLY DISCLAIMED. IN NO EVENT SHALL ATMEL BE LIABLE FOR * ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES * (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; * LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND * ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT * (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS * SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. * * \asf_license_stop * */ #include "compiler.h" #include "preprocessor.h" #include "board.h" #include "gpio.h" #include "sysclk.h" #include "sleepmgr.h" #include "conf_usb.h" #include "udc.h" #include "udd.h" #include "ui.h" //volatile static bool main_b_kbd_enable = false; volatile static bool main_b_kbd_enable = true; /*! \brief Main function. Execution starts here. */ int main(void) { irq_initialize_vectors(); cpu_irq_enable(); // Initialize the sleep manager sleepmgr_init(); sysclk_init(); board_init(); ui_init(); ui_powerdown(); ui_wakeup_enable(); volatile uint32_t freq = sysclk_get_cpu_hz(); freq ++; LED_Toggle(LED3); // Start USB stack to authorize VBus monitoring udc_start(); //udc_attach(); if (!udc_include_vbus_monitoring()) { // VBUS monitoring is not available on this product // thereby VBUS has to be considered as present main_vbus_action(true); } // The main loop manages only the power mode // because the USB management is done by interrupt while (true) { #ifdef USB_DEVICE_LOW_SPEED // No USB "Keep a live" interrupt available in low speed // to scan keyboard interface then use main loop if (main_b_kbd_enable) { static uint16_t virtual_sof_sub = 0; if (700 == virtual_sof_sub++) { virtual_sof_sub = 0; static uint16_t virtual_sof = 0; ui_process(virtual_sof++); } } #else sleepmgr_enter_sleep(); #endif } } void main_vbus_action(bool b_high) { //if (b_high) { // Attach USB Device udc_attach(); //} else { // VBUS not present //udc_detach(); //} } void main_suspend_action(void) { ui_powerdown(); } void main_resume_action(void) { ui_wakeup(); } void main_sof_action(void) { if (!main_b_kbd_enable) return; ui_process(udd_get_frame_number()); } void main_remotewakeup_enable(void) { ui_wakeup_enable(); } void main_remotewakeup_disable(void) { ui_wakeup_disable(); } bool main_kbd_enable(void) { main_b_kbd_enable = true; return true; } void main_kbd_disable(void) { main_b_kbd_enable = false; } /** * \mainpage ASF USB Device HID Keyboard * * \section intro Introduction * This example shows how to implement a USB Device HID Keyboard * on Atmel MCU with USB module. * The application note AVR4903 provides information about this implementation. * * \section startup Startup * The example uses the buttons or sensors available on the board * to simulate a standard keyboard. * After loading firmware, connect the board (EVKxx,XPlain,...) to the USB Host. * When connected to a USB host system this application provides a keyboard application * in the Unix/Mac/Windows operating systems. * This example uses the native HID driver for these operating systems. * * \copydoc UI * * \section example About example * * The example uses the following module groups: * - Basic modules: * Startup, board, clock, interrupt, power management * - USB Device stack and HID modules: * <br>services/usb/ * <br>services/usb/udc/ * <br>services/usb/class/hid/ * <br>services/usb/class/hid/keyboard/ * - Specific implementation: * - main.c, * <br>initializes clock * <br>initializes interrupt * <br>manages UI * - specific implementation for each target "./examples/product_board/": * - conf_foo.h configuration of each module * - ui.c implement of user's interface (buttons, leds) */

Hi all, Would you be able to tell me how I can send Notifications on the Notifications tile on the Dashboard page of the Pineapple firmware.? Many thanks

Hi, i am trying to run different payloads on different keypresses(capslock, numlock); I would usually go for the Naked Duck way but I am trying to run different batch files depending on what key is pressed(and for that I need the mass storage to be loaded). Is there any way to combine these things? Or any way to run different batch files stored on the ducky at different keypresses?

Hey there, guys. Got my ducky in the mail today, and I'd love to get started, but I can't get the damn thing to work for the life of me. I accidentally deleted the inject.bin, and cannot find a single copy of it online. I figured this might be remedied by updating the firmware, but it wasn't (I used duck_v2.1.hex, the tutorial didn't say which of the 19 in \images\ to use). Plugging it in yields a red light. Just not sure how to proceed.

Ok so let me preface this with an apology in case my google fu has failed me. I've had a ducky for about a week now and have to be able to flash new firmware to it. I know you have to push the button during insertion to enter dfu mode. I have tried on a mac, windows 10 VM, and a kali box and have to get it. Nothing even seems to see it... Is there a way to verify dfu mode? Im hoping its not a faulty pin. Any help is greatly appreciated!!

running windows 10 with nano tethered, am getting bulletins and the firmware search found the new version however it sits. have attempted almost 10 times to get it to load.

Hello All, I've continuously racked my brain on this today and repeatedly come up with the same error, perhaps someone can assist. I've tried this on two different Win7 x64 devices. I feel I've done everything mentioned in the tutorials available here but I know I'm missing something as this isn't working. My error occurs, and I've seen it on Darren's Git Page, Flashing Ducky, but the I haven't found the information there to help my case. I error out at the Opening Port stage with a ATLibUsbDfu: 3EB 2FF6 no device present - FAIL Could not open device. I feel some of the guides are incomplete, leaving pieces out that I notice people claim to work in various comments. For instance: Inside the x86 folder of the Atmel Signed Driver is the .sys and .dll, through comments I get the understanding that I'm supposed to rename one of these files then drop them into my syswow64 folder, but the [Tutorial] by Nick mentions none of this. Also, Nick's post and a post by Enjoy0001 slightly contradict themselves in a couple of areas. In Nick's guide, there's no mention at all of dropping the program.bat along with .hex file into the Atmel\Flip 3.4.2\bin folder but it appears that needs to be done to complete the next operation, and per Enjoy0001's he drops the two files into the directory before bin, Atmel\Flip\ 3.4.2. I've tried placing the files in both directories with no luck. I've tried saving the .sys and .dll to both my syswow64 drivers folder and my system32 drivers folder. Do I need to be copying/moving these files at all? Darren's resource explains this is a driver problem and it's resolved by pointing the driver location to the atmel driver folder manually. I believe I've done this but perhaps I'm not doing it correctly as it's not helped yet. In order to download the Atmel driver I had to take this process: I'd like to note that loading the Ducky into my PC while holding the button does not prompt a wizard as some say it does on occasion. My Process on Win7 Ent. x64: Device Manager > Right click at the top > Add legacy Hardware > Show All Devices > Have Disk > Point to Atmel > toggle atmel_flip.inf > toggle AT32UC3B > Install Finishes Is my process of driver pointing incorrect? After performing these steps as instructed in Darren's post, I get the same error: Load Device manager, Find Atmel USB Device(Shows Atmel USB Devices in Device Manager not DFU Device), Update driver, Manual Install, Point windows to Atmel unzipped. C++ Redist and Flip are installed on the devices. Firmware file: c_duck_v2.1.hex Guide in mention by Nick: Guide in mention by Enjoy0001: I feel I did my due diligence of crawling these forums and YT for resolve to this error before posting but I've had no luck. Thanks for any input. If I can provide any additional information, I'll see to it immediately. I'll try this firmware flashing on a Linux device and a Windows 10 device later tonight. I'll report back with the outcome, but either way it'd be nice to solidify this process on a windows device.

Looks like a new release will be coming out soon, but even more exciting is the MITMf integration that is on the cards (Unless this is going to be in the next release!). MITMf will replace some of the infusions we have come to love and hate, and replace them with a one stop shop framework. This will hopefully solve some of the issues we were having running multiple infusions impacting the network. Now we will have the best of hardware and software MITM in one sweet pineapple! Some functionality may not make it due to being CPU intensive (FilePwn), regardless, this is going to be a giant leap! MITMf V0.9.5 Framework for Man-In-The-Middle attacks Availible plugins Responder - LLMNR, NBT-NS and MDNS poisoner SSLstrip+ - Partially bypass HSTS Spoof - Redirect traffic using ARP Spoofing, ICMP Redirects or DHCP Spoofing and modify DNS queries Sniffer - Sniffs for various protocol login and auth attempts BeEFAutorun - Autoruns BeEF modules based on clients OS or browser type AppCachePoison - Perform app cache poison attacks SessionHijacking - Performs session hijacking attacks, and stores cookies in a firefox profile BrowserProfiler - Attempts to enumerate all browser plugins of connected clients CacheKill - Kills page caching by modifying headers FilePwn - Backdoor executables being sent over http using bdfactory Inject - Inject arbitrary content into HTML content JavaPwn - Performs drive-by attacks on clients with out-of-date java browser plugins jskeylogger - Injects a javascript keylogger into clients webpages Replace - Replace arbitary content in HTML content SMBAuth - Evoke SMB challenge-response auth attempts Upsidedownternet - Flips images 180 degrees Changelog Addition of the Sniffer plugin which integrates Net-Creds currently supported protocols are: FTP, IRC, POP, IMAP, Telnet, SMTP, SNMP (community strings), NTLMv1/v2 (all supported protocols like HTTP, SMB, LDAP etc..) and Kerberos Integrated Responder to poison LLMNR, NBT-NS and MDNS, and act as a WPAD rogue server. Integrated SSLstrip+ by Leonardo Nve to partially bypass HSTS as demonstrated at BlackHat Asia 2014 Addition of the SessionHijacking plugin, which uses code from FireLamb to store cookies in a Firefox profile Spoof plugin now supports ICMP, ARP and DHCP spoofing along with DNS tampering Spoof plugin can now exploit the 'ShellShock' bug when DHCP spoofing! Usage of third party tools has been completely removed (e.g. ettercap) FilePwn plugin re-written to backdoor executables and zip files on the fly by using the-backdoor-factory and code from BDFProxy Added msfrpc.py for interfacing with Metasploits rpc server Added beefapi.py for interfacing with BeEF's RESTfulAPI Addition of the app-cache poisoning attack by Krzysztof Kotowicz (blogpost explaining the attack here http://blog.kotowicz.net/2010/12/squid-imposter-phishing-websites.html) Links: https://twitter.com/hak5darren/status/585168796739964928 https://twitter.com/sebkinne/status/585550844260700162 https://github.com/byt3bl33d3r/MITMf/

Hello, is there a way to convert AP121U with Pineapple firmware back to original Alfa firmware? Thanks.

I love this little thing, I've had it for less than a week and I've learned a lot already. Sadly, my WLAN0 has gone missing from my WIFI Client dropdown menu under Networking. I can see that it exsists under the Advanced Menu, I can also change it's MAC address. I was using an AWUS036H, a tiny Edimax Dongle and/or the tiny dongle sold by Hakshop testing out range for about an hour. I turned it off via the GUI, came back to it a few hours later and I was wlan0-less. I wish I knew more about the UNIX commands but I don't at the moment. Somewhere in one of the logs, I believe I saw something that seemed the firmware for one of the dongles had replaced the wlan0 firmware. I'm not sure but I sure do miss it. I get paranoid when powerful little tools act funky. Could you glance over these logs and tell me if something nefarious is going on? I've reset it hard and soft, flashed the firmware and updated it all in different order several times. The logs change slightly from here to there but I can't tell what it all means exactly. Here are the logs from this morning (5am is) DMESG AFTER REFLASHING FIRMWARE: [ 0.000000] Linux version 3.18.23 (sebkinne@Worker) (gcc version 4.8.3 (OpenWrt/Linaro GCC 4.8-2014.04 r46591) ) #13 Thu Jan 21 13:34:28 PST 2016 [ 0.000000] MyLoader: sysp=8a14b024, boardp=44b65156, parts=b69f8d32 [ 0.000000] bootconsole [early0] enabled [ 0.000000] CPU0 revision is: 00019374 (MIPS 24Kc) [ 0.000000] SoC: Atheros AR9330 rev 1 [ 0.000000] Determined physical RAM map: [ 0.000000] memory: 04000000 @ 00000000 (usable) [ 0.000000] Initrd not found or empty - disabling initrd [ 0.000000] Zone ranges: [ 0.000000] Normal [mem 0x00000000-0x03ffffff] [ 0.000000] Movable zone start for each node [ 0.000000] Early memory node ranges [ 0.000000] node 0: [mem 0x00000000-0x03ffffff] [ 0.000000] Initmem setup node 0 [mem 0x00000000-0x03ffffff] [ 0.000000] On node 0 totalpages: 16384 [ 0.000000] free_area_init_node: node 0, pgdat 80355cf0, node_mem_map 81000000 [ 0.000000] Normal zone: 128 pages used for memmap [ 0.000000] Normal zone: 0 pages reserved [ 0.000000] Normal zone: 16384 pages, LIFO batch:3 [ 0.000000] Primary instruction cache 64kB, VIPT, 4-way, linesize 32 bytes. [ 0.000000] Primary data cache 32kB, 4-way, VIPT, cache aliases, linesize 32 bytes [ 0.000000] pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768 [ 0.000000] pcpu-alloc: [0] 0 [ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 16256 [ 0.000000] Kernel command line: board=PINEAPPLE-NANO console=ttyATH0,115200 rootfstype=squashfs,jffs2 noinitrd [ 0.000000] PID hash table entries: 256 (order: -2, 1024 bytes) [ 0.000000] Dentry cache hash table entries: 8192 (order: 3, 32768 bytes) [ 0.000000] Inode-cache hash table entries: 4096 (order: 2, 16384 bytes) [ 0.000000] Writing ErrCtl register=00000000 [ 0.000000] Readback ErrCtl register=00000000 [ 0.000000] Memory: 60944K/65536K available (2465K kernel code, 128K rwdata, 528K rodata, 260K init, 188K bss, 4592K reserved) [ 0.000000] SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1 [ 0.000000] NR_IRQS:51 [ 0.000000] Clocks: CPU:400.000MHz, DDR:400.000MHz, AHB:200.000MHz, Ref:25.000MHz [ 0.000000] Calibrating delay loop... 265.42 BogoMIPS (lpj=1327104) [ 0.080000] pid_max: default: 32768 minimum: 301 [ 0.080000] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes) [ 0.090000] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes) [ 0.100000] NET: Registered protocol family 16 [ 0.100000] MIPS: machine is WiFi Pineapple NANO [ 0.380000] Switched to clocksource MIPS [ 0.380000] NET: Registered protocol family 2 [ 0.390000] TCP established hash table entries: 1024 (order: 0, 4096 bytes) [ 0.390000] TCP bind hash table entries: 1024 (order: 0, 4096 bytes) [ 0.400000] TCP: Hash tables configured (established 1024 bind 1024) [ 0.400000] TCP: reno registered [ 0.410000] UDP hash table entries: 256 (order: 0, 4096 bytes) [ 0.410000] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes) [ 0.420000] NET: Registered protocol family 1 [ 0.420000] PCI: CLS 0 bytes, default 32 [ 0.420000] futex hash table entries: 256 (order: -1, 3072 bytes) [ 0.440000] squashfs: version 4.0 (2009/01/31) Phillip Lougher [ 0.440000] jffs2: version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME) (CMODE_PRIORITY) (c) 2001-2006 Red Hat, Inc. [ 0.450000] msgmni has been set to 119 [ 0.460000] io scheduler noop registered [ 0.460000] io scheduler deadline registered (default) [ 0.470000] Serial: 8250/16550 driver, 1 ports, IRQ sharing disabled [ 0.470000] ar933x-uart: ttyATH0 at MMIO 0x18020000 (irq = 11, base_baud = 1562500) is a AR933X UART [ 0.480000] console [ttyATH0] enabled [ 0.490000] bootconsole [early0] disabled [ 0.500000] m25p80 spi0.0: found mx25l12805d, expected m25p80 [ 0.500000] m25p80 spi0.0: mx25l12805d (16384 Kbytes) [ 0.510000] 5 tp-link partitions found on MTD device spi0.0 [ 0.510000] Creating 5 MTD partitions on "spi0.0": [ 0.520000] 0x000000000000-0x000000020000 : "u-boot" [ 0.520000] 0x000000020000-0x000000134994 : "kernel" [ 0.530000] 0x000000134994-0x000000ff0000 : "rootfs" [ 0.530000] mtd: device 2 (rootfs) set to be root filesystem [ 0.540000] 1 squashfs-split partitions found on MTD device rootfs [ 0.540000] 0x000000db0000-0x000000ff0000 : "rootfs_data" [ 0.550000] 0x000000ff0000-0x000001000000 : "art" [ 0.560000] 0x000000020000-0x000000ff0000 : "firmware" [ 0.590000] libphy: ag71xx_mdio: probed [ 1.190000] ag71xx ag71xx.0: connected to PHY at ag71xx-mdio.1:04 [uid=004dd041, driver=Generic PHY] [ 1.200000] eth0: Atheros AG71xx at 0xb9000000, irq 4, mode:MII [ 1.200000] TCP: cubic registered [ 1.200000] NET: Registered protocol family 17 [ 1.210000] bridge: automatic filtering via arp/ip/ip6tables has been deprecated. Update your scripts to load br_netfilter if you need this. [ 1.220000] 8021q: 802.1Q VLAN Support v1.8 [ 1.230000] VFS: Mounted root (squashfs filesystem) readonly on device 31:2. [ 1.240000] Freeing unused kernel memory: 260K (8036f000 - 803b0000) [ 2.640000] init: Console is alive [ 2.640000] init: - watchdog - [ 5.280000] usbcore: registered new interface driver usbfs [ 5.290000] usbcore: registered new interface driver hub [ 5.290000] usbcore: registered new device driver usb [ 5.350000] SCSI subsystem initialized [ 5.360000] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [ 5.370000] ehci-platform: EHCI generic platform driver [ 5.370000] ehci-platform ehci-platform: EHCI Host Controller [ 5.380000] ehci-platform ehci-platform: new USB bus registered, assigned bus number 1 [ 5.390000] ehci-platform ehci-platform: irq 3, io mem 0x1b000000 [ 5.410000] ehci-platform ehci-platform: USB 2.0 started, EHCI 1.00 [ 5.410000] hub 1-0:1.0: USB hub found [ 5.410000] hub 1-0:1.0: 1 port detected [ 5.420000] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver [ 5.430000] ohci-platform: OHCI generic platform driver [ 5.440000] uhci_hcd: USB Universal Host Controller Interface driver [ 5.450000] usbcore: registered new interface driver usb-storage [ 5.740000] usb 1-1: new high-speed USB device number 2 using ehci-platform [ 5.780000] init: - preinit - [ 6.070000] hub 1-1:1.0: USB hub found [ 6.070000] hub 1-1:1.0: 4 ports detected [ 6.440000] usb 1-1.1: new high-speed USB device number 3 using ehci-platform [ 6.670000] random: procd urandom read with 11 bits of entropy available [ 6.810000] mount_root: loading kmods from internal overlay [ 7.070000] usb 1-1.2: new high-speed USB device number 4 using ehci-platform [ 7.110000] block: attempting to load /etc/config/fstab [ 7.230000] block: extroot: not configured [ 7.230000] mount_root: jffs2 not ready yet, using temporary tmpfs overlay [ 7.280000] usb-storage 1-1.2:1.0: USB Mass Storage device detected [ 7.280000] scsi host0: usb-storage 1-1.2:1.0 [ 7.310000] procd: - early - [ 7.310000] procd: - watchdog - [ 8.230000] procd: - ubus - [ 8.430000] scsi 0:0:0:0: Direct-Access Generic STORAGE DEVICE 0933 PQ: 0 ANSI: 6 [ 8.540000] sd 0:0:0:0: [sda] Attached SCSI removable disk [ 9.260000] procd: - init - [ 13.420000] Loading modules backported from Linux version master-2015-03-09-0-g141f155 [ 13.430000] Backport generated by backports.git backports-20150129-0-gdd4a670 [ 13.470000] cfg80211: Calling CRDA to update world regulatory domain [ 13.490000] cfg80211: World regulatory domain updated: [ 13.490000] cfg80211: DFS Master region: unset [ 13.490000] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time) [ 13.500000] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A) [ 13.510000] cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz, 92000 KHz AUTO), (N/A, 2000 mBm), (N/A) [ 13.520000] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm), (N/A) [ 13.530000] cfg80211: (5170000 KHz - 5250000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (N/A) [ 13.540000] cfg80211: (5250000 KHz - 5330000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (0 s) [ 13.550000] cfg80211: (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s) [ 13.560000] cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A) [ 13.560000] cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A) [ 13.700000] ath: EEPROM regdomain: 0x0 [ 13.700000] ath: EEPROM indicates default country code should be used [ 13.700000] ath: doing EEPROM country->regdmn map search [ 13.700000] ath: country maps to regdmn code: 0x3a [ 13.700000] ath: Country alpha2 being used: US [ 13.700000] ath: Regpair used: 0x3a [ 13.710000] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht' [ 13.710000] ieee80211 phy0: Atheros AR9330 Rev:1 mem=0xb8100000, irq=2 [ 13.730000] usb 1-1.1: ath9k_htc: Firmware htc_9271.fw requested [ 13.740000] usbcore: registered new interface driver ath9k_htc [ 13.790000] cfg80211: Calling CRDA for country: US [ 13.810000] cfg80211: Regulatory domain changed to country: US [ 13.810000] cfg80211: DFS Master region: FCC [ 13.810000] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time) [ 13.820000] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 3000 mBm), (N/A) [ 13.830000] cfg80211: (5170000 KHz - 5250000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2300 mBm), (N/A) [ 13.840000] cfg80211: (5250000 KHz - 5330000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2300 mBm), (0 s) [ 13.850000] cfg80211: (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, 2300 mBm), (0 s) [ 13.860000] cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 3000 mBm), (N/A) [ 13.870000] cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 4000 mBm), (N/A) [ 13.880000] RPC: Registered named UNIX socket transport module. [ 13.880000] RPC: Registered udp transport module. [ 13.890000] RPC: Registered tcp transport module. [ 13.890000] RPC: Registered tcp NFSv4.1 backchannel transport module. [ 13.930000] tun: Universal TUN/TAP device driver, 1.6 [ 13.930000] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com> [ 13.990000] usbcore: registered new interface driver rt2800usb [ 14.000000] usbcore: registered new interface driver rtl8187 [ 14.050000] usbcore: registered new interface driver rtl8192cu [ 14.080000] sd 0:0:0:0: Attached scsi generic sg0 type 0 [ 14.100000] usbcore: registered new interface driver cdc_acm [ 14.100000] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters [ 14.140000] usbcore: registered new interface driver cdc_wdm [ 14.170000] nf_conntrack version 0.5.0 (956 buckets, 3824 max) [ 14.190000] usb 1-1.1: ath9k_htc: Transferred FW: htc_9271.fw, size: 50980 [ 14.240000] usbcore: registered new interface driver ums-alauda [ 14.250000] usbcore: registered new interface driver ums-cypress [ 14.260000] usbcore: registered new interface driver ums-datafab [ 14.260000] usbcore: registered new interface driver ums-freecom [ 14.270000] usbcore: registered new interface driver ums-isd200 [ 14.290000] usbcore: registered new interface driver ums-jumpshot [ 14.310000] usbcore: registered new interface driver ums-karma [ 14.320000] usbcore: registered new interface driver ums-sddr09 [ 14.320000] usbcore: registered new interface driver ums-sddr55 [ 14.330000] usbcore: registered new interface driver ums-usbat [ 14.360000] usbcore: registered new interface driver usbserial [ 14.370000] usbcore: registered new interface driver usbserial_generic [ 14.370000] usbserial: USB Serial support registered for generic [ 14.440000] xt_time: kernel timezone is -0000 [ 14.450000] usbcore: registered new interface driver asix [ 14.450000] usbcore: registered new interface driver cdc_ether [ 14.480000] ath9k_htc 1-1.1:1.0: ath9k_htc: HTC initialized with 33 credits [ 14.480000] ip_tables: (C) 2000-2006 Netfilter Core Team [ 14.530000] usbcore: registered new interface driver pl2303 [ 14.530000] usbserial: USB Serial support registered for pl2303 [ 14.540000] PPP generic driver version 2.4.2 [ 14.550000] NET: Registered protocol family 24 [ 14.560000] usbcore: registered new interface driver qmi_wwan [ 14.570000] usbcore: registered new interface driver rndis_host [ 14.580000] usbcore: registered new interface driver sierra_net [ 14.600000] usbcore: registered new interface driver option [ 14.600000] usbserial: USB Serial support registered for GSM modem (1-port) [ 17.090000] ath9k_htc 1-1.1:1.0: ath9k_htc: FW Version: 1.3 [ 17.090000] ath9k_htc 1-1.1:1.0: FW RMW support: Off [ 17.100000] ath: EEPROM regdomain: 0x0 [ 17.100000] ath: EEPROM indicates default country code should be used [ 17.100000] ath: doing EEPROM country->regdmn map search [ 17.100000] ath: country maps to regdmn code: 0x3a [ 17.100000] ath: Country alpha2 being used: US [ 17.100000] ath: Regpair used: 0x3a [ 17.120000] ieee80211 phy1: Atheros AR9271 Rev:1 [ 25.070000] device eth0 entered promiscuous mode [ 28.170000] eth0: link up (100Mbps/Full duplex) [ 28.320000] br-lan: port 1(eth0) entered forwarding state [ 28.320000] br-lan: port 1(eth0) entered forwarding state [ 30.080000] device wlan0 entered promiscuous mode [ 30.090000] br-lan: port 2(wlan0) entered forwarding state [ 30.090000] br-lan: port 2(wlan0) entered forwarding state [ 30.320000] br-lan: port 1(eth0) entered forwarding state [ 30.560000] eth0: link down [ 31.560000] br-lan: port 1(eth0) entered disabled state [ 32.090000] br-lan: port 2(wlan0) entered forwarding state [ 32.560000] eth0: link up (100Mbps/Full duplex) [ 32.560000] br-lan: port 1(eth0) entered forwarding state [ 32.570000] br-lan: port 1(eth0) entered forwarding state [ 34.570000] br-lan: port 1(eth0) entered forwarding state [ 48.420000] random: nonblocking pool is initialized [ 63.590000] jffs2_scan_eraseblock(): End of filesystem marker found at 0x0 [ 63.590000] jffs2_build_filesystem(): unlocking the mtd device... done. [ 63.600000] jffs2_build_filesystem(): erasing all blocks after the end marker... done. [ 73.340000] jffs2: notice: (1694) jffs2_build_xattr_subsystem: complete building xattr subsystem, 0 of xdatum (0 unchecked, 0 orphan) and 0 of xref (0 dead, 0 orphan) found. [ 74.950000] device wlan0 left promiscuous mode [ 74.960000] br-lan: port 2(wlan0) entered disabled state [ 77.130000] device wlan0 entered promiscuous mode [ 77.130000] br-lan: port 2(wlan0) entered forwarding state [ 77.140000] br-lan: port 2(wlan0) entered forwarding state [ 78.710000] usb-storage 1-1.2:1.0: USB Mass Storage device detected [ 78.720000] scsi host1: usb-storage 1-1.2:1.0 [ 79.140000] br-lan: port 2(wlan0) entered forwarding state [ 79.720000] scsi 1:0:0:0: Direct-Access Generic STORAGE DEVICE 0933 PQ: 0 ANSI: 6 [ 79.720000] sd 1:0:0:0: Attached scsi generic sg0 type 0 [ 79.770000] sd 1:0:0:0: [sda] Attached SCSI removable disk [ 86.470000] br-lan: port 2(wlan0) entered disabled state [ 86.730000] device wlan0 left promiscuous mode [ 86.740000] br-lan: port 2(wlan0) entered disabled state [ 86.780000] eth0: link down [ 87.470000] br-lan: port 1(eth0) entered disabled state [ 88.780000] eth0: link up (100Mbps/Full duplex) [ 88.780000] br-lan: port 1(eth0) entered forwarding state [ 88.790000] br-lan: port 1(eth0) entered forwarding state [ 90.790000] br-lan: port 1(eth0) entered forwarding state [ 232.940000] device wlan0 entered promiscuous mode [ 232.940000] br-lan: port 2(wlan0) entered forwarding state [ 232.950000] br-lan: port 2(wlan0) entered forwarding state [ 233.040000] device wlan0-1 entered promiscuous mode [ 233.050000] br-lan: port 3(wlan0-1) entered forwarding state [ 233.050000] br-lan: port 3(wlan0-1) entered forwarding state [ 233.570000] br-lan: port 3(wlan0-1) entered disabled state [ 233.770000] br-lan: port 3(wlan0-1) entered forwarding state [ 233.770000] br-lan: port 3(wlan0-1) entered forwarding state [ 234.950000] br-lan: port 2(wlan0) entered forwarding state [ 235.770000] br-lan: port 3(wlan0-1) entered forwarding state SYSTEM LOG AT SAME TIME AFTER FM FLASHING: Thu Jan 21 21:34:28 2016 kern.info kernel: [ 14.450000] usbcore: registered new interface driver cdc_ether Thu Jan 21 21:34:28 2016 kern.info kernel: [ 14.480000] ath9k_htc 1-1.1:1.0: ath9k_htc: HTC initialized with 33 credits Thu Jan 21 21:34:28 2016 kern.info kernel: [ 14.480000] ip_tables: (C) 2000-2006 Netfilter Core Team Thu Jan 21 21:34:28 2016 kern.info kernel: [ 14.530000] usbcore: registered new interface driver pl2303 Thu Jan 21 21:34:28 2016 kern.info kernel: [ 14.530000] usbserial: USB Serial support registered for pl2303 Thu Jan 21 21:34:28 2016 kern.info kernel: [ 14.540000] PPP generic driver version 2.4.2 Thu Jan 21 21:34:28 2016 kern.info kernel: [ 14.550000] NET: Registered protocol family 24 Thu Jan 21 21:34:28 2016 kern.info kernel: [ 14.560000] usbcore: registered new interface driver qmi_wwan Thu Jan 21 21:34:28 2016 kern.info kernel: [ 14.570000] usbcore: registered new interface driver rndis_host Thu Jan 21 21:34:28 2016 kern.info kernel: [ 14.580000] usbcore: registered new interface driver sierra_net Thu Jan 21 21:34:28 2016 kern.info kernel: [ 14.600000] usbcore: registered new interface driver option Thu Jan 21 21:34:28 2016 kern.info kernel: [ 14.600000] usbserial: USB Serial support registered for GSM modem (1-port) Thu Jan 21 21:34:28 2016 kern.info kernel: [ 17.090000] ath9k_htc 1-1.1:1.0: ath9k_htc: FW Version: 1.3 Thu Jan 21 21:34:28 2016 kern.info kernel: [ 17.090000] ath9k_htc 1-1.1:1.0: FW RMW support: Off Thu Jan 21 21:34:28 2016 kern.debug kernel: [ 17.100000] ath: EEPROM regdomain: 0x0 Thu Jan 21 21:34:28 2016 kern.debug kernel: [ 17.100000] ath: EEPROM indicates default country code should be used Thu Jan 21 21:34:28 2016 kern.debug kernel: [ 17.100000] ath: doing EEPROM country->regdmn map search Thu Jan 21 21:34:28 2016 kern.debug kernel: [ 17.100000] ath: country maps to regdmn code: 0x3a Thu Jan 21 21:34:28 2016 kern.debug kernel: [ 17.100000] ath: Country alpha2 being used: US Thu Jan 21 21:34:28 2016 kern.debug kernel: [ 17.100000] ath: Regpair used: 0x3a Thu Jan 21 21:34:28 2016 kern.info kernel: [ 17.120000] ieee80211 phy1: Atheros AR9271 Rev:1 Thu Jan 21 21:34:30 2016 user.emerg syslog: this file has been obseleted. please call "/sbin/block mount" directly Thu Jan 21 21:34:31 2016 cron.info crond[1328]: crond (busybox 1.23.2) started, log level 5 Thu Jan 21 21:34:34 2016 daemon.notice netifd: Interface 'lan' is enabled Thu Jan 21 21:34:34 2016 daemon.notice netifd: Interface 'lan' is setting up now Thu Jan 21 21:34:34 2016 kern.info kernel: [ 25.070000] device eth0 entered promiscuous mode Thu Jan 21 21:34:35 2016 daemon.notice netifd: Interface 'lan' is now up Thu Jan 21 21:34:35 2016 daemon.notice netifd: Interface 'loopback' is enabled Thu Jan 21 21:34:35 2016 daemon.notice netifd: Interface 'loopback' is setting up now Thu Jan 21 21:34:35 2016 daemon.notice netifd: Interface 'loopback' is now up Thu Jan 21 21:34:35 2016 daemon.notice netifd: Network device 'lo' link is up Thu Jan 21 21:34:35 2016 daemon.notice netifd: Interface 'loopback' has link connectivity Thu Jan 21 21:34:36 2016 user.info autossh[1409]: starting ssh (count 1) Thu Jan 21 21:34:36 2016 user.info autossh[1409]: ssh child pid is 1411 Thu Jan 21 21:34:36 2016 user.notice firewall: Reloading firewall due to ifup of lan (br-lan) Thu Jan 21 21:34:38 2016 kern.info kernel: [ 28.170000] eth0: link up (100Mbps/Full duplex) Thu Jan 21 21:34:38 2016 kern.info kernel: [ 28.320000] br-lan: port 1(eth0) entered forwarding state Thu Jan 21 21:34:38 2016 kern.info kernel: [ 28.320000] br-lan: port 1(eth0) entered forwarding state Thu Jan 21 21:34:38 2016 daemon.notice netifd: Network device 'eth0' link is up Thu Jan 21 21:34:38 2016 daemon.notice netifd: Bridge 'br-lan' link is up Thu Jan 21 21:34:38 2016 daemon.notice netifd: Interface 'lan' has link connectivity Thu Jan 21 21:34:39 2016 daemon.notice netifd: radio0 (1353): Configuration file: /var/run/hostapd-phy0.conf Thu Jan 21 21:34:39 2016 kern.info kernel: [ 30.080000] device wlan0 entered promiscuous mode Thu Jan 21 21:34:39 2016 kern.info kernel: [ 30.090000] br-lan: port 2(wlan0) entered forwarding state Thu Jan 21 21:34:39 2016 kern.info kernel: [ 30.090000] br-lan: port 2(wlan0) entered forwarding state Thu Jan 21 21:34:40 2016 daemon.notice netifd: radio0 (1353): Using interface wlan0 with hwaddr 00:c0:ca:8d:92:b1 and ssid "Pineapple_92B1" Thu Jan 21 21:34:40 2016 daemon.notice netifd: radio0 (1353): wlan0: interface state UNINITIALIZED->ENABLED Thu Jan 21 21:34:40 2016 daemon.notice netifd: radio0 (1353): wlan0: AP-ENABLED Thu Jan 21 21:34:40 2016 kern.info kernel: [ 30.320000] br-lan: port 1(eth0) entered forwarding state Thu Jan 21 21:34:40 2016 kern.info kernel: [ 30.560000] eth0: link down Thu Jan 21 21:34:41 2016 daemon.notice netifd: Network device 'eth0' link is down Thu Jan 21 21:34:41 2016 kern.info kernel: [ 31.560000] br-lan: port 1(eth0) entered disabled state Thu Jan 21 21:34:41 2016 kern.info kernel: [ 32.090000] br-lan: port 2(wlan0) entered forwarding state Thu Jan 21 21:34:42 2016 kern.info kernel: [ 32.560000] eth0: link up (100Mbps/Full duplex) Thu Jan 21 21:34:42 2016 kern.info kernel: [ 32.560000] br-lan: port 1(eth0) entered forwarding state Thu Jan 21 21:34:42 2016 kern.info kernel: [ 32.570000] br-lan: port 1(eth0) entered forwarding state Thu Jan 21 21:34:42 2016 daemon.notice netifd: Network device 'eth0' link is up Thu Jan 21 21:34:43 2016 daemon.info dnsmasq[1576]: started, version 2.73 cachesize 150 Thu Jan 21 21:34:43 2016 daemon.info dnsmasq[1576]: compile time options: no-IPv6 GNU-getopt no-DBus no-i18n no-IDN DHCP no-DHCPv6 no-Lua TFTP no-conntrack no-ipset no-auth no-DNSSEC loop-detect inotify Thu Jan 21 21:34:43 2016 daemon.info dnsmasq[1576]: DNS service limited to local subnets Thu Jan 21 21:34:43 2016 daemon.info dnsmasq-dhcp[1576]: DHCP, IP range 172.16.42.100 -- 172.16.42.249, lease time 12h Thu Jan 21 21:34:43 2016 daemon.info dnsmasq[1576]: using local addresses only for domain lan Thu Jan 21 21:34:43 2016 daemon.info dnsmasq[1576]: reading /tmp/resolv.conf.auto Thu Jan 21 21:34:43 2016 daemon.info dnsmasq[1576]: using local addresses only for domain lan Thu Jan 21 21:34:43 2016 daemon.info dnsmasq[1576]: using nameserver 8.8.4.4#53 Thu Jan 21 21:34:43 2016 daemon.info dnsmasq[1576]: read /etc/hosts - 1 addresses Thu Jan 21 21:34:43 2016 daemon.info dnsmasq[1576]: read /tmp/hosts/dhcp - 1 addresses Thu Jan 21 21:34:43 2016 daemon.info dnsmasq-dhcp[1576]: read /etc/ethers - 0 addresses Thu Jan 21 21:34:44 2016 kern.info kernel: [ 34.570000] br-lan: port 1(eth0) entered forwarding state Thu Jan 21 21:34:44 2016 user.err autossh[1409]: ssh exited prematurely with status 255; autossh exiting Thu Jan 21 21:34:46 2016 daemon.notice netifd: Network device 'wlan0' link is up Thu Jan 21 21:34:48 2016 daemon.info dnsmasq-dhcp[1576]: DHCPDISCOVER(br-lan) 00:c0:ca:8d:d8:3d Thu Jan 21 21:34:48 2016 daemon.info dnsmasq-dhcp[1576]: DHCPOFFER(br-lan) 172.16.42.223 00:c0:ca:8d:d8:3d Thu Jan 21 21:34:48 2016 daemon.info dnsmasq-dhcp[1576]: DHCPREQUEST(br-lan) 172.16.42.223 00:c0:ca:8d:d8:3d Thu Jan 21 21:34:48 2016 daemon.info dnsmasq-dhcp[1576]: DHCPACK(br-lan) 172.16.42.223 00:c0:ca:8d:d8:3d Thu Jan 21 21:34:58 2016 kern.notice kernel: [ 48.420000] random: nonblocking pool is initialized Thu Jan 21 21:35:13 2016 auth.info sshd[1661]: Server listening on 0.0.0.0 port 22. Thu Jan 21 21:35:13 2016 daemon.err mount_root: no jffs2 marker found Thu Jan 21 21:35:13 2016 kern.warn kernel: [ 63.590000] jffs2_scan_eraseblock(): End of filesystem marker found at 0x0 Thu Jan 21 21:35:13 2016 kern.warn kernel: [ 63.590000] jffs2_build_filesystem(): unlocking the mtd device... done. Thu Jan 21 21:35:17 2016 auth.err sshd[1695]: error: Could not load host key: /etc/ssh/ssh_host_ecdsa_key Thu Jan 21 21:35:17 2016 auth.err sshd[1695]: error: Could not load host key: /etc/ssh/ssh_host_ed25519_key Thu Jan 21 21:35:23 2016 kern.warn kernel: [ 63.600000] jffs2_build_filesystem(): erasing all blocks after the end marker... done. Thu Jan 21 21:35:23 2016 kern.notice kernel: [ 73.340000] jffs2: notice: (1694) jffs2_build_xattr_subsystem: complete building xattr subsystem, 0 of xdatum (0 unchecked, 0 orphan) and 0 of xref (0 dead, 0 orphan) found. Thu Jan 21 21:35:23 2016 daemon.info mount_root: performing overlay whiteout Thu Jan 21 21:35:23 2016 auth.info sshd[1661]: Received signal 15; terminating. Thu Jan 21 21:35:24 2016 kern.info kernel: [ 74.950000] device wlan0 left promiscuous mode Thu Jan 21 21:35:24 2016 kern.info kernel: [ 74.960000] br-lan: port 2(wlan0) entered disabled state Thu Jan 21 21:35:24 2016 daemon.notice netifd: Network device 'wlan0' link is down Thu Jan 21 21:35:25 2016 daemon.err block: /dev/mtdblock3 is already mounted Thu Jan 21 21:35:26 2016 daemon.notice netifd: radio1 (1764): Interface 0 setup failed: BRIDGE_NOT_ALLOWED Thu Jan 21 21:35:26 2016 daemon.notice netifd: radio0 (1827): Configuration file: /var/run/hostapd-phy0.conf Thu Jan 21 21:35:26 2016 daemon.info dnsmasq-dhcp[1576]: DHCPDISCOVER(br-lan) 00:c0:ca:8d:d8:3d Thu Jan 21 21:35:26 2016 daemon.info dnsmasq-dhcp[1576]: DHCPOFFER(br-lan) 172.16.42.223 00:c0:ca:8d:d8:3d Thu Jan 21 21:35:26 2016 daemon.info dnsmasq-dhcp[1576]: DHCPREQUEST(br-lan) 172.16.42.223 00:c0:ca:8d:d8:3d Thu Jan 21 21:35:26 2016 daemon.info dnsmasq-dhcp[1576]: DHCPACK(br-lan) 172.16.42.223 00:c0:ca:8d:d8:3d Thu Jan 21 21:35:27 2016 kern.info kernel: [ 77.130000] device wlan0 entered promiscuous mode Thu Jan 21 21:35:27 2016 kern.info kernel: [ 77.130000] br-lan: port 2(wlan0) entered forwarding state Thu Jan 21 21:35:27 2016 kern.info kernel: [ 77.140000] br-lan: port 2(wlan0) entered forwarding state Thu Jan 21 21:35:27 2016 daemon.notice netifd: radio0 (1827): Using interface wlan0 with hwaddr 00:c0:ca:8d:92:b1 and ssid "Pineapple_92B1" Thu Jan 21 21:35:27 2016 daemon.notice netifd: radio0 (1827): wlan0: interface state UNINITIALIZED->ENABLED Thu Jan 21 21:35:27 2016 daemon.notice netifd: radio0 (1827): wlan0: AP-ENABLED Thu Jan 21 21:35:27 2016 user.emerg syslog: find: /proc/1954: No such file or directory Thu Jan 21 21:35:27 2016 user.emerg syslog: find: /proc/1957: No such file or directory Thu Jan 21 21:35:27 2016 user.emerg syslog: find: /proc/1958: No such file or directory Thu Jan 21 21:35:28 2016 kern.info kernel: [ 78.710000] usb-storage 1-1.2:1.0: USB Mass Storage device detected Thu Jan 21 21:35:28 2016 kern.info kernel: [ 78.720000] scsi host1: usb-storage 1-1.2:1.0 Thu Jan 21 21:35:28 2016 user.emerg syslog: setting up led wlan0 Thu Jan 21 21:35:29 2016 kern.info kernel: [ 79.140000] br-lan: port 2(wlan0) entered forwarding state Thu Jan 21 21:35:29 2016 user.emerg syslog: WiFi Pineapple Controller version 0.1 Thu Jan 21 21:35:29 2016 user.emerg syslog: Thu Jan 21 21:35:29 2016 user.emerg syslog: Usage: pineapple [command] [[options]] [[[args]]] Thu Jan 21 21:35:29 2016 user.emerg syslog: Thu Jan 21 21:35:29 2016 user.emerg syslog: A Program to controll your WiFi Pineapple over the commandline. Thu Jan 21 21:35:29 2016 user.emerg syslog: Thu Jan 21 21:35:29 2016 user.emerg syslog: Commands: Thu Jan 21 21:35:29 2016 user.emerg syslog: karma Thu Jan 21 21:35:29 2016 user.emerg syslog: start - Starts Karma Thu Jan 21 21:35:29 2016 user.emerg syslog: stop - Stops Karma Thu Jan 21 21:35:29 2016 user.emerg syslog: list_ssids - Lists all SSIDs in Karma's black/white list. Thu Jan 21 21:35:29 2016 user.emerg syslog: list_macs - Lists all SSIDs in Karma's black list. Thu Jan 21 21:35:29 2016 user.emerg syslog: add_ssid [SSID] - Adds the specified SSID to the black/white list. Thu Jan 21 21:35:29 2016 user.emerg syslog: del_ssid [SSID] - Delete the specified SSID from the black/white list. Thu Jan 21 21:35:29 2016 user.emerg syslog: add_mac [MAC] - Adds the specified MAC to the black list. Thu Jan 21 21:35:29 2016 user.emerg syslog: del_mac [MAC] - Delete the specified MAC from the black list. Thu Jan 21 21:35:29 2016 user.emerg syslog: Thu Jan 21 21:35:29 2016 user.emerg syslog: led Thu Jan 21 21:35:29 2016 user.emerg syslog: on - Turn's the blue LED on. Thu Jan 21 21:35:29 2016 user.emerg syslog: off - Turn's the blue LED off. Thu Jan 21 21:35:29 2016 user.emerg syslog: reset - Reset's LED behaviour to default Thu Jan 21 21:35:29 2016 user.emerg syslog: Thu Jan 21 21:35:29 2016 user.emerg syslog: module Thu Jan 21 21:35:29 2016 user.emerg syslog: list - Lists all available modules with a CLI component. Thu Jan 21 21:35:29 2016 user.emerg syslog: [Module Name] [[args]] - Runs specified module with args if given. Thu Jan 21 21:35:29 2016 user.emerg syslog: Thu Jan 21 21:35:29 2016 user.emerg syslog: notify [notification text] - Sends a notification to the webinterface Thu Jan 21 21:35:29 2016 user.emerg syslog: Thu Jan 21 21:35:29 2016 daemon.info dnsmasq-dhcp[1576]: DHCPDISCOVER(br-lan) 00:c0:ca:8d:d8:3d Thu Jan 21 21:35:29 2016 daemon.info dnsmasq-dhcp[1576]: DHCPOFFER(br-lan) 172.16.42.223 00:c0:ca:8d:d8:3d Thu Jan 21 21:35:29 2016 daemon.info dnsmasq-dhcp[1576]: DHCPREQUEST(br-lan) 172.16.42.223 00:c0:ca:8d:d8:3d Thu Jan 21 21:35:29 2016 daemon.info dnsmasq-dhcp[1576]: DHCPACK(br-lan) 172.16.42.223 00:c0:ca:8d:d8:3d Thu Jan 21 21:35:29 2016 kern.notice kernel: [ 79.720000] scsi 1:0:0:0: Direct-Access Generic STORAGE DEVICE 0933 PQ: 0 ANSI: 6 Thu Jan 21 21:35:29 2016 kern.notice kernel: [ 79.720000] sd 1:0:0:0: Attached scsi generic sg0 type 0 Thu Jan 21 21:35:29 2016 kern.notice kernel: [ 79.770000] sd 1:0:0:0: [sda] Attached SCSI removable disk Thu Jan 21 21:35:30 2016 daemon.notice netifd: Network device 'wlan0' link is up Thu Jan 21 21:35:30 2016 daemon.info procd: - init complete - Thu Jan 21 21:35:30 2016 daemon.err block: Unkown action change Thu Jan 21 21:35:30 2016 daemon.err block: Unkown action change Thu Jan 21 21:35:36 2016 user.notice root: First Setup: Disable WiFi Thu Jan 21 21:35:36 2016 daemon.notice netifd: Network device 'wlan0' link is down Thu Jan 21 21:35:36 2016 kern.info kernel: [ 86.470000] br-lan: port 2(wlan0) entered disabled state Thu Jan 21 21:35:36 2016 kern.info kernel: [ 86.730000] device wlan0 left promiscuous mode Thu Jan 21 21:35:36 2016 kern.info kernel: [ 86.740000] br-lan: port 2(wlan0) entered disabled state Thu Jan 21 21:35:36 2016 kern.info kernel: [ 86.780000] eth0: link down Thu Jan 21 21:35:37 2016 daemon.notice netifd: Network device 'eth0' link is down Thu Jan 21 21:35:37 2016 kern.info kernel: [ 87.470000] br-lan: port 1(eth0) entered disabled state Thu Jan 21 21:35:38 2016 daemon.notice netifd: Bridge 'br-lan' link is down Thu Jan 21 21:35:38 2016 daemon.notice netifd: Interface 'lan' has link connectivity loss Thu Jan 21 21:35:38 2016 kern.info kernel: [ 88.780000] eth0: link up (100Mbps/Full duplex) Thu Jan 21 21:35:38 2016 kern.info kernel: [ 88.780000] br-lan: port 1(eth0) entered forwarding state Thu Jan 21 21:35:38 2016 kern.info kernel: [ 88.790000] br-lan: port 1(eth0) entered forwarding state Thu Jan 21 21:35:38 2016 daemon.notice netifd: Network device 'eth0' link is up Thu Jan 21 21:35:38 2016 daemon.notice netifd: Bridge 'br-lan' link is up Thu Jan 21 21:35:38 2016 daemon.notice netifd: Interface 'lan' has link connectivity Thu Jan 21 21:35:40 2016 kern.info kernel: [ 90.790000] br-lan: port 1(eth0) entered forwarding state Thu Jan 21 21:35:42 2016 daemon.info dnsmasq-dhcp[1576]: DHCPDISCOVER(br-lan) 00:c0:ca:8d:d8:3d Thu Jan 21 21:35:42 2016 daemon.info dnsmasq-dhcp[1576]: DHCPOFFER(br-lan) 172.16.42.223 00:c0:ca:8d:d8:3d Thu Jan 21 21:35:42 2016 daemon.info dnsmasq-dhcp[1576]: DHCPREQUEST(br-lan) 172.16.42.223 00:c0:ca:8d:d8:3d Thu Jan 21 21:35:42 2016 daemon.info dnsmasq-dhcp[1576]: DHCPACK(br-lan) 172.16.42.223 00:c0:ca:8d:d8:3d Thu Jan 21 21:38:01 2016 auth.info sshd[2343]: Server listening on 0.0.0.0 port 22. Thu Jan 21 21:38:02 2016 daemon.notice netifd: radio1 (2358): Interface 0 setup failed: BRIDGE_NOT_ALLOWED Thu Jan 21 21:38:02 2016 daemon.notice netifd: radio0 (2357): Configuration file: /var/run/hostapd-phy0.conf Thu Jan 21 21:38:02 2016 kern.info kernel: [ 232.940000] device wlan0 entered promiscuous mode Thu Jan 21 21:38:02 2016 kern.info kernel: [ 232.940000] br-lan: port 2(wlan0) entered forwarding state Thu Jan 21 21:38:02 2016 kern.info kernel: [ 232.950000] br-lan: port 2(wlan0) entered forwarding state Thu Jan 21 21:38:02 2016 daemon.notice netifd: radio0 (2357): Using interface wlan0 with hwaddr 00:c0:ca:8d:92:b1 and ssid "Pineapple_92B1" Thu Jan 21 21:38:02 2016 kern.info kernel: [ 233.040000] device wlan0-1 entered promiscuous mode Thu Jan 21 21:38:02 2016 kern.info kernel: [ 233.050000] br-lan: port 3(wlan0-1) entered forwarding state Thu Jan 21 21:38:02 2016 kern.info kernel: [ 233.050000] br-lan: port 3(wlan0-1) entered forwarding state Thu Jan 21 21:38:03 2016 daemon.notice netifd: radio0 (2357): Using interface wlan0-1 with hwaddr 02:c0:ca:8d:92:b1 and ssid "chunbks" Thu Jan 21 21:38:03 2016 kern.info kernel: [ 233.570000] br-lan: port 3(wlan0-1) entered disabled state Thu Jan 21 21:38:03 2016 kern.info kernel: [ 233.770000] br-lan: port 3(wlan0-1) entered forwarding state Thu Jan 21 21:38:03 2016 kern.info kernel: [ 233.770000] br-lan: port 3(wlan0-1) entered forwarding state Thu Jan 21 21:38:03 2016 daemon.notice netifd: radio0 (2357): wlan0: interface state UNINITIALIZED->ENABLED Thu Jan 21 21:38:03 2016 daemon.notice netifd: radio0 (2357): wlan0: AP-ENABLED Thu Jan 21 21:38:04 2016 kern.info kernel: [ 234.950000] br-lan: port 2(wlan0) entered forwarding state Thu Jan 21 21:38:05 2016 daemon.info dnsmasq-dhcp[1576]: DHCPDISCOVER(br-lan) 00:c0:ca:8d:d8:3d Thu Jan 21 21:38:05 2016 daemon.info dnsmasq-dhcp[1576]: DHCPOFFER(br-lan) 172.16.42.223 00:c0:ca:8d:d8:3d Thu Jan 21 21:38:05 2016 daemon.info dnsmasq-dhcp[1576]: DHCPREQUEST(br-lan) 172.16.42.223 00:c0:ca:8d:d8:3d Thu Jan 21 21:38:05 2016 daemon.info dnsmasq-dhcp[1576]: DHCPACK(br-lan) 172.16.42.223 00:c0:ca:8d:d8:3d Thu Jan 21 21:38:05 2016 kern.info kernel: [ 235.770000] br-lan: port 3(wlan0-1) entered forwarding state Thu Jan 21 21:38:06 2016 daemon.notice netifd: Network device 'wlan0' link is up Thu Jan 21 21:38:06 2016 daemon.notice netifd: Network device 'wlan0-1' link is up Thu Mar 31 06:50:48 2016 cron.err crond[1328]: time disparity of 99912 minutes detected Thu Mar 31 06:50:53 2016 auth.err sshd[2652]: error: Could not load host key: /etc/ssh/ssh_host_ecdsa_key Thu Mar 31 06:50:53 2016 auth.err sshd[2652]: error: Could not load host key: /etc/ssh/ssh_host_ed25519_key Thu Mar 31 06:51:53 2016 auth.info sshd[2652]: Accepted password for root from 172.16.42.42 port 52056 ssh2 Also, is there a repository of Commands that are applicable for the nano? Other than Googling? I get overwhelmed with information sometimes when I go looking for information. Thank you again.

I have seen speculation on top of speculation, as well as some confirmation from the makers. SOOOO, with that... 1. Are we getting the new firmware? 2. When might we see anything regarding this release? Please, no speculation in this thread and no re-quotes of various people saying things in different threads as I have seen it all.... Would love someone who ACTUALLY knows to respond and give your many customers that have your device some sort of update on the new firmware. Thank you A long time customer.

Hey, folks. I've tried using my LAN Turtle on a few engagements now, and while it's nice to show it plugged into a computer in the report, I rarely get much love out of it, and the shell feels too slow to be useful (guess that's why it's called a LAN Turtle! - It's a really slow shell!) Anyway - The idea that I wanted to float today is whether or not it would be possible to turn the LAN Turtle into a "TwinTurtle", similar to the "TwinDuck" firmware for the USB Rubber Ducky, but in this case, the LANTurtle would continue to be a USB-to-Ethernet adapter as well as acting as a HID device, so you could have a "blind terminal" into the machine it's physically plugged into. This could allow direct exploitation of the machine through powershell meterpreter, for example - The only problem I can think of is how to tell if the device is actually unlocked before sending the commands. So the reason I'm bringing this here is that I don't currently have the know-how to write a custom firmware which implements this sort of functionality, but I wanted to bring up the idea to the community, to see if this is something that is even possible, and if there are people willing and able to implement it.

yea as the title says...my kid brother unpackaged my pineapple before i got home from work and the little punk that he usually is threw the freaking piece of paper away that had the SD attached to it so now idk what to do....i formatted a thumbdrive to EXT4 and that is pretty much where i am right now....idk how i'm suppose to go about flashing the firmware and i also read in the little owners manual that it can not be run without an SD so does that mean that installing the firmware on the USB would be moot? ANY help would be greatly appreciated...I'm on a macbook pro runninng 10.10.5

Hello everybody My usb rubber ducky arrives in a few days and i have another bunch of questions: 1. It comes with micro SD card, doesn´t it? How much is it capability? (2, 4, 8 GB?) 2. Does it came with pre-installed firmware? 3. Does java version matter when building payloads? 4. Does exists any noob-proof tutorial? you know Thanks in advance!

I've flashed the cm_duck.hex firmware on my USB Rubber Ducky and I cannot get inject.bin or inject2.bin to execute on my Macbook (it works fine on a Windows computer). I've ensured that the caps lock light is on, and also tried pressing the button on the USB. The default duck.hex and c_duck_v2_S001.hex works (S001 requires pressing of button on USB) on my Macbook. Is OS X not supported by the cm_duck.hex firmware? Or am I doing anything wrong? Any help will be greatly appreciated

Hi Everyone, I'm having issues with my pineapple Mark V, as the tittle said, it reboots when Im connected to the management WiFi using my cellphone, and checking the clients connected (even if there isn't any), showing the "entropy bonny" to suddenly lit the red led and reinitiate. This happened with under the following escenario: Pineapple connected to RJ-45 configured with the new client mode to access internet Running Karma, PineAP, Beacon Response, Auto Harvester and SSLStrip. MicroSD Sandisk Ultra 32GB, also tested with the 2GB stock MicroSD. All the rest setting as default. My unsucessful attempt to troubleshoot this was execute the un-brick flashing process using the factory.bin firmware image, to later upgrade the firmware from the 2.0.4 version to the latest 2.3.0. Im currently running the 2.0.4 firmware on the Pineapple, as it seems to be more stable than the 2.3.0 firmware. If any further information is required, please do not hesitate to ask. Any advice or tip will be much appreciate to solve this will be much appreciated

So i just got the Ducky about 2 days ago. I know that i'm compliing everything correctly. The problem is that i have to press the button for it to run the program. once i press the button it works beautifully. I'm not sure why this is. could it be a firmware problem. Is it related to the pulsating blue light? If any anyone has any idea it would be great to hear some possible solutions.