search for: networkmangl

...Linux. And I am a few years old myself. > ----- Original Message ----- > From: "m roth" <m.roth at 5-cent.us> > To: "CentOS mailing list" <centos at centos.org> > Sent: Tuesday, February 14, 2017 10:07:55 AM > Subject: Re: [CentOS] CentOS 7, systemd, NetworkMangler, oh, my > > Johnny Hughes wrote: > <snip> >> I get it .. but no one needed a hand held cell phone before 1973 and no >> one needed a smart phone before 2007. Now, almost everyone has a smart >> cell and land lines are dying. Technology moves forward. People wa...

...were lost by Linux then... Valeri > > ----- Original Message ----- > From: "m roth" <m.roth at 5-cent.us> > To: "CentOS mailing list" <centos at centos.org> > Sent: Tuesday, February 14, 2017 10:07:55 AM > Subject: Re: [CentOS] CentOS 7, systemd, NetworkMangler, oh, my > > Johnny Hughes wrote: > <snip> >> I get it .. but no one needed a hand held cell phone before 1973 and no >> one needed a smart phone before 2007. Now, almost everyone has a smart >> cell and land lines are dying. Technology moves forward. People wan...

Someone else got the 7 pxe install going, and one thing that's annoying is that NetworkMangler appears to be regularly trying to fire up the wifi. On a workstation, in a wired environment. I just want to tell NM to knock it off....It's Monday, and my searching isn't going too well. Clues for the poor? mark

On 10 December 2015 at 15:00, <m.roth at 5-cent.us> wrote: > We've started having a problem with a CentOS 7 server. It looses its IPv6 > address, if I understand this issue correctly. We can get in, if we do ssh > -4, though. > > In the logs, I'm seeing this about twice an hour: > <warn> (pid 98466) unhandled DHCP event for interface ens3f0 > > Now, in

On Thu, 10 Dec 2015 16:00, m.roth at ... wrote: > We've started having a problem with a CentOS 7 server. It looses its IPv6 > address, if I understand this issue correctly. We can get in, if we do ssh > -4, though. > > In the logs, I'm seeing this about twice an hour: > <warn> (pid 98466) unhandled DHCP event for interface ens3f0 > > Now, in googling, I get

James Hogarth wrote: > On 10 December 2015 at 15:00, <m.roth at 5-cent.us> wrote: > >> We've started having a problem with a CentOS 7 server. It looses its >> IPv6 address, if I understand this issue correctly. We can get in, >> if we do ssh -4, though. >> >> In the logs, I'm seeing this about twice an hour: >> <warn> (pid 98466)

This is annoying. I yum removed NetworkManager-wifi... and I'm still getting this junk in the logs: MetworkManager[7723]: <warn> error requesting auth for org.freedesktop.NetworkManager.enable-disable-wifi: (0) Authorization check failed: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus) Anyone have a clue as to what or why this is

On 13/02/17 15:35, m.roth wrote: > My manager tells me a system in the datacenter is down. I go down there, > and plug in a monitor-on-a-stick and keyboard. It's up, but no network. I > try systemctl restart NetworkManager several times, and ip a shows *no* > change. > > Finally, I do an ifdown, followed by an ifup, and everything's wonderful. > > My manager thinks

On 02/13/2017 07:35 AM, m.roth at 5-cent.us wrote: > Finally, I do an ifdown, followed by an ifup, and everything's wonderful. What's in /etc/sysconfig/network-scripts/ifcfg-<interface>? Does it say NM_CONTROLLED=no? > My manager thinks that the NM daemon thinks everything's fine, and > there've been no changes, so it does nothing. He suggests that it might >

On 13 February 2017 at 15:35, <m.roth at 5-cent.us> wrote: > My manager tells me a system in the datacenter is down. I go down there, > and plug in a monitor-on-a-stick and keyboard. It's up, but no network. I > try systemctl restart NetworkManager several times, and ip a shows *no* > change. > > Finally, I do an ifdown, followed by an ifup, and everything's

Gordon Messmer wrote: > On 02/13/2017 07:35 AM, m.roth at 5-cent.us wrote: >> Finally, I do an ifdown, followed by an ifup, and everything's >> wonderful. > > What's in /etc/sysconfig/network-scripts/ifcfg-<interface>? Does it say > NM_CONTROLLED=no? > Good catch. No, it doesn't say no... because the line was commented out. I've just uncommented it,

On 02/13/2017 10:35 AM, m.roth at 5-cent.us wrote: >> What's in /etc/sysconfig/network-scripts/ifcfg-<interface>? Does it say >> NM_CONTROLLED=no? >> > Good catch. No, it doesn't say no... because the line was commented out. > I've just uncommented it, and set it to yes. Commented out should be the same as =yes. Only =no will cause it to be managed by

On 02/14/2017 06:49 AM, Johnny Hughes wrote: > > But as Linux installs become more and more complicated and it is not > some individual machines in a rack but clouds, clusters, and containers > with software defined networking and individual segments for specific > applications spread out within the network, only talking to one another > .. etc. Well, NM will be much more

On 02/14/2017 08:40 PM, Alice Wonder wrote: > Well CentOS 7 doesn't use that, and trying to figure out where in the > mess of /etc/sysconfig/network-scripts the problem is occurring has > caused me much frustration. DHCPv6 is really unusual. IPv6 addressing and routing is set up almost entirely in the kernel, unless you're using static addresses. IPv6 is neither harder

Johnny Hughes wrote: <snip> > I get it .. but no one needed a hand held cell phone before 1973 and no > one needed a smart phone before 2007. Now, almost everyone has a smart > cell and land lines are dying. Technology moves forward. People want > integrated cloud, container, SDN technology, etc. Used a VCR or > Cassette Player lately? I have no intention of *ever*

On 2/15/2017 12:04 AM, Gordon Messmer wrote: > DHCPv6 is really unusual. IPv6 addressing and routing is set up > almost entirely in the kernel, unless you're using static addresses. > IPv6 is neither harder nor easier with NetworkManager, in my experience. It was my understanding that most ipv6 networks don't need DHCPv6, they normally self-configure with 'stateless

On Mon, 2017-02-13 at 16:49 +0000, James Hogarth wrote: > On EL6 yes NM should be removed on anything but a wifi system but on > EL7 unless you fall into a specific edge case as per the network docs: > > https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html-single/Networking_Guide/index.html > > you really should be using NM for a variety of reasons.

> Used a VCR or Cassette Player lately? My VCR broke. Replaced it with a DVD/HDD & USB3 unit. Replaced cassette player and tape recorders with broadcast quality handheld recorder DR-100mk3 and an amazingly good Sony PX440. Still retain the original functionality. C7 doesn't retain all the original functionality :-) -- Regards, Paul. England, EU. England's place is in the

Hi, folks, Freshly built box... but does not get its IPv6 address. Gets its IPv4 with no trouble, and if I *manually* run dhclient -v -N eno1, it gets the correct IPv6, but after that, nope. And INITIPV^=yes in /etc/sysconfig/network-scripts/ifcfg-eno1. I even tried adding NETWORKING_IPV6=yes to an otherwise empty /etc/sysconfig/network. What am I missing? mark

I've a 7 box (actually, it's RHEL, but the general list there is moribund), and I'm trying to configure it "correctly" so that it gets its hostname from the DHCP server. All I've found so far is a script to use from hooks of some kind. *Surely* there's just a configuration file option somewhere.... mark