On 03/10/2015 08:59 AM, Robert Moskowitz wrote:
>
> error: "net.ipv6.conf.eth0.disable_ipv6" is an unknown key
s/eth0/your_interface_name/
...or just leave it out, it will probably work with one, or both of the
other two.
Peter
___
CentOS mailing lis
On 03/09/2015 12:52 PM, Robert Moskowitz wrote:
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 Cent
On 03/09/2015 03:24 PM, Peter wrote:
On 03/09/2015 01:15 AM, Chris Stone wrote:
sysctl -w net.ipv6.conf.all.accept_ra=0
On 03/10/2015 06:52 AM, Robert Moskowitz wrote:
No change after running this and trying both:
system network restart
it's: service network restart
Typo. My dsyelxia at
> On 03/09/2015 01:15 AM, Chris Stone wrote:
>>
>> sysctl -w net.ipv6.conf.all.accept_ra=0
On 03/10/2015 06:52 AM, Robert Moskowitz wrote:
> No change after running this and trying both:
>
> system network restart
it's: service network restart
Try also setting these in sysctl:
net.ipv6.conf.al
On Mon, Mar 9, 2015 at 12:39 PM, Robert Moskowitz wrote:
> 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
On 03/09/2015 02:18 PM, Chris Stone wrote:
How about, in your /etc/sysconfig/network file adding or editing the line
for IPV6 to be:
NETWORKING_IPV6=no
One of the first things I tried. It is still in there and doing no
difference.
What I have is:
# cat network
NETWORKING=yes
HOSTNAME=z9
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
wrote:
> No change after running this and trying both:
>
> syst
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 k
On 03/09/2015 12:55 AM, Ryan Wagoner wrote:
On Fri, Mar 6, 2015 at 11:52 AM, Robert Moskowitz
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).
What els
ed on all our systems!
-Original Message-
From: centos-boun...@centos.org [mailto:centos-boun...@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
sysc
- disabling IPv6 addressing
Sorry - that should be
sysctl -w net.ipv6.conf.all.accept_ra=0
to disable that, not 1.
Chris
On Sun, Mar 8, 2015 at 11:14 PM, Chris Stone wrote:
> Try:
>
> sysctl -w net.ipv6.conf.all.accept_ra=1
>
> to persist between boots, be sure to add this to your /
Sorry - that should be
sysctl -w net.ipv6.conf.all.accept_ra=0
to disable that, not 1.
Chris
On Sun, Mar 8, 2015 at 11:14 PM, Chris Stone wrote:
> 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 sh
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 wrote:
> On Fri, Mar 6, 2015 at 11:52 AM, Robert
On Fri, Mar 6, 2015 at 11:52 AM, Robert Moskowitz
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).
What else do I
On 03/06/2015 10:59 AM, zep wrote:
On 03/06/2015 10:40 AM, Robert Moskowitz wrote:
I have just moved a host from a network that supports static IPv4 and
IPv6. The IPv4 addr is set in ifcfg-eth0, and the IPv6 via RA (I set
the MAC so I get an IPv6 addr that I like).
I just moved the host to
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).
What else do I need to do to disable the listening for RA announcements
and setting an IPv6 global address? I do
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 module
On 03/06/2015 10:40 AM, Robert Moskowitz wrote:
> I have just moved a host from a network that supports static IPv4 and
> IPv6. The IPv4 addr is set in ifcfg-eth0, and the IPv6 via RA (I set
> the MAC so I get an IPv6 addr that I like).
>
> I just moved the host to a network that supports static
>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 that rely on the
I have just moved a host from a network that supports static IPv4 and
IPv6. The IPv4 addr is set in ifcfg-eth0, and the IPv6 via RA (I set
the MAC so I get an IPv6 addr that I like).
I just moved the host to a network that supports static IPv4, but only
dymanic IPv6, so at this time (until I
20 matches
Mail list logo