Darren Kitchen

New to bash and Linux? You'll probably want to dig into these: http://tldp.org/LDP/Bash-Beginners-Guide/html/index.html https://www.gnu.org/software/bash/manual/html_node/index.html http://www.tldp.org/ http://bash.cyberciti.biz/guide/Main_Page

That's exciting. Care to elaborate?

The Pineapple adapter: Ethernet adapter Ethernet 3: Connection-specific DNS Suffix . : lan Description . . . . . . . . . . . : ASIX AX88772A USB2.0 to Fast Ethernet Adapter Physical Address. . . . . . . . . : 00-C0-CA-8B-3C-B9 DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes IPv4 Address. . . . . . . . . . . : 172.16.42.239(Preferred) Static the IPv4 address on your WiFi Pineapple Ethernet adapter to 172.16.42.42 -- that's the default the NANO is expecting to receive an Internet connection from.

Needs more matte black LOVE IT

Agreed. Sounds rad. Takes Tracking to a whole new level :) Oh and speaking of pentest features, Tracking is a fun one if you have a specific target and a few well placed pineapples.

Linux "commands" (usually bash) are the same regardless of what Linux distribution you choose. Saying that, bash is in fact on the WiFi Pineapple so the commands are the same there. That said if you're new to Linux I also vote for Ubuntu as you'll find the most community support on that front. What do you mean by the following statement?

The PineAP log is stored in /tmp along with all of the other log files. You'll have the ability to choose a different location for this in 1.0.2

If you already ordered it'll be in the first batch to go out in 2 weeks. And if you wanna send encouraging notes to sara@hak5.org -- it'll likely brighten her day :) Shannon and Patrick are in Vegas for CES this week so we're just holding down the fort. Oh and Seb isn't allowed to sleep because the code doesn't write itself.... Unless he writes code to write code... Hmm

How are you sharing Internet with the WiFi Pineapple?

TETRA passed all certifications and has been filed. ID will be in the FCC database shortly. NANO passed SAR today and is being filed. Likewise an update to the 6th Generation software is underway with bug fixes and small feature updates, as well as API documentation and it looks like modules are coming together as well. We're on track for a very exciting January.

We just put a brief hold on orders as we're facing an unforeseen delay -- details here: https://forums.hak5.org/index.php?/topic/37235-shipping-delay-for-wifi-pineapple-tetra/-- I'll keep that threat updated re: first batch.

Hey guys - got an update here on the WiFi Pineapple Tetra shipping. Unfortunately there's about a 2 week delay. I'm really bummed about this. The sample units we've been developing on are phenomenal. We approved the first run and figured they'd all be just as great. Unfortunately they're not. We stayed up all night testing units for perfection and sadly some aren't calibrated to the highest degree of performance. It's not ideal and I really want you all to have the same epic experience as we've been having in development. We went as far as to have our manufacturing partner bring units back from the pilot run (comically) in his suitcase so we could start shipping them out today. Now I'm crushed to have to get them redone, and feel terrible to delay your orders. Yes, those are "suitcases" United Airlines ;-) Thankfully the issue isn't a big deal and we've already started spinning up the production line. We're anticipating the shipment around the 18th -- and I'll keep you all informed as we work through the process.

+1 for JuiceSSH. Also like Connectbot and Better Terminal Emulator

The TETRA already includes four onboard boosters and ships with 5 dBi SMA antennas. Like I said -- it's a powerhouse. Try the stock config before upgrading -- I think you'll be pleased :)

I don't have a timeline. Connecting the NANO to your Android device doesn't require a Y-Cable -- just a regular data capable USB cable. Seeing as newer devices are going with USB C I'm contemplating what the best course of action is for adding a Micro USB cable to the bundle.

Since you're bringing up a reference design I think it's worth pointing out here the immense work we've done in regards to integrating the four very high gain amplifiers onboard for the main SoC plus the PCIE second radio. It's no small feat and not something you'll find off the shelf. The RAM specs aren't of much consequence for what we're doing though it's a simple drop in replacement if we want to upgrade down the line. The focus was on making a rock solid long term platform and looking at our roadmap I think we've done just that.

When you setup the WiFi Pineapple you'll be prompted to specify an SSID and WPA passphrase for the management interface. Once configured you can connect to this access point to manage the WiFi Pineapple. For instance, when connecting from an Android device you'll join the WiFi Pineapple's network and be offered an IP address from DHCP in the 172.16.42.x range. Once associated you can then browse to the management web interface in the browser at http://172.16.42.1:1471

Welcome to the community! You're at somewhat of an advantage starting on the 6th generation WiFi Pineapple platform in that it's a new modernized approach to the web interface with an emphasis on the workflow. I'm sure pineapple veterans here are re-learning the layout. The timing wasn't great with the holidays for release, hence not having all of the documentation in order. We're focused now on small update of bug fixes and little features along with developer documentation. Seb and I will be hosting a hangout shortly. I haven't nailed down the exact date with him, but I'm gunning for this coming week. In the mean time I shot a quick WiFi Pineapple Primer video that'll introduce the fundamentals of the PineAP suite.

Try udhcpc root@Pineapple:~# udhcpc --help BusyBox v1.23.2 (2015-08-21 19:26:26 PDT) multi-call binary. Usage: udhcpc [-fbqRB] [-t N] [-T SEC] [-A SEC/-n] [-i IFACE] [-s PROG] [-p PIDFILE] [-oC] [-r IP] [-V VENDOR] [-F NAME] [-x OPT:VAL]... [-O OPT]... -i,--interface IFACE Interface to use (default eth0) -s,--script PROG Run PROG at DHCP events (default /usr/share/udhc pc/default.script) -p,--pidfile FILE Create pidfile -B,--broadcast Request broadcast replies -t,--retries N Send up to N discover packets (default 3) -T,--timeout SEC Pause between packets (default 3) -A,--tryagain SEC Wait if lease is not obtained (default 20) -n,--now Exit if lease is not obtained -q,--quit Exit after obtaining lease -R,--release Release IP on exit -f,--foreground Run in foreground -b,--background Background if lease is not obtained -S,--syslog Log to syslog too -r,--request IP Request this IP address -o,--no-default-options Don't request any options (unless -O is given) -O,--request-option OPT Request option OPT from server (cumulative) -x OPT:VAL Include option OPT in sent packets (cumulative) Examples of string, numeric, and hex byte opts: -x hostname:bbox - option 12 -x lease:3600 - option 51 (lease time) -x 0x3d:0100BEEFC0FFEE - option 61 (client id) -F,--fqdn NAME Ask server to update DNS mapping for NAME -V,--vendorclass VENDOR Vendor identifier (default 'udhcp VERSION') -C,--clientid-none Don't send MAC as client identifier Signals: USR1 Renew lease USR2 Release lease

TL;DR - Mark 6 = TETRA && NANO. No new WiFi Pineapples in 2016. The NANO and TETRA will be the only two WiFi devices in the 6th generation WiFi Pineapple line. They also share the same software platform. The NANO and the TETRA serve two different roles and use cases due to their form factors and frequency ranges. Similarly due to their relative complexity they're at two different cost tiers. This is the first time since the Mark I that a generation has had more than one device. One of the reasons we chose this route is to continue serving the enthusiast market while offering a secondary dual-band solution for professionals. Both devices are very capable, but with the cost and complexity of dual-band, amplifiers, NAND flash, etc in the TETRA - we were unable to produce a single design that would satisfy both markets. We also very much wanted a mobile-centric device, hence the NANO. Depending on the deployment scenario they can work together harmoniously, especially in large scale environments. The NANO was available later than anticipated while the TETRA far sooner than anticipated. While this is not ideal in a mainstream context, both devices are still only in development phases software wise hence being offered to the community first. With the upcoming API release and modules, we're on track for a simultaneous mass market release soon. Developing this hardware requires an immense amount of time and resources -- over a year in fact -- so I think it's a safe bet we won't be moving into a 7th generation in 2016. The next hardware project on the horizon for us is what we're dubbing the "Pineapple Core" -- an ARM-based companion device for both WiFi Pineapples in the 6th generation line. PS: Thanks all for sending me down a wikipedia rabbit hole of IUPAC nomenclature. https://en.wikipedia.org/wiki/IUPAC_numerical_multiplier

1. Power on the NANO 2. Connect a USB cable between the host USB port on the NANO to the Android 3. Enable USB Tethering on the Android 4. Connect a computer to the NANO WiFi network 5. From the computer, SSH into the NANO as root@172.16.42.1 6. From the SSH prompt (root@pineapple) issue the ifconfig command 7. Note the IP Address of interface usb0 8. On the Android, open Chrome and browse to http://<IP Address from step above>:1471 Let us know if that gets you the WiFi Pineapple web interface on your Android device.

;)

I'd say try bending it back. Otherwise the link above is the same cable functionality wise -- and of course you can always email shop@hak5.org

It could also be that the HTC One is using a non-standard way to USB Tether. I'm curious what your WiFi Pineapple shows in the syslog after connecting the HTC One.

Yes, the 5 GHz counterpart to the 6th gen line came in a little before expected. You can learn more at https://forums.hak5.org/index.php?/topic/37173-introducing-the-wifi-pineapple-tetra/