Jump to content

radude210

Members
  • Content Count

    4
  • Joined

  • Last visited

  • Days Won

    1

About radude210

  • Rank
    Newbie

Recent Profile Visitors

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

  1. Also interested in this, running into the same problem :/
  2. Hey guys, I have an update on this! I got a little frustrated and ended up only using the squirrel for basic packet captures (which was still great to have). But it left me empty inside knowing it can do so much more. Finally I had another go at figuring out this payload situation. I tried to run the scripts manually to see the CLI output/errors and it was a simple permission issue. I had to grant execute permission to all for each payload.sh before it would do anything. I'm still a Linux noob. So if there was something I could have done to avoid this in the first place, or anythin
  3. Hello, I've been using my packet squirrel for about 2 weeks now and it's worked great. I can capture packets like nobody's business and VPN out to my VPS in the cloud without any issue. I upgraded the firmware to 1.2 and shortly after, I decided to try some new modules. I've tried the following and they all have behave the same way: ispyintel ngrep nmapdump In every case my host machine indicates there is no cable plugged in and I get no activity on the packet squirrel LED after the boot sequence (I know ngrep is stealthy intentionally, but the button doesn't flash red or g
  4. I have the same exact issue as well. Clients don't get internet, pineapple bar is unavailable, and yet I can ssh in and ping everything without any trouble :/ Interfaces look good, routes look good. I'm not sure why it's not working. Any help is appreciated!
×
×
  • Create New...