similar to: NetworkManager and tinc

Is there a way to have tinc change the interface according to whether it thinks it is successfully connected to a [external] next hop? We've got a problem where the tinc provided tun0 is sitting there (obviously not going anywhere because there's no uplink via eth0 or whatever anymore after a suspend/resume cycle & having moved locations) but various programs see that as "an

Hi, I've followed the guide at: http://blogs.operationaldynamics.com/andrew/software/research/using-tinc-vpn and have a working tinc VPN. Here's my topology: - CentralNode has a fixed public IP address that everyone connects to - Leaf1 and Leaf2 may have different IP addresses depending on where they are, and usually those will be behind NAT (think, two laptops going around and you get

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,

Window allows one to specify a DNS domain name and DNS server for a particular interface. So all DNS queries of your tinc interface are sent to a particular dns server. For instance windows tinc clients can use a particular dns server on a private LAN available only to clients inside that NAT or tinc clients. NetworkManager allows you to specify the same, but the tinc interface does not show up

How to inst that Network manager please ================ Worthy agent of Light ================ Jules Irenge MSc Student University of Liverpool

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

I've been banging my head against the wall trying to get a simple two NIC bond to work. Got really odd behavior from service network restart, then finally decided to disable NetworkManager. Voila! Bonding and the network service script starts working just the way I expect. Does anyone here actually use NetworkManager on anything but a laptop or desktop? I can't seem to figure out a reason

CentOS 7.5 image running on linode. unbound running on localhost. Have to use a cron job once a minute to keep /etc/resolv.conf using the localhost for name resolution - whenever NetworkManager gets restarted (usually only a system boot) it gets over-written. It seems every distro has a different way of preventing NetworkManager from replacing that file. I found instructions for Fedora that

> 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 network "managed" by Networkmanager. We just need to set an IP address, subnet mask, gateway, and DNS servers and we will never be changing that configuration ever

> 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

On Dec 1, 2014, at 10:27 PM, Rob Kampen <rkampen at reaching-clients.com> wrote: > Have you put > NM_CONTROLLED="no" > in the ifcfg-eth0 script? How is that better than systemctl stop NetworkManager systemctl disable NetworkManager Again, I?m not really after a way to make this work without NetworkManager. We?ve already got that. What I want is a way to tell

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

Hi all, I have a CentOS 5.4 server-only installation, i.e. no X installed, and for some odd reason /etc/resolve.conf gets overwritten by NetworkManager on a constant basis. I haven't been able to track down how often, but I think it's on the hour, or something. This is the conents of the file right now: # Generated by NetworkManager # No nameservers found; try putting DNS servers into

Hi, I am facing issue stoping NetworkManager to update resolv.cfg, I am using below configuration for eth0 interface: TYPE=Ethernet BOOTPROTO=dhcp DEFROUTE=yes IPV4_FAILURE_FATAL=no IPV6INIT=yes IPV6_AUTOCONF=yes IPV6_DEFROUTE=yes IPV6_FAILURE_FATAL=no IPV6_ADDR_GEN_MODE=stable-privacy NAME=eth0 UUID=93b90a46-dab5-4a67-8fd0-fefe8874a8b9 DEVICE=eth0 ONBOOT=no PEERDNS=no PEERROUTES=yes

William Kennington <william at wkennington.com> writes: > Agreed. > On Feb 1, 2015 4:21 AM, "Etienne Dechamps" <etienne at edechamps.fr> wrote: > >> Considering how cheap that operation seems to be, would it make sense >> to call res_init() every time tinc retries a metaconnection? It's not >> doing that very often anyway... and it would solve

I've noticed that with NetworkManager running in dom0, there is a lot of bad behaviour on the bridge interface After xend creates the bridge (using the sample network-bridge script in the package), the real interface is known as peth0 NetworkManager starts dhclient on peth0, which means the following: - peth0 gets it's own IP, maybe not the same as the bridge IP - a second default route

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

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

Fred Smith wrote: > On Tue, Jun 09, 2015 at 11:51:46AM +0200, johan.vermeulen7 at telenet.be > wrote: >> Hello All, >> >> on the latest installs I've done, on 2 different types of Latitude >> laptops, with 3 different wireless cars, of Centos7 and Mate desktop, >> it looks to me like NetworkManager is nog managing wireless. >> When clicking the nm icon

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,