Jump to content

flonkyplonk

Active Members
  • Posts

    14
  • Joined

  • Last visited

Everything posted by flonkyplonk

  1. Hey all, Have installed the kismet-server using opkg and it works very well. My only issue is that it wont read an oui file to identify manufacturer. I used the oui-update script that comes with airodump, and referred the kismet.conf file to it, but it never works. have also tried to download oui file from wireshark from the Internet and no luck there either. Has anyone got the oui file working with kismet on the Pineapple?
  2. Bump for interest! I can dump the WPS status to a log with wash, but what I need is the wps status and the chipset used - both of which are reported by airodump-ng, just not dumped to file. Anyone? Anything? If it helps to remedy my stupidity - kismet-server dumps the manufacturer in the xml output, but my regex kung-fu resembles elderly pub fighting, and I can't into tying the data together without it all, being on the same line!
  3. >>What would you like to see performance-wise in wash? Oh, nothing, was on the wrong track with Wash - thought it wasn't updating the signal strength readout on the screen like airodump-ng does (for zero'ing in on access points) but have since run it on Kali and have realised it is a limitation of wash not Pineapple implementation. Looking into this further it seems kismet does most of what I want, but I can't get kismet to recognise the OUI file (manufacturer description) I have dropped on the SD card - it finds it, but reports 0 lines, have tried this with two different OUI files. Also, can't seem to get a kismet client to connect to the kismet server on pineapple (which is sensational btw) So current question(s) anyone got advice on getting device manufacturer to work on pineapple in kismet-server, and any tips on getting external kismet client to connect to kismet-server on pineapple (I am running kismet from a kali vm, have added the subnets to the allowed list, but it just reports connection refused) Thanks all!
  4. Been looking at this a bit more. I have managed to output the WPS data by using wash -o <outputfile> instead of airodump-ng - though this still leaves the issue that the manufacturer is not being reported. Wash has a manufacturer reporting switch but havent got this working yet... Wash seems a little out of sorts on openwrt arch - as others have said, any tips on optimising it's performance? Also, still very keen to find out more about airodump-ng options, as it is my tool of choice and I can't fathom why it wouldn't log out some things it reports on screen?
  5. Hey all, Over SSH, when running airodump-ng with the --wps and --manufacturer flags, the status of both appears on screen during the live capture, but I cannot find this information anywhere within the .csv and .xml data logged. That leaves the .cap files, obvs but I'm a bit noob and haven't dug into them - also, alot of the cap files I get seem corrupted, perhaps due to a lot of weak signals when wardriving? Has anyone had any success with logging this data for later analysis, really scratching my head here. I tried to ask about this on the aircrack-ng forums a couple days ago but the mods havent put the question up so I figured someone here may have experience of this? TIA
  6. OK, My bad. I was connected to the WiPi still on that last post. Duh. I have it enabled in client mode with DHCP and it is working fine, but the WiPi now cannot connect to the Internet. Any thoughts?
  7. OK, Have just enabled DHCP for the client mode. Exact same issue, only now I have Internet from the macbook but that's only because the wipi is Mitm'ing every piece of traffic and it is still assigning the DHCP on my wired network, which already has a DHCP server. I don't have any infusions running at all btw. I have never used a single infusion, just airodump. Pls help???
  8. NB, I'm just about to enable DHCP for wired client mode instead of Static and will report back... But this didn't work in first instance...
  9. Hey all, Just updated to latest firmware, and am trying to use the wired client mode with static IP but feel I'm misunderstanding OpenWRT / the pineapple in general... What's happening is the DHCP server on the Pineapple is hijacking clients on my 192.168.2.* network. My macbook now always picks up a 172 etc etc address when attaching to any of my Apple airports. Anyone got this working? I know the WiPi has its own DHCP server / DNSMasq but my assumption would be that if the interface has an option for wired client it would config itself to not provide DHCP to the host network? Is this a bug with new firmware (didn't have this issue until flashing today?) TIA
  10. 1. First, set it up to run airodump-ng and write to file. I use the following for my dip switch customisation script (if you look at the pineapple dip switch page, funny enough the example config used there is exactly what you want to do - I use - airmon-ng start wlan0 ; airodump-ng -w (SD Card storage which should be /sd/)[yourlognamehere] mon0 2. Now, the box will start airodump-ng every reboot / boot. NB the second adapter(wlan1) needs to be off for channel hopping to work, otherwise wlan0 will just scan the same channel as wlan1. I've been running this, sometimes using tmux installed from opkg manager to maintain a shell long term when I want to SSH back in later and access the airodump-ng live display. Best up time so far has been 23 hrs and counting 3. Airodump gives you all this info, formatted three ways, as well as packet capture if run with no options other than -w (You can use the packet capture for WPA cracking attempts offline) . With no options, it is set to pick up and log every wifi beacon, so you capture all the wifi clients and all the access points. 4. With the config in 1 above, the logs keep rolling with incremental numbers appended to the log file(.01,02,etc), so your logs are preserved well across multiple reboots. The only issue I have now is that I need a way to check if it hung and reboot, without logging back in. Thats it. I use the scp command to get the logs and caps off the pine for analysis, although cat, grep and awk work brilliantly on the pineapple itself.
  11. Thanks for the response mate, So, (sorry couldnt post for a while) OK, So things have improved alot. I have had it running airodump for around 7 hours now and it's solid as a rock. TBH, most of the issues I was coming up against were my own! (You might have guessed that from the tone) I have little experience recently with subnetting and routing and the WiPi (I just invented that name, put a cheque in the post, Hak5) so that's where I came unstuck. I'm still struggling with dropping it into my network but I can't seriously cliam thats a problem with the device at all! Yeah, I'll say this thing is pretty great. It's brilliant that it has the web interface but I would definitely urge anyone in similar position to me to just try and run stuff from the terminal over SSH. Also, I put in a new Type 10 SD card, that is definitely an essential step. Also, I OPKG installed tmux terminal emulation, which allows me to set up a virtual terminal and not lose CMD line tools whenever the SSH connection drops.
  12. Primz, Thanks man for the instructions on unbricking to the latest firmware. I hadn't noticed that guidance online before. Useful info. Sorts my issue with rolling back to factory ROM every time this thing screws up (pretty much every time I try to do ANYTHING) I'm gonna fill in some blanks so anyone searching against this issue has a bit more intel... So, I'm trying to attach it in client mode to an apple airport wifi AP (2.4ghz, 802.11b compatible setting) the AP is working in Bridge mode, I guess that may be causing issues because the Mark5 is utterly unreachable (have nmaped the network segment and nothing shows up on port 1471. I'm guessing it is still set to 147.etc even though I set it to take DHCP off my server on the wire. The sad thing is, even as I did this and rebooted, I knew already that the effing thing was gonna disappear off the wire. Because, y'know, thirty times bitten.... It's now unreachable. Again. And needs to be 'unbricked' Again. I'll be honest here, this thing has never done anything for more than five minutes or so. On a good day, if it's just running, it will stay up. If I try and run an infusion, or something on the CLI, it's been 100 pc failure rate. EVERY time I come back to check the results it's either mute or hung. I'm using a macbook pro without an ethernet adapter, which is a major ballache as every time this thing F's up I can't just attach it and config on the wire. The MBP means I have to re-subnet my entire home network and attach this thing to a switch. I honestly think I've had enough. I'm boxing it and will see what happens. I have a wifi card in an Ubuntu Server that I use for network monitoring with Bro-IDS, It's had five nines availability since day one. This thing? .... five 1's... I'll work with Linux and forget I ever bought this thing. Going forwards I will be building a Snoopy drone instead for my mobile needs. For future reference, the guidance online for this is atrocious. The FAQ needs to be substantially enlarged. The pineapple desperately needs a manual and perhaps a little more focus on the CLI. This is a shame as the community and online support for this thing are otherwise God-tier. Nah, had enough. You guys all rock, sorry to be so negative, but I've poured weeks of my life into this thing and feel a sucker. If anyone has any actually useful troubleshooting steps, or pointers for optimum reliability, I'm all ears, and will reply.
  13. OK, Have calmed down somewhat :-) (not much) It's obvious Hak5 do care about their customers, and the support is generally excellent (eg, there was an issue with my battery charger combination as shipped - Hak5 sent me all new stuff free of charge to the UK within a few days. That was seriously impressive care.) Also, the posts on this forum are great. Anyway, I can only post twice a day(!) so I just wanted to use this to expand upon my rage post earlier and ask if there is a way to reset the mark v without taking it back to factory rom (1.20?). What's killing me is that after twelve hours hell yesterday just getting the system rom up to date, if it turns out the ONLY way to get this thing reset is to drag it ALLLLLL the way back to 1.20 and then update it every time I have an issue, then I'm going to give up on this hardware altogether. I so don't want to have to do that. So, (TLDR lol) can I use the dip switches to reset to the current ROM, without having to go back to 1.20? Thanks in advance guys.
  14. Guys, I'm calling this as I see it - the pineapple is not fit for purpose? We had some penetration testers in. They just sat there looking like idiots for an hour, trying again and again to get a simple Mitm attack going. I'd bought mine nearly a year before that and thrown it in a cupboard because after days of trying to get it working I just ran into too many issues, and too little guidance. So I get it out two days ago, finally get it on the latest firmware (Three attempts, three factory resets required). Wow, it looks like it's working - I have airodump on ssh FINALLY listening to beacons (Which is all I want it do do) I go to bed and it falls over within minutes (it found two MAC addresses as I went to bed - eight hours later, it's clearly locked up within minutes of me leaving it, still showing only two mac addresses, but the SSH tunnel has hung. Now, an hour into my sunday morning, three reboots, and the red light has yet to come on. Yep, that happens pretty much every other time - the wifi adapter wont even start. EVERY.OTHER.TIME. So, why aren't my problems on this forum, is this place just acres of astroturf? OK, I'll try and calm down, but5 seriously hak5 wtf is wrong with this thing?
×
×
  • Create New...