Jump to content

Hike

Active Members
  • Content Count

    21
  • Joined

  • Last visited

About Hike

  • Rank
    Hak5 Fan

Recent Profile Visitors

758 profile views
  1. I sure I'm close but does anyone know an easy way to mount a thumb drive or ssd to the M7? #mount -a ---did NOT work #fdisk -l # mount -t ext4 /dev/sda1 /mnt ---failed but I didn't expect it to work. What file system does the pineapple use? Is there a better place to mount the drive than /mnt or /etc/fstab? Tried - # lsblk -f didn't work either but I found it here...https://openwrt.org/packages/pkgdata/lsblk so I tried this: Stopping on my chain of dead ends and most likely incorrect assumption. Any help is appreciated.
  2. I have to admit that the new terminal feature is pretty sweet. Cuts out a few steps for me here and there. The third antenna also streamlines a few things but I already was using a wifi dongle on legacy Marks. Finally, Do you support what Hak5 does? 2cents thus far...
  3. All- I've had my M7 about a week and just updated to the current beta. For the most part I'd been trying to get data from a BU-353s4** gps dongle to work during lunch hours. Anyway I had the M7 in and out of the university for about 3 days. I was doing zero pentesting. I didn't think about it but I updated to beta over a personal hotspot and accessed the M7 via wifi to setup my password and etc... During the update the M7 sent out a SSID. DUH! University IT was at my desk asking questions in about an hour. LOL It was all good and I even made some friends. Just update your
  4. This is just a guess. I've notice that while xfinity will require a password with reregistering a device. There seems to be MAC tracking or some other form of association. Check this out from the xfinity side and set/force a MAC up on your P7. Once again just guessing. https://www.xfinity.com/support/articles/new-device-sign-in I'm also assuming that if you register the P7 so that you can use any of the Xfinity anywhere-wifis/hotspots there is going to be an extensive device trail. ***I get around really knowing what's really up by plugging an old wireless router in and connec
  5. 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 b
  6. Hey, I think the new firmware upgrade just fixed mine that was doing this.. Only been on it for about 3 hours. Luck
  7. 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
  8. 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).
  9. 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/
  10. 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...
  11. 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 rea
  12. 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
  13. 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?
  14. 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 0
  15. 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 li
×
×
  • Create New...