josealmeidajr Posted August 8, 2019 Posted August 8, 2019 Hello, I've been trying to setup the turtle to autossh back to a ec2 VPS. I've gone through all the configuration steps bellow: 1)Installed keymanager, and autossh 2)Generated key 3)Copied key to VPS 4)Configured autossh to point to my vps. I've looked into /etc/config/autossh and it has the correct settings like: config ssh '-i /root/.ssh/id_rsa -N -T -R 2222:localhost:22 [email protected] -p 22 ' I've copied and pasted this like removing the "config" and the single quotes, and it connects to my VPS with no issues. In the turtle module it shows as "STARTED" and "ENABLED", but it does not connect at all. Only if I manually leave the turtle and run the ssh command above. Same goes for sshfs, configured, enabled/started and it simply does not do anything. Turtle running on the newest firmware.
josealmeidajr Posted August 8, 2019 Author Posted August 8, 2019 The sshsf command from the script itself also works running mannually: sshfs -o idmap=user -C -p 22 [email protected]:/home/user/turtle /sshfs/ But the module does not start it.
rowie Posted August 10, 2019 Posted August 10, 2019 same here!! same working config from the old one ... nothing happens and start/stop doesnt works connecting manually works
Audrick Posted August 15, 2019 Posted August 15, 2019 Having the same issue with auto ssh. Screen grabbed all settings and copied off .ssh fold before update. Can't get it to work through the Turtle app but can connect to VPS from command line.
josealmeidajr Posted August 15, 2019 Author Posted August 15, 2019 No solution yet, my solution was to downgrade to v5 firmware, where the module actually work. 🙂
Audrick Posted August 16, 2019 Posted August 16, 2019 Was thinking about that but I waned to check out the new C2 and I have to upgrade everything to get it to all work together. It is a drag that you can't just update the C2 version without new firmware on all your devices.
sateng Posted September 1, 2019 Posted September 1, 2019 Same problem here. But many of the modules do not run automatically if configured so. Maybe it is a problem with dependencies. As I read the OS is 19.07 now and I also had some trouble to get QuickCreds running. The missing dependencies had to be manually downloaded and installed and could not be loaded via opkg packet manager. I also had a look at the modulemanager itself - but the scripts seem identical to me.
Darren Kitchen Posted September 8, 2019 Posted September 8, 2019 This is the problem with being on the bleeding edge, and early adopting new OS versions. I'll look into it. It could be that this was fixed with v6.1, which we just released. I'll test and report back shortly.
Chandra Sai Posted September 25, 2019 Posted September 25, 2019 I am using v 6.1 and autossh is not working .Can u please give us an update
ApplePie Posted September 27, 2019 Posted September 27, 2019 Confirmed that v6.1 doesn't work out of the box if relying on the Turtle Shell. As above, I got autossh working via the command line.
Chandra Sai Posted September 27, 2019 Posted September 27, 2019 Hii ApplePie, can u please upload the screenshots of autossh through commandline
Darren Kitchen Posted October 4, 2019 Posted October 4, 2019 I have been able to recreate this and found the bug to be related to a missing dependency in firmware v6.1. We're working on a patch now. The workaround now is: 1. Manually add the remote host to the known host file by first connecting via ssh command in the shell. 2. Edit /etc/config/autossh and change enabled from 0 to 1 (or delete and reinstall the autossh module which fixes this issue)
Darren Kitchen Posted October 8, 2019 Posted October 8, 2019 Both the keymanager and autossh modules have now been updated with fixes for these bugs. You can use the update modules function from within module manager to get the latest versions.
Digit Posted November 16, 2019 Posted November 16, 2019 Manual start it : autossh -M 5122 -N -R 5022:localhost:22 your_USER_VPN@your_vpn_IP
DCG Posted November 17, 2019 Posted November 17, 2019 On 11/16/2019 at 7:24 AM, Digit said: Manual start it : autossh -M 5122 -N -R 5022:localhost:22 your_USER_VPN@your_vpn_IP Hi, Sorry but I don't understand, I followed this video below, with the same parameters but when I do ssh root@localhost -p 2222 from my vps, I have a "connection refused". My turtle is connected to my laptop and I use an ssh connection to my vps as root. I removed "the known_hosts" files from my turtle and my vps. On the VPS server, I can see my key in authorized_key. If I do ssh "[email protected]" from my LAN Turtle, it works. If I do "autossh -M 5122 -N -R 5022:localhost:22 your_USER_VPN@your_vpn_IP" , as you mentionned, from my LAN Turtle, I haven't got any error message, so I supposed that it works. but after that, I try again ssh root@localhost -p 2222 from my vps, and it still not working. Could you help me please? I need to access to my LAN TURTLE from my VPS. Thank you in advance
DCG Posted November 17, 2019 Posted November 17, 2019 ok, it works from the GUI so it's ok for me even if it doesn't work from the shell
Recommended Posts
Archived
This topic is now archived and is closed to further replies.