search for: accept_ra

On Tue, Aug 18, 2020 at 01:32:06AM +0200, Stefano Brivio wrote: > The check comes from commit 00d28a78b5d1 ("network: check accept_ra > before enabling ipv6 forwarding"), and it's there because the accept_ra > flag works like this (from Documentation/networking/ip-sysctl.txt): > > 0 Do not accept Router Advertisements. > 1 Accept Router Advertisements if forwarding is disabled. > 2 Overrule forwa...

...beef:55::' prefix='64'> > > </ip> > > </network> > > > > The first problem I hit was trying to start that network: > > > > error: internal error: Check the host setup: enabling IPv6 forwarding > > with RA routes without accept_ra set to 2 is likely to cause routes > > loss. Interfaces to look at: wlp4s0 > > > > wlp4s0 is my wifi card that is configured by NetworkManager in a > > completely unremarkable fashion. By default it gets an ipv6 via SLAAC > > from my router. This feels a bit like...

...9;ipv6' address='fc00:dead:beef:55::' prefix='64'> > </ip> > </network> > > The first problem I hit was trying to start that network: > > error: internal error: Check the host setup: enabling IPv6 forwarding > with RA routes without accept_ra set to 2 is likely to cause routes > loss. Interfaces to look at: wlp4s0 > > wlp4s0 is my wifi card that is configured by NetworkManager in a > completely unremarkable fashion. By default it gets an ipv6 via SLAAC > from my router. This feels a bit like the unresolved bug [1] wh...

Changing the subject line for good ... On Thu, Apr 7, 2011 at 8:58 AM, Lamar Owen <lowen at pari.edu> wrote: > On Thursday, April 07, 2011 11:23:51 AM Brunner, Brian T. wrote: >> AIUI: In previous releases, RH distributed source + patches. ?Starting >> 6.0 RH releases patched source. ?This makes backing out a patch, or >> backporting patches from future development in

...p> </ip> <ip family='ipv6' address='fc00:dead:beef:55::' prefix='64'> </ip> </network> The first problem I hit was trying to start that network: error: internal error: Check the host setup: enabling IPv6 forwarding with RA routes without accept_ra set to 2 is likely to cause routes loss. Interfaces to look at: wlp4s0 wlp4s0 is my wifi card that is configured by NetworkManager in a completely unremarkable fashion. By default it gets an ipv6 via SLAAC from my router. This feels a bit like the unresolved bug [1] which says that systemd-netw...

...I'm using CentOS 7 as a gateway and it's worked great for several versions for IPv4. I'm not seeing any IPv6 default route on the WAN interface. I suspect I'm not getting route announcements. I think I have all the IPv6 variables in ifcfg-em2 set right. But I do notice that the accept_ra file in proc for that interface has value 1, not 2. Changing it to 2 doesn't change anything, though. No route appears. While I wait for an answer to my trouble ticket, is there some way to verify that I'm not receiving any RA packets? Is there a way to force a solicitation for one? Is...

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 <axisml at gmail.com> 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 should prevent...

I do not working with ipv6, I have disable, but I have the same error, I can read in internet that this ipv6 ip 2001:638:603:d06e::80:230: belong to url samba.org.... If I try to connect to this url using some navegator I connected perfect....but when I run git pull using command line I can not connect.. > Am 28.02.2015 um 15:37 schrieb sandy.napoles at eccmg.cupet.cu: >> Hello list,

...CentOS7)?and some gathered on internet # cat /etc/sysctl.d/90-disable_ipv6.conf? net.ipv6.conf.all.disable_ipv6=1 net.ipv6.conf.default.disable_ipv6=1 net.ipv6.conf.eth0.disable_ipv6=1 net.ipv6.conf.eth1.disable_ipv6=1 net.ipv6.conf.all.use_tempaddr=0 net.ipv6.conf.all.autoconf=0 net.ipv6.conf.all.accept_ra=0 net.ipv6.conf.default.autoconf=0 net.ipv6.conf.default.accept_ra=0 net.ipv6.conf.eth0.autoconf=0 net.ipv6.conf.eth1.autoconf=0 But with dhcp, NetworkManager (or something) reenables ipv6 on interfaces. #sysctl -a | grep ipv6 | grep disable net.ipv6.conf.all.disable_ipv6 = 1 net.ipv6.conf.defau...

in /etc/sysctlsysctl.conf net.ipv6.conf.all.accept_ra = 1 net.ipv6.conf.all.autoconf = 1 net.ipv6.conf.eth0.accept_ra = 1 net.ipv6.conf.eth0.autoconf = 1 when i run cat /etc/sysctl.conf | grep ipv6 #net.ipv6.conf.all.forwarding=1 #net.ipv6.conf.all.accept_redirects = 0 #net.ipv6.conf.all.accept_source_route = 0 net.ipv6.conf.all.accept_ra = 1 net.ipv...

...uration for most of my clients. For the servers I prefer to manually assign the address. I have defined the IPv6 address in the ifcfg-eth0 file and set IPV6_AUTOCONF=no. However ifconfig shows both the auto configured and manually assigned address. Looking around I found that net.ipv6.conf.default.accept_ra is set to 1 by default. The ifup-ipv6 is setting net.ipv6.conf.eth0.accept_ra to 0 like it should. From what I can tell the auto configuration is happening right before net.ipv6.conf.eth0.accept_ra is set to 0. If I define net.ipv6.conf.default.accept_ra = 0 in sysctl.conf IPV6_AUTOCONF works as ex...

...T be contributing to > things not working as they would on a 'normal' Centos box. I am awaiting > the start of the Centos7-arm work ;) > > > On 03/09/2015 01:15 AM, Chris Stone wrote: > >> 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 <axisml at gmail.com> wrote: >> >> Try: >>> >>> sysctl -w net.ipv6.conf.all.accept_ra=1 >>> >>>...

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

...-----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 that, not 1. Chris On Sun, Mar 8, 2015 at 11:14 PM, Chris Stone <axisml at gmail.com> 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 should preven...

...using is the F19 kernel. All of this MIGHT be contributing to things not working as they would on a 'normal' Centos box. I am awaiting the start of the Centos7-arm work ;) On 03/09/2015 01:15 AM, Chris Stone wrote: > 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 <axisml at gmail.com> wrote: > >> Try: >> >> sysctl -w net.ipv6.conf.all.accept_ra=1 >> >> to persist between boots, be sure to add this to you...

> 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.all.disable_ipv6=1 net.ipv6.conf.default.disable_ipv6=1 net.ipv6.conf.eth0.dis...

...> # cat /etc/sysctl.d/90-disable_ipv6.conf > net.ipv6.conf.all.disable_ipv6=1 > net.ipv6.conf.default.disable_ipv6=1 > net.ipv6.conf.eth0.disable_ipv6=1 > net.ipv6.conf.eth1.disable_ipv6=1 > net.ipv6.conf.all.use_tempaddr=0 > net.ipv6.conf.all.autoconf=0 > net.ipv6.conf.all.accept_ra=0 > net.ipv6.conf.default.autoconf=0 > net.ipv6.conf.default.accept_ra=0 > net.ipv6.conf.eth0.autoconf=0 > net.ipv6.conf.eth1.autoconf=0 > > > But with dhcp, NetworkManager (or something) reenables ipv6 on interfaces. > > #sysctl -a | grep ipv6 | grep disable > net.ipv...

...a > gateway and it's worked great for several versions for IPv4. > > I'm not seeing any IPv6 default route on the WAN interface. I > suspect I'm not getting route announcements. I think I have all the > IPv6 variables in ifcfg-em2 set right. But I do notice that the > accept_ra file in proc for that interface has value 1, not 2. > Changing it to 2 doesn't change anything, though. No route appears. > > While I wait for an answer to my trouble ticket, is there some way > to verify that I'm not receiving any RA packets? Is there a way to > force a sol...

On Fri, Mar 04, 2016 at 09:43:44PM +0100, Guus Sliepen wrote: > - On Linux, add "echo 0 >/proc/sys/net/ipv6/conf/$INTERFACE/accept_ra" > to tinc-up before any ifconfig or ip commands. Ah, if it's only the default route you don't want, then it's: echo 0 >/proc/sys/net/ipv6/conf/$INTERFACE/accept_ra_defrtr -- Met vriendelijke groet / with kind regards, Guus Sliepen <guus at tinc-vpn.org> ----...

I have been gradually moving more tinc servers over to ipv6 addresses on the tinc 1.1 branch. Tinc is inserting a default route for ipv6 for some reason... default via 2600:3c01:e030:f2::1 dev tinc6 proto static metric 950 pref medium In my case the default route supplied by ra is still the correct thing, but I don't see where in the code tinc is inserting this route from.... which, as