Rurn

Whats your setup?

This happened to me too. With great frustration I wasn't able to SSH in, I even completely disabled the firewall for a little while but that didn't work. In the end I realised that I needed to wait more than 30 seconds for the Turtle to boot. For whatever reason, mine was being a little slow. So maybe try plugging in the turtle, and then wait 10 minutes. Once I did that, the Turtle has been working fine (and booting up after 30 -40 seconds as usual).

This worked for me too, thanks. However I havn't noticed any difference between the function of the Turtle since correcting this error, except I no longer get that error message when exiting the GUI. Did that error have any real impact that I didnt notice?

Hey all, I'm new, had the LAN turtle for about three weeks and I'm loving it. I have limited knowledge of the RF spectrum and I'm new to networks etc, but I've learnt so much by solving problems as I've gone along. However one thing I'm stuck with is setting up an SSH tunnel to the turtle remotely, in order to get a more diverse capture than I believe URLsnarf is capable of. Current setup Windows 10 putty (and/or Kali in Vbox) SSH to a digitalocean VPS SSH into my turtle remotely. I've searched the forums and googled for "wireshark remote ssh capture" etc, but everything I find seems either irrelevant or goes way over my head. From what I did understand it seems like I may not be able to do it. And I figured if it was possible, wouldn't everyone be using Wireshark instead of URLSnarf (which seems basic to me) Questions Do any of you gurus know if it is possible to get a relatively comprehensive live capture from the LAN turtle via SSH? Has anyone done this yet?