Can't connect to the Vera via telnet/ssh

Community Playground General Discussions
1

I just upgrade my Vera-1 to a new release () and I can no longer ssh to the device (no telnet either). I get the following:

$ ssh root@192.168.24.143
ssh: connect to host 192.168.24.143 port 22: No route to host

I see that the Vera pulls the IP from my DHCP server. The cable is currently in WAN port.

Did something get wiped?

I can reach the device via http.

Edit: correct the IP addresses

2

$ ssh root@192.168.1.3 ssh: connect to host 192.168.24.143 port 22: No route to host

I’ve never seen SSH ask for one IP (.1.3) and indicate No route for another IP (.24.143). Are you NAT’ing somewhere?

3

[quote=“guessed, post:2, topic:171071”]$ ssh root@192.168.1.3 ssh: connect to host 192.168.24.143 port 22: No route to host

I’ve never seen SSH ask for one IP (.1.3) and indicate No route for another IP (.24.143). Are you NAT’ing somewhere?[/quote]

Sorry that was my (Failed!) attempt at obfuscation. Let me re-edit the original message to fix that. (24.143).

4

The “no route to host” bit sticks out, and I’d probably focus around the cause of that.

ie. the normal culprits of Router-based FW Rules, Missing routes between subnets, PC-based FW rules, etc, etc

Try a “[tt]telnet 192.168.24.143 80[/tt]” to see if you get connectivity from the cmd line, to isolate everything else a browser my be doing (proxies, different client machines, etc, etc)

5

[quote=“guessed, post:4, topic:171071”]The “no route to host” bit sticks out, and I’d probably focus around the cause of that.

ie. the normal culprits of Router-based FW Rules, Missing routes between subnets, PC-based FW rules, etc, etc

Try a “[tt]telnet 192.168.24.143 80[/tt]” to see if you get connectivity from the cmd line, to isolate everything else a browser my be doing (proxies, different client machines, etc, etc)[/quote]
That’s a normal telnet (unix) message meaning it can’t find it. They’re on the same network (192.168.24.x) so there is no routing. I tried the telnet 192.168.24.143 80 and got this:

$ ping -c 3 vera.uucp
PING vera.uucp (192.168.24.143) 56(84) bytes of data.
64 bytes from vera.uucp (192.168.24.143): icmp_req=1 ttl=64 time=0.472 ms
64 bytes from vera.uucp (192.168.24.143): icmp_req=2 ttl=64 time=0.504 ms
64 bytes from vera.uucp (192.168.24.143): icmp_req=3 ttl=64 time=0.540 ms

— vera.uucp ping statistics —
3 packets transmitted, 3 received, 0% packet loss, time 2000ms
rtt min/avg/max/mdev = 0.472/0.505/0.540/0.033 ms
$ telnet 192.168.24.143 80
Trying 192.168.24.143…
Connected to 192.168.24.143.
Escape character is ‘^]’.
GET /

then it hangs. Same with the ssh connection. It works for a short period of time (as does browser access) then it goes off to la-la land (it hangs). I’d say the lastest code is the problem. Is there a way to reinstall it?

6

Whenever I’d borked mine somehow (many many times), this has always worked for me:

http://wiki.micasaverde.com/index.php/Firmware_Flash

7

Firmware flash is dangerous, if he can access the UI he can either upgrade the firmware (even to the same firmware version) with Restore to factory defaults or he can restore to factory defaults from the UI.

@ncherry
Disconnect the cable from the WAN port, connect your computer to Vera on a LAN port, give your computer a static IP like this 192.168.81.2, default gateway 192.168.81.1 and try now to SSH into Vera. It usually worked for me.

8

I’ll give the factory reset a try first. If that works I’ll let you know. If that fails then on to the firmware attempt. The box is really wonky right now.