Sebkinne

Hi Nimiq, The panel antenna probably has an rp-sma connector (seeing as it connects to an ALFA). The WiFi Pineapple TETRA uses the more professional SMA connector, so unless you are using an adaptor, the antenna doesn't make proper contact (this could also damage the radios!). In regards to MIMO - there is nothing special you need to do. You just have to make sure that they are dual-band antennas (2.4GHz and 5GHz).

Zylla, Thank you again for bringing this to my attention. There have been a couple of interesting bugs with the new Recon mode, but I was sure I had caught them all. I was finally able to reproduce this bug by taking off the antennas, wrapping the WiFi Pineapple in tin foil, putting it into a microwave, and shutting the door. The issue was hard to reproduce because I had a lot of WiFi Traffic in all the places I have available to test in right now. The actual cause of the issue was a string::pop_back() not being safe to use on empty strings in the OpenWRT version of g++. That's what I get for trusting my compiler :) The issue only happened when there was a lack of clients, and would only randomly happen. I have fixed it and will release a firmware upgrade with this fix and an exciting new feature in the next couple of days, so stay tuned and thank you again.

Use evil portal instead :)

Thanks for the report, it looks like a debug version of pinesniffer made it into the NANO tree somehow. Ill get it fixed ASAP.

As I said, most likely somehow defective hardware. If the serial port is dead, and you have no access to the device, I don't see recovery being possible. I that case, you have a device in a soft bricked state.

Yonomas, Please format your SD card to ext4. If you don't know how to do this, the WiFi Pineapple can do it for you. Simply navigate to the Advanced module, and click the dropdown at the top of the Resources panel. To rule out any hardware issues with the WiFi Pineapple radios (you said SSID pool broadcast isn't working), please perform the following: Ensure that your WiFi Pineapple is running the latest firmware Connect to your WiFi Pineapple via Ethernet or WiFi Browse to the WiFi Pineapple to the web interface at http://172.16.42.1:1471 Navigate to the help page From the Feedback and Support section, click the button to download the debug file Wait as the debug file is generated. Once complete, save the file to your computer Copy the contents of the debug file to pastebin and paste the link here.

115200 8N1 and no flow control. There is no factory flashing possible with this bootloader (this was before we did custom hardware) - apart from over serial. Once you get that working, you can follow the steps outlined in Mr-Protocols video. Make sure to download the factory files from here instead, and downloading the WiFi Pineapple MKIV firmware from here. Other than that, sorry for stating your unit was bricked - I hadn't read the entire thread. If you do fix your UART connection (Defective hardware? Broken serial on the MKIV?), you may simply be able to perform a factory reset on the device itself.

No worries, we all make mistakes :) Regarding the posting, I moved it from the "Questions" forum to the WiFi Pineapple NANO forum.

Hi theNetImp, Welcome to the forums! In the future, please use the search function, as many have asked this question before, and there are a number of threads that detail ways to get this working. The reason why we haven't published any instructions for OSX / MacOS is because Apple thinks its a good idea to keep changing internet connection sharing from update to update. Sometimes it's as easy as sharing the connection and setting a static IP, sometimes it requires modifying the Pineapple's IP, sometimes it requires plist editing.. and other times it simply won't work at all. Because of this, most OSX / MacOS users are running a linux VM and simply passing the WiFi Pineapple NANO through to the VM directly. I find this works very well myself. Of course, to simply use the WiFi Pineapple NANO on OSX, without ICS, you can simply plug the device in, open a browser, and navigate to http://172.16.42.1:1471. Just make sure that your internet facing interface is of higher priority in the OSX / MacOS network preferences.

They will work, but you will need to screw in the antennas after putting the NANO into the case. This becomes a hassle if you want to quickly take it out of the pouch, which is why we looked for antennas with a slimmer profile.

We chose those antenna because the connector allowed them to fit seamlessly into the tactical pouch - no antennas poking out and getting caught on other things. This is their primary purpose. A side effect of this is that the connectors swivel, and are not fixed. While it would be preferable if they were fixed and at such a tight angle, this proved difficult to source. Either way, the antennas are not defective - their intended use-case is just a bit different.

Firmware 1.1.1 released with lots of fixes and a few new features.

You might want to factory reset your device if the issue persists - I cannot reproduce this issue at all, unless my filters are in whitelist mode.

They are loose by design - it's the intended behavior.

Right, when talking about unassociated clients, yeah :)

You will receive the standard set and a pair of the upgraded antennas with your order. You'd have to contact shop@hak5.org for more information here. If you choose UPS or DHL, they usually require a signature though (and the package should be insured that way).

Hi 846846, Please follow our firmware recovery steps outlined on our FAQ. On a moderation note, please post in the correct forum section next time.

Probes mainly, but anything that is sent to broadcast and not to an AP (by a client device) will be listed there.

I just connect.

It does not come with a UK plug. You'll need to buy an adapter, or a new PSU (12V, 2A). Either are very cheap on Amazon.

Incorrect, depending on what you mean with seeing. The WiFi Pineapple will detect a client device if it sends any other type of frame to an AP (such as data, etc). It doesn't need to be probing to be visible.

Works perfectly fine for my nexus 6p.

I'm pretty sure your unit is dead, sorry.

Did you set any filters?

Thanks - I'm pretty sure Darren is on top of it though.