You are not logged in.
Pages: 1
I'm attempting to set up SSH/SCP access between my two PCs, but have so far only managed to get it to go one way.
PC #1 has a Fedora install on it. I've set this up with RSA-only access between my Fedora laptop and Android phone using OpenSSH, and all three connect without issues.
PC #2 has my SliTaz install on it. I've installed OpenSSH, and have given it the same sshd_config settings as on my Fedora PC (i.e. RSA key only). I've exchanged keys between the two PCs, but the connection only works one way - SliTaz can SSH/SCP to Fedora, but Fedora to SliTaz returns the following error:
ssh: connect to host 192.168.1.6 port 22: Connection refused
I've installed iptables on SliTaz, and enabled iptables in /etc/firewall.conf. I've also checked that the following in listed under the iptables rules:
# Accept port 22 for SSH.
[c]iptables -A INPUT -i $INTERFACE -p tcp --destination-port 22 -j ACCEPT
iptables -A OUTPUT -o $INTERFACE -tcp --source-port 22 -j ACCEPT[/c]
As best I can tell, this should mean that port 22 is open for business - however, that appears to not be the case.
The two machines can obviously see each other (and Fedora can at least ping SliTaz), and it's not an issue with the RSA keys (at least at this stage) because I've learnt that that returns a different error. My guess was that the firewall was preventing the connection, but as best I can tell, that snippet above ~should~ enable connections over port 22? (I'll grant iptables isn't my strong point...) Besides that, turning the firewall off (/etc/init.d/firewall stop) doesn't make a difference.
Can anyone suggest what might be the issue?
Offline
Verify ssh is running:
[c]pgrep -l ssh[/c]
Should reply with a different pid number:
2085 /usr/sbin/sshd
Slitaz doesn't auto-start most servers after installation or auto-configure servers to start on boot.
Openssh must be manually started.
/etc/init.d/openssh : Start, stop and restart OpenSSH server on SliTaz with the command line.
To start OpenSSH server at boot time, add openssh in the $RUN_DAEMONS
variable of /etc/rcS.conf and configure options with /etc/daemons.conf
Offline
That's resolved it - thank you!
Offline
Pages: 1
[ Generated in 0.018 seconds, 7 queries executed - Memory usage: 1.53 MiB (Peak: 1.77 MiB) ]