Yeah so that gets the tunnel running and then you connect through it to ssh to your device. In another terminal do something like: ssh -p 5000 username@localhost
yeah… I feel a little silly on that one but it’s still not connecting.
i tried it with the gui client and get the same thing, no connection. shh works on this device using the lan connection from other machines on our network, so I don’t think it’s our config.
the connection attempt just times out and I have no failed login attempts in the device’s auth.log file.
How can i check the keys I uploaded to see if they are ok?
If that initial ssh command doesn’t give you an error then the keys are good.
Usually this issue is caused by the routing table not being right on the device. Do you have the ethernet and cellular interfaces up at the same time? It’s probably trying to route the response to the ssh connection back over ethernet instead of cellular. You can try pulling down the ethernet interface before bringing up the cellular interface (assuming you’re not running headless) or you can add a default route back over the cellular connection
I know this should work and I can only believe I have a config error somewhere, so starting from scratch… I did a fresh install of openssh on the device. I then tested with a hard LAN connection and eth0 interface only, ssh works OK with no ssh config mods, password login.
On the device
The device network info is as before, the eth0 is down and physically disconnected:
zbconsole:~ # ifconfig
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:10 errors:0 dropped:0 overruns:0 frame:0
TX packets:10 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1380 (1.3 KB) TX bytes:1380 (1.3 KB)
On the client
Start the tunnel in a terminal, (API key was uploaded):
[rocco@faultred .ssh]$ ssh -p 999 -L 5000:link*****:22 -N -i spacebridge.key htunnel@tunnel.hologram.io
The authenticity of host ‘[tunnel.hologram.io]:999 ([104.130.174.172]:999)’ can’t be established.
ECDSA key fingerprint is ********************************************************.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added ‘[tunnel.hologram.io]:999,[104.130.174.172]:999’ (ECDSA) to the list of known hosts.
I’m not totally sure. It’s almost like the carrier is tearing down the routing when there isn’t anything actively happening for a few seconds. We’ll reach out to our carrier partners and see what’s up. Normally this isn’t needed for things to work.
Hi, what kind of computing device are you using with the E353? Is it running Linux? How are you making the connection? Are you able to connect to Verizon?
I never did get a resolution, the thread just died I guess…
We ended up setting a cron job that runs every 2 minutes and pings a DNS server. This was enough to keep the routes up and since then have had no issues.
Our product is still in development but we are going to a different provider for production as apparently we can’t count on this working…