similar to: Kernel is not compiled with IPv6 support?

So I do not want to run radvd on my public subnet (between the gateway and firewall). I am trying to set up the firewall's public interface. For now in ifcfg-eth0 I have the lines: DEVICE=eth0 BOOTPROTO=static HWADDR=00:40:F4:05:A8:F1 IPV6INIT=yes IPV6_AUTOCONF=no IPV6ADDR="2607:F4B8:3:1:0:40:F405:A8F1" ONBOOT=yes And in network I have: NETWORKING=yes NETWORKING_IPV6=yes

I just did a fresh install of centos 5.0 from cd, followed by yum update which installed 399 packages. No failures or errors that I can see. I have three nics in the box, but am only setting up one at the moment. The box can ping others in my network, but if I try ssh, telnet, ftp, etc I get this: [root at cm network-scripts]# ftp watchdog ftp: connect: No route to host ftp> [root at cm

My old Centos 5.5 servers had a /root/.forward to send things like logwatch to this email account. It did not take any special configuration in sendmail for this to work. Now Centos 6.3 is using postfix (as we well know, and generally I am happy for this) and I have set up the /root/.forward as always, but it seems like postfix is ignoring it. I have restarted postfix with no difference in

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

If a hostname is requested, for example -d ::::foo::dhcp, then include the hostname in the DHCP discover/request. This patch also allows the vendor class identifier to be omitted from the DHCP discover/request by specifying -i "" Signed-off-by: Aron Griffis <agriffis at n01se.net> --- usr/kinit/ipconfig/dhcp_proto.c | 49 ++++++++++++++++++++++++++++++--------

--- sysprep/sysprep_operation_net_hostname.ml | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/sysprep/sysprep_operation_net_hostname.ml b/sysprep/sysprep_operation_net_hostname.ml index 3824d42..7284d63 100644 --- a/sysprep/sysprep_operation_net_hostname.ml +++ b/sysprep/sysprep_operation_net_hostname.ml @@ -30,10 +30,12 @@ let net_hostname_perform (g :

-----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

I want to seriously work with IPv6 and not have stray IPv4 functions messing with me. So in /etc/sysconfig/network, I commented out NETWORKING=yes. I have NETWORKING_IPV6=yes. In /etc/sysconfig/network-scripts I altered ifcfg-eth0, setting BOOTPROTO=none. That was enough for eth0 to only have IPv6 working on it (have IPV6INIT=yes and IPV6_AUTOCONF=yes). But lo had IPv4. So I commented

On Fri, Mar 6, 2015 at 11:52 AM, Robert Moskowitz <rgm at htt-consult.com> wrote: > > > On 03/06/2015 11:00 AM, Robert Moskowitz wrote: > >> >> >> On 03/06/2015 10:55 AM, Barry Brimer wrote: >> >>> >>> >>> IPV6INIT="no" >>>> >>>> But I am still getting a global IPv6 (and of course local scope).

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

Try: sysctl -w net.ipv6.conf.all.accept_ra=1 to persist between boots, be sure to add this to your /etc/sysctl.conf file. This should prevent the box from listening to any RA announcements. Chris On Sun, Mar 8, 2015 at 10:55 PM, Ryan Wagoner <rswagoner at gmail.com> wrote: > On Fri, Mar 6, 2015 at 11:52 AM, Robert Moskowitz <rgm at htt-consult.com> > wrote: > > >

+1 IPv6 = solution looking for a problem. Disabled on all our systems! -----Original Message----- From: centos-bounces at centos.org [mailto:centos-bounces at centos.org] On Behalf Of Chris Stone Sent: Monday, March 09, 2015 01:15 AM To: CentOS mailing list Subject: Re: [CentOS] Centos 6 - disabling IPv6 addressing Sorry - that should be sysctl -w net.ipv6.conf.all.accept_ra=0 to disable

No change after running this and trying both: system network restart ifdown eth0; ifup eth0 Still having an IPv6 addr. The box has been up for 140 days. Would like to keep it running... This box is really Redsleeve 6, which is the port of Centos 6 to arm. The kernel I am using is the F19 kernel. All of this MIGHT be contributing to things not working as they would on a 'normal'

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

I have to disagree on that. NATs is the problem and I am one of the causes of that problem as one of the principals behind RFC 1918. What has happened is that HTTP has become the transport for the Internet. Very bad in a number of ways. But for another time. Perhaps. Right now I have to deal with a new ISP that was on the road to static IPv6 when somehow the lead engineer kind of

Hello Is there a way for the dhcp client to send the current host name of the machine when requesting a lease ? Currently I have to include a line like DHCP_HOSTNAME=appserver2 in my /etc/sysconfig/network-scripts/ifcfg-eth0, but I would like to tell the dhcp client to just 'also send the hostname' and then the client to get the current hostname itself, instead of having the name

Hi, I'm currently reading chapter 13 of the RHEL Deployment Guide, and taking some notes. I have a few minor questions: /etc/sysconfig/network According to the doc: "This file specifies routing and host information for all network interfaces." Here's how mine looks like: --8<----------------- NETWORKING=yes NETWORKING_IPV6=yes HOSTNAME=fujitsu.zuhause

Continuing to 'clean up' my new server by reviewing logged messages. Researching a common one: Feb 26 07:30:29 onlo named[19336]: error (unexpected RCODE SERVFAIL) resolving 'foo.com/MX/IN': 1.2.3.4#53 I get the drift that my server has been directed to a 'lame server' and logs that fact. Supposedly I am to lookup the SOA record and contact the admin to fix this.

A new and improved instance of onlo.htt-consult.com is up and providing DNS service. It is my 1st Centos 6.3 production box. This is Phase I which included IPv6 working 'right'. Phase II will be to sign my zone and get fully with DNSSEC. I want to thank people here in answering my questions. Now on to other projects. I have a couple dozen to tackle.

> Dear Simon, > > >> And can you diff the config of eno1 and eno4. > > # pwd > /etc/sysconfig/network-scripts Okay, nothing to find here. What about eno2, you also have two IP addresses there and even in the same subnet, is this wanted or not? Can the second address of eno2 be found in the ifcfg file? Both eno2 and eno4 have "scope global secondary dynamic"