SeRCH1nER

I was able to recover the squirrel by reflashing it with FW again, so I tried to set it to bridge mode, but nothing would get captured. I set it back to transparent mode, and it failed to capture anything, so I reflashed it again, which fixed it. I don't think it likes to be changed to Bridge mode, or I'm doing something wrong, but I don't see how that can be. Oh well.. It was worth a try

Your reply is also SUPER old, but I've been using the packet squirrel quite a bit still, but I have to modify the timestamps in Wireshark. It's a real pain. SOOOOO, I tried what you suggested, but I'm unable to capture any data while set to Bridge mode. I set the payload back to what it was earlier, and NOW the damn thing won't work at all. Even in transparent mode, the packet squirrel will not capture anything, nor does it blink yellow as it's capturing like it had in the past. Nothing gets saved to the USB stick. It was just working yesterday 😞 Well this sucks. FAWKKK Thanks

Today, I had some testing on our IOT products and it asked me to do a firmware update. Woo, well after the update my Pineapple Mk7 is just displaying a solid red light. 😞 Sooo what's the fastest solution to this so I dont waste to much time troubleshooting this....

Thanks man, I will have to take a look.

Surprised no one has run into this issue before.

Would I run something like ntpdate -s time.nist.gov before running the payload. How would that then get applied to the PS.

I am assuming the Packet Squirrel would sync with a NTP server before running the TCPDUMP Payload. Any tips on how I can do this??

Is there any way to get the correct timestamps on my PCAP captures. Assuming this thing does not have a RTC since every time I log into the PS it has a different timestamp???! Annoying when troubleshooting and testing new network nodes without having a correct timestamp for my failures.... Grrrrrrr.