SSH cant connect.

wmarcio

Anyone have this problem?
I try to connect ssh from my android phone on batocera 5.10 (rpi3), i try with several apps.

Any help?

nadenislamarre

what is the error ?
default logins : root/linux
if you changed, you can get the password in menu>system>security

wmarcio

nadenislamarre no, i don't changed noting... On a real pc work fine...
Very thxs, you always try to help people...

GarrafaSanchez

Activate it from the recalbox config

ssh = 1

dewcansam

I have the same issue. SSH is activated. I CAN login from multiple pc's. Both Linux and Windows. Using a number of different SSH programs. PuTTY and KiTTY. But I try to login from the Samsung Tab and can NOT login. Have tried just about every android app out there and NONE of them will login.

I am working on it and will figure it out. But if anybody else has some ideas. Extra input would be helpful.

So far, I am working on the way that dropbear is configured. I am thinking that there is something to work on there. The thought is that the android apps are not emulating the keyboard input the way that dropbear expects it.

Edit: The ONLY error I get from an android app is "error: -125". Google searches have turned up nothing. Port scans show the port blocked. Batocera wiki was, unfortunately, no help.

dewcansam

Ok so dropbear -V == Dropbear v2018.76 current version is 2019.78 . I got the new version, extracted it, but there does not seem to be any tools to compile the new version.
Any ideas on how to compile for batocera on the pi3 ? I guess i can try to build it on the ubuntu box, but won't that build a debian 64 binary ? Or if someone can point me to the dox on how to compile for batocera.

Edit: okay so I am turning my attention to avahi. For whatever reason port scans from the computers (all desktops and laptops) show port 22 as open . Port scans from the tablet show port 22 as blocked. So, why is the tablet blocked when it has the same subnet as the computers ?

dewcansam

lol Alright here is one for ya. So I did a /usr/sbin/dropbear -Rp 22022 which started a new instance of dropbear on port 22022. Cool. Opened up KiTTY and had NO problems logging into batocera on 22022. BUT opened up the tablet and once again port 22022 shows blocked. What gives ???? And NO android apps were able to login on port 22022. Wow, so I am kinda at a loss for this one. However, at this point it clearly is the fault of the tablet or android. But I am puzzled as to why it is blocking this. I have changed the IP and ports for batocera, and they continue to be blocked. But I have no trouble SSHing into the linux box, so it's not the tablet or is it ???? I am at a loss. Any ideas ??

dewcansam

So, I had tried the VM test platform and it hit me to try using the android apps to log into the batocera-x86 vm on windows and sure enough it worked! Now this is getting to be weird. You can open up an android app and SSH into a batocera VM but NOT a batocera Pi ?? So, it's NOT the apps. Something else has got to be going on.

dewcansam

I got it figured out. It's a rough hack, but it works. The key is to use a SSH forwarder (I guess that is what it is called).
The first thing you have to do is have a forwarding computer. If you you have a linux box like I do, then you are ready to go.
If you have a windows computer you can grab a openSSH port from here >> https://github.com/PowerShell/Win32-OpenSSH/releases and then follow the directions from here >> https://winscp.net/eng/docs/guide_windows_openssh_server . It took me a like 10 minutes and I had it going.
Once you have a forwarding server setup. Use JuiceSSH from the android market (yeah I know it's google play, but I still don't like that name 🙂 https://play.google.com/store/apps/details?id=com.sonelli.juicessh

You need to setup 2 connections. One to your desktop SSH forwarder and the other to the batocera pi.
The key to make it working is on the batocera connection under advanced settings there is an option for Connect Via: . Set that to the primary connection. There you have it SSH from your android tablet.

bandabanda

some common SSH connectivity errors you might encounter.

-deleted spam-