mekvii Posted November 14, 2017 Share Posted November 14, 2017 Hi, Had the Turtle working for about a week. Came back to it a month later and now I cant update modules or do anything really. I get an IP address after I factory restored it. However it still says "no modules available" and when I try to update it says "wget: not an http or ftp url www.hak5.org/gear/lan-turtle" . Not sure if it's a different url now I have to point too? I'm probably missing a simple step somewhere but any direction would be appreciated thanks! Link to comment Share on other sites More sharing options...
dakotad Posted November 14, 2017 Share Posted November 14, 2017 Try plugging in a cable connected to your Internet router on the other end of you the turtle. That worked for me. Link to comment Share on other sites More sharing options...
mekvii Posted November 14, 2017 Author Share Posted November 14, 2017 Update: I used scp to update the device to the latest firmware. It seems to be working so far however I am only able to download one module at a time if I try more than one it fails to download. I follow the tutorial Darren posted on another forum: 1. Download the latest UPDATE file from https://downloads.lanturtle.com/ 2. Verify that the MD5 checksums match 3. Manually SCP the file to the LAN Turtle in /tmp (ex: scp turtle-2.bin root@172.16.84.1:/tmp/) 4. From the LAN Turtle, exit shell to the bash prompt and issue: sysupgrade -n /tmp/turtle-2.bin 5. Wait about 5 minutes for the LAN Turtle to flash the firmware and reboot When you SSH back in keep in mind the password resets back to the default "sh3llz" (and is required to be changed) Link to comment Share on other sites More sharing options...
Thecolorchanges Posted November 15, 2017 Share Posted November 15, 2017 I pulled out one of my older turtles running v2 earlier after @Sebkinne corrected a server side issue and noticed I couldn’t pull the update to v3 either. Got a quick look at wget attempting to pull the .bin and failing due to SSL. Was able to scp the file up and update as wiki/ @mekvii detailed. Though I cannot repeat the moduleManager issue, pulled down 5-6 all at once. Working ok here ? Link to comment Share on other sites More sharing options...
Samuel Godoy Posted January 23, 2018 Share Posted January 23, 2018 I solved, hak5 and lanturtle are running https, but LanTurtle Classic does not support Download turtle-2.bin personalized for other server I just changed the urls in the files Link to comment Share on other sites More sharing options...
CommodoreDad Posted February 11, 2018 Share Posted February 11, 2018 Has anyone solved this? I manually upgraded the firmware to v4, but still am unable to download modules via the Dialog "GUI"...I get back a message saying "No modules available". Additionally, when I exit to the shell and after inspecting /usr/bin/turtle_update, I tried to issue the 'wget' command manually (no, not for modules but to see if the https problem people are taking about was fixed in firmware v4). Turns out, I get the following message: root@turtle:~# wget https://lanturtle.com/updates/current_version --2017-11-22 03:46:25-- https://lanturtle.com/updates/current_version Resolving lanturtle.com... 2400:cb00:2048:1::681b:b041, 104.27.177.65, 104.27.176.65 Connecting to lanturtle.com|2400:cb00:2048:1::681b:b041|:443... failed: Permission denied. Connecting to lanturtle.com|104.27.177.65|:443... connected. ERROR: cannot verify lanturtle.com's certificate, issued by 'CN=COMODO ECC Domain Validation Secure Server CA 2,O=COMODO CA Limited,L=Salford,ST=Greater Manchester,C=GB': Issued certificate not yet valid. To connect to lanturtle.com insecurely, use `--no-check-certificate'. root@turtle:~# So it seems the HTTPS problem still hasn't been solved. I'm presuming this is the same issue with the Dialog scripts for downloading modules though I've not dove into the Dialog scripts yet. Just thought I'd ask if anyone had solved this yet. Thanks! Link to comment Share on other sites More sharing options...
CommodoreDad Posted February 11, 2018 Share Posted February 11, 2018 So I did a little more digging and found adding '--no-check-certificate' to the wget commands in /etc/turtle/modules/modulemanager allowed the Dialog scripts to obtain the modules as expected**. I presume this would work for /usr/bin/turtle_update as well. However, this is obviously not the most secure way. So, I also created a ~/.wgetrc file with the line: ca_directory = /etc/ssl/certs per this link...but no love. Finally, doing a grep on the /etc/ssl/certs/cacerts.pem file for "COMODO ECC Domain Validation" also turned up no love. I'm not an expert on SSL trust chains, but perhaps the CA (COMODO ECC Domain Validation Secure Server CA 2) cert just isn't available in the collection of /etc/ssl/certs/cacerts.pem. Perhaps someone more skilled with SSL chains can provide some insight. Hope this helps... ** WARNING: after changing all wgets to "wget --no-check-certificate" in the modulemanager script, not only did I successfully download the modules I wanted, but also ran the "Update Installed Modules" successfully. HOWEVER, updating the modules also updated modulemanager, thereby losing my wget changes. *forehead smack* Link to comment Share on other sites More sharing options...
hakstarr Posted April 18, 2018 Share Posted April 18, 2018 CommodoreDad Not sure if you are still having this issue. But I reset the latest firmware of the lanturtle and I started experiencing this exact issue. After a few hours of installing openssl etc. I finally figured out what the issue was. Check the date of the lanturtle. For some reason ntpd was not pulling the current date and time from openwrt servers. So the date was over a year old that is why wget would complain about the cert. i configured clock.google.com and ntpd still did not pull the right date. I ended up just using the date command date -s YY-MM-DD This seemed to work once the right date was set wget no longer gave ssl errors. My suggestion to Darren would be to have it prompt for the right date just like it prompts for the new password on a freshly flashed turtle. Link to comment Share on other sites More sharing options...
lafintiger Posted May 15, 2019 Share Posted May 15, 2019 On 4/18/2018 at 11:17 AM, hakstarr said: CommodoreDad Not sure if you are still having this issue. But I reset the latest firmware of the lanturtle and I started experiencing this exact issue. After a few hours of installing openssl etc. I finally figured out what the issue was. Check the date of the lanturtle. For some reason ntpd was not pulling the current date and time from openwrt servers. So the date was over a year old that is why wget would complain about the cert. i configured clock.google.com and ntpd still did not pull the right date. I ended up just using the date command date -s YY-MM-DD This seemed to work once the right date was set wget no longer gave ssl errors. My suggestion to Darren would be to have it prompt for the right date just like it prompts for the new password on a freshly flashed turtle. That worked!!! Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.