Hi all
For the first time I do stuff with linux. And I have to say so far it’s a great experience.
currently I’m playing arround. I have an Dell OptiPlex 3080. It has two network interfaces. the first one ist ethernet and the second one is a WLAN antena.
What I want to achive is the following scenario:
Boot up the machine into init 3
connect the WLAN interface with the WLAN router
connect to the machine via SSH from my MacBook
Cool would be if I e.g. could login into the WLAN via cronjob after lets say 2min the system booted up.
Runlevel 3 (multi-user.target nowadays) does include starting the network. Thus as you have configured the network (probably using YaST > System > Network Settings and then choosing Wicked an filling in all that is required for the Wifi to start at boot), your system will be “alive” on your LAN. And thus can be connected from all other partners on the LAN (depending on services running, ports open nad firewall allowing).
That is the normal way of running a system since about the soemwhere in the 1970’s.
Many thanks - well I agree with you. But due to the fact that I’m playing arround I:
a) don’t want to use the LAN interface
b) I do not want to use the grafical runlevel 5 YAST
c) I want be able to login into WLAN via cronjob
Imagine the following scenario. A pc from the mid. 80’ with no grafical user interface. I want to learn to manage everything via the console init3 an I do only want to use console commands to set up my WLAN access after booting up.
The reason for that is:
The OptiPlex is not connected via ethernet and also not to a monitor (in the future). I want be able to boot up the system and than connect via WLAN SSH from my MacBook. Hope this helps to understand.
with wicked?
with** NetworkManager**?
with** systemd-networkd**?
wicked and NetworkManager both use plain text files to configure a network connection. You can use vi to edit these files from the command line. With both (wicked and NetworkManager) a network connection can be configured to start automatically on system startup.
I’m not familiar with systemd-networkd. However i would expect it can be configured by editing some files as well.
As hcvv already described wicked might be the best fit for your demands. You do not need YaST to configure wicked. You can edit the file /etc/sysconfig/network/ifcfg-wlan0 (might have a slightly different name on your system) with vi from the command line.
And you seem to think (I may be wrong) that you can not use YaST because your in runlevel 3. That is wrong. YaST has the ncurses interface and runs fine from an ANSI type terminal emulation (like the console). Just run
Your constraint “b)” → as Henk mentions “yast” at a VT CLI with the user “root” but, “yast” actually resolves to “yast2” which is a script which decides if the GUI shall be invoked or, ncurses …
Your constraint “c)” however, may well be better served by “systemd-networkd” – which isn’t currently supported by YaST –
One does not login into a WLAN. One logs in in a system.
So please explain from which system the login should be done and into which system. Give them names please so we will have no confusion on what should run or be done on which system.
Understood - I think this is a great input. my problem at the moment is:
a) I can’t boot by default into init3.
b) in init5 there pops-up the ksdWallet all the time so the WLAN is by default not connected (because no password will be released if kdeWallet isn’t served)
I think problem a) will not be a huge one. I saw that runlevel tables will fix this.
but if I managed the system to boot by default into runlevel 3 than the password problem with my WLAN is still unsolved. any idea?
a) well my WLAN uses a password so I need to login into my WLAN.
b) Current Scenario.
Boot up the “server” with SuSE Leap as OS
Login into the OS (Name / Password)
Login into kdeWallet (OS Password)
OS logs into WLAN Router automatically
I check the iNetconnection by open the Browser and entering an URL
If iNet okay I…
…disconnect the monitor
…open up a terminal window on my mac
enter ssh name@IPOFSUSESYSTEM
enter credentials again
sudo init3
enter password
and offline I am
the reasen for that is, that after the reboot the WLAN does not connect automatically because there is no way the system connects to the WLAN (because the password is required)
therefor I want to be able to enter the credentials via Cronjob after booting into runlevel 3. hope I explained myself
First it’s conneced. I share the peripherals with an other PC therefore I can’t let them plugged in all the time.
I have to be able to manage the SuSE-System via ssh from my Mac’s console.
I know that this is not the intelligent from a professional point of view. but as I mentioned I want to understand if it can be done like that.
So I only need to “activate” the WLAN (incl. password entering and so on and so on) after the system booted into runlevel 3.
Most of your assumptions are incorrect.
IMO you are completely mezmerized by the use of GUI in general and KDE specially.
The information about how you shoule work with this is already in eralier posts above. I will repeat.
Because you do not need any GUI at all, even using the GUI does already confuses you, you should boot the system in target multi-user (formerly called runlevel 3). YaST > System > Services Manager; then at the top you have Default System Target; change that from the menu to Multi-User System, Apply bottom-right; Leave YaST and reboot.
After the boot you are now presented with a login prompt; login with a normal user and then “become root” with
su -
, enter root password.
You can now start YaST with
yast
(NO, not with yast2, that is NOT what I told you).
The ncurses interface is something to get used to. You can use the arrow keys to step through lists, the Tab key to jump through commands, then the Return key to execute those commands. You can also execute the commands directly by typing the bold letter show within the command while pressing the Alt key. E.g you can always leave a screen with Alt-Q to activate the Q
uit bottom-right. - Now inside YaST go forSystem > Network settings; from the tabs above choose G
lobal Options; from there Network Setup Method and from the menu Wicked Service; OK. - From The Overview select the Wifi card you want to configure and then go for Edi
t. Fill in the required fields, that includes the password to your wireless acces point (not that is not called login). After all continues and OKs you will now have after boot a working Wifi connection to your router. Directly after boot, no GUI needed, no KDE needed, No Kwallet needed.
I think that working out the above, inclusing asking back when you want more advice is enough home work for you for the moment.
BTW. the steps with YaST Network Setings can also be done before you switch to Multi-User System, in the way you are used to working with Yast. After you then found out that the Wifi works already before you login in the GUI, you can then do the switch. Either way is possible, but I thought the doing the switch first and using YaST ncurses after would force learning the ncurses interface upon you
And much more general: try to forget all you apparently know about how an MS Windows system works. The whole GUI and desktop are in Linux only add-ons to a full blown operating system. You do not need them except for end-users (mimd the plural) who need a desktop for their work.
Sounds like you are using NetworkManager to manage your Networks.
Just create a new connection and allow it to be used by all users. The network secret will be stored in the connection file and the connection will be established without any prompting on system start up.
Or switch to wicked. There you will get that behaviour for every connection anyway.
All people above tell you the same in different words.
Maybe to make it is a bit easier, your first step should be to switch to Wicked. Just use YaST from the GUI and do the steps I mentioned. Then, after a reboot, you should report here if your connection is still there, without asking you for the KWallet password.
Also, testing if you have a connection to the internet is not normally done “with a browser”. It is done with ping:
Everything is “systemd” – even if, you attempt to “move back to the old way of doing things” …
The systemd equivalent to “init3” is “multi-user.target” – even if “runlevel2/3/4/5.target” are defined …
“systemctl set-default multi-user.target
” will setup the machine to boot to a non-graphical (VTs only) multi-user state, with the network up and running.
[HR][/HR]A question –
If the box is to be principally a stand-alone Terminal-only machine, why have you installed a GUI?
*=2]In your case, presumably KDE Plasma …
[HR][/HR]Why didn’t we pick up on this earlier?
UNIX® System V Run Levels are more dead than a dead parrot …
so I need to login into my WLAN.