Jump to content

saf

Members
  • Content Count

    4
  • Joined

  • Last visited

  • Days Won

    1

About saf

  • Rank
    Newbie
  1. I installed a wifi lan adapter today and it works great as an additional lan. This adapter has an activity LED which flashes in the usual way when there's activity. When I shutdown the pineapple from the GUI, or shell the blue light on the pineapple goes out, but the LED on the USB lan adapter doesn't. This seems to mean that something is still drawing power even when the device is "off". I can't ping, or otherwise access the pineapple so it seems like it's truly shut down. But I'm wondering what is still powered and does it have to be? A few observations. I can disconnect the WLAN adapter and when I plug it in again, the light doesn't go on. Does this mean the light was just powered by some residual capacitance in the system? But when I turn the battery power to the pineapple off, the light on the WLAN adapter goes off, so that seems to indicate that the power is coming from the pineapple's power source. My concern is simply that I don't want to waste battery power when I'm not using the pineapple. So if I shut it down, i'd like it to stop drawing down my battery. Anyone know what's really going on?
  2. While it's certainly not reasonable to expect to get the password of an SSID/AP if you don't know it. It would be useful to be able to broadcast a spoofed SSID if you DO know the password. That's a very likely scenario when you're testing a network which you are authorized to test. What happens now is you capture the SSID of the encrypted network, and then start broadcasting an unencrypted SSID for it. That is less than optimal. What's really needed, though I admit, I haven't considered if it's technically feasible or not, is a way to broadcast the SSID of the network that you want to capture with encryption using the passkey that you know because it's well known by customers of the establishment, or company.
  3. I've had limited success with it. Sometimes I've seen the same image displayed over and over. Often it'll work for a minute or so then just stop. As for overall stability, the nano I have is far from stable. I have spent more time resetting and starting over than I have working with it. Installing modules just makes it more unstable to the point where there's nothing to do but nuke and pave. I really hope the 1.1.0 release is imminent and helps to take it to a stable platform.
  4. Installed this (p0f 1.0) module today on nano 1.05 to SD card. When starting up, it seems to be unable to find the p0f.fp fingerprint file. It's looking for it in /etc/p0f but it's located at /sd/etc/p0f. When I changed the /pineapple/p0f/scripts/p0f.sh script so that the start command adds the '-f' switch (see below), it does start. However not really being familiar with this stuff yet, I'm not sure if this is the best way to solve the problem so I that it works properly if it was installed on internal storage. if [ "$1" = "start" ]; thenp0f -i ${MYINTERFACE} \ -o /pineapple/modules/p0f/log/output_${MYTIME}.log \ -f /sd/etc/p0f/p0f.fp
×
×
  • Create New...