Jump to content

Bricked? Turtle getting a self assigned IP :SOLVED


anode
 Share

Recommended Posts

Plugged in the turtle and now just getting the self assigned IP on the USB side.

169.254.xx.xx

So I can't ssh in. 

It does get a legit IP on the ethernet port.

nmap shows no open ports on the ethernet port.

 

EDIT:  found solution ( and to avoid reading through full thread)

Set IP manually, ssh in and in /etc/config/dhcp  At bottom make sure

option maindhcp '1' 

and not '0'

Edited by anode
solution
  • Upvote 1
Link to comment
Share on other sites

OK, wandered around and still lost.

How to enable DHCP server on the USB connector, so the Turtle will dole out an IP to the host PC?

Which interfaces are wihch?

(I've re-flashed at least 3 times with no joy)

Edited by anode
Link to comment
Share on other sites

Have you tried just setting the IP manually on the ethernet device that's getting a 169.254.x.x address?  You should be able to change it manually to 172.16.84.3 (for example) and that should make it possible to communicate with the LAN Turtle over its USB network so that you can log in with ssh, do your updates from there, and then try again with an updated device.  I really should "just work" but if you aren't getting DHCP that's usually related to the host OS not getting a response from the Turtle fast enough for its liking, and assigning the self IP instead of doing DHCP.  The turtle is taking too long to initialize after it's recognized as a network device.  If you can't log in after setting a manual IP in the 172.16.84.x range (that isn't .1) then there's something up with the device.

Link to comment
Share on other sites

12 hours ago, UnixSecLab said:

Have you tried just setting the IP manually on the ethernet device that's getting a 169.254.x.x address?  You should be able to change it manually to 172.16.84.3 (for example)

Thanks

Yes, I can manually set the IP.  Stated that earlier.  But it renders the LAN Turtle basically useless for it intended use.

The Mac (10.9) has zero problem getting a DHP lease via any other adapter (WiFi, built in E-Net, Tetra, MK4, ReaverPro, several USB-Ethernet adapters)

Same with the Lenovo Kali box.

The turtle worked fine in the past, then poof.  No Leases after a simple reboot.  Been re-flashed 3 or 4 times.

Edited by anode
Link to comment
Share on other sites

Found it !!!!

 

in /etc/config/dhcp

at the bottom

config odhcpd 'odhcpd'
	option maindhcp '1'
	option leasefile '/tmp/hosts/odhcpd'
	option leasetrigger '/usr/sbin/odhcpd-update'

option maindhcp '1'  was set to '0'  putting it to 1 fixed the prob.

woohoo!

  • Upvote 1
Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...