Jump to content

BeNe

Active Members
  • Posts

    184
  • Joined

  • Last visited

  • Days Won

    6

Everything posted by BeNe

  1. Summary After 14 days still no solution and no rection except this (https://forums.hak5.org/index.php?/topic/33757-mark-v-reboots-understanding-problem-maybe/?p=251929) There are seven hak5 supporters and MarkV owner with the same problem: Emorrow.df tango73 javibag ZeroZeroSeven chickentech prusayn BeNe I 'm sure there are some more.. Hak5 is manufactor and software/firmware developer so in _any_ case you need to do something! But nothing... That no reaction game sucks damn hard!!! In my case it costs ~ 237$ for two MarkV and a Pineapple Plug. Wow, best deal ever. Thanks for nothing! BeNe
  2. Maybe it's bricked ?! Here is an instruction (Unbricking a bricked WiFi Pineapple MKV) --> https://www.wifipineapple.com/?flashing
  3. This Powershell Script works perfect! But the most of the clients have a Proxy with authentication active. Is there a way to use the system default proxy settings to get the script running ? Or to put the powershell Script and needed dll to the SDCard ? Mimikatz_xy.exe is set off by the AV - the script not.
  4. And your Pineapple is stable with so many WiFi-Devices ? Check this Thread here --> https://forums.hak5.org/index.php?/topic/30998-track-pineapple-via-gps/?p=251068
  5. "ac:22:0b:6d:3c:10" is my Nexus 7 2013. Maybe it has something todo with the situation how vendors implement WiFi-Security ? The rt2800 is my Asus AWUS036NEH if it is not an internal interface. Don't know. The Load itself is more or less OK. Here is an example (last output from top until the pineapple reboots...) Mem: 58728K used, 3076K free, 0K shrd, 4780K buff, 14704K cached CPU: 1% usr 31% sys 2% nic 0% idle 58% io 0% irq 5% sirq Load average: 3.05 1.47 1.32 1/82 14656 PID PPID USER STAT VSZ %VSZ %CPU COMMAND 12156 12155 root S N 10320 17% 6% pinejector mon0 11 00:13:37:A5:3D:6C 7154 7007 root R N 2748 4% 5% aireplay-ng -0 0 --ignore-negative-on 11819 2 root RW 0 0% 5% [kworker/u:0] 1623 1 root S 1624 3% 4% hostapd -P /var/run/wifi-phy0.pid -B 7146 7007 root S N 2748 4% 4% aireplay-ng -0 0 --ignore-negative-on 7701 2 root SW 0 0% 3% [kworker/u:4] 4118 2 root SW 0 0% 3% [kworker/u:3] 7141 7007 root S N 2748 4% 3% aireplay-ng -0 0 --ignore-negative-on 3 2 root SW 0 0% 2% [ksoftirqd/0] 2234 2229 root R 1524 2% 1% top 1878 1 root S 1636 3% 1% wpa_supplicant -B -P /var/run/wifi-wl 14319 2 root SW 0 0% 0% [kworker/u:2] 9752 1 root S N 12472 20% 0% python /usr/bin/sslstrip -k -f -w /sd 12254 12253 root S 9472 15% 0% /usr/bin/php-fcgi -b /var/run/php5-fc 11816 11815 root S N 5600 9% 0% urlsnarf -i br-lan 2227 1963 root S 5488 9% 0% {sshd} sshd: root@pts/0 1935 1933 root D 4288 7% 0% nginx: worker process 1933 1 root S 3852 6% 0% nginx: master process /usr/sbin/nginx 1963 1 root S 2864 5% 0% /usr/sbin/sshd Write failed: Broken pipe 1860 3% 0% {mobile-keepaliv} /bin/bash /etc/pine [bene@desk ~]$ I'm sure it was to much for the pineapple (PineAP, Urlsnarf, deauth, sslsrtip) but the load was 3.05. In some situations the Load is >6.0 for a short time. Thats the reason why i want to use TangoMode and spilt the services. Perfect! Thanks seb. I'm glad to hear from you
  6. Here is an example. A client try to connect to the Pineapple - but it doesn't work! Oct 6 16:50:44 KARMA: Probe Request from ac:22:0b:6d:3c:10 for SSID 'FreeWiFi' Oct 6 16:50:44 KARMA: Probe Request from ac:22:0b:6d:3c:10 for SSID 'FreeWiFi' Oct 6 16:50:44 KARMA: Probe Request from ac:22:0b:6d:3c:10 for SSID 'FreeWiFi' Oct 6 16:50:41 KARMA: Successful association of ac:22:0b:6d:3c:10 Oct 6 16:50:41 KARMA: Checking SSID for start of association, pass through FreeWiFi Oct 6 16:50:41 KARMA: Probe Request from ac:22:0b:6d:3c:10 for SSID 'FreeWiFi' Oct 6 16:50:40 KARMA: Successful association of ac:22:0b:6d:3c:10 Oct 6 16:50:40 KARMA: Checking SSID for start of association, pass through FreeWiFi Oct 6 16:50:40 KARMA: Probe Request from ac:22:0b:6d:3c:10 for SSID 'FreeWiFi' Oct 6 16:50:39 KARMA: Successful association of ac:22:0b:6d:3c:10 Oct 6 16:50:39 KARMA: Checking SSID for start of association, pass through FreeWiFi Oct 6 16:50:39 KARMA: Probe Request from ac:22:0b:6d:3c:10 for SSID 'FreeWiFi' Oct 6 16:50:38 KARMA: Successful association of ac:22:0b:6d:3c:10 Oct 6 16:50:38 KARMA: Checking SSID for start of association, pass through FreeWiFi Oct 6 16:50:38 KARMA: Probe Request from ac:22:0b:6d:3c:10 for SSID 'FreeWiFi' Oct 6 16:50:38 KARMA: Successful association of ac:22:0b:6d:3c:10 Oct 6 16:50:38 KARMA: Checking SSID for start of association, pass through FreeWiFi Oct 6 16:50:38 KARMA: Probe Request from ac:22:0b:6d:3c:10 for SSID 'FreeWiFi' Oct 6 16:50:37 KARMA: Successful association of ac:22:0b:6d:3c:10 Oct 6 16:50:37 KARMA: Checking SSID for start of association, pass through FreeWiFi Oct 6 16:50:37 KARMA: Probe Request from ac:22:0b:6d:3c:10 for SSID 'FreeWiFi' Oct 6 16:50:36 KARMA: Successful association of ac:22:0b:6d:3c:10 Oct 6 16:50:36 KARMA: Checking SSID for start of association, pass through FreeWiFi Oct 6 16:50:36 KARMA: Probe Request from ac:22:0b:6d:3c:10 for SSID 'FreeWiFi' Oct 6 16:50:35 KARMA: Successful association of ac:22:0b:6d:3c:10 Oct 6 16:50:35 KARMA: Checking SSID for start of association, pass through FreeWiFi Oct 6 16:50:35 KARMA: Probe Request from ac:22:0b:6d:3c:10 for SSID 'FreeWiFi' Oct 6 16:50:34 KARMA: Successful association of ac:22:0b:6d:3c:10 Oct 6 16:50:34 KARMA: Checking SSID for start of association, pass through FreeWiFi Oct 6 16:50:34 KARMA: Probe Request from ac:22:0b:6d:3c:10 for SSID 'FreeWiFi' Oct 6 16:50:33 KARMA: Successful association of ac:22:0b:6d:3c:10 Oct 6 16:50:33 KARMA: Checking SSID for start of association, pass through FreeWiFi Oct 6 16:50:33 KARMA: Probe Request from ac:22:0b:6d:3c:10 for SSID 'FreeWiFi' Oct 6 16:50:32 KARMA: Successful association of ac:22:0b:6d:3c:10 Oct 6 16:50:32 KARMA: Checking SSID for start of association, pass through FreeWiFi Oct 6 16:50:32 KARMA: Probe Request from ac:22:0b:6d:3c:10 for SSID 'FreeWiFi' Oct 6 16:50:32 KARMA: Successful association of ac:22:0b:6d:3c:10 Oct 6 16:50:32 KARMA: Checking SSID for start of association, pass through FreeWiFi Oct 6 16:50:32 KARMA: Probe Request from ac:22:0b:6d:3c:10 for SSID 'FreeWiFi' Oct 6 16:50:30 KARMA: Successful association of ac:22:0b:6d:3c:10 Oct 6 16:50:30 KARMA: Checking SSID for start of association, pass through FreeWiFi Oct 6 16:50:30 KARMA: Probe Request from ac:22:0b:6d:3c:10 for SSID 'FreeWiFi' Oct 6 16:50:29 KARMA: Successful association of ac:22:0b:6d:3c:10 Oct 6 16:50:29 KARMA: Checking SSID for start of association, pass through FreeWiFi Oct 6 16:50:29 KARMA: Probe Request from ac:22:0b:6d:3c:10 for SSID 'FreeWiFi' Oct 6 16:50:28 KARMA: Successful association of ac:22:0b:6d:3c:10 Oct 6 16:50:28 KARMA: Checking SSID for start of association, pass through FreeWiFi Oct 6 16:50:28 KARMA: Probe Request from ac:22:0b:6d:3c:10 for SSID 'FreeWiFi' Oct 6 16:50:26 KARMA: Successful association of ac:22:0b:6d:3c:10 Oct 6 16:50:26 KARMA: Checking SSID for start of association, pass through FreeWiFi Oct 6 16:50:26 KARMA: Probe Request from ac:22:0b:6d:3c:10 for SSID 'FreeWiFi' Oct 6 16:50:26 KARMA: Successful association of ac:22:0b:6d:3c:10 Oct 6 16:50:26 KARMA: Checking SSID for start of association, pass through FreeWiFi Oct 6 16:50:26 KARMA: Probe Request from ac:22:0b:6d:3c:10 for SSID 'FreeWiFi' Oct 6 16:50:25 KARMA: Successful association of ac:22:0b:6d:3c:10 Oct 6 16:50:25 KARMA: Checking SSID for start of association, pass through FreeWiFi Oct 6 16:50:25 KARMA: Probe Request from ac:22:0b:6d:3c:10 for SSID 'FreeWiFi' Oct 6 16:50:24 KARMA: Successful association of ac:22:0b:6d:3c:10 Oct 6 16:50:24 KARMA: Checking SSID for start of association, pass through FreeWiFi Oct 6 16:50:24 KARMA: Probe Request from ac:22:0b:6d:3c:10 for SSID 'FreeWiFi' Oct 6 16:50:23 KARMA: Successful association of ac:22:0b:6d:3c:10 Oct 6 16:50:23 KARMA: Checking SSID for start of association, pass through FreeWiFi Oct 6 16:50:23 KARMA: Probe Request from ac:22:0b:6d:3c:10 for SSID 'FreeWiFi' Oct 6 16:50:22 KARMA: Successful association of ac:22:0b:6d:3c:10 Oct 6 16:50:22 KARMA: Checking SSID for start of association, pass through FreeWiFi Oct 6 16:50:22 KARMA: Probe Request from ac:22:0b:6d:3c:10 for SSID 'FreeWiFi' Oct 6 16:50:21 KARMA: Successful association of ac:22:0b:6d:3c:10 Oct 6 16:50:21 KARMA: Checking SSID for start of association, pass through FreeWiFi Oct 6 16:50:21 KARMA: Probe Request from ac:22:0b:6d:3c:10 for SSID 'FreeWiFi' Oct 6 16:50:20 KARMA: Successful association of ac:22:0b:6d:3c:10 Oct 6 16:50:20 KARMA: Checking SSID for start of association, pass through FreeWiFi Oct 6 16:50:20 KARMA: Probe Request from ac:22:0b:6d:3c:10 for SSID 'FreeWiFi' Oct 6 16:50:20 KARMA: Successful association of ac:22:0b:6d:3c:10 Oct 6 16:50:20 KARMA: Checking SSID for start of association, pass through FreeWiFi Oct 6 16:50:20 KARMA: Probe Request from ac:22:0b:6d:3c:10 for SSID 'FreeWiFi' Oct 6 16:50:19 KARMA: Probe Request from ac:22:0b:6d:3c:10 for SSID 'FreeWiFi' Oct 6 16:50:19 KARMA: Probe Request from ac:22:0b:6d:3c:10 for SSID 'FreeWiFi' Oct 6 16:50:19 KARMA: Probe Request from ac:22:0b:6d:3c:10 for SSID 'FreeWiFi' Oct 6 16:50:19 KARMA: Probe Request from ac:22:0b:6d:3c:10 for SSID 'FreeWiFi' This is really disappointing that none of my/our questions are answered by the developer team. The pineapple is not stable for me! We all support hak5 and buy the WiFiPineapple & Accessories @hakshop but it is not fair that we do not recieve support within a week.
  7. It is available --> http://hakshop.myshopify.com/collections/usb-rubber-ducky/products/usb-rubber-ducky-deluxe
  8. So far (~ 15. min) the Pineapple without ANY infusion seems to be stable. Fine! Now i go and add one infusion after one. During my test the connection from a client to the pineapple was not that stable. The client lost the connection and reconnect many times. //Edit I have hundred of dmesg entry's and the clients are unable to connect now to the Pineapple! Tested with my Android Smartphone, Notebook and iPhone. [ 3828.580000] ieee80211 phy2: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 6 in queue 2 [ 3828.600000] ieee80211 phy2: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 6 in queue 2 [ 3936.300000] ieee80211 phy2: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 15 in queue 2 [ 3936.310000] ieee80211 phy2: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 15 in queue 2 [ 3936.320000] ieee80211 phy2: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 15 in queue 2 [ 3945.920000] ieee80211 phy2: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 1 in queue 2 [ 3945.920000] ieee80211 phy2: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 1 in queue 2 [ 3945.930000] ieee80211 phy2: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 1 in queue 2 [ 3945.950000] ieee80211 phy2: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 1 in queue 2 [ 3945.950000] ieee80211 phy2: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 1 in queue 2 [ 3945.970000] ieee80211 phy2: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 2 in queue 2 [ 3945.980000] ieee80211 phy2: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 2 in queue 2 [ 3945.990000] ieee80211 phy2: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 3 in queue 2 [ 3946.000000] ieee80211 phy2: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 4 in queue 2 [ 3946.010000] ieee80211 phy2: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 5 in queue 2 [ 3946.020000] ieee80211 phy2: rt2800usb_txdone: Warning - Got TX status for an empty queue 2, dropping [ 3946.020000] ieee80211 phy2: rt2800usb_txdone: Warning - Got TX status for an empty queue 2, dropping [ 3946.030000] ieee80211 phy2: rt2800usb_txdone: Warning - Got TX status for an empty queue 2, dropping [ 3946.040000] ieee80211 phy2: rt2800usb_txdone: Warning - Got TX status for an empty queue 2, dropping [ 3946.050000] ieee80211 phy2: rt2800usb_txdone: Warning - Got TX status for an empty queue 2, dropping [ 3950.740000] ieee80211 phy2: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 12 in queue 2 [ 3950.740000] ieee80211 phy2: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 12 in queue 2 [ 3950.750000] ieee80211 phy2: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 12 in queue 2 [ 3950.770000] ieee80211 phy2: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 12 in queue 2 [ 3950.780000] ieee80211 phy2: rt2800usb_txdone: Warning - Got TX status for an empty queue 2, dropping [ 3972.580000] ieee80211 phy2: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 11 in queue 2 [ 3972.580000] ieee80211 phy2: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 11 in queue 2 [ 3972.590000] ieee80211 phy2: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 11 in queue 2 [ 3972.610000] ieee80211 phy2: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 11 in queue 2 [ 3972.620000] ieee80211 phy2: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 11 in queue 2 [ 4009.400000] ieee80211 phy2: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 5 in queue 2 [ 4009.400000] ieee80211 phy2: rt2800usb_entry_txstatus_timeout: Warning - TX status timeout for entry 5 in queue 2
  9. PineAP use wlan1 or not ? If i use wlan1 for ICS and enable PineAP - it goes down! OK, no problem i have an Alfa and use wlan2. But, if i enable PineAP why is wlan1 still disabled and the red light is off ?
  10. Hi there, i have some pineapple tango mode question. I'm useing the pineapple plug and an Alfa from the hakshop. Enabled tango mode on PA2 with: uci set network.lan.ipaddr=172.16.42.2 uci set network.lan.gateway=172.16.42.1 uci commit network Tango mode works fine. Pineapple 1 + connected Alfa PA1 is connected with wlan1 to my Router (ICS) wlan 0 is unsed (it is in AP mode per default ?!) wlan 2 (Alfa) does deauth (whitelisted both PA + Router) Pineapple 2 wlan0 -> collect clients (AP) wlan1 is unsed MK5 Karma & PineAP are enabled wlan2 on PA1 is not needed because wlan0 can do the same ? sslstrip should run on PA1 (Gateway for PA2) or PA2 ? Is there a better loadbalacing for the services ? DNS Spoof and URLSnarf on PA1 or PA2 ? wlan2 suggestions ? Greez BeNe
  11. No news, no reaction! I tested also my second pineapple with the same result. Tango mode works not without any problems (used the pineapple plug). After ~15 min. one of both reboots and break the system. @seb @darren How can i debug the problem ? Hardware issue ? (both pineapples reboots) Software error ? Wrong handling ?
  12. OpenWrt 14.07 is released. --> https://openwrt.org/
  13. Your university use WPA2 Enterprise with an Radius Server (802.1.X EAP) ?
  14. I have written to seb a private message. In the hope that he can help us.
  15. Remove the SD-Card from the Pineapple and try it again with an SD-Card reader in a Linux/Unix PC/VM. It is ext4 formated so dont use Windows. Or you Format it with FAT32 under windows and insert it back into your pineapple and format it there again with ext4.
  16. I will post the output tomorrow cause i´m not at home now. I use a 172.16.17.0/24 subnet at home. Should not be that problem. Will try to use my Android with an AP to share Internet or USB Tethering for a new test. No, i have no solution! I/we need to talk to seb and darren about that problem.
  17. Flashed "c_duck_v2.1.hex" successfully under Windows 8.1 x64!
  18. Hi Armaal, no the MarkV is not hot.I held it in my hand during the test. I have a second MarkV here and can reproduce the same behavior. I'm on the MarkV with ssh and ping my gateway that is connected via wlan2 (Alfa) for ICS. If i enable Karma wlan2 disconnects. I'm unable to bring it up. Pineapple reboots! ...damn...
  19. BeNe

    Firewalls

    I changed from a ALIX Board to the follower APU 1C. That small board comes with 4GB RAM, AMD G series T40E 1 GHz dual core (Bobcat core) with 64 bit support and a 32 GB Kingston mSSD. Tested some Firewall but none of them was that stable and has all features i need like pfSense. But this i only my point of view.
  20. BeNe

    Firewalls

    Just google and you will find enough sites and stuff -> http://www.mondaiji.com/blog/other/it/10175-the-hunt-for-the-ultimate-free-open-source-firewall-distro -> http://www.tecmint.com/open-source-security-firewalls-for-linux-systems/ IPFire is a good Firewall by the way. And if you like it - use it! You need to check what features you need and than start to compare. There is no "BEST FIREWALL FOR EVERYONE"! I for my part use pfSense because i love FreeBSD and it has all features i need. If possible use a own Hardware and no VM. Don´t use a "Firewall" that comes with a cloud, printerservice etc. This has nothing to do with a security product.
  21. The File and Link is ok for me and not corrupt! Maybe your AntiVirus don´t like the file ? Here is an alternative download --> http://www.deluxe-stylez.de/files/ducky/Duck_Programming.zip
  22. BeNe

    socks5

    You can try proxychains, simpleproxy or ssh Proxychains -> http://www.ehacking.net/2013/01/proxychains-tor-backtrack-5-r3-tutorial.html Simpleproxy -> http://sourceforge.net/projects/simpleproxy/ SSH + IPTables -> http://dtbaker.net/random-linux-posts/redirect-all-traffic-through-transparent-socks5-proxy-in-linux/
  23. So we have a general problem with the Hardware or Software ? Please describe: in what situations you MarkV reboot (enable PineAP, enable Infusion xy,...) what is connected (WLAN Stick, USB-Stick...), power is connected via (the default power adapter, pineapple juice, anker...) We need to sort out the problems! I´m also willing to provide a remote access for a dev to my MarkV like TeamViewer, SSH, Webinterface...
  24. The dips are wrong in my eyes! --> Power off your WiFi Pineapple MKV and set the DIP switches to up, up, up, up, down (from left to right). Here is the Link to the wiki --> https://wifipineapple.com/?flashing Unbricking a bricked WiFi Pineapple MKVBricked your WiFi Pineapple MKV? Unbricking is easy and doesn't require any extra hardware! Download the special factory image. This image is the WiFi Pineapple MKV's 1.2.0 firmware, packaged differently to allow unbricking. Please verify it's md5 checksum to be 167b1533b9dd5c49f7107413fb960bfa. Power off your WiFi Pineapple MKV and set the DIP switches to up, up, up, up, down (from left to right). Connect to your WiFi Pineapple MKV via ethernet and set your network interface to a static IP of 192.168.1.2 Boot up the WiFi Pineapple MKV. After around five seconds, you can navigate to http://192.168.1.1 Upload the factory-1.2.0.bin file through the interface. Wait for it to complete. Set all the DIP switches back to the default configuration up, up, up, up, up (from left to right). Make sure the SD card is inserted and powercycle the WiFi Pineapple MKV. Your device will now boot the 1.2.0 firmware. Please wait patiently and refer to the first boot instructions in your WiFi Pineapple MKV instructions. You may skip any information relating to the stager. You are done. Enjoy your freshly flashed WiFi Pineapple MKV!
×
×
  • Create New...