bored369

Someone posted this link in the IRC chat a bit ago (forgot who :( ) but there's lots of options for different screens Note that when it has hdmi it can accept any hdmi input (so the compute sticks, rPis, desktop/laptop graphics cards or anything with HDMI output all work with these) https://www.adafruit.com/categories/287

Did you find/figure out the answer? I don't have a mac to play around with but looking at the payload for osX here: https://github.com/midnitesnake/USB-Rubber-Ducky/wiki/Payload---OSX-Ascii-Prank Looks like it maybe "GUI SPACE" which would kinda make sense because that GUI is the windows super key so if it was on a mac it would be the mac super key. but again i don't have a mac to test it out on This payload shows "COMMAND SPACE" though so now I'm not sure lol: https://github.com/midnitesnake/USB-Rubber-Ducky/wiki/Payload---OSX-Passwordless-SSH-access-%28ssh-keys%29 I didn't try searching the forums very much for it though, so you may want to try that if you haven't already or you could also check in the #ducky channel on the IRC and see if anyone in there might know (though I don't see much if any chatter in there since i've joined it a week or two ago)

I suppose if you want to you could reverse the setup internally (you have access to the shell and can change all the ip settings and dhcp server/client settings if you want to). What you were describing in your first post was you wanted your laptop {plugged into the actual ethernet port "eth1") to get internet from the desktop (plugged using the usb ethernet port "eth0"), assuming the desktop has an internet connection from an existing separate connection (wired or wireless). What he says in the video is the default config is for the opposite direction and you can change it if you want. You'll want to know about setting up IP addresses for ethernet ports, defining them as dhcp servers or clients and configuring the firewall for both eth0 and eth1 to allow this type of setup. Also remember the connections are bridged by default (this will play into the settings I believe). What you say in your second post I don't think you even need to do, but you could if your dhcp server on your domained network is assigning ip addresses by mac address. By default though you can just plug the usb port into the desktop, take it's ethernet wired connection plug it into the turtle and you're set. You can ssh into the turtle from the desktop "eth0" which would have an assigned address in the range of 172.16.84.X (but not from the local network connected to the wired "eth1" which would have an ip address assigned by the dhcp server on local network the wired connection is plugged into on the other end of the wire. The turtle would have internet access through "eth1" via the normal networking, just as if the wire was plugged directly into the desktop. The most you would really have to do to stay "invisible" to the end user is setup the static "eth0" to be a dhcp server in the range of the local network (this way if the user checks their ip it has an address that would be expected to be assigned if on the local network dhcp). For the first post setup, you would basically need: --desktop to have a wired or wireless connection already enabled and working --plug in the turtle to the desktop and don't have a wire going to it yet --ssh into the turtle, configure the eth0 and eth1 to basically be swapped so eth0 is now a client and the eth1 is a server (you'll also want to make sure ssh can be accessed from the eth1, which by default it is not accessible and all ports coming into the turtle from the wire are blocked if i'm not mistaken) --configure the eth0 that appears on the desktop to be a dhcp server to assign the usb connected eth0 an address and share the internet with that connection via the existing desktop connection --plug the laptop via wire to the turtle and the ehternet port on the laptop --theoretically the laptop will pull an ip address from eth1 you setup to be a dhcp server and will allow the laptop to get on the internet via the connection existing on the desktop again I don't think this was what it was really designed to do and i'm not sure how the modules would handle connecting out (since you now have the firewalls on both the desktop and the local network the desktop is connected to get through), but theoretically it could be done this way. You probably want to make sure you review this page on resetting the lan turtle back to default if you mess up something on the configuration of the eth0 and eth1 and can't connect to it again from either side: http://lanturtle.com/wiki/#!index.md#Factory_Reset_/_"Unbricking" I really think it would be easier to have the laptop connected to wifi, share the internet connection with the wired port of the laptop. Plug the ethernet into the lan turtle and then the usb to the desktop. The desktop would receive internet through the lan turtle and you could ssh into the turtle form the desktop to configure modules which you could setup to setup a reverse shell to the laptop and work with it from the laptop. But again, seems like a weird setup and not the intent of the original design in general because normally you would want the desktop to just be connected to the local network through the lan turtle (man in the middle) and then have it reverse shell out to a connection either on the local lan or out to the wan somewhere. Just my opinion though and it's a pretty powerful little device with an embedded linux you can pretty much configure however you'd like as long as you know what you are doing.

It'd be better to run cable and use a ethernet extender about halfway between (like this one http://www.veracityglobal.com/products/ethernet-and-poe-devices/outreach-lite.aspx)it will cost a little more to get cable you can bury but that would be cheaper and more reliable than trying to extend a wireless that far through directional antennas and such. The cable route could be done with the $300 budget (including the extender bit)

I'm not positive but i think internet has to come from the ethernet side of the turtle. So in your diagram there, if your laptop has internet, then you connect it to the turtle in your desktop the desktop can get internet via that route, but not the way you are describing there. Basically the turtle just needs internet coming from the ethernet side so it's modules can get out, it doesn't have to be plugged into a system to work. There may be a way to share the internet between the network connections on the desktop, but i don't think that's the way it's designed to work. I could be wrong, I've only had mine for a little bit as well and haven't played with it as much yet.

It sounds like a bad capacitor somewhere, you may be able to find it by looking at the board and looking for broken/leaking/bulging tops. Basically when you remove power it has to fully discharge before it will work again, then when it does and you reapply power it overloads itself again and won't reboot till it's fully discharged. (at least that's my simple understanding of it all, i'm by no means an expert on electronics mind you) If you find one that's bad, it's normally just a matter of finding the same one for replacement and a careful hand with a soldering iron. I've replaced them on motherboards before and they work well again.

You can try the "Upgrading Manually" section or just go straight for the "Unbricking a bricked Wifi Pineapple MKV" (I know it's not bricked but it would work the same still) from this page: https://www.wifipineapple.com/?flashing

Well done Sebkinne! That has to be the nicest way I've ever seen anyone say don't use IE since the turn of the century! On another note (since it sparked my curiosity): M$ Edge appears to "work", will that also be "supported"? I wouldn't blame you if you didn't (just FYI) Lastly (again the curiosity was killing me :) ): It looks like DataHead may have been correct on the clicking the "Show" links bit. It does "work" under IE, but it also does "look" broken and I can understand the not supporting it for sure!

Start with the Wiki Videos and & guides: http://wiki.wifipineapple.com/#!index.md Then on the forum there is a ton of information in this forum sub: https://forums.hak5.org/index.php?/forum/78-mark-v/ This blog post has lots of informative stuff on it for getting started too (disclaimer i didn't actually read all of this or use it myself, just bookedmarked it to come back to later or maybe for this specific purpose): http://4nzx.blogspot.com/2015/05/so-you-bought-new-wifi-pineapple-markv.html Nothing beats just turning it on and playing around with it some before you try to go out and really "use" it. I've only really played around with mine at a recent Linux Fest and just had it setup to Rick Roll like described here: That's for the mark IV but it's about the same (or really even easier) to do on the mark V Best thing at the conference for me tho, was turning around when I heard "never gonna give you up" for someone that had their speakers on high and a really confused look on their face. For the various infusions I'd suggest starting off with the the name of them and then searching the web for the tool they are built on so you can get your best understanding of their various uses (in and outside of the webGUI) It's a great device but has it has more potential the more knowledge you have behind it.

On the back of the card that came with it, it suggest that but also mentions that it should install the Realtek RTL8152 driver if you want to search it out

These anker powercore batteries work well (I use them with my pineapple) I have the 10050, 13400, & 16000, all tested and work with my MKV. The 20100 is going for 39.99 on US amazon and your best bang for your buck, about the same size as the juice pack. Since I started playing Ingress years ago, i've heavily tested external battery packs and anker's seem to hold up the best over time imo.