[SOLVED] Suse LEAP 42.2 not starting wlan0 automatically
SUSE / openSUSEThis Forum is for the discussion of Suse Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Exactly the same as before running NetworkManager except this time the network and the internet are available!
It's not going to break me to have to type 'NetworkManager' each time I boot but it would be nicer for it to start automatically!
All the other typical network starting commands like ifup don’t work either and of course I don't need them once its running so I haven't pursued that very far.
You need to decide whether to use wicked or NetworkManager explicitly. The latter is more useful to those changing network environments frequently. This can be done via
YaST > System > Network Settings > Global Options
Select NetworkManager.Service from 'Network Setup Method', then OK.
Confirm NetworkManager is now enabled and active with
Hi ferrari,
Thanks for your response, sorry about the delay, I've been away!
As you can see from my initial post, NetworkManager is what is being used.
I'm not involved with multiple networks and so it sounds, according to your response, that 'wicked' makes more sense however, I am primarily interested in the network connecting automatically on boot or during that process somewhere and don’t really care how that happens.
Your reply shows how I can set up NetworkManager but that is not what I want.
If you are saying that NetworkManager can't start the network automatically and that I should therefore use wicked, then I have to say that the message isn't at all clear.
If I change to wicked, will it start in the manner I require?
Regards
Chris
Code:
crb999@linux-dxa1:~> systemctl status NetworkManager
● NetworkManager.service - Network Manager
Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; disabled; vendor preset: disabled)
Active: inactive (dead)
crb999@linux-dxa1:~> systemctl status wicked
● wicked.service - wicked managed network interfaces
Loaded: loaded (/usr/lib/systemd/system/wicked.service; enabled; vendor preset: disabled)
Active: active (exited) since Tue 2017-03-07 11:43:50 GMT; 5 days ago
Process: 845 ExecStart=/usr/sbin/wicked --systemd ifup all (code=exited, status=0/SUCCESS)
Main PID: 845 (code=exited, status=0/SUCCESS)
Tasks: 0 (limit: 512)
CGroup: /system.slice/wicked.service
Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.
Either can be used to get a connection up at boot. For wicked, you may need to configure first via
YaST > System > Network Settings > Overview, select the device concerned and 'Edit', follow the prompts....
crb999@linux-dxa1:~> sudo systemctl enable NetworkManager
Created symlink from /etc/systemd/system/network.service to /usr/lib/systemd/system/NetworkManager.service.
Created symlink from /etc/systemd/system/multi-user.target.wants/NetworkManager.service to /usr/lib/systemd/system/NetworkManager.service.
Created symlink from /etc/systemd/system/dbus-org.freedesktop.nm-dispatcher.service to /usr/lib/systemd/system/NetworkManager-dispatcher.service.
Right but still no network!
So back to my original technique, which is to invoke NM
Code:
crb999@linux-dxa1:~> sudo NetworkManager
And I'm connected to everything I want to be connected to! I get a little confidence icon on the tray for the wifi connection.
Finally, just to see if there is a material difference, I run ifconfig again, truncated as before.
Yes I have. I use the gui version provided by kde.
I have had various network problems and have certainly tried to sort them using YaST, not very successfully I might add.
For example, when I first installed Suse 42.1,i was presented with two 'eth0' devices and was never connected to the network because the one that the system chose was a ghost!
All I had to do in network manager was to disconnect one and connect the other and all was right with the world.
Nothing in YaST gave me a clue as to why this was happening or how to eradicate it.
I plugged in my wifi card and though it was detected immediately it never connected automatically (hence this thread) but invoking NM connects to the network without further action on my part. I don't have to select it or switch its state if do anything at all except Sudo NetworkManager, and I'm connected.
I would still like it to be an automatic process but perhaps I have to learn a lot more about networking in general.
YaST asks too many question that I cannot find answers to, yet! One day perhaps.
Do not underestimate my ignorance quotient!
I'm prepared and ready to learn but I'm slow and getting slower. I'm at ease with that.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
