Jump to content

PatriceKing

Active Members
  • Posts

    15
  • Joined

  • Last visited

Posts posted by PatriceKing

  1. Still no one answered, I know I just voided the warranty but I think I might fixed it, there was a loose cable, with a tiny tiny tiny soldered spot on one end... just fixed that and now it seems to be working.

    I have a few questions though: 1) Does the red light in the juice pack ever goes away? 1a) When charging it, it also stay red all the way the 10+ hours? 2) Does it get slightly warm like most batteries? 3) How you guys use it, in terms of "I've been using it for 2 hours, should I recharge it a little bit? (is that good for the battery, or better drain the whole charge, and then start over?), 4) "any way to know how much charge is left?" and some other silly questions that I'm holding back :)

  2. Hello everybody,

    I installed DNSSpoof infusion from the Bar, but I'm seeing there's no support (yet?) for it in the forums. I've tried porting some stuff from what I've used on the Mark IV, but no good results...

    I can't get no credentials captured. I'm not really good with PHP, and now everything has changed, the locations of the files and such. Been reading everything on the forums, and haven't found it... there are some guides on the net, but everything is for the Mark IV.

    Probably if I start diggin' deep I'll manage to get it working. But right now it's not possible,

    If someone has it working smoothly (thesugarat maybe?), and is willing to shoot me a PM, that'll be great. (*)

    (*) Not that I want an easy way out, right now I just could use the device for a greater plan, and as grandiloquent as it may sound, it could be my small contribution to make a better world (I know how it sounds, I know...) ... I'm not really THAT bad with this stuff, but my programming days go back to the 90s, ASM, C, virii on good old DOS, ... but right now I'm in other field. Anyways... I've been a great supporter of this Project since Mark III, and also bought a lot from the hak shop... but this project always seems to be on a beta stage... and the main vulnerabilities out there are being patched as we surf the forums, like HSTS, and the browsers are getting smarter...

    It's a great device, but it's too buggy still, nothing really work out of the box... maybe if you are professional pentester, or you can code scripts on the fly, it's good as it is... let alone I've had a defective battery juice now, and with my Mark IV (got those first dibs!) when I've got the juice pack later on, from all the different AC removable adaptors no one was the right fit for the pineapple... oh well... and, no, I'm not in the US... return the unit is not an option.

    ok, going to bed,... help over here! </rant>

  3. Thanks for being there Seb!

    Already did, with CC to snubsie too... but I'm not in the US, I'm afraid a return it's not really possible, I had to wait months for friend to bring me the Mark V. It won't happen again soon.

    I'm seeing other threads with people having this very same issue... apparently it's matter of resoldering/reconnecting something... I'm horrible with hardware... maybe a quick guide for the unlucky ones? I know it voids the warranty, but it's easier, and faster, and probably cheaper geting it fixed locally.

    Btw, big fan!

  4. hi guys! i've been doing some other stuff, but I've got my Pineapple VI when the first dibs where available, and right now is wow... waiting for this module to be packaged too...

    c'mon guys I need to find out what Santa has planned this time!! :P

  5. It feels pretty dead to me at this point. That is not to say there is no hope for it.

    As a customer, $80 is a good price for a completed, user-friendly product with the capabilities advertised for the Ducky. But for a budding open source project with poor developer communication? Not worth the money.

    As an unpaid contributor, my time is the most valuable thing I give. Duplication of effort is a complete waste of my time. I could spend my time working on fixing the Linux compatibility issue. But since Darren posted weeks ago that he was testing a FW with Linux support, I'm not interested in wasting my time on it. Why isn't the previously referenced beta FW in the repository for others to help test, find bugs, and submit patches? This is how open source works. Or is supposed to work. So, what we have here is not really an example of working open source.

    Until the development and communication process is fixed, the Ducky will not mature into the kind of product that I want to use or support.

    The Ducky is a great finding, and has huge potential, but I agree with Kenny pretty much. I wish I have more time (o more konwdlege! that will save time!) to colaborate more. So far, I can make this post :) and wish for the best.

  6. it's me again...

    still can't get clients to the web.

    @iamk3 ... now I get your reply. But no, the DNS Spoof Service was never active.

    I believe I'm making mistakes when configuring ICS.

    From my main box I'm able to access the web using my usual wifi connection and also the MkIV Control Center (I'm connected to it via eth) and I'm able to Ping 42.42 from the clients.

    I have ICS enabled on eth and IPv4 Address is 172.16.42.42 / Subnet Mask 255.255.0.0 / Default Gateway <empty_here>

    and right there I'm kinda lost...

    My Network connections are:

    Local Area Connection: pineapple, shared

    Wireless Network Connection: RTL8176, [MyISP]

    I know I'm doing something wrong with the ICS... I tried different things on my eth and then rebooting the MkIV... and so on... but no luck yet...

    Help! and Thanks

    *** next time I'll try without doing the laundry at the same time

  7. 1st post, noublesse obligue, i love u all guys.

    can't figure it out yet, trying in windowz though.

    * running 1.0.2

    * ICS enabled: main box connected to my Wireless AP and with the MK VI on Ethernet (with IPv4 set to 42.42) ... I'm able to surf the web and to access the Pineapple CC just fine.

    * then, only activating Karma, client connects fine, I'm able to ping 42.42 from the client, the default "redirect" script works, etc.

    but no love yet, for the web, that is.

×
×
  • Create New...