search for: networkmang

Hi all, I've recently started using NetworkManger service and nmcli tool, I like it much better than the old network service and manually modifying network scripts. I've seen many online questions on how to disable NetworkManger but I have the opposite question! I am wondering if it be OK to disable network service altogether and just use Ne...

Shorewall 4.5.15 3 Interface setup em1 p3p1 p4p4 ppp0 Hi, Since changing to NetworkManger on Fedora 18 I can no longer connect to the DSL Modem, which is connected to Interface em1. When the NetworkManger brings up the interfaces and ppp0, it no longer assigns an IP to em1. If I have ppp0 disabled and NetworkManger brings up the interfaces, em1 gets an IP of 192.168.1.2. Then when...

...master; bond works as > expected. > When I restart NetworkManager, it creates a new bond with the same name but > not connected to any device. Two bonds with the same name is confusing for > my other monitoring scripts. > I'm wondering why a second bond is created? Is it a bug in NetworkManger? > > > #Create a bond with two slaves > nmcli con add autoconnect no type bond con-name bond0 ifname bond0 > nmcli con mod bond0 ipv6.method ignore ipv4.method manual ipv4.addresses > ${BOND_IP}/${BOND_CIDR} ${BOND_GW} ${BOND_DNS} ${BOND_DNS_SEARCH} > ipv4.never-default no...

...When I restart NetworkManager, it creates a new bond with the same name > but > >> not connected to any device. Two bonds with the same name is confusing > for > >> my other monitoring scripts. > >> I'm wondering why a second bond is created? Is it a bug in > NetworkManger? > >> > >> > >> #Create a bond with two slaves > >> nmcli con add autoconnect no type bond con-name bond0 ifname bond0 > >> nmcli con mod bond0 ipv6.method ignore ipv4.method manual > ipv4.addresses > >> ${BOND_IP}/${BOND_CIDR} ${BOND_GW} $...

...ide. I enable slaves and master; bond works as expected. When I restart NetworkManager, it creates a new bond with the same name but not connected to any device. Two bonds with the same name is confusing for my other monitoring scripts. I'm wondering why a second bond is created? Is it a bug in NetworkManger? #Create a bond with two slaves nmcli con add autoconnect no type bond con-name bond0 ifname bond0 nmcli con mod bond0 ipv6.method ignore ipv4.method manual ipv4.addresses ${BOND_IP}/${BOND_CIDR} ${BOND_GW} ${BOND_DNS} ${BOND_DNS_SEARCH} ipv4.never-default no ipv4.ignore-auto-dns no nmcli con...

On Fri, 2 Sep 2016, Toralf Lund wrote: > Hi, > > I'm trying to connect my CentOS 6.8 laptop to the wireless net at work, which > is secured with WPA2 and AES. I've done this successfully in the past using > NetworkManager, but a new safety feature was recently introduced: A CA > certificate is required. After this, I've not been able to connect. I have a > DER

Folks In Centos 6.5, I am getting the message in the log file every few minutes: NetworkManager: <info> Trying to start the supplicant... There is no wireless on that computer, but there are two NICs, because it is my home gateway. Is there some tweak that can prevent this message? The installation is a relatively new one, so all packages are "up-to-date". David Kurn

...s >> expected. >> When I restart NetworkManager, it creates a new bond with the same name but >> not connected to any device. Two bonds with the same name is confusing for >> my other monitoring scripts. >> I'm wondering why a second bond is created? Is it a bug in NetworkManger? >> >> >> #Create a bond with two slaves >> nmcli con add autoconnect no type bond con-name bond0 ifname bond0 >> nmcli con mod bond0 ipv6.method ignore ipv4.method manual ipv4.addresses >> ${BOND_IP}/${BOND_CIDR} ${BOND_GW} ${BOND_DNS} ${BOND_DNS_SEARCH} >...

On 05/09/16 11:08, John Hodrien wrote: > On Fri, 2 Sep 2016, Toralf Lund wrote: > >> Hi, >> >> I'm trying to connect my CentOS 6.8 laptop to the wireless net at >> work, which is secured with WPA2 and AES. I've done this successfully >> in the past using NetworkManager, but a new safety feature was >> recently introduced: A CA certificate is

Hi, I'm trying to connect my CentOS 6.8 laptop to the wireless net at work, which is secured with WPA2 and AES. I've done this successfully in the past using NetworkManager, but a new safety feature was recently introduced: A CA certificate is required. After this, I've not been able to connect. I have a DER format file, whose path I've entered in CA certificate: in the

Dear All, I'm currently troubleshooting NetworkManger scripts. I see a difference in machine A : drwxr-xr-x 2 root root 4096 apr 24 16:33 . drwxr-xr-x 5 root root 4096 jan 9 12:13 .. -rwxr-xr-x 1 root root 175 jan 9 12:13 00-netreport -rwxr-xr-x 1 root root 335 okt 22 2012 04-iscsi -rwxr-xr-x 1 root root 345 jan 9 12:13 05-netfs -rwxr-xr-x...

So, I'm getting an error where the network service and NetworkManager apparently don't agree on how to bring up vlans on bonded nics. Things come up if you 'ifup ..' manually. I thought I'd check if there were any updates, forgetting to fix what NetworkManger had done to /etc/resolv.conf and: http://centos.arvixe.com/7.0.1406/os/x86_64/repodata/repomd.xml: [Errno 12] Timeout on http://centos.arvixe.com/7.0.1406/os/x86_64/repodata/repomd.xml: (28, 'Resolving timed out after 30381 milliseconds') Trying other mirror. ^C^C^C ^C^C^C Current down...

...ey are configure and connected or not. How can we do that? More back ground information: I am using NetworkManager and nmcli tool to configure multiple wired Ethernet interfaces on CentOS 7. I want to set common DNS name server and search domain for all interfaces. /etc/resolv.conf is generated by NetworkManger and we cannot manually modify it. Thanks, Joe

Yup, verified those options are *not* set in 7.2. For a quick test I simply removed them from /usr/lib/systemd/system/NetworkManager.service, did a systemctl daemon-reload, restarted NetworkManager, logged back in as root, and was able to whack /home (7.3). On Tue, Dec 20, 2016 at 11:07 AM, Matthew Miller <mattdm at mattdm.org> wrote: > On Fri, Dec 16, 2016 at 02:29:28PM -0500, Jonathan

On Tuesday 10 January 2017 08:53:17 John R Pierce wrote: > On 1/9/2017 7:11 PM, fred roller wrote: > > On Mon, Jan 9, 2017 at 12:04 PM, Frank Cox<theatre at melvilletheatre.com> > > > > wrote: > >> That sounds like a weak signal from your wifi transmitter. > > > > Or signal interference. Where is the antennae located on the server? > > Ran

...;> So, I'm getting an error where the network service and NetworkManager >> apparently don't agree on how to bring up vlans on bonded nics. >> Things come up if you 'ifup ..' manually. I thought I'd check if >> there were any updates, forgetting to fix what NetworkManger had done >> to /etc/resolv.conf and: >> >> http://centos.arvixe.com/7.0.1406/os/x86_64/repodata/repomd.xml: >> [Errno 12] Timeout on >> http://centos.arvixe.com/7.0.1406/os/x86_64/repodata/repomd.xml: (28, >> 'Resolving timed out after 30381 milliseconds...

...this time) nodeA & nodeB comprise a HA cluster now... - nodeA can ping IPaddr2 IP - nodeB can ping kvm guest IP - kvm guest can get to nodeB's IP but* Only a bit non-common bit in my setup is: - both nodeA & nodeB be interfaces which are relevant to the subnet on which it operates are NetworkManger bridges put on top of NM team devices, like: ifaceSlaveA + ifaceSlaveB = teamInt = bridgeInt But maybe it's common, maybe many do that(?) And it seems that that "bridge ontop of nm-team" is doing something not... well, not doing something(?) *but - If I do not nmcli c d & n...

...> wrote: > So, I'm getting an error where the network service and NetworkManager > apparently don't agree on how to bring up vlans on bonded nics. > Things come up if you 'ifup ..' manually. I thought I'd check if > there were any updates, forgetting to fix what NetworkManger had done > to /etc/resolv.conf and: > > http://centos.arvixe.com/7.0.1406/os/x86_64/repodata/repomd.xml: > [Errno 12] Timeout on > http://centos.arvixe.com/7.0.1406/os/x86_64/repodata/repomd.xml: (28, > 'Resolving timed out after 30381 milliseconds') > Trying other mi...

On Fri, Feb 20, 2015 at 04:13:13PM -0700, Chris Stone wrote: > try CTRL-Z to put that running process in your shell to sleep, then: > > bg 1 You're missing a % there > killall -TERM yum Or just "control-Z" and then 'kill -9 %1' You don't need to background the job and then kill every process matching a name. -- rgds Stephen

On 12/23/2015 08:38 AM, Sylvain CANOINE wrote: > Then I'm wondering : > 2/ why "After=foo" does not imply "Requires=foo" for systemd 219, while it appeared to be in systemd 208. Either it's a regression, or the behaviour of 208, although logical, is buggy. I'm not entirely certain, but "After=" is independent of "Requires=", as documented