On 2024-02-26 14:55, Ben T. Fender wrote:
Mon, 26 Feb 2024 12:36:56 +0100 "Carlos E. R." <robin.listas@telefonica.net> :
On 2024-02-26 03:12, Ben T. Fender wrote:
Mon, 26 Feb 2024 02:52:38 +0100 "Carlos E. R." <> :
On 2024-02-26 02:38, Ben T. Fender wrote:
...
this is what was missing, systemd commands
~ # systemctl status sshd.service ○ sshd.service - OpenSSH Daemon Loaded: loaded (/usr/lib/systemd/system/sshd.service; disabled; preset: disabled) Active: inactive (dead) ~ # systemctl start sshd.service
You have to use "enable" to make it permanent.
Having the ssh sever permanently active (ie, ready to accept a connection) is the normal thing to do in the Linux world. You probably said "no" when you installed the system.
When I need somethoing on another drive I mount it manually, then following I immediately umount it. Same with most other chores. This ssh thingie started saving IP's, I'll have to getrid of that bad habbit too, especially with a router that gives them dynamically which is the correct way (for me).
You probably can configure your router to always give the same IP to the same computer. This is usually done by associating the MAC address to an IP, using the router management web page. You can find the MAC address in Linux with the command "ip link". Find the paragraph for the network interface you use (say eth0, wlan0, etc), and there the entry for "link/ether". On Linux machines, it is typical to have the sshd daemon running always, on every boot. This facilitates connecting from another computer when there is trouble, or just for anything. Not having it running is rare, IMO, but some people have their reasons. ... -- Cheers / Saludos, Carlos E. R. (from 15.5 x86_64 at Telcontar)