Jump to content

Hike

Active Members
  • Posts

    21
  • Joined

  • Last visited

Recent Profile Visitors

1,001 profile views

Hike's Achievements

Newbie

Newbie (1/14)

  1. Hey, I've been having some thing similar to this happen to me. See post: https://forums.hak5.org/index.php?/topic/33239-mk5-refusing-ap-connections-after-period-of-time/?p=248282 I've been watching the forums like a hawk for something like this so please post any resolution. I've only been able to glimps the power of the pine one log on at a time....followed by wireless rest, factory rest, re flash and even unbricking procedures. Currently running 2.0.3. I'm looking at the logs and it seems that the MkV is not receiving an authentication response. When I try on another device I can connect but only once. After which I'm locked out.
  2. Hey, I think the new firmware upgrade just fixed mine that was doing this.. Only been on it for about 3 hours. Luck
  3. The battery is not the problem. I've had the pineapple up and running although the MKV had very limited infusion use. 12hrs via wall and ~6hrs via a battery setup. Multiple log in / outs with an Ipad. Gotta be something I'm doing... Edit!> Enabling wlan1 followed by starting client mode using infusion "Network" seems to be part of the trigger that locks out access to the MV5 via Wlan0. Eth0 will still work. cheers, H
  4. I've had similar problems with the NHR but the pineapple wiki clearly lists it as "unsupported". http://wiki.wifipineapple.com/index.php/Compatible_Wireless_Cards The NHA works great out of the box so I stopped messing around with the NHR. I know there are drivers that can be loaded and I've gotten the NHR into monitor mode, max power.... in Kali (VM and on the Raspberry Pi). I'm not sure how to load drivers onto the pineapple but this might be a resource for others: http://www.alfa.com.tw/press_c_show.php?sn=5 (info) and http://www.rokland.com/mask/drivers/awus036nhr-linux.zip (driver). cheers
  5. For a better discussion see: https://forums.hak5.org/index.php?/topic/30941-how-to-add-a-alfa-wifi-usb-adapter-to-my-mark-v/
  6. Thanks guys. good question. I normally start with the provided power supply then switch to a pineapple juice or car-adapter. I've just re-flashed and am intent on reproducing this with very detailed notes. ug...
  7. Ok- step 1- I've refashed firmware. Edited the AP connection to wlan0 changing the name and setting the security to WPA2. I can log into the pineapple through kali linux, ssh, or an i"device". Starting infusions and wlan1 & wlan2 (afla 36NHA) goes without a glitch. I leave and come back. step 2- All devices give me "Unable to join the network". Plug in Eth0 and ... Resetting Wireless config works at clearing out vaules in the network infussion but doesn't solve the issue. i"devices" will not show Pineapple5_2965 at all and while kali can connect to the wifi, it is lock out of even reaching the logon for the MK5. Rebooting doesn't help. So I factory reset pineapple via the conifguration infusion. Pineapple bar updates from SD card. Wlan0 is active and reachable. wlan1 is disabled in the network infusion and wlan2 will not enable [usually ??] until I enable wlan1. Change Pineapple5_2965 to HP2965 without any security (ch11). Disconnect the Eth0 and log into the MK5 via another device.. Use WPS or Deauth or Karma (blacklisting my devices after every firmware and or reset).... it doesnt' seem affect the outcome. After aperiod of time and infusion use i'm back to step 1! For the most part I'm sure I'm doing some stupid NOOB thing. Yet, twice I've had infusions up and going only to be followed by "Unalbe to join network" on subsequent checks. I guess something could always go wrong with karma (user input) but why should using reaver on wlan1 cause "lockouts". The MK5 does seem to get very hot. I've also had this series of events happen with and without the alfa 36nha plugged in. Anyway I'm stumped.
  8. I thought that I would update the status. As Darren has posted elsewhere the 36NHR is unsupported [yet?]for the Pineapple. I wish I had started by looking at the wiki - http://wiki.wifipineapple.com/index.php/Compatible_Wireless_Cards. Duh! There was nothing wrong with the USB and I've tested a 38NHA that worked wonderfully out of the box. The NHR will only light up during a connection to an AP (raspberrypi) vs lighting up as soon as I plug it into a windows machine. Trying to save infusions to the USB thumbdrive only confused the issue. Saving infustions to the USB on the MKV was answered (no, nada, and only on the MKIV)... see: https://forums.hak5.org/index.php?/topic/33119-usb-install-unavailable/ I've yet to load the drivers for the NHR on the MKV ( http://www.alfa.com.tw/press_c_show.php?sn=5 ). The NHA works.... Thanks and adios!
  9. update: the I've formatted an USB thumb-drive and mounted it to the Pineapple. Any suggestions for getting the wifi adapters to be recognized?
  10. I'm having trouble getting any of my USB wifi appaters to power up and/or show up with ifconfig or iwconfig. I've got all 4 lights going on the pineapple and currently using it's wifi between my ap and laptop. Going into configuration infusion and running 'lsusb' returns the following. Executing 'lsusb': Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 058f:6254 Alcor Micro Corp. USB Hub Bus 001 Device 003: ID 0bda:8187 Realtek Semiconductor Corp. RTL8187 Wireless Adapter Bus 001 Device 004: ID 058f:6366 Alcor Micro Corp. Multi Flash Reader Bus 001 Device 007: ID 0bda:8176 Realtek Semiconductor Corp. RTL8188CUS 802.11n WLAN Adapter What would be the best way to test the USB port on the MarkV? Any other ways to start trouble shooting this or better googling terminology. I keep hitting dead ends. Is there a tutorial/wiki that I've missed out on? The adapters used thus far: AWUS036NHR small unknown no-name usb wifi dongle USB thumbdrives will light up... this is next on my list of todo's https://scotthelme.co.uk/wifi-pineapple-usb-storage-and-infusions/ thx, H
  11. Sabkinne/fringes- thanks for the quick responses. I was just about to treat as a bricked Pineapple. You just saved me a bit of time. Update- Re-flashed the MV and reformated the SD. Did not load Wifi-Manager yet Network Infusion was not connecting the hidden net work(didn't see Sabkinne's response in time.). FYI...the key is never shown when revisiting the Network infusion. Also, If i unhide the Hidden-AP, set the Network infusion, and then reset the AP to hidden, the pineapple will work.... for a undisclosed time. Eventually, It will stop. Probably because I try to use monitor mode most likely.. No promises but I'll work more on the copy-replay wifi config via DIP switches.. THX,H
  12. Step one- I'm currently trying to connect the M5 to an AP with a hidden SSID named "hidden" and "5$$" as the password [see below]. Yet, the infusion wifi-manager v1.8 keeps chaining the $'s to two digit numbers similar to this "5$$"=> "53395" config wifi-iface option device 'radio1' option mode 'sta' option macaddr '00:ed:ed:ed:ed:ed' option ssid 'hidden' option network 'wan' option encryption 'psk2+tkip' option hidden '0' option key '53395' ..........should be 5$$ I can SSH, and use the web interface on radio 0 and via etho. Here is the kicker. It works when I set it up via a windows7 machine and etho cable. Initial the settings will allow devices to that connect via radio 0 and access internet from radio 1 even with the pass key visibly incorrect in the Wifi Manager. YET, putting radio 1 into monitor mode and then back to wlan causes the setting to "break". Rebooting the M5 doesn't help.There is no way to connect to the AP without re-config the wifi-manager from scratch via Ethernet cable. Reboot the M5 doesn't help. I'm sure I'll get this to work better but I don't know what the M5 is doing with the pass key or why I can't comeback from monitor mode using the web interface and radio 0. Second step- This should work with a boot command using the dip switches...right? ifconfig wlan1 up; iwconfig wlan1 essid "hidden" key 5$$ ap co:ff:ee:co:ff:ee
×
×
  • Create New...