Catch22

Make sure you have the right drivers. Linux installs don't always find the right drivers and that can cause hell!

I know but I figured anyone interested could post haha Just a small task for me to do when I get sick of staring at a screen and want something easy to do!

I've noticed many community members here are showing off the default profile picture so to help you guys out I'll design you a pretty little tile profile picture sort of like mine! Just comment a few things you like, your username you want on it, and any other suggestions for what you would like me to try to incorperate! I'll make them for free in my spare time for anyone just drop a comment!

I actually learned all this from putting dd-wrt on an old Lynksys router and it did fry about 5 months later after regular use at nearly full power. Just use a little sense when your changing these settings, if you don't have a reason to send packets 1/2 mile then you can probably keep the power somewhere around half and be content with it!

If that worked for you great! I had the same problem awhile back and it was because I used the composite duck firmware which does not support automatic exicution. Very annoying thing to track down!

It can also shorten the lifetime of your hardware. Imagine the stock setting being 10 lets call it. This would be the equivilant of letting your car idle at 1,000 rpm. Now if you bump that up to 30 imagine you just redlined your car at 6,000 rpm, it won't last as long! It may not kill your device in days or even weeks if you crank it up but it will push it harder and it can cause hardware failures.

Alright so tonight I tested two more firmwares. One was c_duck_v2_S002.hex which had the same behavior as the previously mentioned firmware that would not autorun. I wasn't overly shocked by this with it also being a composite firmware. Then I tested the m_duck_v2.hex and to my amazement it worked as intended and autoran the payload like it should! Little sad that I can't use to composite driver as I really liked having the storage space for executables I plan to look into this more and still try to pick the minds of the community because it doesn't seem anyone else has had this issue. Anyway hope these results can help! On a final note when flashing the new firmware everything worked without a hitch and all three times every one of the 11 tests passed.

I haven't looked into playing with Windows 8 and getting it to boot from a USB but I assume there are guides out there like the link you posted that would explain the process. The reason I haven't bothered with Windows 8 is because any server/large network isn't likely to use Windows 8 as it is not created to be used in a professional enviroment so knowing more about Windows 7 has been my priority

Haha yeah still a newbie oops hahaha and I'm going to flash it with the newest non-composite firmware and see what happens later tonight! I'll post the results!

In that they are explaining how determine the drive letter or name then they refer to a .bat file as being the payload I believe (not sure why since the injection.bin should be the payload) but it still doesn't help me. The problem I'm having is my ducky doesn't autorun. It will run if I press the button but not just from being plugged in. Thanks for post though!

Sorry! I copied the link just forgot to hyperlink it :D Anyway I added it now so you can look!

Yes you could cogitoero I was just posting that as an example of the ducky could be used to help gain access not a full system to automate the entire process but with some more effort and thought you sure could expand on that to do more. Most BIOs I have run into besides machines running Win8 have had PIN codes and they have been run by very simple code that allowed for brute-force attacks. I was just giving him an example of how the ducky could possibly be used to do what he asked. And I did say that when making the code I assumed it used a PIN/passcode, not a passphrase or word.

Exile yes there is, check out this video: HERE It walks you through it step by step and its not hard at all :D Just make sure you have the new composite firmware! If you have questions ask away!

Just for the sake of anyone who stumbles on this there is a way to make a USB drive look like a CD drive, I used this guide to do it once and it did actually work. Only catch for me was my "CD" was write protected so I could only put things on it by making an iso and using that to create the disk. Anway have a look HERE!

I'm going out on a limb and going to say this is a computer you bought used and need to do this for ethical reasons... But anyway if you need to gain access to the bios the Rubber Ducky can help in one way, that is if the bios is locked with a passcode. If when you try to access the bios it asks you to enter a keycode or passcode you could write a payload that will attempt to brute force the bios passcode. This could be accomplished by writing a program to generate a long payload for the rubber ducky (assuming you dont want to type out lines of code for each number 0-9999 and assuming the bios is only protected by a 4 digit code). Here's an example of the code (This assumes you plug the rubber ducky in after you get to the passcode lock screen and that pressing enter once will allow you to try again): STRING 0001 ENTER STRING 0002 ENTER STRING 0003 ENTER STRING 0004 ENTER ... STRING 9998 ENTER STRING 9999 ENTER