Disabled the openvswitch.service and removed my ifcfg-* files to insure that was not an issue. It wasn’t
Switched from wicked to NetworkManager in YaST, rebooted, and made sure the network functioned. Then switched back to wicked in YaST, rebooted, and checked to insure the network was working. I still received the same INFO error when rebooting with wicked.
I enabled the NetworManager-dispatcher.service, and rebooted but this did not resolve the issue.
I understand that removing NetworkManager or masking the services would probably solve the issue. I am just not ready to give-up yet on trying to figure out what my system is doing
Thanks for everyone who is using wicked and confirmed they are not seeing the scenario I am seeing. I can certainly live with the issue since it does not affect boot time. However, I am like a dog with a bone. I will keep chewing on it when I have time, or until I move to version 15
I tried to remove it. An this is the output:
zypper rm NetworkManager
Loading repository data...
Reading installed packages...
Resolving package dependencies...
The following application is going to be REMOVED:
The following 19 packages are going to be REMOVED:
NetworkManager NetworkManager-branding-openSUSE NetworkManager-lang NetworkManager-openconnect NetworkManager-openconnect-lang
NetworkManager-openvpn NetworkManager-openvpn-lang NetworkManager-pptp NetworkManager-pptp-lang patterns-kde-kde
patterns-kde-kde_imaging patterns-kde-kde_plasma plasma-nm5 plasma-nm5-lang plasma-nm5-openconnect plasma-nm5-openvpn
plasma-nm5-pptp plasma5-session plasma5-session-wayland
The following 3 patterns are going to be REMOVED:
kde kde_imaging kde_plasma
19 packages to remove.
After the operation, 19.9 MiB will be freed.
**Continue? [y/n/...? shows all options] (y): **n
Given that, the system default, these days, is to use ‘nscd’, which seems to be reliable enough for folks such as myself and, it doesn’t seem to cause any issues with ‘wicked’ and also, none with ‘Network Manager’, why bother to setup BIND as a caching client?
I guess there are a couple of reasons to use a bind caching server then.
On a standalone it speeds up my web activity because most of my queries are to the same sites generally, and since places like youtube make around 250 web queries per page the time lag adds up.
In a production environment internal DNS servers are often tied to DHCP servers so doing split DNS and using a proxy and caching server keeps your internal DNS servers from cache poisoning and attempted malicious zone transfers.