jmelody

So...... Anyone got that location where the AP's are stored? I've done some basic looking, but no joy. Edit: Found it! it's located at /etc/pineapple/ssid_file for anyone else interested.

koolkarnt, I am still playing with PineAP myself, but I think I can answer some of your questions. I have not played with the Source/Target section yet, Dogma seems to actually broadcast the AP's listed in the PineAP SSID Management section, and Auto Harvest will automatically add SSID's that devices are currently looking for to the SSID Management section. I have a simple question that I'm too lazy to search for myself. Where is the file for the SSID Management stored? My list became quite long during testing, and I would like to copy it to another file before deleting all of the collected AP's. When I enable Dogma, the list is so large that it takes several minutes for "most" of the names to be viewed by any device. I've even seen a device or two that quit trying all together after 10-20 AP's populated.

Sorry, my example was for wired connection to the pineapple with the end devices. The pineapple being used as the AccessPoint (AP) will use DHCP to give the connecting pineapple (the one using client mode) an address (I believe it will be 172.16.42.228). Is that not the case when you try to setup the network? I thought you were having trouble with the wired end not playing nice with the wireless network.

Though I'm no practitioner of law, but I believe Cooper is right. When someone "willingly" connects to you, they give "consent". Using Jasager/Karma to get a target to connect to you might be something difficult to defend in court. Naming your AP something that others have theirs named (even starbucks) should not be illegal. Just as I've talked to others about in person; Many people drive cars but don't know how to change their oil or a flat tire. They know that the key/button makes the car start, and they know how to make it go where they want. The same goes for wireless; They connect to one of those names on the wireless list, and they can type example.com to make it go where they want it. If you're not able to click the box that says "Auto connect to this network when in range", I see it being no different from ignoring the light that says "check engine".

Point-to-point would be something like 192.168.0.0/30 for the network. This leaves: 192.168.0.1 and 192.168.0.2 as the usable addresses. Seb has the easiest way to make what you want to do work. Use wlan1 as the client, and wlan0 as the access point If you have trouble make a backup of /etc/config/network first (name it something easy like network.orig). Then change /etc/config/network to a different network for the eth network (under the section named "config interface lan"). This should make the wired network different from the wireless network.

TIL using my MKV in public (for my own safety), and being a young looking white male with hair on my face, will be the cause of the police shooting me and my dog. I have to agree with some of the other posters here. 1. Go talk to someone with a similar interest as you 2. Leave because you feel unsafe 3. Deauth what? Your title says "clearly using it illegally". Your post says you see an antenna sticking out of a backpack. I live in the bible belt, and come across people with FOX News knowledge daily. Don't be that guy/gal who causes a fellow human more stress than they already have to deal with because you "know" their up to no good. When the fact is you're jumping to conclusions. Did you ever think that this person was keeping their pineapple in a backpack so people like you wouldn't point the righteous finger at them and proclaim "1337 H4x0r!!!"? As Sitwon posted, Collect as much evidence as you can. When I first got my pineapple, I was ecstatic when the smallest thing went right. I'm sure I did the Mr. Burns "Excellent" move countless times. Was I up to no good? Not in the slightest. Could I have been seen as doing something illegal to someone with your knowlage? Apparently.

Tiz an MKV for sure. Do we have an infusion that will plot the GPS locations on a map like the videos show, or was that plugged into the map after the fact? I've been using the Pineapple since the MKV came out. Until recently I felt alone, outside of our community, in knowing what it was and what it could do. Now, it seems, that people are at least familiar with the name Pineapple as a tool. I can't wait till DefCon for any new information we can get about the future of the MKV.

Can confirm what Seb is saying. I too watched the latest video, and was working on my spoofed webpage, when I decided to see if there was some code in evil portal infusion that I could use (there's not). After I installed the infusion my DNSspoof quit working. Upon reflashing the 1.4.1 firmware, everything worked as normal. Thanks for finding the change in nginx.conf though! I knew it was something to do with nginx, but it was just easier for me to reflash and start fresh.

I have tried using Chrome and Firefox (IE wouldn't load any tiles at all. I hate IE). I have tried disabling all add-ons, allowing pop-ups, and clearing the cache/history. Edit: New windows that I minimize seem to work fine. I will factory reset and see if this fixes the problem. Edit2: Re-flashed, reboot, problem solved.

So I thought I'd be cool and minimize all of the tabs I wasn't using. Now I can't get them back up to where I can use them. When I click on the box with the name, the tile goes away. When I refresh the page they come back as the minimized tiles again. Am I a nub?

Glad you pointed out the wlan 1 part. I almost replied with bad info. I have wlan1 connected in client mode to the internet, and wlan0 set up in AP mode. To avoid any further confusion I'll just place the output in question here (I edited some info for safety) Dec 21 20:45:10 Pineapple daemon.info hostapd: wlan0: STA 50:46:5d:xx:xx:xx WPA: group key handshake completed (RSN) Dec 21 20:43:00 Pineapple daemon.warn dnsmasq-dhcp[1826]: no address range available for DHCP request via wlan1 Dec 21 20:41:15 Pineapple daemon.info hostapd: wlan0: STA 50:46:5d:xx:xx:xx WPA: pairwise key handshake completed (RSN) Dec 21 20:41:15 Pineapple daemon.info hostapd: wlan0: STA 50:46:5d:xx:xx:xx IEEE 802.11: associated (aid 1) Dec 21 20:41:15 Pineapple daemon.info hostapd: wlan0: STA 50:46:5d:xx:xx:xx IEEE 802.11: authenticated Dec 21 20:39:15 Pineapple daemon.warn dnsmasq-dhcp[1826]: no address range available for DHCP request via wlan1 Dec 21 20:35:10 Pineapple daemon.info hostapd: wlan0: STA 50:46:5d:xx:xx:xx WPA: group key handshake completed (RSN) Dec 21 20:25:10 Pineapple daemon.info hostapd: wlan0: STA 50:46:5d:xx:xx:xx WPA: group key handshake completed (RSN) Dec 21 20:15:10 Pineapple daemon.info hostapd: wlan0: STA 50:46:5d:xx:xx:xx WPA: group key handshake completed (RSN) Dec 21 20:08:30 Pineapple daemon.info dnsmasq-dhcp[1826]: DHCPACK(br-lan) 172.16.42.228 50:46:5d:xx:xx:xx mydesktopcomputername Dec 21 20:08:30 Pineapple daemon.info dnsmasq-dhcp[1826]: DHCPREQUEST(br-lan) 172.16.42.228 50:46:5d:xx:xx:xx Dec 21 20:08:30 Pineapple daemon.info dnsmasq-dhcp[1826]: DHCPOFFER(br-lan) 172.16.42.228 50:46:5d:xx:xx:xx Dec 21 20:08:30 Pineapple daemon.info dnsmasq-dhcp[1826]: DHCPDISCOVER(br-lan) 50:46:5d:xx:xx:xx Dec 21 20:08:27 Pineapple daemon.info hostapd: wlan0: STA 50:46:5d:xx:xx:xx WPA: pairwise key handshake completed (RSN) Dec 21 20:08:27 Pineapple daemon.info hostapd: wlan0: STA 50:46:5d:xx:xx:xx IEEE 802.11: associated (aid 1) Dec 21 20:08:27 Pineapple daemon.info hostapd: wlan0: STA 50:46:5d:xx:xx:xx IEEE 802.11: authenticated Dec 21 20:08:16 Pineapple daemon.warn dnsmasq-dhcp[1826]: no address range available for DHCP request via wlan1 Dec 21 20:08:11 Pineapple kern.info kernel: [ 4257.250000] br-lan: port 1(eth0) entered disabled state Dec 21 20:08:11 Pineapple kern.info kernel: [ 4257.250000] eth0: link down Dec 21 20:07:32 Pineapple daemon.warn dnsmasq-dhcp[1826]: no address range available for DHCP request via wlan1 Dec 21 19:56:28 Pineapple daemon.warn dnsmasq-dhcp[1826]: no address range available for DHCP request via wlan1 Dec 21 19:55:46 Pineapple daemon.warn dnsmasq-dhcp[1826]: no address range available for DHCP request via wlan1 Dec 21 19:25:18 Pineapple daemon.info hostapd: wlan0: STA 30:85:a9:xx:xx:xx IEEE 802.11: deauthenticated due to local deauth request Dec 21 19:15:10 Pineapple daemon.info hostapd: wlan0: STA 30:85:a9:xx:xx:xx WPA: group key handshake completed (RSN) Dec 21 19:06:50 Pineapple daemon.info dnsmasq-dhcp[1826]: DHCPACK(br-lan) 172.16.42.161 30:85:a9:xx:xx:xx android-infoforTF700T Dec 21 19:06:50 Pineapple daemon.info dnsmasq-dhcp[1826]: DHCPREQUEST(br-lan) 172.16.42.161 30:85:a9:xx:xx:xx Dec 21 19:06:49 Pineapple daemon.info hostapd: wlan0: STA 30:85:a9:xx:xx:xx WPA: pairwise key handshake completed (RSN) Dec 21 19:06:49 Pineapple daemon.info hostapd: wlan0: STA 30:85:a9:xx:xx:xx IEEE 802.11: associated (aid 1) Dec 21 19:06:49 Pineapple daemon.info hostapd: wlan0: STA 30:85:a9:xx:xx:xx IEEE 802.11: authenticated Dec 21 19:05:29 Pineapple daemon.info dnsmasq[1826]: using local addresses only for domain lan Dec 21 19:05:29 Pineapple daemon.info dnsmasq[1826]: using nameserver 8.8.8.8#53 Dec 21 19:05:29 Pineapple daemon.info dnsmasq[1826]: using nameserver 192.168.0.1#53 Dec 21 19:05:29 Pineapple daemon.info dnsmasq[1826]: reading /tmp/resolv.conf.auto Dec 21 19:05:21 Pineapple user.notice firewall: Reloading firewall due to ifup of wan (wlan1) Dec 21 19:05:21 Pineapple daemon.notice netifd: Interface 'wan' is now up The part about eth0 "going into a disabled state" is there because I had it hooked up to the desktop computer, and removed it to test the USB wireless card. I have no problem connecting the devices to my AP upon normal start up of the pineapple, and Karma works fine too. I have to stop testing from time to time, and I am too lazy to keep rebooting the pineapple. If I were to deploy the pineapple with the problem I am having it would limit the available tagrets drasticly.

I have read some other posts about android connections dropping after some time. I am having an issue like that. I checked Karma logs and found nothing out of the ordinary. Syslog shows that the connection did get "deauthenticated due to local deauth" When I tried to reconnect with a TF700T (android tablet), and a Nexus5 (which was never connected to the pineapple), both fail to get a DHCP/drop the connection instantly. The Syslog shows that as "no address range available for DHCP request via wlan1" The funny thing is I am able to get a connection from a desktop using a USB wireless card. Is there something, like a config file, that I've missed?

Can confirm, the mark v antennas work well.

I see there have been some views made on this topic, so I'll post some other progress. After installing SteamOS, I was able to dual boot Xubuntu 13.04 via the normal install process. Everything seems to work just fine, but I am short on space to install games on the SSD. I have harvested a 320gb drive from an older computer, and will be placing the SteamOS install on that. If anyone is intrested, I can also make a VirtualBox installation. From what I can gather, running Steam on a Windows PC will allow you to stream Windows games to the VM.

Yes the switch needs to be in the "on" position with the 1800 as well

I rebooted and plugged in my HDD that has games installed, but haven't found a way to mount it yet. When I use nautilus the drive is there, but won't let me mount it. Using sudo makes the drives go away. Hopefully this will get someone started. Games can be downloaded to the OS drive using the normal methods, but I'm limited on space on this drive.

So I wanted to share with everyone how I installed SteamOS. There are other guides out there, but this one uses Hak5 equiptment, so I'm posting it here. Please note: THIS WILL WIPE YOUR DRIVE. Do not install this on something you are wanting to use for anything other than SteamOS! Reddit has topics on installing on a VM, dual booting, ect. Go check out reddit.com/r/steamos for more on that. First off, download the SteamOS installer from http://repo.steampowered.com/download/SteamOSInstaller.zip Other things you'll need: A MOBO that supports UEFI bios WiFi Pineapple (I am using a Mark V, but others should work too as long as you can get client mode) USB drive (I had problems with a Kingston DT101, so I used a Cruzer Fit that came with a black friday order from the Hak shop) processor that is 64bit ready (most modern processors) Nvidia GPU (work arounds can be found on reddit for AMD/Intel) hard drive you don't need the data off of (I used a 64gb SSD that had Xubuntu 13.04 on it) some Linux CLI smarts (It should work without this, but it's good to know what your doing) 1. Start by formatting the USB to the default FAT32 format. This takes off any preloaded items that may cause problems. 2. Next unzip the installer to the root of the USB. Do not unzip then copy the folders. I read that this leaves out something the installer looks for, but try it if you want. 3. Shut down your computer 4. (Optional) Unplug any hard drives you want to keep the data on 5. Restart your computer and boot from the "UEFI usbvendornamehere" drive 6. Select the Autoinstall option (I tried the expert install with the Kingston DT101 drive and it tried to install it to the same drive it was reading from) 7. Let the installer do its thing (make sure you read the nottice and pull the USB before your reboot) 8. Boot into the new OS 9. Change the login to use the GNOME session and use login name: steam pass: steam All of that was straight forward and can be found in the FAQ http://steamcommunity.com/groups/steamuniverse/discussions/1/648814395741989999/ Next the instructions say to run steam and accept the EULA blah blah blah. If your using wireless, you'll nottice that the firmware is missing. This is where I come in to help our community. Bust out your Pineapple (I assume you have already used it and it is connected as a client to your WiFi), and plug it into your Ethernet. Sweet, now you have an internet connection. The instructions Steam provides says to run steam to get the EULA, but they didn't put an icon on the desktop to make it easy. Click the "Activities" button and then click the "Applications" button. Select the "Terminal" and just type "steam" (no "s) and hit enter. You should get the EULA. Sign your life, and first born child, over to Gaben and let it run. After it has finished updating, log out of the account. This time you won't need to log into GNOME, so just enter the login name: desktop pass: desktop Get back to the Terminal, like we got there before, and enter ~/post_logon.sh and hit enter. Let it do its thing. The screen will go blank, and text will scroll on the screen. When it gets to the end you will have to choose (y/n)...... choose y and hit enter (this is for the recovery). When it's done reboot, and you'll be in the SteamOS. This is basicly "Big Picture" mode, and to get back to a desktop enviornment: press Ctrl+Alt+F2 you will be prompted to login from the CLI (use the desktop or steam login and password) to get a GUI type startx and hit enter if you want to use root you need to make a password by opening a terminal and typing passwd and pressing enter.