dark_pyrro

What keyboard language does the target use and what language file did you use when encoding the payload?

Ask in the O.MG section of the forums

No, there are no Pineapple related modules there. And, the user is probably not that interested anymore since last visit (and join) was on the 8th of May 2016. GitHub is more relevant in that case.

Well, there's no valid factory to send it back to. The Tetra has been end of life for years now and has also reached end of support status. Even if it was supported and still sold, it wouldn't be the correct way to send it to the factory anyway. No idea if that YouTube video is valid for the Tetra. The only OpenWrt Hak5 device that I've seen being "reset" using serial is the Signal Owl. Don't know at all if that procedure is applicable to the Tetra. https://forums.hak5.org/topic/49420-recovery-reset/?do=findComment&comment=325670

wlan0

So, when saying that, you tried to access the recovery web UI by following the firmware recovery procedure? Just want to be sure you have actually tried that. I.e. holding the reset button and apply power and hold the button for 10 seconds followed by accessing the Tetra using the Micro USB ETH port (as described in the link in your post).

What's in the docs is what's supported when it comes to the Packet Squirrel as a product. If you want to poke around and change things other than that, it's up to you, but don't expect to get support about such stuff from Hak5. I haven't seen many things that are closed source (but of course there is) when it comes to Hak5 products. Most Hak5 specific functionality is fully readable and possible to change (at your own risk). I'm on vacation now far away from my Packet Squirrel so I can't point in any specific direction, but a lot of things (most) are located in /usr/bin and if you find something that you can't look into since being closed source, then it is closed source. Nothing to do about it. Either it'd be Hak5 specific things or other packages/features that might be possible to install in OpenWrt. I'd suggest starting to get familiar with basic out-of-the-box features of the Packet Squirrel and read the documentation before starting to think about changing things related to the product. Especially if you barely know what you are doing.

What specifically do you want to tweak? What part of OpenWrt do you consider "closed source" in such a way that you can't get access to it?

So, the C2 server is started with the sshport parameter using the alternative port -sshport 2222 and then the device.config file for the Pineapple is generated and transferred to the Pineapple?

It depends on the chipset used

What was the content of the alternative payload that you tried?

Is that specific port used for a reason? It's not the default port needed for devices to connect to Cloud C2.

LOL

Have you tried to change the payload?

There's no reason or logic in this. Totally unclear what issues you face. First it's about WiFi interfaces, then all of a sudden it's about setting up evil portals. Being specific and detailed is key to get as good troubleshooting help as possible. Setting up an evil portal on the Tetra is not a difficult thing. It's just to install the Evil Portal module and add the evil portal of choice (either make one of your own or download existing ones, such as Kleo's pre-made evil portals). I installed the Evil Portal module on my Tetra just now and added the Kleo portals and connected a client device to the open AP and it all worked without any issues.

Are you starting C2 with the debug option/parameter?

OK, so compared to your other thread about the Tetra you seem to have; 1) the Tetra connected to the internet and 2) you can scan for networks around you using recon Why is this a problem? What do you want to accomplish/do? Define "nothing". Apparently some things are working, so to keep on saying that "nothing" works seems a bit exaggerated.

Yes, you scp the file to the Turtle. You say that anyone referring to the docs shouldn't bother, but the docs show exactly how it's done. It's done like the docs say and it's not rocket science at all. scp device.config root@172.16.84.1:/etc/ If you can't manage the task of using scp commands, you could put the device.config file on some web server and ssh into the Turtle and wget the file to the Turtle form the web server. Knowing from what OS you are trying to get the device.config file from is also good to know to be able to try to give some advise on how to move forward.

Which one is the "best" really depends on what you want to do and achieve. I can't say anything really about the O.MG device since I don't have one. I just know that it is a really skilled bunch of individuals behind it. The Ducky has always been good, but taken big leaps forward since the gen2 was introduced along with Ducky Script 3 and Payload Studio. My personal favorite is probably the Bunny though. Not really sure why, but it runs Debian, enables the use of keyboard and network features along with storage (internal and Micro SD) and Bluetooth capabilities. It's the "width" and flexibility that I like the most with the Bunny and that you easily can get "under the hood" of the device. For someone totally new to it all, trying to get oneself introduced to the Hak5 family of products, I would probably recommend the Ducky though as the first device to get. But, as said, it all depends on what you want to do with it. Read the texts in the shop, the documentation and look through the Hak5 GitHub to learn more before buying.

Not sure if it's relevant due to your other post that states that your Turtle isn't possible to be used because of some boot failure. But, in any case, it should be all possible to execute Responder on the Turtle after installing python3 and the python3-netifaces packages (along with other packages that the module needs). However, the Quickcreds module for sure needs some general tweaking though, but just getting the latest version of Responder running on the Turtle is possible.

Use the same command line parameter for scp

I would suggest to contact the reseller from where you bought the Turtle and get assistance. Contacting official Hak5 support will probably result in that you will be directed to the reseller, but you can always try submitting a support ticket to official Hak5 support and ask. Trying to access the Turtle using hardware serial is something I wouldn't advise to do since it will probably void warranty.

https://docs.hak5.org/hak5-usb-rubber-ducky/unboxing-quack-start-guide#2.-mod-the-case-for-a-squeeze-to-press-button

So, in what way did you try to serial into the Bunny?

Can you serial into the Bunny when it's in arming mode?