Jump to content

funnybunny

Active Members
  • Posts

    21
  • Joined

  • Last visited

Everything posted by funnybunny

  1. I was in the process of wget the upgrade-1.0.1.bin to the shark jack and unsure if it finished. The wget was uploading to the default directory location upon initial SSH connection. I suspect the power could have gone out. There was a red blue light combo before all lights went out. Didn't find a red blue light combo in the description. Now there are no lights what so ever when I charge. Flipping the selection switch to Arm or Attack has no lights what so ever. Following the above unofficial reset doesn't appear to be working either. I dont get the html page on 192.168.1.1. Any other ideas on resetting? Thanks. Update: If I plug the RJ45 in and turn the switch to Arm after 7 seconds a green light flashes once. No other lights after. Not sure what that is.
  2. OK so modified the spoofhost (2.19.81.119 whitehouse.gov) address=/cnn.com/2.19.81.119 address=/www.cnn.com/2.19.81.119 address=/foxnews.com/2.19.81.119 address=/www.foxnews.com/2.19.81.119 the DHCP works now and the PS receives an IP ping www.cnn.com reports 2.19.81.119 ping www.foxnews.com reports 2.19.81.119 nslookup www.cnn.com reports 2.19.81.119 nslookup www.foxnews.com reports 2.19.81.119 use firefox to browse cnn.com or www.cnn.com it results in a "invalid URL" page use firefox to browse foxnews.com or www.foxnews.com it actually goes to the correct web page my understanding is that going to cnn.com on a machine behind the PS should go to the web page 2.19.81.119 whitehouse.gov but it does not same with foxnews.com
  3. Ah maybe I'm not clear on the use of dnsspoof. Appears that is only going to redirect traffic to the PS. In your example when someone want to go to <ps>.com it will send it to the PS IP 172.16.32 1 assuming there will be a fake site there? My issue involves more the fact that I'm not getting an IP from DHCP therefore the client is not able to surf the internet. Works on the tcpdump and openvpn switches and gets an IP so not quite sure why it's not working. Tried on Windows and Linux
  4. how I got OpenVPN to work on my packet squirrel (PS) i have a seedbox out in the cloud with OpenVPN installed downloaded the *.ovpn file to payloads/switch3 as config.ovpn modified the config.ovpn file where it says auth-user-pass to auth-user-pass pass.txt created a pass.txt file under payloads/switch3 with the username and password for the OpenVPN login username password i'm sure there is a way to mask these instead of plain text i had to change payloads/switch3/payload.sh to get the client to get out to the internet # Set to 1 to allow clients to use the VPN FOR_CLIENTS=0 to # Set to 1 to allow clients to use the VPN FOR_CLIENTS=1 attached the PS to the network i wanted access to remotely it established the connection to my seedbox the seedbox showed a tun0 connection with ifconfig command 10.10.10.14 from the seedbox I ssh'd to the PS through the tunnel ssh root@10.10.10.14 logged in and presented with the PS banner
  5. wanted to determine if anyone else is having issue with switch2 DNSSpoof of the packet squirrel (PS) firmware v1.2 reloaded twice default switch2\payload.sh modified switch2\spoofhost with address=/www.cnn.com/www.foxnews.com i have got both switch1 TCPDump and switch3 OpenVPN to work flawlessly switch2 the client computer connected to the PS does not receive an IP therefore is not able to surf the internet for spoofing to even be a problem when connected to the same client computer switch1 receives an IP and records network traffic and the client computer is able to browse the internet when connected to the same client computer switch3 receives an IP, starts OpenVPN connection to seedbox, seedbox tun0 active and SSH back through the tunnel is successful to the PS i understand the DNSSpoof switch2 being more just a trickery option and more than likely something not used in the wild except for screwing with friends point being i'm wondering if something wrong with my PS
  6. The 5V usb isn't enough power. Should power the MKV only. Thought process behind this is that the MKV requires power and the USB also. USB shares 5v to power its attached device if that is the limit to the power being provided its clearly not enough for both MKV and USB devices. What power can I feed my WiFi Pineapple MKV? The WiFi Pineapple MKV will take anything between 5V and 12V. Please note however that it is happiest (if under load, external devices etc) if it has 9-12 Watts of power. This means the following three power configurations are advisable: 9V 1A (9 Watts), 5V 2A (10 Watts), 12V 1A (12 Watts). Some success here: https://forums.hak5.org/index.php?/topic/26412-how-to-power-the-pineapple-for-mobile-usage/ Appears the trick is to find a power source that will supply 12V 1A especially if you’re using the USB port.
  7. Recommend attaching to your AP SSID (Internet) with wlan1 to establish the connection using the gui Network tile. It should reconnect upon reboot. Setup a dip switch autostart PineAP and Karma. pineapple karma start; sleep 2; pineapple infusion pineap start; sleep 30; pineapple infusion pineap dogma start; sleep 2; pineapple infusion pineap responder start; sleep 2; pineapple infusion pineap harvester start reboot with the dip switch setting This has worked for me to automatically start PineAP and Karma with client connection using wlan1 to my cell phone and home AP.
  8. My MKV is configured with PineAP and Karma on. I have one wifi client connected which is a S3 samsung phone and connected via PineAP faked wifi "guest". Only the wlan0 and wlan1 are available, no USB wlan device. Eth0 is not providing internet. Wlan1 is connected to my SSID wifi providing internet. Wlan0 pulls in the clients. This is the radio that clients connect to. Wlan1 is put into monitor mode, does beacon responses, beacons, deauth etc. Since the onset of v2.3.0 you have the capability to use wlan1 to also provide internet access also for your clients. The S3 client is able to browse the internet. I have infusion urlsnarf running when I went to cnn.com. I'm connected via laptop to the MKV by the Secure Management Access Point SSID under Network --> Access Point. The MKV is currently providing internet for my kali to create this post using wlan1 to go out to the internet. Using the infusion Connected Clients we can see both the S3 and my kali laptop connected via wlan0/wlan0-1. Can't say I did anything funky to change the MKV, thought that was how it was designed.
  9. According to the lastest firmware 2.3.0, it is not required to use wlan2 for Internet. Wlan1 can be used for providing Internet access while running PineAP. (https://forums.hak5.org/index.php?/topic/35117-release-23x-codename-logasaurus/) Under Network using wlan1 scan and connect to your SSID. Start PineAP and Karma. I have had sometime where the red light (wlan1) goes out after starting PineAP. Blue light for wlan0. Both blue and red lights should be on. Reboot with PineAP and Karma autostarting if your red light goes out. Wlan1 should automatically connect to your SSID as previously selected. I do not get an Internet IP on the Network tile when I select "Show". Not sure why this is but it is connected to the Internet. If you ssh to your MKV, see if you can ping 8.8.8.8. If your successful then you have Internet. Another tile that doesn't appear to work correctly in this setting is pineapple bar. Also unknown why.
  10. Has anybody seem this error and then had a reboot? I'm only showing three here but there are a lot more during my logread -f command output. Seems to be pretty consistent. I get two or three clients connecting and then reboot. Set up; firmware v2.3.0 wlan2 (ALFA USB WiFi AWUS036NEH) connected to MKV as client to internet PineAP and Karma running logread -f Jun 22 18:29:43 Pineapple kern.warn kernel: [ 348.470000] ieee80211 phy2: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 14 in queue 0 Jun 22 18:29:43 Pineapple kern.warn kernel: [ 348.480000] ieee80211 phy2: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 14 in queue 0 Jun 22 18:29:43 Pineapple kern.warn kernel: [ 348.490000] ieee80211 phy2: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 14 in queue 0
  11. You say your trying to run programs remotely using dip switches. I'm going to assume you mean you want programs on the MKV to start automatically using the dip switches. To run programs remotely technically that would be connecting to the MKV via ssh and then running a program on the MKV. Correct me if I'm wrong in my assumption. So depending on your commands written into the dip switches will ultimately determine if information is getting over written. If your command for example is: urlsnarf -i br-lan > urlsnarf.log then every time your command is run it will over write the log file. I've been playing around with some dip switch commands and I'm hoping others will chime in. This particular dip switch setting will merely sniff url traffic so nothing MKV intensive. Should not reboot your MKV. Obviously the more programs and connected devices you have running will ultimately impact the MKV's resources. I first started with the pineapple command. ssh to your MKV We see that pineapple has sub commands that need to be issued. Like starting Karma would be: pineapple karma start Karma hosts spoofed APs. This is going to be critical if we want our victims to connect to us. Now PineAP is an infusion. So the next item to start would be PineAP. pineapple infusion pineap start Getting the rest started will be: pineapple infusion pineap dogma start pineapple infusion pineap responder start pineapple infusion pineap harvester start Now another one that might be important for you is to clear the ssids for your active list. This comes into play when its a new area that you want to attack. If you find your current list is nice then don't kill your list and only build onto it. pineapple infusion pineap clear_ssids I've taken two dip switches here and added the clear_ssids but the other does not. Again options. I've also added some sleep times to the command. In my experience it plays nicer if there is a little time between commands. Each command is proceeded by a ; Now at the end of starting Karma and PineAP I then start urlsnarf. pineapple karma start; sleep 2; pineapple infusion pineap start; sleep 2; pineapple infusion pineap clear_ssids; sleep 2; pineapple infusion pineap dogma start; sleep 2; pineapple infusion pineap responder start; sleep 2; pineapple infusion pineap harvester start; sleep 2; bash /sd/infusions/urlsnarf/includes/autostart.sh you should call the program which will start the shell script and in the case of MKV we use bash bash /sd/infusions/urlsnarf/includes/autostart.sh my infusions I installed on my SD because there is more storage space. this comes in handy as large file sizes can be generated by some programs. A lot of the infusions have there own shell scripts to start themselves. You will also see that they store there information in certain locations as default. You could change these if you wanted. Problem will be having them show in your http of the MKV. These script have variables imbedded to prevent overwriting. Hope this helps.
  12. so you followed the http://wiki.wifipineapple.com/#!ics.md specifically the Internet Connection Sharing for Windows no Windows firewall or it is disabled or specifically allowed by IP? no third party ex: McAfee / Symantec firewall / AV products installed or they are disabled or specifically allowed by IP or port (1471)? if you've followed the ICS directions for Windows your LAN IP should be 172.16.42.42 / 255.255.255.0 and you should also have an internet connection probably WIFI from the sony to your internet router...this should facilitate the internet connection between the two devices on your laptop |-----------| |--------------| | Internet | | Sony PC | | Router -|-----------------|-Wifi Adapter | |192.168.1.1| Wifi Connection | 192.168.1.2 | |-----------| | LAN Adapter | |--------|-172.16.42.42 | | |--------------| |-----------| | | MKV -|--------| |172.16.42.1| Ethernet |-----------| connect to your MKV through the sony via SSH...assuming you know how to use putty.exe? attempt to ping your internet router IP...successful? If not then there is something wrong with ICS. I tested Win8.1 ICS procedures to see if there are any differences and notice a message confirmation that it automatically changes the Ethernet to a static IP of 192.168.137.1. Make sure your LAN adapter didn't get changed to 192.168.137.1. If so change back to 172.16.42.42 / 255.255.255.0 and DNS 8.8.8.8 I had Symantec Endpoint Security installed and had to disable to get internet to work on MKV.
  13. This is a little crud but might help some people in the mean time if they are experiencing their SSIDs being replicated. ssh to your MKV cd /sd nano remove_these_ssid.sh copy and paste...replace <YOUR SSID> here #!/bin/bash sed -i '/<YOUR SSID>/d' /etc/pineapple/ssid_file exit 0 save (ctrl+o) exit (ctrl+x) chmod +x /sd/remove_these_ssid.sh add * * * * * /sd/remove_these_ssid.sh to configuration --> schedule task and save should remove your SSID from the fake list every minute
  14. I'll try to reproduce again. Stock loaded firmware 2.3.0 with no infusions. Connected via laptop eth0 (kali) to MKV. Power via MKV provided wall power. ./wp5.sh to provide internet Laptop connect to SSID 3MTA3_nomap, Linksys e4200 Tomato Firmware 1.28, via Kali wifi. Internet functioning PineAP --> Karma --> add 3MTA3_nomap to SSID black list black mode Karma log still set to /tmp All PineAP started ssh connection with top running just after starting PineAP added a spare cell phone via wifi to SSID 3MTA3_nomap to beacon the request reviewed karma log and found 3MTA3_nomap after the cell phone beacon MKV set to UTC reviewed current active faked SSIDs and 3MTA3_nomap is there Let me know if I'm doing something wrong. That last SSID is pretty funky. Anyway...focus. Hey do you think its because of the _ ? Cleared SSIDs, black list, karma log. Change wifi AP to 3MTA3. Reconnected to 3MTA3 SSID on kali laptop. ./wp5.sh again Internet still good and PineAP off. Added 3MTA3 to SSID black list in black mode Sorry reached my image limit in the forum so bear with me. All PineAP started. Added cell beacon to 3MTA3. 3MTA3 shows in PineAP. Shows as faked also. So not the _ Maybe my MKV is sP3ci4L...
  15. To prevent your own SSIDs from being faked you should black list them. Now there is an issue within firmware 2.3.0 where some SSIDs are not getting black listed. I went back to firmware 2.2.0 and the black list is working fine.
  16. Your title indicates you can't connect to the Internet, correct? But you can connect to the MKV? What Firmware are you on? Are you connected to the MKV via ethernet cable with your Sony? Have you tried: http://wiki.wifipineapple.com --> Guides --> Internet Connection Sharing ?
  17. Yes I can reproduce. Firmware flash factory.bin 2.0.4. Firmware upgrade to 2.3.0. eth0 --> Kali 172.16.42.42 for Internet PineAP tile --> Karma tab --> SSID Black mode --> added WOPR_nomap, Roomba (Secure Management Access Point), 3MTA3_nomap, and WOPR karma log still set to /tmp/ After about 10min WOPR_nomap appears in PineAP list. Hosting as an open network. karma log Jun 7 22:53:30 Probe Request from 00:25:ae:##:##:## for SSID 'SkyNet' Jun 7 22:53:23 Probe Request from 78:4b:87:##:##:## for SSID 'guest' Jun 7 22:53:14 Probe Request from 8c:7b:9d:##:##:## for SSID 'Bumpk1ns2' Jun 7 22:53:12 Probe Request from 80:96:b1:##:##:## for SSID 'Wang Chung' Jun 7 22:53:10 Probe Request from 28:10:7b:##:##:## for SSID 'KPCY2' Jun 7 22:53:10 Probe Request from 28:10:7b:##:##:## for SSID 'KPCY2' Jun 7 22:53:09 Probe Request from 6c:ad:f8:##:##:## for SSID 'WOPR_nomap' Jun 7 22:53:09 Probe Request from fc:c2:de:##:##:## for SSID '3MTA3_nomap' Jun 7 22:53:04 Probe Request from 28:10:7b:##:##:## for SSID 'KPCY2' Jun 7 22:52:58 Probe Request from 28:10:7b:##:##:## for SSID 'KPCY2' Jun 7 22:52:54 Probe Request from fc:c2:de:##:##:## for SSID '3MTA3_nomap' Jun 7 22:52:48 Probe Request from 28:10:7b:##:##:## for SSID 'KPCY2' Jun 7 22:52:44 Probe Request from 50:1a:c5:##:##:## for SSID 'XN2HQ' Jun 7 22:52:43 Probe Request from 8c:7b:9d:##:##:## for SSID 'Bumpk1ns2' Jun 7 22:52:36 Probe Request from 28:10:7b:##:##:## for SSID 'KPCY2' Jun 7 22:52:33 Probe Request from 8c:7b:9d:##:##:## for SSID 'Bumpk1ns2' Jun 7 22:52:32 Probe Request from 28:10:7b:##:##:## for SSID 'KPCY2' Jun 7 22:52:16 Probe Request from fc:c2:de:##:##:## for SSID '3MTA3_nomap' Jun 7 22:52:14 Probe Request from 80:96:b1:##:##:## for SSID 'Wang Chung' Jun 7 22:52:08 Probe Request from 6c:ad:f8:##:##:## for SSID 'WOPR_nomap' Jun 7 22:52:08 Probe Request from f4:09:d8:##:##:## for SSID 'BustersBrounce' Jun 7 22:52:07 Probe Request from 28:10:7b:##:##:## for SSID 'KPCY2' Jun 7 22:52:06 Probe Request from 28:10:7b:##:##:## for SSID 'KPCY2' Jun 7 22:52:05 Probe Request from 78:4b:87:##:##:## for SSID 'guest' Jun 7 22:51:48 Probe Request from 80:96:b1:##:##:## for SSID 'Wang Chung' Jun 7 22:51:41 Probe Request from 8c:7b:9d:##:##:## for SSID 'Bumpk1ns2' Jun 7 22:51:39 Probe Request from 78:4b:87:##:##:## for SSID 'guest' Jun 7 22:51:37 Probe Request from f4:09:d8:##:##:## for SSID 'BustersBrounce' Jun 7 22:51:35 Probe Request from 28:10:7b:##:##:## for SSID 'KPCY2' Jun 7 22:51:31 Probe Request from 8c:7b:9d:##:##:## for SSID 'Bumpk1ns2' Jun 7 22:51:18 Probe Request from 28:10:7b:##:##:## for SSID 'KPCY2' Jun 7 22:51:11 Probe Request from 28:10:7b:##:##:## for SSID 'KPCY2' Jun 7 22:51:09 Probe Request from 78:4b:87:##:##:## for SSID 'guest' Jun 7 22:51:08 Probe Request from 80:96:b1:##:##:## for SSID 'Wang Chung' Jun 7 22:51:06 Probe Request from 6c:ad:f8:##:##:## for SSID 'WOPR_nomap' Jun 7 22:51:06 Probe Request from f4:09:d8:##:##:## for SSID 'BustersBrounce' Jun 7 22:51:04 Probe Request from 28:10:7b:##:##:## for SSID 'KPCY2' Jun 7 22:51:02 Probe Request from 28:10:7b:##:##:## for SSID 'KPCY2' Jun 7 22:51:00 Probe Request from fc:c2:de:##:##:## for SSID '3MTA3_nomap' Jun 7 22:50:51 Probe Request from 80:96:b1:##:##:## for SSID 'Wang Chung' Jun 7 22:50:48 Probe Request from 28:10:7b:##:##:## for SSID 'KPCY2' Jun 7 22:50:47 Probe Request from 34:23:ba:##:##:## for SSID 'BustersBrounce' Jun 7 22:50:44 Probe Request from 50:1a:c5:##:##:## for SSID 'XN2HQ' Jun 7 22:50:42 Probe Request from 28:10:7b:##:##:## for SSID 'KPCY2' Jun 7 22:50:32 Probe Request from 28:10:7b:##:##:## for SSID 'KPCY2' Jun 7 22:50:30 Probe Request from 28:10:7b:##:##:## for SSID 'KPCY2' Jun 7 22:50:29 Probe Request from 8c:7b:9d:##:##:## for SSID 'Bumpk1ns2' Jun 7 22:50:13 Probe Request from 80:96:b1:##:##:## for SSID 'Wang Chung' Jun 7 22:50:10 Probe Request from 00:11:95:##:##:## for SSID '92I33' Jun 7 22:50:05 Probe Request from 28:10:7b:##:##:## for SSID 'KPCY2' Jun 7 22:50:04 Probe Request from 6c:ad:f8:##:##:## for SSID 'WOPR_nomap' Jun 7 22:49:58 Probe Request from 80:96:b1:##:##:## for SSID 'Wang Chung' Jun 7 22:49:52 Probe Request from 28:10:7b:##:##:## for SSID 'KPCY2' Jun 7 22:49:44 Probe Request from 50:1a:c5:##:##:## for SSID 'XN2HQ' Jun 7 22:49:37 Probe Request from 28:10:7b:##:##:## for SSID 'KPCY2' Jun 7 22:49:32 Probe Request from 80:96:b1:##:##:## for SSID 'Wang Chung' Jun 7 22:49:28 Probe Request from 8c:7b:9d:##:##:## for SSID 'Bumpk1ns2' Jun 7 22:49:10 Probe Request from f4:09:d8:##:##:## for SSID 'BustersBrounce' Jun 7 22:49:06 Probe Request from 28:10:7b:##:##:## for SSID 'KPCY2' Jun 7 22:49:06 Probe Request from 28:10:7b:##:##:## for SSID 'KPCY2' Jun 7 22:49:04 Probe Request from 28:10:7b:##:##:## for SSID 'KPCY2' Jun 7 22:49:03 Probe Request from 6c:ad:f8:##:##:## for SSID 'WOPR_nomap' Jun 7 22:48:49 Probe Request from f4:09:d8:##:##:## for SSID 'BustersBrounce' Jun 7 22:48:40 Probe Request from 80:96:b1:##:##:## for SSID 'Wang Chung' Jun 7 22:48:38 Probe Request from 28:10:7b:##:##:## for SSID 'KPCY2' Jun 7 22:48:36 Probe Request from 28:10:7b:##:##:## for SSID 'KPCY2' Jun 7 22:48:36 Probe Request from 28:10:7b:##:##:## for SSID 'KPCY2' Jun 7 22:48:22 Probe Request from 28:10:7b:##:##:## for SSID 'KPCY2' Jun 7 22:48:16 Probe Request from 28:10:7b:##:##:## for SSID 'KPCY2' Jun 7 22:48:12 Probe Request from f4:09:d8:##:##:## for SSID 'BustersBrounce' Jun 7 22:48:05 Probe Request from 28:10:7b:##:##:## for SSID 'KPCY2' Jun 7 22:48:02 Probe Request from 78:4b:87:##:##:## for SSID 'guest' Jun 7 22:48:01 Probe Request from 6c:ad:f8:##:##:## for SSID 'WOPR_nomap' Jun 7 22:47:57 Probe Request from 28:10:7b:##:##:## for SSID 'KPCY2' Jun 7 22:47:46 Probe Request from 78:4b:87:##:##:## for SSID 'guest' Jun 7 22:47:44 Probe Request from 00:11:95:##:##:## for SSID '92I33' Jun 7 22:47:33 Probe Request from a4:77:33:##:##:## for SSID '9DQLS' Jun 7 22:47:30 Probe Request from 00:00:48:##:##:## for SSID '6GOR5' Jun 7 22:47:24 Probe Request from 8c:7b:9d:##:##:## for SSID 'Bumpk1ns2' Jun 7 22:47:22 Probe Request from 28:10:7b:##:##:## for SSID 'KPCY2' Jun 7 22:47:11 Probe Request from 28:10:7b:##:##:## for SSID 'KPCY2' Jun 7 22:47:06 Probe Request from 28:10:7b:##:##:## for SSID 'KPCY2' Jun 7 22:47:05 Probe Request from 00:25:ae:##:##:## for SSID 'SkyNet' Jun 7 22:47:04 Probe Request from 28:10:7b:##:##:## for SSID 'KPCY2' Jun 7 22:47:04 Probe Request from 34:23:ba:##:##:## for SSID 'BustersBrounce' Jun 7 22:46:59 Probe Request from 6c:ad:f8:##:##:## for SSID 'WOPR_nomap' Jun 7 22:46:50 Probe Request from 00:25:ae:##:##:## for SSID 'SkyNet' Jun 7 22:46:44 Probe Request from 50:1a:c5:##:##:## for SSID 'XN2HQ' Jun 7 22:46:43 Probe Request from 78:4b:87:##:##:## for SSID 'guest' Jun 7 22:46:42 Probe Request from 28:10:7b:##:##:## for SSID 'KPCY2' Jun 7 22:46:42 Probe Request from 28:10:7b:##:##:## for SSID 'KPCY2' Jun 7 22:46:42 Probe Request from 28:10:7b:##:##:## for SSID 'KPCY2' Jun 7 19:16:50 Probe Request from b0:e8:92:##:##:## for SSID 'BustersBrounce' Jun 7 19:16:49 Probe Request from 28:10:7b:##:##:## for SSID 'KPCY2' Jun 7 19:16:48 Probe Request from 78:4b:87:##:##:## for SSID 'guest' Jun 7 19:16:38 Probe Request from 00:11:95:##:##:## for SSID '92I33' Jun 7 19:16:34 Probe Request from 28:10:7b:##:##:## for SSID 'KPCY2' Jun 7 19:16:32 Probe Request from 28:10:7b:##:##:## for SSID 'KPCY2' Jun 7 19:16:32 Probe Request from f4:09:d8:##:##:## for SSID 'BustersBrounce' Jun 7 19:16:23 Probe Request from 28:10:7b:##:##:## for SSID 'KPCY2' Jun 7 19:16:10 Probe Request from 78:4b:87:##:##:## for SSID 'guest' Jun 7 19:16:05 Probe Request from 28:10:7b:##:##:## for SSID 'KPCY2' Jun 7 19:16:04 Probe Request from 28:10:7b:##:##:## for SSID 'KPCY2' Jun 7 19:16:01 Probe Request from f4:09:d8:##:##:## for SSID 'BustersBrounce' Jun 7 19:15:40 Probe Request from f4:09:d8:##:##:## for SSID 'BustersBrounce' Jun 7 19:15:39 Probe Request from 28:10:7b:##:##:## for SSID 'KPCY2' Jun 7 19:15:36 Probe Request from 00:11:95:##:##:## for SSID '92I33' Jun 7 19:15:35 Probe Request from 00:25:ae:##:##:## for SSID 'SkyNet' Jun 7 19:15:33 Probe Request from 28:10:7b:##:##:## for SSID 'KPCY2' Jun 7 19:15:32 Probe Request from 28:10:7b:##:##:## for SSID 'KPCY2' Jun 7 19:15:19 Probe Request from f4:09:d8:##:##:## for SSID 'BustersBrounce' Jun 7 19:15:15 Probe Request from 28:10:7b:##:##:## for SSID 'KPCY2' Jun 7 19:15:09 Probe Request from 78:4b:87:##:##:## for SSID 'guest' Jun 7 19:15:08 Probe Request from 28:10:7b:##:##:## for SSID 'KPCY2' Jun 7 19:15:04 Probe Request from 00:25:ae:##:##:## for SSID 'SkyNet' Jun 7 19:15:02 Probe Request from 28:10:7b:##:##:## for SSID 'KPCY2' Jun 7 19:15:00 Probe Request from b0:e8:92:##:##:## for SSID 'BustersBrounce' Jun 7 19:14:53 Probe Request from 78:4b:87:##:##:## for SSID 'guest' Jun 7 19:14:44 Probe Request from f4:09:d8:##:##:## for SSID 'BustersBrounce' Jun 7 19:14:43 Probe Request from 00:11:95:##:##:## for SSID '92I33' Jun 7 19:14:36 Probe Request from 28:10:7b:##:##:## for SSID 'KPCY2' Jun 7 19:14:32 Probe Request from 28:10:7b:##:##:## for SSID 'KPCY2' Jun 7 19:14:26 Probe Request from fc:c2:de:##:##:## for SSID 'osf_comm' Jun 7 19:14:26 Probe Request from fc:c2:de:##:##:## for SSID 'OSF_COMM_1' Jun 7 19:14:20 Probe Request from f4:09:d8:##:##:## for SSID 'BustersBrounce' Jun 7 19:14:04 Probe Request from 28:10:7b:##:##:## for SSID 'KPCY2' Jun 7 19:14:03 Probe Request from 28:10:7b:##:##:## for SSID 'KPCY2' Jun 7 19:13:59 Probe Request from f4:09:d8:##:##:## for SSID 'BustersBrounce' Jun 7 19:13:54 Probe Request from 28:10:7b:##:##:## for SSID 'KPCY2' Jun 7 19:13:41 Probe Request from 00:11:95:##:##:## for SSID '92I33' Jun 7 19:13:33 Probe Request from 28:10:7b:##:##:## for SSID 'KPCY2' Jun 7 19:13:10 Probe Request from 78:4b:87:##:##:## for SSID 'guest' Jun 7 19:13:08 Probe Request from 28:10:7b:##:##:## for SSID 'KPCY2' Jun 7 19:13:05 Probe Request from f4:09:d8:##:##:## for SSID 'BustersBrounce' Jun 7 19:13:04 Probe Request from 78:4b:87:##:##:## for SSID 'WOPR_nomap' Jun 7 19:12:59 Probe Request from 78:4b:87:##:##:## for SSID 'guest' Jun 7 19:12:54 Probe Request from 00:25:ae:##:##:## for SSID 'SkyNet' Jun 7 19:12:42 Probe Request from 28:10:7b:##:##:## for SSID 'KPCY2' Jun 7 19:12:39 Probe Request from 00:11:95:##:##:## for SSID '92I33' Jun 7 19:12:32 Probe Request from 28:10:7b:##:##:## for SSID 'KPCY2' Jun 7 19:12:31 Probe Request from f4:09:d8:##:##:## for SSID 'BustersBrounce' Jun 7 19:12:17 Probe Request from 50:1a:c5:##:##:## for SSID 'XN2HQ' Jun 7 19:12:05 Probe Request from f4:09:d8:##:##:## for SSID 'BustersBrounce' Jun 7 19:12:01 Probe Request from 28:10:7b:##:##:## for SSID 'KPCY2' Jun 7 19:12:01 Probe Request from 78:4b:87:##:##:## for SSID 'guest' Jun 7 19:11:42 Probe Request from f4:09:d8:##:##:## for SSID 'BustersBrounce' Jun 7 19:11:37 Probe Request from 00:11:95:##:##:## for SSID '92I33' Jun 7 19:11:31 Probe Request from 28:10:7b:##:##:## for SSID 'KPCY2' Jun 7 19:11:28 Probe Request from 78:4b:87:##:##:## for SSID 'guest' Jun 7 19:11:26 Probe Request from 28:10:7b:##:##:## for SSID 'KPCY2' Jun 7 19:11:22 Probe Request from 00:c0:ca:##:##:## for SSID 'WOPR_nomap' Jun 7 19:11:17 Probe Request from 50:1a:c5:##:##:## for SSID 'XN2HQ' Jun 7 19:11:14 Probe Request from 00:c0:ca:##:##:## for SSID 'WOPR_nomap' Jun 7 19:11:09 Probe Request from f4:09:d8:##:##:## for SSID 'BustersBrounce' Jun 7 19:11:09 Probe Request from 78:4b:87:##:##:## for SSID 'guest' Jun 7 19:11:06 Probe Request from 28:10:7b:##:##:## for SSID 'KPCY2' Jun 7 19:11:04 Probe Request from 28:10:7b:##:##:## for SSID 'KPCY2' Jun 7 19:10:55 Probe Request from 28:10:7b:##:##:## for SSID 'KPCY2' Jun 7 19:10:48 Probe Request from 28:10:7b:##:##:## for SSID 'KPCY2' Jun 7 19:10:45 Probe Request from 00:11:95:##:##:## for SSID '92I33' Jun 7 19:10:44 Probe Request from 28:10:7b:##:##:## for SSID 'KPCY2' Jun 7 19:10:39 Probe Request from 00:25:ae:##:##:## for SSID 'SkyNet' Jun 7 19:10:38 Probe Request from f4:09:d8:##:##:## for SSID 'BustersBrounce' Jun 7 19:10:33 Probe Request from 78:4b:87:##:##:## for SSID 'WOPR_nomap' Jun 7 19:10:31 Probe Request from 28:10:7b:##:##:## for SSID 'KPCY2' Jun 7 19:10:20 Probe Request from f4:09:d8:##:##:## for SSID 'BustersBrounce' Jun 7 19:10:13 Probe Request from 28:10:7b:##:##:## for SSID 'KPCY2' Jun 7 19:10:12 Probe Request from 28:10:7b:##:##:## for SSID 'KPCY2' Jun 7 19:10:10 Probe Request from 78:4b:87:##:##:## for SSID 'guest' Jun 7 19:09:35 Probe Request from f4:09:d8:##:##:## for SSID 'BustersBrounce' Jun 7 19:09:09 Probe Request from 78:4b:87:##:##:## for SSID 'guest' Jun 7 19:08:53 Probe Request from b0:e8:92:##:##:## for SSID 'BustersBrounce' Jun 7 19:08:40 Probe Request from 00:25:ae:##:##:## for SSID 'SkyNet' Jun 7 19:08:34 Probe Request from f4:09:d8:##:##:## for SSID 'BustersBrounce' Jun 7 19:08:31 Probe Request from 00:c0:ca:##:##:## for SSID 'WOPR_nomap' Jun 7 19:08:30 Probe Request from 28:10:7b:##:##:## for SSID 'KPCY2' Jun 7 19:08:30 Probe Request from 28:10:7b:##:##:## for SSID 'KPCY2' Jun 7 19:08:23 Probe Request from f4:09:d8:##:##:## for SSID 'BustersBrounce' Jun 7 19:08:19 Probe Request from 00:25:ae:##:##:## for SSID 'SkyNet' Jun 7 19:08:17 Probe Request from 28:10:7b:##:##:## for SSID 'KPCY2' Jun 7 19:08:10 Probe Request from 28:10:7b:##:##:## for SSID 'KPCY2' Jun 7 19:08:03 Probe Request from 28:10:7b:##:##:## for SSID 'KPCY2' Jun 7 19:07:59 Probe Request from 00:25:ae:##:##:## for SSID 'SkyNet' Jun 7 19:07:52 Probe Request from 80:96:b1:##:##:## for SSID 'Wang Chung' Jun 7 19:07:50 Probe Request from 00:11:95:##:##:## for SSID '92I33' Jun 7 19:07:45 Probe Request from 28:10:7b:##:##:## for SSID 'KPCY2' Jun 7 19:07:37 Probe Request from 28:10:7b:##:##:## for SSID 'KPCY2' Jun 7 19:07:36 Probe Request from 28:10:7b:##:##:## for SSID 'KPCY2'
  18. Others correct me if I'm wrong but as I understand ref; PineAP wlan0 pulls in the clients and is the radio that clients connect to. Wlan1 is put into monitor mode, does beacon responses, beacons, deauth etc. So yes both wlan0 and wlan1 are supposed to be in use at the same time. Now as it relates to Network --> Access Points --> Open Access Point and Secure Management Access Point are running from wlan0. See /etc/config/wireless (ssh to your pineapple) radio0 you should see wifi-iface --> option ssid "Pineapple5_####" and an additional wifi-iface --> option ssid "YOUR CREATED SSID AT INSTALL CONFIG". Make sure your option key 'stupidpassword' is correct and your typing the right key. config wifi-device 'radio0' option type 'mac80211' option channel '11' option hwmode '11ng' option macaddr '00:13:37:##:##:##' option htmode 'HT20' list ht_capab 'SHORT-GI-20' list ht_capab 'SHORT-GI-40' list ht_capab 'RX-STBC1' list ht_capab 'DSSS_CCK-40' config wifi-iface option device 'radio0' option network 'lan' option mode 'ap' option ssid 'Pineapple5_####' option encryption 'none' option hidden '1' config wifi-iface option device 'radio0' option network 'lan' option mode 'ap' option encryption 'psk2+ccmp' option ssid 'Roomba' option key 'stupidpassword' option disabled '0' config wifi-device 'radio1' option type 'mac80211' option channel '11' option hwmode '11g' option macaddr '00:13:37:##:##:##' config wifi-iface option device 'radio1' option network 'lan' option mode 'sta' option ssid 'Pineapple5_%%%%' option hidden '0' option encryption 'none' Those wifi's are running on one device wlan0. Radio1 (wlan1) should have another Pineapple5_#### but the last four numbers are different. Wlan1 should not be up and running as an AP because its being used to listen and other stuff in PineAP. If after looking at your /etc/config/wireless and verifying your password, I'm not sure whats going wrong. I hate to tell you to factory.bin again, trust me I've done that alot myself, but I would also recommend doing the factory.bin and then manual upgrade-2.2.0.bin. See if the other firmware allows you to connect to your Secure Management Access Point.
  19. Might want to check your Network tile --> Access Point tab. There are two areas Open Access Point and Secure Management Access Point. Take note of the ? and review for their purpose. By default the Open Access Point will be hidden and the Secure Management Access Point you would have first setup during your initial flash.
  20. Appears it has already been posted to the bug-tracker: https://www.wifipineapple.com/?bugs_pub&action=view&id=302
×
×
  • Create New...