similar to: Disable IPV6

I thought I'd done that standard stuff /etc/modprobe.conf: alias net-pf-10 off alias ipv6 off /etc/sysconfig/network: NETWORKING_IPV6=no But on reboot I still see ipv6 entries against the eth devices, ipv6 module is still loaded, and sit0 tunnel is present. What needs to be done to disable ipv6? -- rgds Stephen

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

Hello! I am having a strange issue with CentOS 5.4 that I cannot seem to solve. Every DNS lookup results in AAAA records being requested first before A records. As a result, this causes a large amount of unnecessary DNS traffic on the network. IPv6 has been completely disabled on these servers: /etc/modprobe.conf, ipv6 off and net-pf-10 off /etc/sysconfig/network, NETWORKING_IPV6=no lsmod |

Can I use puppet to ensure that a file includes certain text but not be required to maintain the entire file? For example, I would like /etc/modprobe.conf to contain the following lines but the file will also contain lines that are system dependent. --------------------------------------------------------------------------------------- # Disable IPV6 alias net-pf-10 off alias ipv6 off

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

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

Hi there, I'm trying to set tinc and I get the following messages: Sep 6 13:31:33 leibniz tinc.acvpn[12352]: tincd 1.0.1 (Aug 14 2003 15:09:44) starting, debug level 0 Sep 6 13:31:33 leibniz tinc.acvpn[12352]: /dev/net/tun is a Linux tun/tap device (tun mode) Sep 6 13:31:33 leibniz tinc.acvpn[12352]: Script tinc-up exited with non-zero status 126 Sep 6 13:31:33 leibniz tinc.acvpn[12352]:

Dear All, I am a student enrolled google summer code 2007. My job is to write security regression testsuites for FreeBSD under the guidance of my mentor Dr. Robert Watson. Under his encourage, I write following request for comments RFC :-) ////////////////////////////////////////////////////////////// What I plan to do: 1) to test the stability of Mandatory Access Control and Audit

http://wiki.centos.org/FAQ/CentOS5#head-47912ebdae3b5ac10ff76053ef057c366b421dc4 This tip suggests creating a /etc/modprobe.d/disable-ipv6 file. However modprobe from module-init-tools >= 3.7 will output this warning for it: | WARNING: All config files need .conf: /etc/modprobe.d/disable-ipv6, it will | be ignored in a future release. Simply changing the recipe to create a

Tried that :D yum is still trying to connect via ipv6 (ip_resolve=4 in config file) -----Original Message----- From: centos-bounces at centos.org [mailto:centos-bounces at centos.org] On Behalf Of Alikhan Damirov Sent: Thursday, December 25, 2014 11:59 AM To: CentOS mailing list Subject: Re: [CentOS] (py)curl error 7 Hi, from man yum.conf: ip_resolve Determines how yum resolves

Hi, [I have added freebsd-security to recipient list as I consider this issue a security risk] Paul Schenkeveld wrote: > Hello, > > On Fri, Jul 14, 2006 at 01:26:38PM +0300, Ari Suutari wrote: >> Hi, >> >> Does anyone know if there are any plans to bring >> pf boot-time protection (ie. /etc/rc.d/pf_boot and >> related config files) from NetBSD to FreeBSD

Hello folks, Since I started using CentOS4, one thing has been bugging me: sshd's ipv6 logging as seen here: Failed password for root from ::ffff:83.220.130.10 port 43511 ssh2 Not a big deal, but I'd be really happy if I could get it to log in ipv4 format like on CentOS3. Any suggestion? Thanks, Francois

I am having a problem with a couple servers. They both have a Digium TE110P and a TDM04B card. I have setup the system so the TE110P uses channels 1-31 and the TDM04B 32-35. The problem is that when we reboot the server sometimes the TDM04B is recognized first and the TE110P second so the configuration fails. I do not know why this happens and to solve this I have to do a "service

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). >> >> What else do I need to do to disable the listening for RA announcements >> >> and setting an IPv6 global address? I do not want to reboot the box. > There are other modules, most notably bonding

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

On 2015-11-26 14:16, Darren Tucker wrote: > On Thu, Nov 26, 2015 at 4:49 PM, Tinker <tinkr at openmailbox.org> wrote: >> On 2015-11-26 13:33, Darren Tucker wrote: > [...] >>> What is the script going to do? > > You didn't answer this. Register the login to the group's login database. >> How would you do it using bsdauth? >> >> (PAM

Hi all, I'm pretty new to CentOS. I am working with a newly set-up server: [cbearden at host ~]$ lsb_release -a LSB Version: :core-4.0-amd64:core-4.0-noarch:graphics-4.0-amd64:graphics-4.0-noarch:printing-4.0-amd64:printing-4.0-noarch Distributor ID: CentOS Description: CentOS release 6.3 (Final) Release: 6.3 Codename: Final I'm trying to solve this problem (X11 forwarding)

In Rails 3.0 (both RC and edge), any constant that''s defined while loading a file in development mode will get unloaded on each request, regardless of whether it comes from an autoload path in the application or from external code such as a gem. Example file (tested on a fresh edge app): # kittens.rb require ''nibbler/json'' # "nibbler" is a gem specified

Hi, Can puppet autosign work by giving vlan IP instead of domain? For example, in the autosign.conf file, instead of using *.mydomain.org, I want to give 172.18.133.* But it does not seem to work if I give the IP address. But I don''t want to limit the client from *.mydomain.org by only allow certain vlan client not all the are in the same domain. Thanks, -Haiyan -- You received this

By adding the a module alias, programs (or users) won't have to explicitly call modprobe. Vhost-net will always be available if built into the kernel. It does require assigning a permanent minor number for depmod to work. Choose one next to TUN since this driver is related to it. Also, use C99 style initialization. Signed-off-by: Stephen Hemminger <shemminger at vyatta.com> ---