x0Jakeyboy0x

Howdy, Snubs. Fancy meeting you round these parts. Thanks a lot for the answers. Seems the red iteration must also come in white, because the one I recently received is white. Looks very good too. If anyone else has some questions, feel free to post.

I thought we might start a FAQ thread. Q My USB Rubber Ducky seems to be keen on skipping the first line or two of my code. What do I do to fix this? A Placing a "DELAY 1000" at the very top of the script seems to give the computer alittle extra time to recognize the USB Rubber Ducky. If your code seems to be skipping at random, you may try using DEFAULTDELAY which will change the DELAY amount between every command.(Thanks Snubs) Q I have heard other people talk about a newer red version of the USB Rubber Ducky. Is it better...er? A The biggest difference is the actual hardware of the two. The first one has a flip door for the Micro SD card and was a bit flimsy. The red(or white) (second) iteration of the Ducky comes with a slot for the SD card to be pushed into. It's a much more solid holder and doesn't have the problem on the SD card popping out. (Thanks Snubs) Please add to this thread if you can.

Thank you itsm0ld. I too had this problem and editing the actual php file manually was the quickest fix. I appreciate it.

Installed and works great. Thanks.

Thanks dreadloft. After some frustration, I too found this.

Glad to be of service, Darren. Great product and I look forward to its future. No problem, allison.

Did you change any settings at all? http://forums.hak5.org/index.php?showtopic=22574

Problem solved. It is not the factory reset. It is the in-browser text editor that you can edit the config files with. I SSHed onto the box and used vi to look at the /etc/hostapd/karma.conf file. After a few tests I found that anything updated with the in-browser text editor had "^M" added to the end of each line. This was screwing up the commands sent to hostapd. After removing the ^M's everything worked perfectly. This was quite a frustrating dilemma and I hope I save some of you a headache. Darren, you might want to make note of this in your future guides. Thanks.

Back up off my thread guys. You have your own, allison.

Hey Darren, This is lengthy but thorough. Plugged it in (power and ethernet), booted up Linux(Backtrack 5 r1), followed the quick start, turned everything on(karma, dnsspoof, ngrep, everything), connected to the AP "internet" with my phone, went to a website, didn't work, ran script again, changed a line I had messed up on, worked, disconnected from AP typed in random AP name, connected successfully. Everything worked. Went to the configuration page, read thru the files to get a feel for it, proceeded to change the name of the AP. In the non-karma AP I changed "Pineapple" to "Free Wifi." Hit update. Didnt reboot or leave the page. Was worried about the space. Changed it to "XYZ". Hit update. Changed the karma config AP name to "XYZ!" Was worried about the exclamation but hit update anyway. Went to advanced tab and rebooted. Couldn't connect. Waited a minute. Nothing. Unplugged power, plugged back in. Waited a minute. Got on via the ethernet on laptop. No AP up so far. Waited another minute. Was too impatient and decided I'd just clear my cache and revert back with the factory settings. Hit the button. Reverted( with no "are you sure?" prompt surprisingly, though I see in the source you did code one?), says it will take effect on next reboot. Checked and the AP was up successfully with "XYZ", said to myself "you should know routers are slow", punched self for not waiting, went to advanced tab, rebooted, came back up, changed AP names again. Rebooted. Thought everything was cool. Clicked karma. Wouldn't start. Cried. Clicked it again. No go. At this point I went thru a variety of reboots and factory resets but the only thing I ever touched in settings was the AP names. Went and looked thru the log files. Here's my config and karma log which I've played with after the fact of it not working. But minorly. I did SCP/SSH in and look at the backup files. Most look very similar if not match identically. http://pastebin.com/JL1rDc8t The main problem in the log is the invalid/unknown driver complaint. Which I googled and it said to recompile the newest karma'd version hostapd with the nl80211 driver enabled. However I know this was not the case because I know it worked in the beginning. I also read an obscure thread about changing the network mask and it fixing the problem with hostapd. Anyway. So after that thorough run down. I come to the following possibilities in the order of most likeliness. 1- Factory reset is pointing to broken versions of config files. 2- Me running that script and messing up the first time with ICS somehow screwed it up. 3- I somehow broke hostapd or the driver? 4- Pineapple packet poultrigeist are screwing with me. Your thoughts? Thanks for any help.

Yeah you really have to becareful changing around your config files when they control your ability to talk to it in the first place. Though all I did was try to change the name of my access point and did a factory reset, so you never know. Try hooking up to it with the ethernet cable. If it gives you an ip still you should be able to connect. Try the website or via SCP like in the rick roll tutorial.

I have been trying to fix this for awhile now and I think I have narrowed it down to a possible fault in the "Factory Reset" button and settings. Could someone with a new Mk III and working karma copy all their settings for me?

Me too unfortunately. It worked at first. Then I changed the name of my access point and did a reboot and it wouldn't start. Then I did a factory reset and no go. Any ideas anyone?

I ordered my Mark 3 and everything got here quick and it looks great. It seems all you have to do is tether it to your computer and run a script(Linux) or change a few settings( Windows). I got it fully working within 5-10 minutes. However I started playing with a few settings and changed them and rebooted. The reboot was taking a few minutes so I ended powering it on and off. Then when It got back, my Karma setting won't enable. Everything else works and I know it did work because that's the first thing I tried. But it won't now. Any help would be very much appreciated.

I am debating between a few different netbooks. I would love to hear any input anyone has. I have read many threads but want more comments. I am looking for a netbook with... ~ > 4 Hours of battery life/3 Cell Battery ~ < 1.5 inches-ish in height ~ 10 inches-ish screen ~ Backtrack compatible ~ Packet Injection ~ Pretty B) The ones that seem to fit these requirements are... ~ Toshiba NB305 : ~ Acer Aspire One : Which exact models supports packet injection though? ~ Asus eee 1005's : Please add to my list and help me choose which to get.