lunokhod

Hi Everybody, I've done some searching but haven't been able to find what format the URL Snarf and SSL Strip infusion uses for log file names. I presume it's some kind of date/time format. The actual file time stamp is in local time, as are the log file contents... but the infusions show UTC time when you click on the history tab. It would be nice if the date/time in the history tab could take the system UTC offset into account when being displayed. eg :- URL Snarf History tab shows :- 2014-11-16 23-18-10 File in /sd/infusions/urlsnarf/includes/log/ is :- Nov 17 11:29 output_1416179890.log Bear in mind that the file date stamp shows when it was last modified/updated... I am at UTC +1030 at the moment. How does the infusion turn "1416179890" into a date and time... or vice versa? Regards, Lunokhod.

Hi Everybody, I flashed my WiFi Pineapple with v2.0.2 last night and have been playing with it at work today. One thing I noticed is that the Karma tile information seems to be duplicated in the PineAP tile. The Karma Log tab in the Karma tile seems to have reverted back to the "old" style log, no Karma Log Filters option. Are others seeing this? Is there any need to interact with the Karma tile when everything "Karma" seems to be in the PineAP tile? Lunokhod

Are you trying to connect the WiFi Pineapple Ethernet socket to your existing network/router/switch via an Ethernet cable? If so... by default the Pineapples Ethernet port doesn't get an IP address via DHCP (I believe it's connected to the bridge adapter and 172.16.42.1 IP address?) and indeed the WiFi Pineapples own DHCP server operates on that hardware Ethernet port. Having dueling DHCP servers on the same network segment handing out different IP addresses isn't a good idea! There has been a recent discussion on this :- https://forums.hak5.org/index.php?/topic/33125-ethernet-client-mode/ Not sure on the exact steps needed to turn the Ethernet socket into a "client"... I have tried various things to do this in the past, but my attempts usually end in frustration. I'm happy to wait for an "official" remedy.

I'm the one that put the suggestion up on wifipineapple.com I did try to reconfigure the eth0 interface to work in this manner... but my Linux sorcery skills were not up to the task and it didn't work very well. It would be nice to be able to use one of the DIP switches to change the operation of the eth0 interface. Default switch position leaves eth0 in it's current mode... flip the switch, reboot and the eth0 is in "client" mode... ready to be assigned an IP address and gateway via DHCP.

:-( USB is 5V only! As Seb mentioned, the WiFi Pineapple will run on 12V... but only via the 2.1mm DC input jack.

v1.4.1 fixed my 3G modem connection... it works! Very much appreciated!

I've got a Huawei E173u USB modem that I'm dying to get working with my WiFi Pineapple... I will be following this thread with interest! Using a USB 3G modem is still quite foreign to me. I'm using this thread as a guide :- https://forums.hak5.org/index.php?/topic/26108-huawei-modems-with-a-pineapple-iv/ I hit a stumbling block trying to insert the kernel module root@Pineapple:/proc/tty/driver# insmod usbserial vendor=0x12d1 product=0x1436 insmod: can't insert 'usbserial': File exists I'm fortunate that my wireless ISP does not use NAT and I have a static publicly accessible IP address... easy access to the Pineapple! ***EDIT*** Firmware v1.4.1 has fixed this problem. Please disregard! Lunokhod.

Not a thread hijack... I see something similar while at work using the WiFi network (wlan1 in client mode). WiFi Pineapple configures and connects fine to the WiFi access point at work and things are peachy. Then randomly, sometimes after 10 minutes, sometimes an hour, sometimes a couple of hours... I cannot access the Pineapple via the client WiFi connection. It does not ping, no HTTP access, no SSH. The red LED is off. BUT...any client(s) connected to the WiFi Pineapple wlan0 AP radio seems to be fine. They have internet access though the Pineapple AND can access the WiFi Pineapple web management page. Not sure what is going on here when this happens. Restarting the WiFi Pineapple OR the work WiFi access point providing the internet access brings things back to life. I haven't noticed this on any other WiFi client device I use at work. This behaviour has been consistent through three firmware revisions. I don't have this problem at home using my Minitar UltraWAP WiFi access point, I can stay connected for days! I will try to get some logs next time. Lunokhod

Just out of interest and because I haven't done it before, I checked my WiFi Access Point (old Minitar UltraWAP) "associated clients" and found that my WiFi Pineapple wlan1 radio is connected at 54 Mbps. Is it just the throughput that get limited to 11 Mbps? My access point certainly thinks that an 802.11g radio is on the other end. Lunokhod

My WiFi Pineapple was upgraded smoothly to 1.4.0. I really like the web interface speed increase! The Karma Log Filters are most welcome! All around thumbs up! Many thanks to the Hak5/WiFi Pineapple team... this amazing device keeps on getting better and better... for NO additional cost!

I'm looking forward to this too!

Hi Everybody, I've recently bought my first smartphone... a Google Nexus 5. (I'm a long time Nokia fanboi) Is there anyway to optimize the Wifi Pineapple web interface "experience" when using a web browser on a smartphone. Chrome seems to be better than Firefox. The text in the tiles when using Firefox is TOO BIG! Chrome seems more like you would expect from a 1920x1080 display... but the text is very small and if I didn't have my glasses on I would not be able to read it. I'm forever zooming in and out to read what is going on. Can the WiFi Pineapple web server tailor the web pages for the device viewing them? Or is that asking too much of it? Lunokhod.

RandomRoll does not copy the index.php file from /sd/infusions/randomroll/assets/files/ it creates a sym link to the original file... this is fine. DNS caching is my main problem with RandomRoll not working. This is something that I can fix on my own machines... but not easy to circumvent if it happens on "someone else's" PC. :-) I'm more concerned that my carefully crafted index.php, error.php and redirect.php files in /www/ are not backed up before being removed by the infusion. The .orig ones stored in /sd/infusions/randomroll/assets/files/ are most certainly copied back to www when the the infusion is stopped. I can manually copy my files over (changing the suffix to .orig) and RandomRoll will replace them when it's stopped. Now I understand what is happening I can work around it. Lunokhod

Another "stupid" question on top of my previous post. I'm still trying to get RandomRoll working reliably... I've got v1.2 installed. When I start RandomRoll my existing existing /www index.php, error.php and redirect.php files are not copied into the /sd/infusions/randomroll/assets/files directory... with .orig suffix. I see the new index.php, roll .php file/s and roll folder symbolic links in /www. When I stop RandomRoll, the .orig files are copied back into the /www folder (with .php suffix) overwriting the files that are there. Is this what others are experiencing with RandomRoll?

Just be careful with the SMA connectors on the WiFi Pineapple. You can snap them like a twig or do damage to the PCB with an antenna like that... lots of leverage!

my WiFi Pineapple wlan0 is set at 18dBm wlan1 is 27 dBm

An exception to the 172.16.42.42 default gateway rule is when you connect wlan1 in client mode to a WiFi Access point to reach the internet. The WiFi Pineapple will use IP settings obtained from the DHCP server on the Wifi Access Point and the default gateway will point there instead of 172.16.42.42. You can see this in the Network tile. Lunokhod

Are you connecting the MkV directly to an existing Ethernet based network with it's own DHCP server/router/etc? The DHCP server on the MkV also works on the Ethernet port... it's configured to connect to a computer/laptop/client device and hand out an IP address. I tried changing the erh0 config in my Mk5 by disabling the built in DHCP server and assigning a fixed IP address so it could connect to an exisiting Ethernet network to access the internet. It sort of worked... but this also seemed to break a lot of stuff. It's probably not a good idea to have two fighing DHCP servers on a single wired network. I'm hoping that one day I can plug in a USB-Ethernet adapter into the Mk5 (2nd wired Ethernet eth1) and then connect this to an existing network for internet/admin access. It's the one method of getting internet connectivity to the MkV that has been overlooked. Lunokhod

I'm after some guidance on getting Random Roll v1.2 working on my WiFi Pineapple (firmware v1.3). I select the Roll I want, click on "Apply Selected Roll.", then click on "Start Random Roll". I see a brief message at the top informing me that Random Roll has started... and then a log entry below. dnsspoof: listening on br-lan [udp dst port 53 and not src 172.16.42.1] I confirm that DNSSpoof is running. ... and then nothing! Clients connected to the WiFi Pineapples wlan0 access point seem to be unaffected. Their web browsing either seems to work fine... or it stops altogether after some time of the Random Roll infusing running. What am I doing wrong? Any tips? Lunokhod

I've noticed something else weird with the Karma logs too... If I add a blacklisted client MAC address using the Karma GUI... it gets added fine and appears in the list. If I then check the log file "cat /tmp/karma-phy0.log" I see an entry stating, "There are now 1 MAC addresses in the list". If I then remove that MAC address I do not see a log entry about it being removed, but it no longer appears if I click "View List". If I then add a different MAC address using the GUI, the log file gets updated to say, "There are now 2 MAC addresses in the list"... even though I have removed the first MAC address! The web GUI only shows the 2nd added MAC address. The Karma web GUI does not show these log entries under the Karma Log tab. I'm also wondering in future versions of Karma can timestamp the log entries... I find that log entries are only partly useful if you don't know excatly when the events took place.

I'm having some minor trouble with URLSnarf too. It doesn't seem to start in a timely fashion after enabling it. I can click enable (on br-lan), enable auto-refresh and then it can take some minutes before things start appearing in the output window and log file... even when I know there is traffic on br-lan. is this normal?

While I've got a Karma thread happening... What criteria need to be met for a client to appear in the Karma Intelligence Report screen? I've left Karma running on an external antenna today and see a lot of these messages in Karma Log :- KARMA: Successful association of c4:62:ea:7a:61:1dKARMA: Successful association of 00:02:6f:34:fa:35 KARMA: Successful association of 10:68:3f:7a:15:ac KARMA: Successful association of 00:0a:eb:30:0f:23 ...but only this client has appeared in the Karma Intelligence Report :- 00:0a:eb:30:0f:23 172.16.42.183 android-78e774527501d209 Can anyone tell me why I'm seeing this?

Does HSTS affect the use of dns spoofing?

Nope I wasn't "Karma ed"... my kali laptop connects to "Free WiFi" of it's own accord. I have Windows laptop that has previously connected to other open WiFI access points (not Free WiFi) that Karma successfully works with. I just wanted to make sure that a seeing non Karma "assisted" connection appearing in the Karma tile was normal. Can't wait for black/white lists to be persistent. Sort of painful having to set them up each time the WiFi Pineapple is powered up.

Hi Everybody, I tried to find a specific help thread on Karma but couldn't... please move this to the appropriate thread if needed. I'm playing around with Karma during a quiet time at work and need some clarification how the black listing works. I have both Mk V wireless interfaces up and working. wlan0 is my Pineapple AP (SSID "Free WiFi"), wlan1 is in client mode and is connected to my works WPA protected WiFi Access Point for internet connectivity. Using my Kali laptop as an example, I entered the MAC address my laptops WiFi adapter in the Karma Client Blacklisting box and clicked add. Karma log does not seem to show that I added the MAC address. I purposely connect to the Mk V via "Free WiFi" for admin purposes, this works OK. But I do notice that my laptop appears in the Karma log section as having a successful association... even though my laptops WiFi adapter is blacklisted. Is this normal behaviour? Lunokhod