Jump to content


Active Members
  • Content Count

  • Joined

  • Last visited

Everything posted by Merlintime

  1. I do not claim to be an expert in the Signal Owl, Linux, scripting, etc; but hope that someone will be able to find this information helpful. There are multiple ways to accomplish some tasks. The commands listed below are what I used to get my Signal Owl up and running with a simple payload (first one was WiFi Connect). First, I highly recommend everyone check out Darren's Signal Owl - Getting Started video. It's very helpful to understand the Signal Owl setup and most important (for me) the LED sequence and when to push the button for Arming Mode. I've seen several posts which indicate their Signal Owl does not copy payloads/extensions from a USB Drive. Currently my Signal Owl is behaving in a similar fashion. I'm using a FAT32 formatted drive with the payload in the root of the drive but so far, no success. My Workaround: Manually copy the file from the USB drive to correct location on the Signal Owl (/root/payload). Steps: 1. Power on the Signal Owl. 2. Push the button during Select Mode (Red fast blinking) 3. Connect your device (compute, phone, etc) to the Owl_xxxx Access Point 4. Connect to Signal Owl ( via Putty (or some other SSH terminal utility) as the root account. 5. type: df -h (This should list the volumes mounted by the Signal Owl. My USB drive was /mnt/sda1). 6. type: cd /mnt/sda1 7. type: ls -l (if you want to list the files in the directory) 8. type: cp <payload file name> /root/payload 9. type: cp extensions/<filename> /root/payload/extensions (Optional: Only if extensions need to be copied also) 10. type: cd /root/payload 11. type: ls -l (if you want to list the files in the directory) 12. Verify the payload file has execute permissions (At least for the owner). If not, type: chmod 744 <payload file name> 13. type: cd /root/payload/extensions 14. type: ls -l (if you want to list the files in the directory) 15. Verify the extension file has execute permissions (At least for the owner). If not, type: chmod 744 <extension file name> Personally, I check a couple times to make sure I've updated everything correctly. That will be up to you. At this point, you should be ready to test the payload. Power off the Signal Owl, ( I count to 10) then power on the Signal Owl and watch the boot process. Depending on the payload, the LED should indicate when the payload has been successfully executed. Alternate Transfer Method: An alternate method to copy files from your system is to use (if using a Windows OS) the Putty utility PSCP or PSFTP. Linux should have those SCP or SFTP already loaded. Once the files have been transferred to the Signal Owl, I recommend verifying the file(s) have the correct permissions for execution. Rotating Payloads: Personally I prefer to not constantly copy files to and from the device when which switching payloads. I connect to the Signal Owl and rename payloads not in use. Which ever payload I want to be active is renamed to payload.txt (or payload.sh or payload.py; whichever fits best). Example: WiFi Connect: /root/payload/payload.txt is renamed to /root/payload/payload.txt_wifi_connect Garbage SSID: /root/payload/payload.txt is renamed to /root/payload/payload.txt_garbage_spammer Extending USB Ports: I used a Anker USB 4-port hub (plugged into the USB 2.0 port on the Signal Owl) to extend the available USB ports. This allowed me to have an additional WiFi adapter (RT5370) and a USB Drive connected to the Signal Owl simultaneously. In the future, I'm hoping to test running an extra WiFi adapter and a GPS module from the USB hub connected to the Signal Owl.
  2. I've not had any luck with the Signal Owl mounting a USB drive since following the initial setup instructions. To get payloads in place, I've been using the PSFTP utility to connect to the Owl. This method isn't likely going to help you since need to re-flash the firmware. Plan to test out the USB drive more this weekend. Keep the info coming so we can continue to learn from each other. 🙂
  3. I find that it wasn't necessary to have the /root/payload/extensions/wifi_connect.sh file rename to WIFI_CONNECT.sh. This file creates a WIFI_CONNECT function and exports this function for the payload during the session. For me, a key step was making the following files executable. /root/payload/payload.txt /root/payload/extensions/wifi_connect.sh <-- Used with the WiFi-Connect payload On a slightly different note, I also found the USB port would extend to a USB hub which should allow additional devices (SDR, GPS, etc) to be connected. You provided good information which helped point me in the right direction to get the Signal Owl up and running with a simple payload. I also recommend people check out Darren's Tutorial Video to help explain the LED sequences. I noticed the video after spending a little too much time figuring out the sequences to get into arming mode. Looking forward to some awesome payloads the community develops.
  4. I made a mistake when posting my comment. I would seem I probably shouldn't post with it's nearly 1AM. ? When gathering SSIDs for the pool I use the 'Deny' filter (I originally stated 'Allow'). My 'Deny' filter is usually empty which allows the Pineapple to add any new SSIDs. encountered.
  5. If you are attempting to add SSIDs to the pool, the filter needs to be set to 'Deny'. If set to 'Allow', only SSIDs with matching MAC Addresses will be allowed to connect, this would include adding the SSID pool. At least that's my understanding of how it should work. I have mine set to 'Deny' when gathering SSIDs for the pool which has been working fine. WiFi Pineapple Wiki
  • Create New...