Hi!
I have tried SSHDroid, QuickSSHD and also Dropbear directly from the command line with logging to STD_ERR, but I am not able to connect to my GalaxyTab 10.1. Using nmap from WinXP I see the port, but it is filtered:
PORT STATE SERVICE
22/tcp filtered ssh
Using netstat on the tab shows that the connection has begun, but it stops with syn_recv and never get established. Using DropBear with logging it seems like no traffic is passed on to the server as no new log appears at the connection moment (or later).
The problem occured after rooting the device and has been persistent even though I have changed back to stock ROM and manager. Now I am using "recovery-cwm_4.0.0.4-sam-tab-10.1.tar.md5" and "Task650&Phantom_V5_Final.zip".
Using netcat I am able to send traffic both ways on the same ports.
I would really appreciate any suggestions on how to solve this as I have I feel lost without SSH
BR,
Henrik
It works okay for me with stock rom, rooted and SSHDroid. Set the superuser to grant automatic root permissions. Launch the SSHDroid and set - require wifi and password to yes.Check the port and make sure its 22 in the SSHDroid settings. Then start the server, you should see a confirmation saying the process is listening in port 22. You would also see a prompt stating the SSHDroid has been granted SU permissions. LEt me know if this helps!
SOLVED
Thanks for suggestions mango1122! I have for sure tried all those things too many times already But I got a breakthrough today by using the Overcome ROM and kernel (see galaxytabhacks).
Using this ROM, SSHDroid worked out of the box. I have unfortunately no clue why this works, but what made me try this ROM was this comment:
"For Custom roms: Be aware, I’ve put the wifi module right in the ramdisk (which is where it is on 10.1 stock). Please move over the modules folder in /system/lib prior to flashing, if this applies to you."
BR,
Henrik
Solved...again...
Update...had to take a long break as it didn't work when I got home from work that day in Nov...it was my home router that caused the problem, I guess combined with something in the Dropbear/SSHDroid application for Android 3.0 as there is no problem using SSHDroid on my smartphone with Android 2.3.3 on the same router. I assume it has something to do with the fact that it listens on tcp6?
Using another router solved the problem.
BR,
Henrik
Related
Hi all, I'm trying to get OpenVPN working on my SGS2 - connecting to a WRT54G router running DD-WRT (with OpenVPN).
This is my first Android device and I previously had the same tunnel working on my Nokia N900 before I dropped it and killed the touchscreen.
So the phone is rooted using this kernel here. I've added OpenVPN Installer, OpenVPN Settings and Busybox, copied some keys and created a config file. The settings app says that it connects fine but I don't appear to have a tunnel.
Firstly, I appreciate I may need a tun.ko module seeing as I've not added one. How do i check if I've already got one?
Many thanks in advance
Solved it with the zip from this thread.
I'd read that before but hadn't realised it was going to work for me. Got nowhere with the tun module as modprobe was showing nothing. lsmod is still showing nothing even with the tunnel up and running!
At least it works!
So, I downloaded an adbWifi widget, and followed the instruction and - woohoo - it works.
I'm trying to understand how is this secure (if it is at all).
I click with widget and it tells me an IP and a port. I tell adb/Eclipse this ... and it connects. So how come someone out there port-sniffing can't do the same, and connect to my phone?
GaJ
GreenAsJade said:
So, I downloaded an adbWifi widget, and followed the instruction and - woohoo - it works.
I'm trying to understand how is this secure (if it is at all).
I click with widget and it tells me an IP and a port. I tell adb/Eclipse this ... and it connects. So how come someone out there port-sniffing can't do the same, and connect to my phone?
GaJ
Click to expand...
Click to collapse
What wifi network are you using? If it's your own wifi network you control the security with a WEP key or hopefully something better. For example I have my own wireless router at home and I use WEP (to lazy to use something better).
By the way, which adb wifi program did you download and where are the instructions? I would like to try it.
-Vince
Nothing stops anyone on the same network from connecting to your wireless adb session if they know the port.
The best you could do is use a non standard port instead of the default 5555
I know the toggle I use doesn't give the option to choose a port but it is possible and asking the dev as a feature request might get the option. I have never bothered because I only use it on my secure network and don't know anyone irl that would know what adb is.
To start wireless adb with any port from a shell run "adb tcpip <port>" to restart the daemon on the specified port.
I personally think we should be able to password protect adb for if our phones are stolen.
Hoi,
can someone please tell me (us), HOW the Eclipse config must be modified ?
Right now i type in a dos-box the command adb connect <MyTCP>:5555.
When i click RUN in Eclipse it finds the device and all works fine.
I want to use this method permanently, so i am interested in the Config-Solution because my device didn't suck so much energy from the batterie as in WiFi-Mode (awesome effect, isn't it ?)
Doei
If you've never given permissions to a particular computer, it can't connect.
I have been using Connectbot to forward a local port (higher than 1024) to a remote mail server, on my Android phone, and it has worked well. After I rooted my Nook Tablet, I used the same settings as on my phone and it worked, but today it no longer works. I can connect to the remote SSH server but Connectbot is not forwarding the ports. I suspect it is a problem with permissions. Is there a way to fix the permissions for Connectbot so it can forward ports?
Another possible problem is that my Nook does not (it seems) know what 'localhost' means. I even tried 127.0.0.1 in a terminal and the terminal could not find it. This might be the actual problem causing port forwarding to fail, but it was working earlier and just stopped working.
BTW the same setup still works on the phone so I know the remote host is not the issue.
OK for fix permissions you could try the option for that in CWM recovery if you have it installed. You could change permissions by using root explorer or ES file explorer apps too but im not sure which files you should fix, but you can try giving more permissions to the Connectbot app and change owner to root aswell if you dont know how to do it check this how to made by me.
About the localhost address adfree app that i use to get rid of advertisings use 127.0.0.1 ip to install hosts, make sure you have installed busybox that means open busybox app and verify that you have busybox 19.x.x installed, if not then install it.
~ Veronica
I will check but I am almost certain I have Busybox installed. I went to a cafe and my setup works, it just does not work at the library where they do NOT block port 443 and I am able to do port forwarding at the library on Linux (OpenSSH) and also Windows (with Proxifier).
I think it might be a DNS problem which can be addressed within ConnectBot, and this setup was working last week at the library. I will check the things you mentioned in your reply. Thanks
BTW, it does not appear to be permissions related, since I am able to do port forwarding on ConnectBot when at an open access point (no credentialed login required).
[SOLVED]
Thanks for your help. I installed the "Hosts" host file editor and then added the localhost to it. I suspect that the ROM Toobox app might have removed the localhost when it added 3 addresses to the hosts file (at my request). When I used the hosts file editor to add "localhost", it removed those additions made by the ROM Toolbox. I will have to look into this and make sure that when I add entries, the old entries do not disappear.
ConnectBot is now forwarding ports again at the library, after this fix.
I'm looking for an app that can handle SSH tunneling with RSA keys instead of a simple password.
It should work like "SSH Tunnel" or "ProxyDroid" (I need to encrypt my internet traffic when using public wi-fi) but with RSA autentication.
Any suggestion?
Thanks
Try connect Bot
morph1us said:
Try connect Bot
Click to expand...
Click to collapse
Can't figure out how to bypass all my internet traffic trought SSH (like I can do with ProxyDroid). Is there a command to use or a special configuration? I can't find anything in the options.
Ok, I managed to use port-forwarding on connect-bot and use ProxyDoroid, as described here.
The problem is that it works only for a few seconds (I suspect it stops working after I successfully connected to the first website I want to visit).
Any suggestion?
zudrev said:
Ok, I managed to use port-forwarding on connect-bot and use ProxyDoroid, as described here.
The problem is that it works only for a few seconds (I suspect it stops working after I successfully connected to the first website I want to visit).
Any suggestion?
Click to expand...
Click to collapse
After long research I found out there was a bug in my SSH server. Now the problem is solved.
I have several android boxes which run Hola VPN, but my friend gave me his CS918 box to install it on it. This box will not allow me to run any VPN at all, it just keeps disconnecting all the time, even with a paid VPN I have on trial
Hola throws up a message about superuser access denied, but I do not have this installed on the device at all
Can anyone help me please?
markeymark said:
I have several android boxes which run Hola VPN, but my friend gave me his CS918 box to install it on it. This box will not allow me to run any VPN at all, it just keeps disconnecting all the time, even with a paid VPN I have on trial
Hola throws up a message about superuser access denied, but I do not have this installed on the device at all
Can anyone help me please?
Click to expand...
Click to collapse
I'm afraid, Hola need Rooting on Android versions below 4.0. It's because Hola's Android API is not available on older versions (Android 2.3.7 and below), so Hola requires Root access to handle these requests.
If you don't want to root your device, I suggest flashing your current router with DD_WRT firmware.
DD-WRT is a free open source project aimed at developing a Linux based firmware solution that removes the restrictions placed on routers by their default programming. Fortunately, it has the option of selecting different VPN configurations like: PPTP, L2TP or OpenVPN and Once configured, users on the network don’t need to enter a log in process when they need to activate the VPN. It just starts automatically, so any device connects automatically and easily, giving you all the benefits of using a reliable VPN service.
In order to check whether your router is DD-WRT supported or not, please check your router here : http://dd-wrt.com/site/support/router-database
And here is a configuration guide that will give you better idea of how you can config it on your router.
Hope it could help.