wedge Posted October 4, 2022 Share Posted October 4, 2022 I've had my LAN Turtle for a couple of weeks now. Going through all the menu options, added a 64GB SD and generally screwing around with the modules. One of the last modules I went to was DHCP Settings... that does what, I do not know. Whenever I select it, the Window hangs (no navigation to other options permitted) and dumps back to the root screen (Format SD, change password, etc.) after ~10 seconds. I'd love to troubleshoot but not sure where to start. Thoughts? Link to comment Share on other sites More sharing options...
dark_pyrro Posted October 4, 2022 Share Posted October 4, 2022 What module are you using? Name? Origin? Link to comment Share on other sites More sharing options...
dark_pyrro Posted October 4, 2022 Share Posted October 4, 2022 Are you referring to the configuration of the Turtle (not any actual module)? I.e. the WAN IP settings. Link to comment Share on other sites More sharing options...
wedge Posted October 5, 2022 Author Share Posted October 5, 2022 Yes, configuration. Not one of the modules. Link to comment Share on other sites More sharing options...
dark_pyrro Posted October 5, 2022 Share Posted October 5, 2022 My guess is that it likely "freezes" because the network service is restarting when entering that menu item. The menu screen that is shown where the DHCP menu item is available is in the file: /usr/lib/turtle/config.menu The function that handles the DHCP menu item specifically is called: network_ip_popup This is what happens for the DHCP menu item within the function above: uci set network.wan.proto='dhcp' &>/dev/null uci del network.wan.ipaddr &>/dev/null uci del network.wan.netmask &>/dev/null uci del network.wan.gateway &>/dev/null uci del network.wan.dns &>/dev/null uci commit network &>/dev/null /etc/init.d/network restart It's possible that the last line (that restarts the network service) kills your session making the window appear to hang/freeze and being unavailable. All the settings are made on the WAN interface (which should be eth1, i.e. the RJ45 side of the Turtle), and you are probably connected using the USB side/eth0. But, since the network service is restarted as a whole, it might affect the LAN side as well. If you keep the frozen window open and start another ssh session from another window, the Turtle is responding allowing you to connect a new ssh session, so it's not all "dead". Link to comment Share on other sites More sharing options...
wedge Posted October 19, 2022 Author Share Posted October 19, 2022 *facepalm* I did NOT have eth1 connected at the time. I'll have to try that when I get home. Thanks @dark_pyrro! I'll mark your post as the solution if that's what ends up being the issue (operator error). Link to comment Share on other sites More sharing options...
dark_pyrro Posted October 19, 2022 Share Posted October 19, 2022 You will most likely get the same behavior when the network service is restarted which possibly would include all interfaces. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.