Active Topics

 


Reply
Thread Tools
Posts: 54 | Thanked: 5 times | Joined on May 2008 @ Oulu, Finland
#1
Hi, has anyone had problems setting up an OpenSSH server on the n810?

I have a WLAN network at home and can't access the shh server on my n810. I was wondering if it was the network or the device, so I set up an openSSH server on another pc and had no problems accessing it.

Here's the error I get trying to connect to the n810...
ssh user@192.168.10.104
ssh: connect to host 192.168.10.104 port 22: No route to host

192.168.10.104 is a static local ip address for the n810. Port 22 is also opened for this address on the router.

Any ideas?

Thanks.
__________________
Hardware: n810 running the latest supported OS.
 
tso's Avatar
Posts: 4,783 | Thanked: 1,253 times | Joined on Aug 2007 @ norway
#2
If both desktop and N810 are on the inside of the router, there is no need to open a port on the router. Now if your outside the router, a local IP will not help much as the router is likely applying NAT. As such, you need to use the IP the outside world sees.
__________________
Be warned, posts are often line of thoughts at highway speeds...
 
Posts: 54 | Thanked: 5 times | Joined on May 2008 @ Oulu, Finland
#3
Originally Posted by tso View Post
If both desktop and N810 are on the inside of the router, there is no need to open a port on the router. Now if your outside the router, a local IP will not help much as the router is likely applying NAT. As such, you need to use the IP the outside world sees.
If I try to pretend I'm outside the network, I get a slightly different error (with debugging)...
ssh -v -v -v user@useraccount.dyndns.org
OpenSSH_5.3p1 Debian-3ubuntu7, OpenSSL 0.9.8k 25 Mar 2009
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Applying options for *
debug2: ssh_connect: needpriv 0
debug1: Connecting to useraccount.dyndns.org [91.155.45.*] port 22.
debug1: connect to address 91.155.45.* port 22: Connection refused
ssh: connect to host useraccount.dyndns.org port 22: Connection refused

useraccount.dyndns.org is linked to the n810's local, static ip address.
__________________
Hardware: n810 running the latest supported OS.
 
Posts: 54 | Thanked: 5 times | Joined on May 2008 @ Oulu, Finland
#4
Oh, just realised I can't ping the n810 from the client.
__________________
Hardware: n810 running the latest supported OS.
 
tso's Avatar
Posts: 4,783 | Thanked: 1,253 times | Joined on Aug 2007 @ norway
#5
When you say linked, you mean that the router NAT/firewall is set to forward incoming port 22 traffic to the N810?

so you have:
Client > router > N810?
__________________
Be warned, posts are often line of thoughts at highway speeds...
 
Posts: 54 | Thanked: 5 times | Joined on May 2008 @ Oulu, Finland
#6
Originally Posted by tso View Post
When you say linked, you mean that the router NAT/firewall is set to forward incoming port 22 traffic to the N810?

so you have:
Client > router > N810?
Yep -- well I think that's correct. I'm a bit of a networking noob.
__________________
Hardware: n810 running the latest supported OS.
 
Posts: 54 | Thanked: 5 times | Joined on May 2008 @ Oulu, Finland
#7
I want to disable iptables (to eliminate the problem), but there is no 'service' command nor is iptables in /etc/init.d
How can I stop it?
__________________
Hardware: n810 running the latest supported OS.
 
tso's Avatar
Posts: 4,783 | Thanked: 1,253 times | Joined on Aug 2007 @ norway
#8
Ok, lets take this from the top.

1. are you trying to connect to the N810 from a computer connected to the same wlan as the N810?

2. if not, what computer are you trying to connect from?
__________________
Be warned, posts are often line of thoughts at highway speeds...
 
Posts: 54 | Thanked: 5 times | Joined on May 2008 @ Oulu, Finland
#9
Ok, solved the problem. Found the solution in another thread.

Perhaps i can shed some light on problems connecting SSH to the n900.

Step 1. Simply enable the extras repository and install openSSH client and server. You can check SSH is now running by using 'ps -ef |grep ssh'

Step 2. try simply ssh root@<lanIP> from another device on the same subnet.....Note: in most cases this will NOT work, even though SSH is set up.

The reason this doesnt work is the way the n900 conserves wifi power and doesnt 'keep alive' the wifi connection

3. From the terminal on the n900, try 'ssh root@127.0.0.1'. Note: in many cases 'localhost' will not resolve so no point using that.

4. if the n900 cant ssh to itself you have an additional problem, but if it does work then all is normal.

5. set the n900 to ping the router.

6. ssh to the n900. the 'pings' keep the wifi alive and you should have no problem getting in
Pinging my router while trying to connect from the client worked fast and flawlessly. Is there a better service/setting that will 'keep alive' the connection to the router?
__________________
Hardware: n810 running the latest supported OS.
 
tso's Avatar
Posts: 4,783 | Thanked: 1,253 times | Joined on Aug 2007 @ norway
#10
Ah yes, the wifi sleep issue. Had forgotten about that one.
__________________
Be warned, posts are often line of thoughts at highway speeds...
 
Reply


 
Forum Jump


All times are GMT. The time now is 03:26.