Foxtrot

I have heard that using batteries while charging them is bad for its health, I wouldn't do it.

Thread moved.

I think it's pretty insulting when people have an issue and ask for help, but include these little negative comments such as "Did I just buy a $100 box" or "did I just get took for $100?". Please have some respect for the team when they put countless hours into bringing you a product. You included next to no information on your issue other than what OS you are using, not any other valuable information such as the configuration of the target access point.

Can you try opening the UI in Incognito mode (or your browsers equivalent) and trying to scan then?

It would be much easier to just link the page you are talking about, rather than copying and pasting bits in and messing up some formatting.

For anyone else who encounters this problem, Please attach the /tmp/recon-* files to a post in this thread, along with any other information on activities you did with the WiFi Pineapple since boot time. Thanks

What is the output of "ifconfig" on the Kali machine when connected to an Access Point?

A packet capture of this behaviour would be incredibly interesting. What device was this?

As has been explained before, the NANO has no "shutdown" because it has no ACPI. You can reboot, and you can halt the CPU, but it's perfectly okay to pull the plug on it when you want to stop using it. I've been doing since the NANO came out and there has never been a problem. The UI already has a "Power off" and a Reboot menu. Advanced -> General

It's not.

You should use the Y-Cable at all times. Whether you have something plugged into the NANO or not, as many laptops cannot provide enough power through 1 USB port. Using the Y-Cable "fully" with both male ends plugged into a laptop etc, and the female end plugged into the NANO is fine - regardless of whether accessories are connected or not.

Hi Lunokhod, You're correct, if you want to connect wirelessly to another access point without disturbing PineAP, you'll need a third radio to plug in for client mode.

The red light flashing indicates monitor mode running on wlan1mon. Disabling PineAP will not disable wlan1mon in-case something else is using it.

Interesting. Did you flash the firmware with the NEH plugged in?

Make sure you have the newest version of the Recon module installed... Go to Module Manager -> Get Modules from www.WiFiPineapple.com -> Update.

This is (afaik) an issue with which NICs are being detected first, and has existed in the past. Booting the Mark V without the NEH, and plugging it in after boot will work fine.

But how is the client supposed to connect to the fake but encrypted AP?

Blacklist your devices MAC addresses or whitelist your targets MAC addresses.

What you are saying makes no sense at all (Incredibly bad translation) Speak in your native language.

No.

System Module logs (PineAP in particular) are stored in /tmp/ (By default). Your output from the Resources panel shows /tmp/ is its own tmpfs, indicated no relation to space being filled up on the "internal" storage. User-developed modules may store there logs elsewhere, common place being in /root/ under a hidden directory. Explore these commands: ls /tmp/ ls -la /root/ df /tmp/ df /root/

The firmware is closed source. Binaries inside the the firmware such as PineAP utilities are closed source, so they wont work on a Raspberry Pi anyway. The firmware is made and intended to run on WiFi Pineapples, not Raspberry Pi clones.

...there is no USB port on that device.

What USB? You are talking about this right? http://hakshop.myshopify.com/collections/wireless-gear/products/long-range-wifi-kit

If you explore https://wifipineapple.com, you will see what modules are available.