@NiLuJe
I looked into SSHD over Wi-FI not starting automatically, and here are my findings so far:
1. Renaming DISABLED_auto to auto *does* work, in a sense that it starts the scripts automatically.
2. Starting SSHD automatically does *not* work. Well, it works every other restart.
Looks like a bug/feature in usbnetwork script, since it simply toggles SSHD status, depending on the pid file (if it present or not). With hard resets, the pid file is being left there, and the script simply tries to turn off the sshd during the startup, once it sees the pid file. And it removes the pid file, so the next restart leads to SSHD started. So, this thing toggles
Most probably, usbNetwork script needs to be changed to accomodate auto-starting of SSHD *every* time.
3. Even when SSHD server starts, it is impossible to connect to it via Wi-Fi, since for some unknown to me reason the iptables are *not* updated with proper rule. I see in the logs that "tweaking iptables config" is present, but it doesn't work for some reason (or the rules being changed somewhere later on again).
Manually entering:
iptables -A INPUT -i wlan0 -p tcp --dport ssh -j ACCEPT
makes it possible to connect to SSHD.
This 3rd point needs a bit more investigation on why the iptables are not properly updated. Maybe too early in the boot process?
UPDATE: I verified that iptables call from usbnetwork script does succeed and it does update the iptables rules, but it seems that they are being changed later on somewhere/somehow.
UPDATE #2: I updated /etc/sysconfig/iptables file, added that wlan0 rule there, and now SSHD access is not filtered out anymore. Good! At least, a workaround for now.