I apologize in advance for this stupid question, but something seems to have changed and I can’t figure my way through it.
In the “good old days” (say, 6 months ago), I used to be able to boot Leap 14.3 or TW and, without logging in on the console, be able to ssh in from my Mac or another Raspberry Pi. That is, the network services started up automatically at boot time.
That seems to have changed. I’ve checked the Yast/…/network services setup panels, and it says that both wlan0 and eth0 will start at boot time. Right now, on RPi-3B+, eth0 doesn’t work at all, but wlan0 won’t start up until I log in from the console.
I can’t figure out where to look to get networking to really start up at boot time. Any suggestions of where to look would be appreciated.
Are you using NetworkManager or wicked? If the latter, configuring the network connection to start automatically and ‘available to all users’ (system-wide) should do the trick to have the connection started before login.
Well, I’ve tried both. I’m back to wicked, and I did have it “available to all users” and “start at boot time”. Let me try again and confirm.
OK, this time I booted into graphical mode using wicked for network management, and I was able to log in from remotely without logging in on the console.
Did a “systemctl set-default multi-user”, left wicked for network management, and rebooted. I was again able to log in remotely without logging in on the console.
My apologies: somewhere in my debugging earlier this evening, I couldn’t. But it’s working as expected, so I must have made a mod without realizing it earlier.
Thanks for the quick response and confirmation that what I thought should happen was right, and that encouraged me to go back and double-check. Much appreciated.