Bricked? Turtle getting a self assigned IP :SOLVED

[anode]

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 September 14, 2016 by anode
solution

[Just_a_User]

Don't know, you could try the factory reset/unbricking method in the wiki tho https://lanturtle.com/wiki/#!index.md

[anode]

Yup.  Done it twice with no joy.

Also tried other computers

 

edit: If I manually assign the IP things work.  Now off to investigate the DHCP server issue.

Edited September 7, 2016 by anode

[Forkish]

http://thehackernews.com/2016/09/hack-windows-password.html

USB S.O.C. dongles are getting a taste of the badusb-ish.  i think it's spread to the pineapple...

[barry99705]

39 minutes ago, Spoonish said:

http://thehackernews.com/2016/09/hack-windows-password.html

USB S.O.C. dongles are getting a taste of the badusb-ish.  i think it's spread to the pineapple...

What the hell does this have to do with the OP's problem?

[anode]

36 minutes ago, barry99705 said:

What the hell does this have to do with the OP's problem?

Nothing.  And even if it did spread to the pineapple, its still not my issue on a LAN turtle :)

[anode]

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 September 11, 2016 by anode

[barry99705]

If you're reflashing to stock, it should "just work"™.  Have you tried a different pc?

[anode]

Yup a mac and a linux box.  (both real PCs not VMs)

Edited September 12, 2016 by anode

[UnixSecLab]

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.

[anode]

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 September 13, 2016 by anode

[anode]

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!