similar to: C7, NetworkMangler, and IPv6

Displaying 20 results from an estimated 10000 matches similar to: "C7, 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
2006 Sep 10
2
Disabling IPv6 in Centos 4.x Experiences
Hi there, While I was looking "how to disable ipv6 under centos" I have found a gazzillion pages about how to do it and some of then even list things that i am not sure where they came from, so for the record I list most of them here in case someone else need them. Some of the methods involved the direct modification of system scripts, and I am against that so I wont list them here
2015 Dec 10
6
CentOS 7, NetworkMangler, and ipv6
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 very few hits putting quotes around "unhanded dhcp exception" - in fact, the
2017 May 15
0
kickstart: dracut-initqueue fails due to unresolvable hostname even though network config looks perfectly ok
This problem still bites us. I've tried to play around with DHCP settings (rd.net.timeout.dhcp, rd.net.dhcp.retry) to no avail. I'm happy about /any/ hint. Cheers frank On 04/24/2017 11:57 PM, Frank Thommen wrote: > Hi, > > kickstarting fails due to problems with host resolution, even though the > network seems to be properly configured through DHCP. eno1 and eno2 are
2017 Apr 24
2
kickstart: dracut-initqueue fails due to unresolvable hostname even though network config looks perfectly ok
Hi, kickstarting fails due to problems with host resolution, even though the network seems to be properly configured through DHCP. eno1 and eno2 are both attached to the network, but only eno1 gets an IP via DHCP. Still `curl` cannot resolve the mirror host and the kickstart host during dracut-initqueue: rdsosreport.txt ------------------------------------------------ [...] [ 14.780428]
2020 Jun 16
2
Missing Quote from latest Update
Received these error message during update 16Jun2020. Running scriptlet: kmod-kvdo-6.2.1.138-58.el8_1.x86_64 750/1181 /etc/sysconfig/network-scripts/ifcfg-eno1: line 21: unexpected EOF while looking for matching `"' /etc/sysconfig/network-scripts/ifcfg-eno1: line 22: syntax error: unexpected end of file /etc/sysconfig/network-scripts/ifcfg-eno1: line 21: unexpected EOF while looking
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
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)
2011 May 07
2
Configuring ipv6 reboot persistence, CentOS 5.6
Hello, I'm running a CentOS 5.6 server through linode. I am atempting to configure it for ipv6, previously this had been done though not by me on a ubuntu box so the hardware can take it. I've got an ipv6 tunnel through Hurricane Electric and at a shell prompt have done the following: ifconfig sit0 up ifconfig sit0 inet6 tunnel ::IPV4 Address ifconfig sit1 up ifconfig sit1 inet6 add IPV6
2011 Mar 01
2
unable to assign static IPv6
I'm having a problem permanently assigning a static IPv6 address to my CentOS v5.5 box. I have IPv6 enabled and the link local address is automatically brought up. I can manually ifconfig the address but when I configure it in ifcfg-eth0 and restart the network init script the IPv6 address is not assigned. Anyone have any ideas on how to fix this?
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
2012 Mar 30
1
IPv6 routing failure on CentOS5
I can't get IPv6 routing to configure correctly despite everything I've read saying it should This is my network config on a fully-updated CentOS 5.8 system: # cat /etc/sysconfig/network NETWORKING=yes NETWORKING_IPV6=yes HOSTNAME=my.hostname.com GATEWAY=aaa.bbb.ccc.ddd IPV6_DEFAULTGW=2a02:aaaa.bbbb::1 IPV6_DEFAULTDEV=eth0 # cat /etc/sysconfig/network-scripts/ifcfg-eth0
2013 Jan 09
0
network not accessible through bridged interface but traffic visible
I had a major HD failure and need to rebuild my host server and the virtual servers that resided on it. I am moving from CentOS 5.6 to CentOS 6.3. I am using the same configuration, as best as I can tell, that was working only hours ago on 5.6 but does not work on 6.3. My guest server can see network traffic on the bridged network device but I cannot seem to interact with it. Iptables turned
2008 Jul 10
0
1st static IPv6 address
My ISP assigned prefix is: 2607:F4B8:3::/48 So I am building my internal IPv6 firewall/router/ etc. I want to have a static IPv6 address on its eth0 so that I can create static v6 routes to it from the gateway. I add the following lines to ifcfg-eth0: HWADDR=00:40:F4:05:A8:F1 IPV6INIT=yes IPV6_AUTOCONF=no IPV6ADDR="2607:F4B8:3:1" if-up eth0 gets the error: Error: an inet prefix
2008 Jul 10
2
Kernel is not compiled with IPv6 support?
How did I get this? I am current on my 5.2 upgrades on this system. Running kernel: 2.6.18-92.1.6.el5 I did a service network restart and got: Shutting down interface eth0: [ OK ] Shutting down loopback interface: [ OK ] FATAL: Module off not found. CRITICAL : [ipv6_test] Kernel is not compiled with IPv6 support Bringing up loopback
2009 Jun 10
1
IPv6 range provisioning question
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 A few months back, I tried to use the network scripts to provision an IPv6 range like can be done with IPv4. I was using CentOS 5.2 at the time and was informed that 5.2 was broken in this regard. I have upgraded to CentOS 5.3 now and I am trying to get IPv6 to provision an entire range of IPs, but I am still getting the old behavior and no IPs are
2020 Sep 22
2
nmcli: unwanted secondary ip-address
Dear Simon, every second IP-address is unwanted. We restarted? eno4: nmcli con down eno4; nmcli con up eno4 and the second address vanishes. Then after a few ours, the second ip address reappears. This is the config-file of eno2: # cat ifcfg-eno2 TYPE=Ethernet PROXY_METHOD=none BROWSER_ONLY=no BOOTPROTO=none DEFROUTE=yes IPV4_FAILURE_FATAL=yes IPV6INIT=no IPV6_AUTOCONF=yes IPV6_DEFROUTE=yes
2015 Mar 09
1
Centos 6 - disabling IPv6 addressing
How about, in your /etc/sysconfig/network file adding or editing the line for IPV6 to be: NETWORKING_IPV6=no and then try a 'service network restart' and see what you get. Chris On Mon, Mar 9, 2015 at 11:52 AM, Robert Moskowitz <rgm at htt-consult.com> wrote: > No change after running this and trying both: > > system network restart > > ifdown eth0; ifup eth0
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 >