Jump to content

ssh login vodia mini


fonny
 Share

Recommended Posts

Any idea how I can login to the vodia mini ?

 

I have given a password to the default administrator (security->general>administrator login) but I can't get access via ssh.

 

I always get Permission denied.

Any idea what's can be wrong?

 

 

 

Link to comment
Share on other sites

Seems like the first version had a glitch with writing the password on Linux level. I believe the problem is now solved in 5.2.0a. However before you try, you can try to log in with username root and password root; that's the default. If you are logged in with SSH it is safe to try changing your password from the PBX; make sure you stay logged in so that you can still change it back in case you have lost it.

Link to comment
Share on other sites

Tried with root / root but no go. Updated to v5.2.1 but still nothing. Not with root / root or admin / password.

 

And I also can't get a config from an existing v5.1.3 uploaded to the mini.

In fact, there is not much happening on this box

 

This is the log.

 

[7] 1:00:08.153 APP: syslog is disabled on the PBX [1] 1:00:08.166 GENE: Starting up version 5.2.1 [7] 1:00:10.241 GENE: Found time zones HST AKDT AKST PDT PST MDT MST CDT CST2 EDT EST ADT AST NDT NST BST CET GMT+2 TUR GMT+3 GMT+4 GMT+6 GMT+7 GMT+8 GMT+9 GMT+10 GMT+11 GMT+12 CST CAT IST AUS1 AUS2 AUS3 AUS4 AUS5 AUS6 NZST CHAST MXTC MXTM MXTP GMT [7] 1:00:10.242 GENE: Found Interface lo with IP 127.0.0.1 [7] 1:00:10.244 GENE: Found Interface usb0 with IP 192.168.7.2 [1] 1:00:10.244 GENE: Adding DNS server 127.0.0.1 to the dns server list [8] 1:00:10.456 GENE: Scheduler precision is 0 us [1] 1:00:10.456 GENE: Working Directory is /pbx [5] 1:00:11.681 GENE: Starting threads [7] 1:00:11.683 GENE: UDP(IPv4): Opening socket on 0.0.0.0 [7] 1:00:11.684 GENE: UDP(IPv6): Opening socket on [::] [7] 1:00:11.689 GENE: Found Interface lo with IP 127.0.0.1 [7] 1:00:11.689 GENE: Found Interface eth0 with IP 192.168.120.50 [7] 1:00:11.689 GENE: Found Interface usb0 with IP 192.168.7.2 [8] 1:00:11.689 EMAI: No from address for sending text email [7] 1:00:11.690 GENE: TCP(IPv4): Opening socket on 0.0.0.0:80 [7] 1:00:11.691 GENE: TCP(IPv6): Opening socket on [::]:80 [7] 1:00:11.691 GENE: TCP(IPv4): Opening socket on 0.0.0.0:443 [7] 1:00:11.691 GENE: TCP(IPv6): Opening socket on [::]:443 [7] 1:00:11.691 GENE: TCP(IPv4): Opening socket on 0.0.0.0:2345 [7] 1:00:11.691 GENE: TCP(IPv6): Opening socket on [::]:2345 [7] 1:00:11.692 GENE: TCP(IPv4): Opening socket on 0.0.0.0:2346 [7] 1:00:11.692 GENE: TCP(IPv6): Opening socket on [::]:2346 [7] 1:00:11.692 GENE: UDP(IPv4): Opening socket on 0.0.0.0:161 [7] 1:00:11.692 GENE: UDP(IPv6): Opening socket on [::]:161 [7] 1:00:11.692 GENE: UDP(IPv4): Opening socket on 0.0.0.0:69 [7] 1:00:11.692 GENE: UDP(IPv6): Opening socket on [::]:69 [3] 1:00:11.700 GENE: Done reading large tables [0] 1:00:11.706 GENE: UDP(IPv4): bind() to broadcast port 67 failed [5] 1:00:11.712 GENE: Set scheduling priority to 1 [5] 1:00:11.712 GENE: Set process affinity to 0 [7] 1:00:11.771 GENE: UDP(IPv4): Opening socket on 0.0.0.0:5060 [8] 1:00:11.778 GENE: Joined multicast group 224.0.1.75 [7] 1:00:11.778 GENE: UDP(IPv6): Opening socket on [::]:5060 [7] 1:00:11.778 GENE: TCP(IPv4): Opening socket on 0.0.0.0:5060 [7] 1:00:11.778 GENE: TCP(IPv6): Opening socket on [::]:5060 [7] 1:00:11.779 GENE: TCP(IPv4): Opening socket on 0.0.0.0:5061 [7] 1:00:11.779 GENE: TCP(IPv6): Opening socket on [::]:5061 [7] 1:00:11.779 GENE: UDP(IPv4): Opening socket on 0.0.0.0 [7] 1:00:11.779 GENE: UDP(IPv6): Opening socket on [::] [7] 22:36:15.255 GENE: Found Interface lo with IP 127.0.0.1 [7] 22:36:15.255 GENE: Found Interface eth0 with IP 192.168.120.50 [7] 22:36:15.255 GENE:

Found Interface usb0 with IP 192.168.7.2

 

Link to comment
Share on other sites

  • 2 months later...

Tried today to login on another mini via SSH and got these errors. Any idea what's wrong?

 

Mini has firmware v5.2.2. Admin password has been set & changed. Access enabled for local network.

Any idea what could be wrong?

 

ssh root@192.168.6.20 -v
OpenSSH_6.2p2, OSSLShim 0.9.8r 8 Dec 2011
debug1: Reading configuration data /etc/ssh_config
debug1: Connecting to 192.168.6.20 [192.168.6.20] port 22.
debug1: Connection established.
debug1: identity file /Users/admin/.ssh/id_rsa type -1
debug1: identity file /Users/admin/.ssh/id_rsa-cert type -1
debug1: identity file /Users/admin/.ssh/id_dsa type -1
debug1: identity file /Users/admin/.ssh/id_dsa-cert type -1
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_6.2
ssh_exchange_identification: read: Connection reset by peer
Link to comment
Share on other sites

I have 2 mini's which were original at firmware v5.2.0. Had problems with the first one to log in via ssh due to problem with the firmware.

Updated to v5.2.2, changed password in the web admin from default and after I could login via ssh as root and the new password.

 

I have a second mini which doesn't allow me via ssh. As said before; this one has firmware v5.2.2, default password set and changed, but still no go.

 

I am connecting from the same client eg Terminal on a MacBook with OS X 10.9.2

Even forcing v2 in the ssh cmd doesn't help.

 

Do you have some other ideas what I could do?

Link to comment
Share on other sites

  • 1 month later...

I am connecting from the same client eg Terminal on a MacBook with OS X 10.9.2

Even forcing v2 in the ssh cmd doesn't help.

 

Do you have some other ideas what I could do?

Did you ever manage to get this resolved ?

 

I'm trying SSH to the pbx mini from a mac also, and the same issue exists. A quick search online shows that perhaps permissions may be wrong within the unix structure of the pbx image...?

 

 

 

Cheers

Link to comment
Share on other sites

  • 1 month later...

Hi bencrosby,

 

No I still have this problem.

 

On one mini I have no problem. On the other I can't get ssh working. And as it works on one and not the other I don't think it has anything to do with ssh client. Both mini's have firmware 5.2.2 builddate april 13 2014 21:09:38

 

@vodia: any clue how to get this working?

Link to comment
Share on other sites

  • 2 weeks later...

Well honestly we are also wondering what is going on. The new beagle bones are coming with Debian pre-installed, a distribution that we understand much better and which probably behave a lot more stable than the Ångström one. We don't have any magic backdoor; we would try to use the USB connection to get a grip on the device.

Link to comment
Share on other sites

  • 3 weeks later...

For that you would have to "nuke" the mini using a SD card and re-install the PBX.

 

I'm totally happy to try this. Without ssh access, I cannot modify the logging and add some of the customisations I want.

 

I've started on a rebuilt image that leverages the TI Sitara hardware a bit better - including the built in crypto and I'm chasing down DSP support for echo cancellation and transcoding at the moment.

 

How do I get the arm PBX distro ? Is there source available for a local compile ?

 

Thanks!

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

×
×
  • Create New...