similar to: NetworkManager on servers

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,

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

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 Mon, 10 Feb 2020 at 02:55, Nicolas Kovacs <info at microlinux.fr> wrote: > 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

Le 13/02/2020 ? 17:50, Stephen John Smoogen a ?crit?: > In the end, the problem is that NetworkManager, FirewallD, and other > 'automatic' helpers are 'part' of the OS.. and while it was easy to tear > them out in earlier versions.. as time goes on it is not. > > For a car analogy, it was much easier to convert any 1970 car from > automatic back to manual as many

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 -

Le 18/02/2020 ? 17:43, Jonathan Billings a ?crit?: > According to 'man nm-settings-ifcfg-rh', PEERDNS=no is the old > network-services services mechanism for not changing /etc/resolv.conf, > while in NM it just means never add automatic nameservers to > resolv.conf from DHCP, PPP, VPN, etc. Turning off all DNS > updates means adding: > > [main] > dns=none >

> 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

Hi, I've done my fair share of CentOS 7 installations, but this is the first time I have this kind of weird problem. Here goes. In my office I have a battered Dell Optiplex 320 PC with two NICs that I'm using as a bare metal sandbox server for testing purposes. The CentOS 7 installer sees the connected network card as eth0. But after the first reboot, the interface comes up as eth1.

Hi, I have to do some maintenance on a CentOS 7 proxy installed on a routerboard without a video card. The only way to access this machine directly is via Minicom and serial port. I'm using NetworkManager TUI (nmtui) to configure network interfaces, but Ncurses rendering in Minicom works in the sense that chickens fly and horses swim. What you get is a forest of question marks with a few

Le 11/02/2020 ? 16:27, Stephen John Smoogen a ?crit?: > 1. Red Hat is a company of 14,000 people many of which have diverging views > on how things should be run and why. This means that you may see 4-5 > different tools to fix a problem all of which solve the part that they were > originally developed for but not for everyone (mainly because the tool that > is solving it for

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 7.5. Here's a script to create such a dummy: https://github.com/larsks/fakeprovide If you do this,

Hi, I just sanded down the remaining edges of my CentOS 7 post-install configuration script and published it on a Github repository, along with some detailed instructions. * https://github.com/kikinovak/centos-setup Feel free to use it (and/or adapt it to your needs). Cheers from the sunny South of France, Niki -- Microlinux - Solutions informatiques durables 7, place de l'?glise -

On 05/06/2016 09:33 AM, Nicolas Kovacs wrote: > Le 06/05/2016 08:50, Nicolas Kovacs a ?crit : >> Now what would be the simple systemd equivalent of doing that? E. g. on >> any CentOS installation (be it graphical, "Web Server", "File Server", >> whatever), strip down services to the status that they're at just after >> installing a "Minimal

Hi, I'm currently experimenting with CentOS 7 on a couple of installations. I'm reasonably proficient with CentOS 5.x and 6.x. I'd like to manage networking using a more traditional approach (Keep It Simple Stupid). Here's what I tried so far, starting from a minimal install: Install net-tools (to be able to use ifconfig). Get rid of NetworkManager: # yum remove

Hi, I have CentOS 7 running on half a dozen public servers. For some stuff like automatic updates using yum-cron, I have Postfix installed with a relatively basic configuration. This allows me to send important notifications to my mail address info at microlinux.fr. When there's a batch of updates, I get one mail per machine, so I can check quickly if everything went OK without having to

Le 17/11/2019 ? 18:56, Jonathan Billings a ?crit?: > You should never be using ntpdate anymore (which is why the ntp project is deprecating it, http://support.ntp.org/bin/view/Dev/DeprecatingNtpdate <http://support.ntp.org/bin/view/Dev/DeprecatingNtpdate> ). I really only ever suggest ntpd unless you?re running an NTP server that provides NTP service to your network, and needs to

Am 09.02.2020 um 16:14 schrieb Nicolas Kovacs: > Le 09/02/2020 ? 14:10, Nicolas Kovacs a ?crit?: >> Any suggestions ? > > I forgot to add. The onboard NIC is a Broadcom card. > > $ lspci | grep -i net > 02:02.0 Ethernet controller: Realtek Semiconductor Co., Ltd. > RTL-8100/8101L/8139 PCI Fast Ethernet Adapter (rev 10) > 02:09.0 Ethernet controller: Broadcom Inc.

Le 17/11/2019 ? 14:15, Jonathan Billings a ?crit?: > I?m curious why you list these as ?cruft? packages? > > chrony > firewalld > iperf > NetworkManager-libnm * chrony: I'm using ntpd and ntpdate * firewalld: https://github.com/kikinovak/firewall * iperf: replaced by iperf3 * NetworkManager: great on laptops, useless on servers > > Also, I?m sure it?s helpful for