Jump to content

vepr

Active Members
  • Posts

    25
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

vepr's Achievements

Newbie

Newbie (1/14)

  1. Ahh thank you. I actually had a "sleep 60" in my recent code. But it was in a slightly differently place and causing it to not work. I just wanted to get some basic functionality, then I'll start customizing it properly. Thanks for posting your example code. That will definitely help me. I started down this path because I was not able to get the original Nmap payload to run properly. I haven't had issues with many of the other payloads. I even created a Responder payload that works pretty well. I thought the original Nmap payload was too complicated. I see that it's written that way to provide options and perform checks. But I don't really need all of that for my personal use.
  2. I think I got the Interface from some other code. It might have been tied to a function that I didn't see. I've edited the code above. The PS isn't grabbing an IP from my router on eth0 or eth1.
  3. Yeah, I don't know. When I plug my P.S. into my router and get network info, it lists: 2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000 inet 172.16.32.1/24 brd 172.16.32.255 scope global eth0 valid_lft forever preferred_lft forever 3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000 inet6 fe80::213:37ff:fea6:e934/64 scope link tentative valid_lft forever preferred_lft forever My home network is 192.168.90.0/24. So it's not getting an IP. My script only port scans 172.16.32.1 which is the actual Packet Squirrel.
  4. If possible, I want to be able to plug my Packet Squirrel into a router or switch, get an IP assigned to the P.S., get the network's subnet, and run an Nmap scan on the network. I know there is already an Nmap payload, but I want to keep my code simple and do it from scratch. Here is my current script I am playing with: #!/bin/bash # Nmap for the Packet Squirrel LED STAGE1 # NETMODE BRIDGE # NETMODE TRANSPARENT NETMODE NAT sleep 5 #### OPTIONS LootPath="/mnt/loot/nmap" # Path to store results LOG="nmap_$(date +%Y-%m-%d-%H%M)" # File name scheme #### # Grab the network you are in mynet=$(ip -o -f inet addr show | awk '/scope global/{sub(/[^.]+\//,"0/",$4);print $4}') echo $mynet >> $LootPath/$LOG sleep 2 LED ATTACK nmap -F -T 4 $mynet >> $LootPath/$LOG LED FINISH I can only seem to get an IP when I use Nat mode and plug the Packet Squirrel in via the Ethernet Out. But I only get the IP 172.16.32.1 which is the local IP. I can't get an IP/subnet using any other modes. Is there another way I should be doing this? As I'm typing this, I'm wondering if I'm checking for the subnet with the incorrect NIC. I'll see if I can dump a list of NICs that the P.S. uses in Nat mode.
  5. I'm just curious, does "lsusb" show the device?
  6. That is interesting. Something is wrong with my Owl. I've been messing with it for a few hours tonight and discovered that it only works part of the time. It connects to the Wifi AP about 25% of the time. I have several APs that I have tested this on and it won't even connect to some of them. About 50% of the time, the Owl boots up going through the usual LED pattern, then it just goes black and doesn't do anything at all. This is really frustrating.
  7. I also have a Wifi Pineapple and the Packet Squirrel. They do have reset options. The signal Owl seems like it was released too quickly. Maybe they'll provide some updates in the near future. I did have a bad experience with the Keysy RFID cloner though.
  8. Sect10_9 helped me figure it out. My wifi_connect.sh was not in all caps. It should be WIFI_CONNECT.s
  9. ahhhhh I didn't have WIFI_CONNECT.sh in all caps. That did it. Thanks for analyzing that! I'm not using a flash drive for the payload. I have the payloads directly on the Owl device. I checked and it works with both /etc/init.d/sshd start and /etc/init.d/ssh start
  10. Yeah, I'm out of ideas. I have added the #!/bin/bash. I've run the payload with the SSH line commented out. I've also tried using /etc/init.d/ssh and sshd. I wiped everything and copied and pasted the .sh and .txt. Both files are executable. No luck with multiple AP names and passwords. I guess I can try and set a static IP instead of using DHCP.
  11. Yeah, that is strange. I'll try /ssh again. Are you using a USB adapter on the host port of your Owl device? I wasn't sure if I should be trying to connect with the built in wifi or an external wifi adapter. I've tried both. Also, do you keep % on your SSID and Password or do you just have that there to show that it is a user variable? I don't have % but I'm just checking every option. lol
  12. So one method we can get information on the device when connected to a large network is have it reach out to a web server on the internet and relay it's information. Maybe create a simple form and write a script to have the Owl post to that form with it's current IP address and other information. If the network allows SMTP, we could possibly use a Python script that sends an email using Gmail credentials? When I get some time, I can help you guys do this if you want.
  13. That's strange that you have to run /etc/init.d/ssh instead of /etc/init.d/sshd When I'm SSH'd in arming mode, I have to restart SSH using /etc/init.d/sshd restart. Just giving SSH will give me command not found. Does attack mode use a different SSH service?
  14. I can edit the LED settings in my payload and the LEDs run just fine. But when I check my network, the Owl is not connecting in Attack mode. I decided to edit this line in extensions/wifi_connect.sh so that it gives me a log: wpa_supplicant -B -Dnl80211 -i wlan0 -c /tmp/wpa.conf > /root/payload/log.txt The log is telling me that wlan0 is not recognized when booting into Attack mode. I'm using the default settings. Do I need to change it to br-lan in my wifi_connect.sh? my log.txt: Successfully initialized wpa_supplicant Could not read interface wlan0 flags: No such device nl80211: Driver does not support authentication/association or connect commands nl80211: deinit ifname=wlan0 disabled_11b_rates=0 Could not read interface wlan0 flags: No such device wlan0: Failed to initialize driver interface Do I need to use an additional wifi adapter on the USB Host Port? I can plug in one of my adapters with (for example) a Ralink 2870 chipset and my log no longer gives me errors. But it still does not connect to my network via wifi. I have also run the payload using a usb drive and it makes no difference.
  15. I haven't had a chance to check it but the Owl does continue blinking in a pattern I set after turning it on. You can get the Mac address of your Owl with the command "ip a". Then when you boot your payload, you can check your router for connected devices. You can also use the app called Fing to search for your device Mac address. It also allows you to Port scan.
×
×
  • Create New...