I recently updated to the 2.2.0 update. Everything is working as expected using Firefox on my laptop, but I am having a lot of problems using the web API on my cell. Its an old cell, using Android 5.0.1. I can not open the PineAP module's page, and on the Recon module's page, when I pause or stop the scan, there are no drop down ( carets? ) next to the MACs. I haven't seen any other reports about this, is there anything else needed to help resolve this?
Whenever I go into the Network tab and try to set a new MAC or Set Random MAC the radio that I try to change shuts off and becomes unusable. I have waited for them to become usable for up to 5 hours with no success, it doesn't matter if I do just one at a time or all of them, and doesn't matter how patient I am. And once this happens they are permanently unusable unless I preform a factory reset, which I've done several times. And I've also performed one Firmware Recovery, to no avail. Any ideas of what I can do?
Hi There! Im relatively new then Wifi Pineapple NANO and its various modules, as such i've just been playing around with it on my Macbook Pro. Some very awesome tech. Ive wanted to start using it with my Kali Linux VM running through Virtual box and have run into some issues, particularly in regard to the device, once configured, being detected and the correct gateways to use for a MacOS VM. As you are probably well aware, Apple has a different default gateway to the rest of the world (using 192.168.2.1 instead of 172.16.42.42 i believe). I've configured my Kali box to have a bridged adaptor to eth0 which is my laptops internet connection and have done the correct usb configuration to allow the pineapple to be detected. Im using the wp6.sh script to configure the pineapples connection through the VM. After following the Guided setup and setting the appropriate default gateway etc. the pineapple refuses to be detected, i.e. gets stuck when i try to connecting saved setting... Its probably something simple that i'm forgetting, as i said, i'm fairly new and having a mac is difficult for trouble shooting....any help would be greatly appreciated!
Mac foreign keyboard mystery solved ?
I have been unable to get my bashbunny to show up as a usb network interface for linux/mac. i have set my ATTACKMODE ECM_ETHERNET. other modes are working. anyone else seen this? ideas?
Hi all, I know this topic has been covered in the past but I did not find anything specific to mac. I am having problem with network connectivity. When I run the script, on step 3 it prompts me to connect pineapple, however even after I connect pineapple to my mac, the script the keeps running with nothing happening. I cannot load bulletins from wifipineapple.com. I have shared the internet to ethernet on my mac. I tried almost everything I could think of, resetting, changed default gateway to 172.16.42.1. My routing table looks like: Destination Gateway Genmask Flags Metric Ref Use Iface default Pineapple.lan 0.0.0.0 UG 0 0 0 br-lan 172.16.42.0 * 255.255.255.0 U 0 0 0 br-lan Any help is much appreciated.
I just recently got my tetra. It works great on linux systems, but I have a macbook that I would like to use the tetra on doesn't connect with the default IP address and does not show up in ifconfig. What am I doing wrong? Am I missing a step?
Got my nano last night, super pumped! When I got to Networking I only see the option to select wlan1 as my interface, but it looks like this interferes with PineAP. Is there a way I can select eth0 as the interface and have it use my wifi on my mac to connect to the internet? Or is there an option to free up the second radio that I'm missing so I can use PineAP and be connected to the internet at the same time? I tried selecting Disable Management AP under the Access Points menu and I'm still only given the option to choose wlan1 as my interface in client mode. On a side note, when I plug in an additional alfa usb adapter to the nano, it recognizes wlan2 automagically. Are there any other options for client mode?
Apologies for the length of this, but it may help other people So yesterday I received my shiny new Tetra and thought "great, lets plug it in and have a play" :) The instructions are nice and simple: Download the latest WiFi Pineapple TETRA firmware - complete	Plug the TETRA into your computer using the included USB Y cables - yep, done, pair of USB3 ports on my main Windows 10 PC. Also plugged in the mains adapter. Solid blue LED showing	Browse to http://172.16.42.1:1471 (Only Chrome and Firefox are officially supported) - yeah. Nope. Not happening. Nada. Zip	Follow the onscreen instructions to complete setup So, opened a command prompt and ran IPconfig APIA address on the USB-Ethernet port - not a good start. So its not picking up DHCP from the Tetra. OK thats probably the PC. Swap to laptop number 1. Windows 10 Plug in the Tetra to the two USB ports on the side. Still got a solid blue light on the Tetra. Still got APIA address on the USB Ethernet port Re-install the drivers for the USB-Ethernet port - still nada. The interface in windows is showing as connected, unidentified. Cannot connect to the management page Check the Wifi networks showing - 2x Pineapple_xxxx networks (presuming one 2.4 and one 5Ghz) - lets try connecting to them, and yep can "connect" but again, no DHCP address. Now mildly frustrated. Swap to laptop number 2. Windows 10 Plug in the Tetra to the two USB ports on the side. Still got a solid blue light on the Tetra. Still got APIA address on the USB Ethernet port Re-install the drivers for the USB-Ethernet port - still nada. The interface in windows is showing as connected, unidentified. Cannot connect to the management page Now getting more frustrated Swap to laptop number 3. Kali Linux 2 Plug in the Tetra to the two USB ports on the side. Still got a solid blue light on the Tetra. Still got APIA address on the USB Ethernet port Re-install the drivers for the USB-Ethernet port - still nada. The interface is showing in ifconfig but with not IP Cannot connect to the management page Now beginning to think hardware failure Swap to laptop number 4. Mac Install the Realtek driver for Mac, new USB 10/100 adapter appears Plug in the Tetra to the two USB ports on the side. Still got a solid blue light on the Tetra. Still got APIA address on the USB Ethernet port Re-install the drivers for the USB-Ethernet port - still nada. The interface in windows is showing as connected, unidentified. Cannot connect to the management page Now VERY frustrated and thinking about DoA's, RMA's back to the states.... OK, lets try something radical At this point the only thing I've got left is to rebuild my Kali box as a Windows 7 box. Which completes and then takes another couple of hours to patch. By this time I've gone down the pub for the evening. Laptop number "5". Kali Box rebuilt as Windows 7 Install the Realtek driver for Mac, new USB 10/100 adapter appears Plug in the Tetra to the two USB ports on the side. Still got a solid blue light on the Tetra. Still got APIA address on the USB Ethernet port Re-install the drivers for the USB-Ethernet port - still nada. The interface in windows is showing as connected, unidentified. Cannot connect to the management page Now convinced there is something wrong with the hardware. 5 different platforms, 4 different OS' and not one DHCP address. Nothing on the forums that seems to apply. Last thing to do - reapply the factory firmware Follow the instructions on the FAQ page and bang, once the firmware is "refreshed" back to factory, all of a sudden everything is working on my W7 laptop, and I could login, complete the setup etc. So its finally all working. TL;DR - if you really really can't connect to a new tetra and you've tried drivers, connectors, everything you can - try reapplying the factory firmware.
So you put how to setup internet sharing on both the windows installation and linux, I was wondering if you can help me do the internet sharing on my mac because i cannot find anywhere where it says ethernet on network settings ..
how can i make MAC changes persist a power cycle ?
Hell-Low H5 FolkZ @SF, Just got a new Turtle and waz playin around with it. Seems to be quite k3wL, but there are problems with the mac changer of the wan interface. 1st issue - it does not work - the interface goes down and does not come back (eth1). after manually /etc/init.d/network restart all worx fine (with static IP settings and faked mac 2 deploy device in an secured environment with mac binding). 2nd issue - how can i make the mac change persist a power cycle. I want to deply that tiny device in a secured environment with static ip settings and mac binding. So i will loose contact to the turtle after a power cycle. The scenario ist to drop the device @ a network with static IP settings and i must fake the mac of an registered device to be able to autossh out of the network. The fake mac and the static ip settings must persist a power cycle or the device is "lost". Any suggestions ? Maybe a tiny shell script ? but where to put (for persistance) ?