Jump to content

bl4ckc4t

Active Members
  • Posts

    12
  • Joined

  • Last visited

Everything posted by bl4ckc4t

  1. I was experiencing the same issues as well. I changed the channel from 11 to 1 and at least now the SSID doesn't drop.
  2. Thanks for that clarification on the Tx and Rx difference, while testing on the MK4 the results from the signal strength were less then what the MK3 produced, that's when I noticed the difference.
  3. I thought the stronger the signal of the pineapple the higher success rate of redirected connections it receives.
  4. Is there any reason why the txpower on the MK4 was set lower than the MK4? And I've tried to change the settings, but will not go beyond 18 dBm. I issued the following commands, just to try if it will go beyond 18 dBm: iw reg set BO iw dev wlan0 set txpower fixed 2700 Comparison: -------WiFi_Pineapple MKIV root@Pineapple:~# iwlist txpower lo no transmit-power information. eth0 no transmit-power information. eth1 no transmit-power information. br-lan no transmit-power information. wlan0 unknown transmit-power information. Current Tx-Power=18 dBm (63 mW) mon.wlan0 unknown transmit-power information. Current Tx-Power=18 dBm (63 mW) -------WiFi_Pineapple MKIII root@Pineapple:~# iwlist txpower lo no transmit-power information. eth0 no transmit-power information. br-lan no transmit-power information. wlan0 unknown transmit-power information. Current Tx-Power=27 dBm (501 mW) mon.wlan0 unknown transmit-power information. Current Tx-Power=27 dBm (501 mW)
  5. Been powering the MK4 over USB and it does maintain the power, what I did notice is that when you connect an external USB storage; it appears to power on the storage device but the MK4 will not recognize it. Only after I plug in the power adapter will it recognize the external USB drive connected.
  6. Got the notification last night and just placed my order this morning....
  7. Now added a couple of holes to my back pack for the Ethernet cable that runs through the harness into the case. And here is the front. Exceeded my upload quota on images so I had to throttle down the resolution.
  8. Great minds think alike Darren. This is what I did with the Mak3, but combined it with my Alfa card and threw it in a bag. This was my initial setup with a battery pack. This was the guts underneath the battery. Then it started heating up just like others did and decided to convert the power to USB and remove the battery pack and add a fan. Now much more simplified I ended up with this. The external view with a mesh grill. External USB connector for my Alfa. Bottom portion of the Mak3.
  9. Appears that hostapd is starting the interface with the label "mon.wlan0".
  10. Seb on the same note around mon.wlan0: What is setting the mon.wlan0 interface label when the pineapple starts monitor mode with airmon-ng? From shell when you manually stop the monitor interface (airmon-ng stop mon.wlan0) and start it back up (airmon-ng start wlan0), the monitor interface is labeled (mon0).
  11. I've been following this thread and been doing some testing myself. What seems to be working for me right now without changing much, aside to the sequence is changing the SSID before starting Karma. On initial start-up the device broadcasts "pineapple" with Karma off. I change the SSID and get the successful message, I notice the broadcast SSID changes to what I've specified and no longer see "pineapple". I then start Karma and noticed that the new broadcast SSID changes back to "pineapple", but through the hostapd_cli with the get_config, it does reflect the SSID that I specified. Approximately 1 minute the new SSID begins to broadcast. I've repeated this process multiple times and appears to be consistent. Not sure if it's a sequence issue here or if it was initial designed to be executed in that manner before Karma starts. Curious if the sequence helps anyone else, but prior to trying the sequence I was messing with the permissions of the "hostapd" directory, but reverted back to it's original state.
×
×
  • Create New...