similar to: CentOS 7, NetworkMangler, and ipv6

Displaying 20 results from an estimated 2000 matches similar to: "CentOS 7, NetworkMangler, and ipv6"

2015 Dec 10
1
CentOS 7, NetworkMangler, and ipv6
Yamaban wrote: > 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
2015 Dec 10
1
CentOS 7, NetworkMangler, and ipv6
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)
2015 Dec 10
0
CentOS 7, NetworkMangler, and ipv6
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
2015 Dec 10
0
Re: CentOS 7, NetworkMangler, and ipv6
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
2017 Feb 14
8
CentOS 7, systemd, NetworkMangler, oh, my
On 02/13/2017 11:36 AM, peter.winterflood wrote: > On 13/02/17 16:49, James Hogarth wrote: >> On 13 February 2017 at 16:17, peter.winterflood >> <peter.winterflood at ossi.co.uk> wrote: >>> >>> >>> there's a really good solution to this. >>> >>> yum remove NetworkManager* >>> >>> chkconfig network on
2017 Jul 12
3
CentOS 7, NM, and IPv6
Hi, folks, I and the other admin here have just been assigned a mission... here's what's happening: only very recently - the last week? our CentOS 7 boxes, or at least some of them, will lose their IPv6 addresses, and not get it back. 1. We're running dibbler on the same box that serves DHCP. 2. It's been working for many months. 3. The lease file remains in place.
2014 Jul 23
1
CentOS 7, networkmangler, and hostname
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
2017 Feb 13
8
CentOS 7, systemd, NetworkMangler, oh, my
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 that the NM daemon thinks everything's fine, and there've been
2017 Feb 14
1
dhcpcd.conf
Hi, ran into a problem w/ linode hosted VM where IPv6 address changed after they migrated it to a different host. They claim I can fix it with sed -i 's/slaac private/slaac hwaddr/' /etc/dhcpcd.conf However there appears to be no dhcpcd.conf on any of my CentOS 7 systems. What is the CentOS 7 equivalent?
2017 Feb 15
0
CentOS 7, systemd, NetworkMangler, oh, my
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
2015 May 19
3
Turning off wifi in CentOS 7
On 5/19/2015 10:24 AM, James Hogarth wrote: > On 19 May 2015 11:40, <me at tdiehl.org> wrote: >> >> >> Or if you want a bigger hammer: >> >> systemctl disable NetworkManager.service >> systemctl enable network.service >> systemctl stop NetworkManager.service >> systemctl start network.service >> >> The above will disable
2018 Oct 17
1
C7, NetworkMangler, and IPv6
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
2008 Mar 10
3
A stats question -- about survival analysis and censoring
Dear UseRs, Suppose I have data regarding smoking habits of a prospective cohort and wish to determine the risk ratio of colorectal cancer in the smokers compared to the non-smokers. What do I do at the end of the study with people who die of heart disease? Can I just censor them exactly the same as people who become uncontactable or who die in a plane crash? If not, why not? I'm thinking
2017 Feb 15
0
CentOS 7, systemd, NetworkMangler, oh, my
On 02/15/2017 07:34 AM, Leroy Tennison wrote: > Too much temptation to resist, I don't know which one of us is older but I have a feeling it's a "horse race". Like you, I still have a land line, WiFi is too slow and "WiFi security" seems to be an oxymoronic phrase. Why people text (or IM for that matter) anything other than a one-liner is beyond me. > > Now
2015 Dec 14
0
CentOS 7, NetworkMangler
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
2017 Feb 13
0
CentOS 7, systemd, NetworkMangler, oh, my
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
2017 Feb 13
0
CentOS 7, systemd, NetworkMangler, oh, my
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 >
2017 Feb 13
0
CentOS 7, systemd, NetworkMangler, oh, my
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
2017 Feb 13
2
CentOS 7, systemd, NetworkMangler, oh, my
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,
2017 Feb 13
0
CentOS 7, systemd, NetworkMangler, oh, my
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