Am Dienstag, 11. Dezember 2018, 15:51:58 CET schrieb Сергей Петяшков via CentOS:
Hi,
Just to clarify (you didn’t mention it) - do you have “NM_CONTROLLED=no” line in NICs ifcfg scripts?
Yes I set up "NM_CONTROLLED=no" but NetworkManager create a other NIC config with DHCP ?
The big problem is the NetworkManager, I mean there are many Problems in 1810 update.
So what can I do "configure", to stop the broken configured network!
Sent from my iPhone
On 11 Dec 2018, at 16:22, Günther J. Niederwimmer gjn@gjn.priv.at wrote:
Hello,
On my systems I have after update to last centos 1810 a big Problem with the network??
Om my system I have three NIC two are connected from hardware (hostdev) the last is connected from the bridge on the host. (NetworkManager was disabled)
Now after the update the client can't start the NIC's correctly :-( My Problem is the bridged NIC ethX
I must Install and activate the NetworkManager or I have a LSB Error [ INFO ] Network Manager is not active. [DEPEND] Dependency failed for Network Manager Wait Online.
Starting LSB: Bring up/down networking...[FAILED] Failed to start LSB: Bring up/down networking.
But now NetworkManager create sometimes a new config for a new ethX this is configured from dhcp, but I must have a static address to connect other server (ldap...)
Also the resolv.conf is overwritten and have wrong nameserver (ipv6) and duplicate search entries ...
Now it is the Problem after a reboot the network is not running correct with or without NetworkManager?
Thanks for a answer or help,
CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos