How to set up ssh login

[cssgalactic]

Hello. I have a DSL modem connected to the web all the time. I would like to connect remotetly. I had followed the documentation but so far every time the conection time out. What can I do?

[BSDfan666]

Well, if you have an always-on connection and a system running 24/7... then, read the appropriate man pages and configuration files, ensure OpenSSH is running, (I advice you to disallow root logins..) and permit only SSHv2.

If you can confirm the daemon is running, you'll need a way to easily address your computer... if you have a domain delegated to you it's an easy task, afraid.org can get you a free one. (And clients exist to monitor changes to your IP address..).

Finally, if you bpf/ipfw configured... allow connections to tcp port 22.

[cssgalactic]

But I have spent countles hours reading and setting up the config files. The connection is 24/7 the IP is always the same.

I have:

1. added sshd_enable="YES" to the rc.conf and

2. when I check the daemon seems to be working

3. I have configured the ssh_config. To listen to the IP address, not to accept root login, to allow one specific user, etc....

Using my laptop I can login using ssh (inside my home network) But when I'm outside (office) I can't login using ssh. It times out. Can you give a list of all the files I should be configuring and maybe some samples. Maybe I'm missing a step. I promise you I have been doing my homework before I come to the forum to ask for help.

[18Googol2]

Originally Posted by cssgalactic

but so far every time the conection time out

Sounds like you havent done port forwarding on the router

[cssgalactic]

On the actual DSL router control panel?

[adamk]

Yes, you need to configure the router to forward port 22 to your freebsd machine.

Adam

[TerryP]

the sshd server should listen on the local network (as necessary) on the designated port.

the router needs to forward incoming connections on the designated port to your external ip/domain to that machine.


Other wise generally, the router will tell anyone outside your home network to go to hell when trying to ssh in ;-)

[Seb74]

Originally Posted by TerryP

the sshd server should listen on the local network (as necessary) on the designated port.

the router needs to forward incoming connections on the designated port to your external ip/domain to that machine.


Other wise generally, the router will tell anyone outside your home network to go to hell when trying to ssh in ;-)

Even if it doesn't (maybe it hasn't got any specific firewall and just runs PAT) it doesn't know which pc in the LAN to forward the traffic to.
Maybe you got 3-4 pc's there, how should the router know which one that incoming ssh-request is meant for.
So, as others have said, of course you need to forward that port on the router to the specific machine/port.

[cajunman4life]

It could be your router; It could be your work disallows connections on certain ports. For sure check your router config.

[tad1214]

Once you get it working, it may be wise to change your port number. While security through obscurirty isn't security at all, it sure does seem to stop the bots from hammering away.

[TerryP]

Originally Posted by Seb74

Even if it doesn't (maybe it hasn't got any specific firewall and just runs PAT) it doesn't know which pc in the LAN to forward the traffic to.
Maybe you got 3-4 pc's there, how should the router know which one that incoming ssh-request is meant for.
So, as others have said, of course you need to forward that port on the router to the specific machine/port.

I thought that such issues would be considered implicitly with my previous post.

[cssgalactic]

I now have established all the services I need ssh, ftp and http. Thank you very much. I'm feeling the love my FreeBSD Box.

[18Googol2]

Originally Posted by cssgalactic

I now have established all the services I need ssh, ftp and http. Thank you very much. I'm feeling the love my FreeBSD Box.

Being able to ssh LAN from internet is great, isnt it? Do you feel like home now?