Notices

Thank you, nice improvements!

..While you are at it, why not add an autostart (if not active) for some kind of connectivity or profile?
example:
autostart sshd when:
[ ] usb pc suite mode
- wifi profile:
[x] wifi_home
[ ] wifi_job

Then, another interesting feature would be the automatic switch of the wifi power management also for an outgoing ssh session.

Hey, weren't you that asked some ideas?

Is this just an idea or are there in fact the same input lags for client connections (that's what is meant by outgoing ssh session?) as for server connections? I just installed the client and connected to my Linux Mint, but there didn't seem to appear those input lags?

If indeed needed, I'll add this.

@rasmarc

yes, the latency is the same also for an ssh client session since it is due to the lower power state of the wifi driver, just like it happens in any platform.
You can easily check the latency difference with a simple ping.
ping with power save to local ip =40-50 ms
ping without power save to local ip =3 ms

I've done the following:

The wifi pm feature now includes client connections. There is no option for it. As for wifi pm client connections are handled in the same way as server connections are.

v2.0-1 of yesterday still isn't listed in Extras-devel. I will wait uploading the current version 2.1-0. If you download v2.1-0rc1 from here and install it with HAM, the new dependency on package "openssh" can't be resolved due to local installation. If need be the package "openssh" has to be installed manually.

Changelog for v2.1-0rc1:
* Extended wifi pm feature to support client connections
* Option "Stop server when not connected" moved to section "OpenSSH Options"

Thank you. It's simply more fun using openssh.

Thank you for the update.
Sadly, it seems that it can't detect the ssh client session since the wifi power status remains unchanged.

Hmmm, on my device I check wifi pm with It says "on". Then, after doing it says "off".

If you don't mind, you could check several things:

In /etc/ssh/ssh_config is there an entry saying:
Does /usr/lib/openssh/session_client exist?

In /usr/lib/openssh/wifi-power-management does line 22 contain
or ?

With an active client connection and no server connections what does say? Is /usr/lib/openssh/wifi-power-management running?

@rasmarc
the problem is due to the write permission/owner of /home/user/nohup.

You mean /home/user/nohup.out ? What's wrong with that? What makes you think there's a problem with nohup?

Who has write permission and is the owner of /home/user/hohup.out on your device?

Just delete it and try again...?

..if triggered by the sshd daemon the nohup.out is owned by root, then when an ssh client sessions tries to created the same nohup.out it can't exec the command since the file is still there and owned by root.

Generally talking, place in the home folder a nohup.out file is not a good choice. It would be better to move it in some temporary folder.