similar to: CentOS 7.5 (1804) and NetworkManager

On 15 May 2018 at 16:55, Michael Lampe <lampe at gcsc.uni-frankfurt.de> wrote: > Gnome's control-center now requires NetworkManager-wifi. But it's only a > soft requirement, no shared libs involved. > > To keep your workstation NM-free, you want to install a dummy package that > provides NetworkManager-wifi but actually contains nothing, ideally before > updating to

Hi, I'm running CentOS on all kinds of setups: servers, workstations, desktops and laptops. Up until now, I'm only using NetworkManager on laptops, since it makes sense to use it there. On servers and desktop clients, I usually remove it and configure the network "traditionally" by simply editing /etc/sysconfig/network-scripts/ifcfg-whatever, /etc/resolv.conf, /etc/hosts,

Le 18/02/2020 ? 12:28, Anand Buddhdev a ?crit?: > Neither. The DNS configuration should not normally be bound to a > specific interface, so don't configure it with any interface. If you do, > and that interface goes down, your DNS config also disappears. I would like to do that very much, only NetworkManager makes you jump through burning loops to do so. With network-scripts, it

Le 11/02/2020 ? 14:11, Jonathan Billings a ?crit?: > I've mentioned on this list countless times about how NetworkManager > is actually pretty good for a general server. Automatic link > detection and activation/deactivation, a dispatch service on link > activation/deactivation, support for bringing up secondary interfaces > after a primary goes up, a dbus interface for

On 8 March 2017 at 11:15, Alice Wonder <alice at domblogger.net> wrote: > On 03/08/2017 01:57 AM, Giles Coochey wrote: >> >> >>> The recommended configuration for EL7 is to use NetworkManager unless >>> you have a very specific edge case preventing you from doing so: >>> >> The truth is a lot of us run servers that don't need to have their

Hello Guys, update my post, because of a route from ipv6 on same networkcard, with only ipv4 enabled Sincerely Andy

Hi: I always use network-scripts to start network at EL7. NetworkManager is not as good as network scripts under that OS. but now EL8 said that network-scripts is depreciated. I wonder if I should still use network-scripts to start network? I am afraid there will be new bugs for the network-scripts, like systemd service unit dependency. although it is solid at EL7.

> On 09/02/2020 23:55, Nicolas Kovacs wrote: > > Hi Nicolas, > > [snip] > >> Maybe there's a reason to make NetworkManager more or less mandatory >> from now on, but I don't see it. So I thought I'd rather ask on this >> list. > > Like you, I read about NetworkManager becoming the default tool for > CentOS 8. So I sat down with a colleague

I'm experimenting with 6.2 now. Things seem to be really great so far! Distribution closure is one of my favourite pets. So I tried to install everything. I found only one problem, but that's another (minor) thing. But I found almost nothing under /usr/lib. So, Biarch is really dead? Funny! A couple of years back, I finally opted for CentOS instead of Debian just because of Biarch

On Tue, May 15, 2018 at 12:40:06PM +0200, Nicolas Kovacs wrote: > [..] On servers and desktop clients, I usually remove > it and configure the network "traditionally" by simply editing > /etc/sysconfig/network-scripts/ifcfg-whatever, /etc/resolv.conf, > /etc/hosts, /etc/hostname and /etc/sysconfig/network. Running > NetworkManager on anything else than a laptop has never

On Tue, May 15, 2018 at 12:40 PM, Nicolas Kovacs <info at microlinux.fr> wrote: > Hi, > > I'm running CentOS on all kinds of setups: servers, workstations, > desktops and laptops. > > Up until now, I'm only using NetworkManager on laptops, since it makes > sense to use it there. On servers and desktop clients, I usually remove > it and configure the network

Hi, I'm running CentOS 7 on all my servers, in three different contexts : 1. simple local server 2. public facing server 3. router/gateway/firewall I'm currently in the process of moving my KISS-style network-scripts-style configurations to something more orthodox based on NetworkManager. Scenarios (1) and (2) caused no problems, but (3) is giving me some headache. Let me

Hello! For me it was best practice to disable "NetworkManager" on headless installations. Now suddenly I ran into an problem with several programs not starting correctly upon boot anymore. The problem seems to be that their unit files contain "After=network.target" but network.target wont wait till network is up and working, just waits for some low level network stuff.

Latest really rude show stoppers were/are: el6: - librsvg2: your private fork bomb for gnome - kernel: scheduler completely broken on numa systems - qt: kde unusable when going up from -26 to -28 el5: - firefox hangs on quit after latest ESR update - (totem plugins no longer work too) What I am using an enterprise distro for?? -Michael PS: I'm only wondering :)

Hi, I just installed CentOS 7 on my Asus S300 laptop. Wireless was working OK at first, but now for mysterious reasons the NetworkManager icon seems to have disappeared from the notification area. When I click on that area, there's only information showing about sound, brightness, battery status and the connected user. Which leaves me clueless. Any suggestions? Niki Kovacs -- Microlinux -

On Tue, Feb 11, 2020 at 8:12 AM Jonathan Billings <billings at negate.org> wrote: > > On Tue, Feb 11, 2020 at 06:11:04AM +0100, Simon Matter via CentOS wrote: > > Unfortunately, instead of fixing/refactoring the whole bash networking > > script mess, another new project was started instead, called > > systemd-networkd :-) > > Actually, I'm sad that

Namely: * hivex * hivex-devel * librdmac * librdmac-devel * sanlock-libs * sanlock-devel and maybe others. Is this on purpose (I don't know if upstream has removed or updated the 32-bit rpms, but the old ones are still in C6.3/x86_64), or is it just the usual sloppyness (I've been told here on previous occasions the biarch is a pain in the ass to maintain, nobody cares anyway,

Hi, I'm currently reading the upstream "Considerations in adopting RHEL 8" document. The chapter about networking states that traditional networking scripts (shipped with the network-scripts package) are considered obsolete. I bluntly admit I don't see the point in this. As far as I'm concerned, I've been a happy user of NetworkManager since the early days (when

On Fri, Mar 04, 2016 at 04:57:30PM +0000, Daniel P. Berrange wrote: > What version of libvirt ? We had an unfortunate implementation mistake > which caused us to waste tonnes of time in memmove(). versions since > 1.2.19 have a fix that addresses it Ah, this is on F23, which has: libvirt-1.2.18.2-2.fc23.x86_64 There's nothing more recent right now in either updates or

I was hoping that I could delegate creation of bridge devices to libvirt for address-less bridges, in order to not have to deal with the various ways distributions handle persistent network configuration, but while this creates a libvirt network... <network> <name>provision</name> <forward mode='bridge'/> <bridge name='brprov'/>