Jump to content

Mark V reboots / understanding problem maybe ?


BeNe
 Share

Recommended Posts

I want to build a setup with Client Mode (ICS) + SSLStrip + PineAP.

But it does not work. The Mark V reboots after i enable the services. Here is what i have done exactly:

  1. Format SD-Card
  2. Re-Flash 2.0.4
  3. Conneted to WiFiPineapple via WiFi (Pineapple5_xy) on wlan0
  4. Connected extern Alfa USB (AWUS036NEH) and added as Client Mode (ICS) on wlan2
  5. Installed sslstrip and deauth to SD-Card
  6. Installed mdk3 to SD-Card
  7. Deauth -> Enable wlan1 -> Start Monitor on wlan1 (RED Led is still off!!!)
  8. Whitelisted all my WiFi Networks (includes Pineapple itself + my WiFi ICS source)
  9. Start WiFi Deauth with Aireplay-ng on wlan1 / mon0
  10. RED LED is still off but wlan1 is in use!?
  11. Deauth works fine, but does not show all MAC's that are currently DeAuth`ing (only once on startup but not new MAC's)
  12. Enabled MK5 Karma
  13. Enabled PineAP
  14. Enabled Dogma
  15. Enabled Beacon Response
  16. Enabled Auto Harvester
  17. RED Led is ON - BLUE Led is OFF for a short time
  18. PineApple reboots!

Maybe i'm doing something wrong and it is my fault that i used the wrong interfaces or order to enable the services ?

Thanks for any help!

Greez BeNe

Link to comment
Share on other sites

Is it a power problem ? I use the normal power adapter that comes with MarkV. Should be enough for the Mark V itself an the Alfa or ?

Hope that i´m doing something wrong, like: "Hey you use the wrong Interface..." or "Hey this doesn´t work so do it like this..." whatever.

Don´t know why the MarkV is that unstable for me.

Edited by BeNe
Link to comment
Share on other sites

So we have a general problem with the Hardware or Software ? :unsure:

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...

Link to comment
Share on other sites

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...

Link to comment
Share on other sites

Ok

That sounds like a conflict between differents "route" with WLAN 0 & 1 & 2 but reach a reboot system it's not normal.

Your WLAN2 it's the : AWUS036NEH ? (I think yes your first post)
Could you do : iwconfig wlan2 and paste here ?

I'm waiting for a
AWUS036NEH (buy in your country!) to France. If your problems is not resolv in few days I think I could help easier

stay in touch

Edited by Armaal
Link to comment
Share on other sites

I run PineAP Suite and sslstrip. It'll run for a few minutes and reboot. Doesn't get hot at all. I can also replicate this when running wifite.

I'm using the default ac adapter, the usb dongle i bought with the pineapple. Seems to be quite a few people with this problem, but no comments from anyone about it from hak5.

Link to comment
Share on other sites

Ok

That sounds like a conflict between differents "route" with WLAN 0 & 1 & 2 but reach a reboot system it's not normal.

Your WLAN2 it's the : AWUS036NEH ? (I think yes your first post)

Could you do : iwconfig wlan2 and paste here ?

I'm waiting for a AWUS036NEH (buy in your country!) to France. If your problems is not resolv in few days I think I could help easier

stay in touch

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.

Bene i have the same problem do u find a solution? Please post it

No, i have no solution!

I/we need to talk to seb and darren about that problem.

Link to comment
Share on other sites

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 ?

Link to comment
Share on other sites

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

Edited by BeNe
Link to comment
Share on other sites

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.

Customer support is a top priority of the WiFi Pineapple. Whether a single user or large enterprise deployment, we have the right support option for you.

:blink::rolleyes:

Link to comment
Share on other sites

@ BeNe :

What kind of client target is the "ac:22:0b:6d:3c:10" ? (mobile? laptop ?)

The rt2800_usb in your first log are the AWUS050NH ? is your AP mod ?

Did you check the CPU graph when you activate everything (karma beacon harvester etc..?)*

It's maybe a overload cause the PineApple as just a 400mhz cpu and she doesn't work anymore if you push process in the limit.

Edited by Armaal
Link to comment
Share on other sites

The point is when running simple tasks such as wifite, or even JUST pineap. the pineapple reboots. Even in a closed environment where the pineap suite only has one client connected and only 1 essid in the list. after about 15 min it reboots. Literally any load on the thing and itll crash. Obviously not working as intended.

Link to comment
Share on other sites

@ BeNe :

What kind of client target is the "ac:22:0b:6d:3c:10" ? (mobile? laptop ?)

The rt2800_usb in your first log are the AWUS050NH ? is your AP mod ?

Did you check the CPU graph when you activate everything (karma beacon harvester etc..?)*

It's maybe a overload cause the PineApple as just a 400mhz cpu and she doesn't work anymore if you push process in the limit.

"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.

Sorry guys, I have had to take the last week off unexpectedly.

II'll get back to his thread asap tomorrow.

Best regards,

Sebkinne

Perfect! Thanks seb. I'm glad to hear from you :cool:

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...