hfam

Sitting here, I just tried it with my Kindle Fire, and achieved the same results. So I fired up PuTTY, logged into the MK4, and I *am* able to ping 8.8.8.8 from the MK4. Any ideas? It's got to be at the MK4. The Internet Connection Sharing is working as it should, and the MK3 functioning proves that out. It's got to be on the MK4. Anyone? ETA: I am unable to ping the Laptop's eth0 (172.16.42.42). I am able to ping 172.16.42.1. Fing shows the following on the Android: Net: 172.16.42.0/24 IP: 172.16.42.161 Gate: 172.16.42.1 DNS: 172.16.42.1 - Can ping my gate. Cannot ping the next hop (.42) - From the MK4 (PuTTY) I can ping (.42) and out to the Internet Still no love. Anyone?

Thanks for the reply (and the tip on Fing!!)! This is driving me absolutely crazy. I installed Fing on the Androis, got Karma'd up on the MK4, and pinging 8.8.8.8 on the Android comes up 100% packet loss. I'm completely out of ideas...just out of gas on and really bummed out. I've spent hours eliminating anything in my equation and proving out the issue exists on the MK4. What it is I haven't the faintest idea... I can take my MK3, swap it out for the MK4 right now, and it works flawlessly. It's GOT to be something on the MK4 not allowing packets through, everything else works perfectly, including the MK3. I can see the 172 network, I can grab the GUI page, but I can't get Internet. Just comes up empty. I even tried my 2nd MK4 to be certain, and got the same results. MK3 works perfectly though. :(

Got my MK4s!! However, I can NOT get my pwnt clients to connect to the Internet. (I know it looks lengthy, but it's just defining the steps I took clearly) Everything is setup just as it was with my MK3s, same laptop, same cables: - Laptop/W7 - Tethered correctly. - 42.42 is the local eth0 - 42.1 is the MK4 POE/LAN - WiFi on Laptop is providing Internet, Sharing is enabled - Internet is accessible on the laptop - I can ping (.42), (.1), as well as the IP my "pwnt" client gets from the pineapple (.161)..all from the laptop - Android Tbolt is the pwnt client in this case - The MK4 fires up and I get the interface via browser on the MITM laptop, and log into it. - I fire up Karma, and I can see the logs showing it's working, and can see it associating with a few local APs. - I add an AP called "PWNT" on my Android - Android connects to "PWNT", Karma does it's thing, associates with PWNT, and the MK4 provides my Android with an IP (.161) On the Android, I can see I've got full WiFi bars, but I open a browser and cannot get anywhere. Instant "page not found" On the Android, I reconnect to my real AP (the one providing Internet to the laptop), and can get to anywhere on the Internet. On the Android, I reconnect to "PWNT", and again, the Android dutifully connects to the Karma'd MK4. On the Laptop, I ping the IP that I see the Android's been given (.161) by the MK4, and sure enough, it responds. The MK4 will not let my pwnt client onto the internet. I then pulled out my MK3, powered/decabled the MK4, powered/cabled the MK3, let it boot up, and accessed the GUI on the MK3. In the meantime, my Android had reconnected to my local AP, and again, internet on the Android is working fine. On the Android, with the MK3 now powered up on the same laptop, I now connect to "PWNT", Karma does it's thing, and I can see my Android has re-leased the same IP (.161), I can ping it from my Laptop. The Android connects to the Internet just fine, as it should, through the MK3. So, you can see that the laptop is setup fine, the MK3 pwns my Android perfectly, but the MK4 in the identical situation will not allow the pwnt clients to access the Internet. What am I missing here? Is there something else I need to do on the MK4?? I've turned on Karma, and turned on URLSnarf. Client gets pwnt, but cannot get to the Internet. ETA: On the pwnt Android, when connected to "PWNT" (karma), I *CAN* get to http://172.16.42.1/pineapple, but I cannot get through the AP to the Internet ETA2: I've tried removing the ICS and resetting up the ICS to no avail. Still no Internet for the pwnd clients, still can connect to the MK4 GUI from the clients. Also tried my 2nd MK4 just to be sure and got the same results. I also again re-confirmed that removing the MK4 and putting in the MK3, everything works perfectly. ETA3: I tried running it off of straight power (was using USB power) and got the same results. I'm really stumped here gang, any help would be really appreciated!

SNUBSIE!!!! Thanks for takin' such good care of us at the HakShop!!!

Hi Darren, Outstanding, thanks for the reply! Sounds like you're well on your way to making the USB Storage/Modem dual functionality happen. I too LOVE the idea of having the dual-purpose device on the single USB port! Here's hoping you can get the issues sorted, keep up the great work!! On the 3G issue, thanks for the heads-up on the Ting option! I did notice that there is a $35 activation fee on their 3G dongle which is no big deal to me since you essentially get the device for free with the Hak discount. Most important to me, however, is that I don't see a way to use their service unless I sign up for it with monthly usage (i.e. I have to provide a CC to use their service). For those that don't mind doing that, it's great as it looks like it rolls over the minutes and/or only bills you for what you use. The prices are definitely right, and the "$50 off" bonus is awesome! I've got the Virgin Mobile version of the 760 you used in the early MK4 demo video, and the only advantage I see to that version is that you can activate it anonymously, and also buy "top-up" cards in an anonymous fashion to top off the service without providing any CC info, etc, that ties to the account. On the "jasager app store", I am absolutely blown away at your vision for where Jasager is headed!! That sounds absolutely amazing!!! Couple that with the Neinsager, Tactical kits, and all the rest of the goodies on the way and you have an AMAZING recipe for longevity and endless functionality! I've said a million times, and I'll say it a million more, you guys have really taken this project (at the risk of sounding cliche) to a whole other level. I couldn't be more excited for the MK4 hitting 1.0, and you just keep packin' the excitement into the expectations for upcoming improvements!! Your vision on this project is amazing, and that you built it on a "beginning of life" chipset makes it REALLY exciting to see where it's going to go! Thanks again for the thoughtful responses, Darren. Keep up the amazing work, brother!!

AAHAH! I'm such a dolt. I read your Neinsager post, and interpreted one of the statements in there to mean that, in order for Neinsager to work, you'll have to have both units the same, both either being MK3 or MK4. I bought a second MK4. D'OH!!! Oh well, I'll have a !#%!#$% Pineapple ARMY..."COME GET SOME, STARBUCKS!!" :) :) :)

In anticipation of the MK4, and based on Darren's demonstration previously, I purchased a Virgin Novatel 760 3G pay-as-you-go modem. I noted that it ALSO can act dually as USB storage, taking a MicroSD card up to 8GB. So, we know the MK4 will natively support the 760 as a modem. When I use the 760 on the MK4 as the 3G connectivity, is there a way to get the MK4 to also address the 8GB USB storage the 760 provides? That would really "kill 2 birds with one stone" by providing the 3G, PLUS providing 8GB of storage for SSLstrip, etc. As a secondary question, if the answer is "yes" to the above, will there be plans for HakShop (per earlier discussions on future MK4 plans) to release an 8GB MicroSD card which contains the extra scripting and functionality...so for the many of us who are going to use the 760 could seamlessly purchase the "pre-loaded" 8GB cards when they're ready to release? Thanks again to everyone involved with this project...amazing work!!

Telot's plans are really nice, and had I not found them pre-made, I would have been making my own with these plans. If you're a bit lazy on the DIY side (I was on this cable! :) ), you can also choose to purchase one ready to go on Amazon for fairly cheap: http://www.amazon.com/StarTech-com-USB2TYPEM-Barrel-Power-Cable/dp/B003MQO96U I've purchased a number of these for my MK3's and the fit and finish on these is flawless, they work perfectly.

This is AWESOME!!! Ok, ok...I just grabbed another MK4, there's no damn WAY I'm gonna miss out on Neinsager from the git go!! Sehr gut, Herr Kitchen!!! Danke schön!! ;)

I am soooo excited!!! You guys REALLY brought the heat on this one, the new features are unbelievable!!! Thanks to all you guys on the dev team for this amazing work, and snubs and hakshop for all their work!! I'm thrilled to be a tiny part of it all out here, thanks again!!

Guess who I just got email from?? And if you guess that, then you can certainly guess what I just purchased!!! AWWWWWWWWWWW YEEEEAAAAHHHHHHH!!!! w000w0000!! :) :) :) B) B) B) Is it wrong to tell you I love you Darren?? Like bros though...no skin!! ;) I'm so excited I'm not going to sleep all weekend! ahahahah! Check your email all you hakshop MK3 early adopters, because "You got mail!!" :)

I have not received my email yet. :(

Oh my GOD I've been hovering over my email today like a kid on Christmas Eve waiting for that email to arrive!!!!!!! AAARRRRGGG!!! FFFFFFFFFFUUUUUUUUU......... :) I just can't WAIT to get my hands on the new MK4!! <shatner> Must....get....new..........pineapple.... </shatner>

Dude, you're implementing the "first dibs" email for us MK3 customers!! That's AWESOME, thanks Darren!! I'm SOOOOO excited, I cant WAIT, and that Tactical Assault MK4 is SUCH a sweet idea!! I am electric with anticipation for where you guys are taking this platform!! Thanks again to the entire dev team for this amazing project, you guys are incredible!!

Nice!! LOTS of great info there, thanks Darren! Unfortunately, the link to the MK4 Firmware comes up empty though. Any thoughts? Thanks again for all you do, brother!! :)

Have either of you tried a different flavor browser? I can see OP is using Chrome. I've not had this issue with Firefox (or on the rare occasion I've fired it up, IE) on any version of the firmware. Install Firefox and see if that doesn't clear things up. I'd bet money it's a Chrome issue, but then again, I've been known to lose a few bets. :) Worth a shot. Good luck fellas. ETA: didn't notice the additional shots of FF....I'm out of ideas. :( Sorry.

Ha!!! I love you guys soooo much!!! Good LORD I cant wait, thank you Darren, Seb, Digininja, Snubs, and all the awesomness that is Hak5!!! Hey Darren, how about this for us loyal HakShop patrons who jumped on the MK3: Give us first crack at the first batch of MK4s? Send out a pre-release email to.those of us who invested in the MK3 platform and let us order a "one per customer" before the HakShop puts em up for all to buy? ;) This is great news fellas, and thanks for posting this info up Darren, keep up the great work brother! Off to dream about the MK4...counting packet monkeys jumping n00bcakes to help me sleep. ;)

Confirm fixed here! :) High style, thanks again Seb, this all looks to be working great!!

I absolutely love the MK3 and am having a LOT of fun with this platform, but an MK4 already on the horizon?!?! SWEEEEET!!! I sure wish I was closer to shmoocon, I'd LOVE to attend!! Great work all around, fellas...keep up the outstanding work, we're all very grateful for all the efforts! Very exciting news on the MK4! Darren, are you gonna give us a taste of the MK4 on an upcoming Hak5 show on Shmoocon coverage?? PLEEEEASE?? :) :) :) I'd love to see even the prototype and get a glimpse of the hardware, maybe some commentary on new features and improvements!! ;)

Is it wrong to say I love you? :) :) :) Eternal thanks seb, you're the best!!!

Heya seb, thanks again for all your hard work...it's brilliant how this just keeps improving and I know that it's a labor of love for ya that we're all benefiting from! That said, the Association Log display doesn't appear to be working for me in 2.1.1 (at least via the GUI), it just stays empty. The logging may be working, but I'm not exactly sure where to look for the log the GUI is parsing to see if it's just the GUI not updating correctly. I didn't get a chance to grab 2.1 before you added the minor update, so I can't confirm if this broke for me in 2.1 or not. However, I have all the other firmwares, so I flashed one of my AP51's back to 2.0.1, and the Association Log works on that version just fine. (EDIT: I just modded the firmware download URL to grab a copy of 2.1, I flashed it, and it definitely IS working for me on 2.1 as well, so 2.1.1 is where it stopped working for me.) Otherwise, everything else appears to be working correctly (except what you've noted above). - If you can point me to where I find the log that the GUI parses to display the Association Log, I'll look to confirm whether or not it's just the GUI failing to update, or if there is actually no logging taking place If there's anything else I can do to help track this one down please let me know. I'm really excited about this release, and Karma is working like a dream, great work seb!!

Alright, I'm with you guys at this point, something isn't working correctly with karma. EDIT: I re-read the above, and the one thing I didn't try was simply to yank the power on the "open" wifi, and sure enough, the Karma'd AP did it's thing in a fraction of a second!!! So, Karma IS working for me too, as OP stated, but I'm having exactly the same problem as OP and others are indicating with regard to changing Karma SSID, and it appears that trying to deauth from the MK3 does work, but I'm not able to get the Karma'd MK3 (the same one I'm issuing DEAUTH from) to grab the clients it's bumping off. I'll leave the original context of my details intact below as maybe it will help explain to someone know knows far more than me why: Karma SSID doesn't change using GUI Deauthing via GUI on MK3 doesn't appear let the bumped clients back on It very well could be me, but I have scoured Seb's explanation of the new version of Karma, and while I understand what he's saying, I simply can NOT get karma to do it's job. It's like it's not working at all, including the changing the Karma SSID issue. I've FINALLY had some time to break all this out and start testing function in 2.0.1. Here's what I'm seeing: (2) Alfa AP51's, flashed with 2.0.1 (1) Android (Thunderbolt) - using as the "target" or "client" I want to force onto my MK3 (1) Laptop (connected to one of the MK3s), Windows 7, working perfectly interfacing with said MK3. - I've set one AP51 to be a Karma'd MK3. Set it to come up as "FREEWIFI" via the GUI Configuration editor. I've confirmed it comes up as this, I can see it in W7 and Android. I then connect via GUI, confirm "interface" and "airmon-g" are both enabled, then I turn on "MK3 Karma". entropy bunny does it's thing, and it comes back to the main page and "MK3 Karma" shows "enabled" and green. - I'm using the other AP51 MK3 in default mode; Power it up, left it as "pineapple", just an open AP to connect my Android to. This is "pretend coffee shop open WiFi AP" that I connect the Android to. So, everything is as above. - MK3/Laptop are working perfectly, and "FREEWIFI" is shown on W7 and Android. Karma has been enabled. Still shows "FREEWIFI" as available to all devices. - MK3 #2 is setup as the "pretend coffee shop", and "pineapple" is showing up as an Open Network on Android and W7 clients. - Android is connected to "pineapple". It also sees "FREEWIFI" (the Karma enabled MK3). - From my GUI which is connected to FREEWIFI (Karma enabled), I take the BSSID of "pineapple" (open wifi), and I enter that into the DEAUTH section where it asks for it. I hit "DEAUTH" and look at my Android. - My Android does indeed get knocked off of "pineapple" (open wifi), but it just continues to try "pineapple" until it reconnects to "pineapple", the same physical AP it was connected to before the deauth. I've tried this so many times I lost count, but I've tried everything...forgetting the SSIDs on the Android device, rebooting everything, rebooting the Android only, etc. It's always the same, Karma never seems to do anything. FREEWIFI just sits there, awaiting a connection...saying karma is enabled, but it never does it's thing. - I then, through the GUI, use the dialog box to attempt to change the Karma SSID. I try to change it from FREEWIFI to "pineapplek" (k for Karma). It says it's completed, but I go back to the Android, and there is "FREEWIFI". - I then reboot the Android. Comes back up and sees "FREEWIFI", and not "pineapplek". - I then delete the SSID on the Android, and reboot the Android. Comes back up and sees "FREEWIFI", and not "pineapplek". - I then select "FREEWIFI" (remember, it should DEFINITELY be showing up as "pineapplek" by now) on the Android, and it connects to the Karma'd MK3, as expected. This shows (I believe) that the "Change Karma SSID" dialog box on Configuration page is not working either. I then pulled out a Kindle Fire and went through the exactly the same steps with exactly the same results. I then switched the roles of the (2) MK3's and went through exactly the same steps with exactlyh teh same results. The APs are both flashed with 2.0.1. Spent hours on this with no love at all. :(

Ok...WUT?!?!?! BT5 ARM installed successfully on a rooted Xoom?!?!?!?! I just *happen* to HAVE such a device basically sitting here collecting dust!!! I am going to be SOOO busy tonight! BT5 ARM on a Xoom

Oh man I can't WAIT to get my hands on some raspberrypi B models!!! Indeed, looks like we'll be able to get our hands on 'em sooner than later according to the site! And that damn telot has been like broken record with his raspberrypi!!! :) :) :) :) :) j/k! I would have never known about the raspberry had telot not brought it up (thanks for the info, brother!!)! It looks like an amazing project, and I really dig the charitable angle on that project, it'll be money well spent! I'm sooo excited...BT5R1 would be incredible to have on one of those units. I've got some extra AP51/MK3's..I'd LOVE to pair one with a raspberrypi and see where it goes. Getting BT5R1 on there would be pure nirvana!! Now I'm gettin' all pins & needles about it...gonna have to check the site every day to try to get my hands on 'em! :)

Hi Fellas, I'm pretty sure this was covered in the 2.0 hardware release thread...because I had some of the same questions and issues. The 2.0 version of Karma is a new implementation. As seb explained, both the non-Karma AND the Karma SSID are both the same in this new version. You can see this on the configuration page of the MK3 in the Karma section. The SSID set in that location is what it will be when you start Karma. Previous versions (1.9 and earlier) used a karma.conf, and also had different SSIDs for Karma and non-Karma modes. 2.0 is distinctly different in that it uses the same SSID for both modes. The best way I've found to deal with this is to make a "hard change" in the Karma section on the configuration page of the MK3. For instance, maybe changing it to something like "airport_free_wifi", or "starbucksguestwifi1"...you get the idea. something that doesn't give it away. Edit the change in the editing "window", not the dialog box, then save it. Now when you power up, Karma or not, your SSID will come up as that one you edited in. YOu can then change it on the fly if you need to (via the editing window, or the dialog box). The important thing to remember, however, is that the SSID will remain the same whether Karma is on or not. Hopefully that helped resolve what sounds like it's the concern here. I went through the same thing. Nothing's broken, it's just different than it used to be. Thanks to Seb for patiently explaining it to me in another thread! ;)