infosecwriter

I did. then made it all the way through until the reboot and dip switch reset as mentioned before. I reset a couple others with no problem to rule out TSTO errors. "try that address" I'll email the shop

Should I just send it back for a new one?

P.S. Green light is solid and blue is blinking after the flash and reboot. Left it sit for a couple days and still no response from the IP, so I believe I waited long enough for it to come back up. ;)

Out of the box, I connected to the Mark V and it asked for the initial password. Then it looped. Reset the box, same thing. So I followed the steps to reflash the mark V. reset the dip switches, after the flash and reboot. I can not access the device on 172.16.42.1. I reflashed it 6 times with the same result. No response on the normal IP address. Any suggestions?

My blue is the only one flashing. red and yellow are off. Did you reset the dip switches then reboot?

I also have the same problem. I just got a pineapple for Christmas. It wasn't functioning properly, so I went through the hardware flash. Dip switch all up except the last. got to 192.168.1.1 to flash fine. Reboot. Blue light and green light are on. Can't even ping 172.16.42.1. nmap shows no ports open. I tried it with the sd formatted ext4 and without an sd card. both have the same results. Suggestions?

I've tried this on 3 MarkVs and get the same result. Even after updating the 2.0.3 and making sure teh infusions are up to date. Jan 01 00:04:00.342 [notice] Tor v0.2.2.39 (git-bec76476efb71549). This is experimental software. Do not rely on it for strong anonymity. (Running on Linux mips) Jan 01 00:04:00.381 [notice] Initialized libevent version 2.0.19-stable using method epoll. Good. Jan 01 00:04:00.463 [notice] Opening Socks listener on 127.0.0.1:9050

Power... OK... I was using the battery. My moron self didn't even think about that option. Ok. I connected to wall power and when powered up, connected through wifi. Once logged in, Karma was started. Went into jammer and started mon0. It started to deauth. It seems to reboot at the 10 second sleep cycle. I changed the sleep to 30 and deauths to 20 Reboots around 30 seconds now, so the consistency seems to revolve around the sleep cycle and not the refresh. P.S. Thanks for the quick responses on a weekend.

thesugarat Thanks. I assumed the start in step 9 was just an ifconfig up. 1.) it was removed from SD and installed internal 2.) rebooted and connected to 3.) hit stop [auto], then start monitor, then wifi jammer | start. waited 5 seconds and hit refresh. It found half a dozen APs and started to deauth. Within 10 seconds it rebooted.

I'm not trying to talk down to anyone, but here are the steps so I don't miss anything Default install with jammer, site survey, RandomRoll, tcpdump, and network tools installed 1.) Start the pineapple 2.) wait 5 min until only the green and blue lights are solid 3.) Log in 4.) Configure Karma SSID "Linksys" with persistent checked 5.) Left click update 6.) close windows 7.) Enable Karma 8.) Left click Jammer 9.) WLAN Interface wlan1 [start] 10.) WLAN interface wlan1 [start monitor] 11.) Monitor Interface mon0 12.) WiFi Jammer [start] 13.) wait 5 seconds [Refresh] If fails with both aireplay-ng and mkd3 I'm not sure of any other variables. I have reset the firmware a dozen times. Next time, I will only install the jammer. Then the occupineapple to see if that makes a difference.

Thank you for the responses. As long as I do not use wlan0, the device works fine. It may be hardware failure. not sure. I will have to wait until next month before I can justify another purchase for testing. As far as consistency, I get it to reboot after I use karma on wlan0 with mon0 and use jammer on wlan1 with mon1. Then hot the refresh. Takes about 10 seconds. I will try an alfa card on wlan2 this coming week to see if I still get the reboot. Keep up the good work with the custom hardware product.

mw3demo Thanks. It is the RT card. I can consistently reproduce the issue. If it is a USB issue, that would make sense. I did not realize that they made the hardware themselves, that is awesome. I was trying to be patient while waiting for a resolve, but I reported the bug tracker a while ago and emailed a month+. I understand they are a small team and respect the grumpiness of the developer that lashed out on that link since I was a programmer in a previous life. It is still frustrating to have to wait for someone to finally respond. Especially when using the product in front of clients. My work around has been to deauth with another device which in not an automated drop and go attack. With all this said, the rest of the product seems to work well for the most part. Bugs here and there, but it is a great path and direction they are going.

I have used the Mark V only a couple of times. I was using Karma on wlan0/mon0 and turned on the wifi jammer on wlan1/mon1 using either aireplay-ng and mdk3. After I start the jammer, the markV reboots within a minute. I am also having some issues with the wlan1 working (indicator light rarely turns on). Any suggestions?