Jump to content
Hak5 Forums

Find the error......

Recommended Posts


My goal is to make my LanTurtle accessible over the entire LAN or the very best in the WAN.

For this I proceed as follows

Step 1: Without LanTurtle plugged in -> Windows 10 -> ipconfig


Step 2: LanTurtle via Ethernet cable cable to the router, other side -->  USB at the laptop -> ipconfig



Step 3 SSH into the LanTurtle


Step 4: Update modules



Now, if i plug out the LanTurtle after Step 4 and connect it to the LAN like in those two Pics below i cant receive the LanTurtle over LAN anything else....


What is my fault?


Edited by hanshaze

Share this post

Link to post
Share on other sites

So if I understand correctly, you have the LT plugged into a laptop which has the internal address and also into the LAN which received the address correct ? 

* From here, you mention that you plug it through a direct power source ? 

What I get from here is that the scheme is not accessible because the interface it is responsible for connecting to when plugged into a device through USB is not accessible as it's just a power source. 

You should technically still have a LAN connection, however. 

Also, if you're looking to access the turtle remotely you will want to look into setting up the Open VPN server either at your home on a Raspberry PI or on a router / networking device if it supports it. Hope I understood your hang ups here. 


Share this post

Link to post
Share on other sites

Thanks for your answer......

Yes, the LT is plugged to a direct power source.....

So at least one of the two IPs should be achievable, but this is not the case...

Do i have to forward Port 22 for Or for 192.168.178.xx?

For now this is the output of my screen


Edited by hanshaze

Share this post

Link to post
Share on other sites

Well, the interface would not be available because there is no interface to connect to if it's just a power source as this interface relies on a physical interface to attach to. As for the 192.168.x.x failing, did you set this statically ? It's possible the ip changed. 

Try doing a ping sweep of your LAN to ensure it is reachable - `nmap -sS -p 22 --open`

Share this post

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.