Linux上ipv6的RA配置

╰半橙微兮° 2022-08-27 03:20 551阅读 0赞

ipv6的相关配置：

http://www.tldp.org/HOWTO/Linux+IPv6-HOWTO/proc-sys-net-ipv6..html

关于NDP的RA相关配置：

http://strugglers.net/~andy/blog/2011/09/04/linux-ipv6-router-advertisements-and-forwarding/

## [Linux, IPv6, router advertisements and forwarding][Linux_ IPv6_ router advertisements and forwarding] ##

By default, a Linux host on an IPv6 network will listen for and solicit router advertisements in order to choose an IPv6 address for itself and to set up its default route. This is referred to as [stateless address autoconfiguration (SLAAC)][stateless address autoconfiguration _SLAAC].

If you don’t want a host to automatically configure an address and route then you could disable this behaviour by writing “0″ to**/proc/sys/net/ipv6/conf/\*/accept\_ra.**

Additionally, *if the Linux host considers itself to be a router then it will ignore all router advertisements*.

In this context, what makes the difference between router or not are the settings of the **/proc/sys/net/ipv6/conf/\*/forwarding** files (or the **net.ipv6.conf.\*.forwarding** sysctl). If you turn your host into a router by setting one of those to “1″, you may find that your host removes any IPv6 address and default route it learnt via SLAAC.

There is a valid argument that a router should not be autoconfiguring itself, and should have its addresses and routes configured statically. Linux has IP forwarding features for a reason though, and sometimes you want to forward packets with a Linux box while still enjoying autoconfiguration. In my case I have some hosts running virtual machines, with IPv6 prefixes routed to the virtual machines. I’d still like the hosts to learn their default route via SLAAC.

It’s taken me a long time to work out how to do this. It isn’t well-documented.

Firstly, if you have a kernel version of 2.6.37 or higher then your answer is to set **accept\_ra** to “2″. From [ip-sysctl.txt][]:

> accept\_ra – BOOLEAN
> 
> > Accept Router Advertisements; autoconfigure using them.
> > 
> > Possible values are:
> > 
> >  *  0 Do not accept Router Advertisements.
> >  *  1 Accept Router Advertisements if forwarding is disabled.
> >  *  2 Overrule forwarding behaviour. Accept Router Advertisements even if forwarding is enabled.
> > 
> > Functional default:
> > 
> >  *  enabled if local forwarding is disabled.
> >  *  disabled if local forwarding is enabled.

This appears to be a type of boolean that I wasn’t previously familiar with – one that has three different values.

If you don’t have kernel version 2.6.37 though, like say, everyone running the current Debian stable (2.6.32), this will not work. Helpfully, it also doesn’t give you any sort of error when you set **accept\_ra** to “2″. It just sets it and continues silently ignoring router advertisements.

![fuuuuuuuuuuuuuuuuuuuuuu][]

Fortunately [Bjørn Mork posted about a workaround][Bj_rn Mork posted about a workaround] for earlier kernels which I would likely have never discovered otherwise. You just have to disable forwarding for the interface that your router advertisements will come in on, e.g.:

# echo 0 > /proc/sys/net/ipv6/conf/eth0/forwarding

Apparently as long as **/proc/sys/net/ipv6/conf/all/forwarding** is still set to “1″ then forwarding will still be enabled. Obviously.

Additionally there are some extremely unintuitive interactions between “default” and “all” settings you may set in **/etc/sysctl.conf** and pre-existing interfaces. So there is a race condition on boot between IPv6 interfaces coming up and sysctl configuration being parsed. martin f krafft [posted about this][], and on Debian recommends setting desired sysctls in pre-up headers of the relevant iface stanza in**/etc/network/interfaces**, e.g.:

iface eth0 inet6 static
        address 2001:0db8:10c0:d0c5::1
        netmask 64
    # Enable forwarding
        pre-up echo 1 > /proc/sys/net/ipv6/conf/default/forwarding
        pre-up echo 1 > /proc/sys/net/ipv6/conf/all/forwarding
    # But disable forwarding on THIS interface so we still get RAs
        pre-up echo 0 > /proc/sys/net/ipv6/conf/$IFACE/forwarding
        pre-up echo 1 > /proc/sys/net/ipv6/conf/$IFACE/accept_ra
        pre-up echo 1 > /proc/sys/net/ipv6/conf/all/accept_ra
        pre-up echo 1 > /proc/sys/net/ipv6/conf/default/accept_ra

You will now have forwarding *and* SLAAC.

![everything went better than expected][]

This entry was posted on Sunday, September 4th, 2011 at 05:55 and is filed under [Debian][], [IPv6][], [Linux][]. You can follow any responses to this entry through the [RSS 2.0][] feed. You can [leave a response][], or [trackback][] from your own site.

### 12 Responses to “Linux, IPv6, router advertisements and forwarding” ###

1.  [Wildcard SSL Certificate][] Says:   
    [September 5th, 2011 at 09:39][September 5th_ 2011 at 09_39]
    
    WE have just started upgrading our test network to IPv6, it was much harder than i thought it would be, then the biggest head ache of all setting up the VLANS again ![:(][icon_sad.gif] lets just say its been a long long day
2.  kissg Says:   
    [December 22nd, 2011 at 10:08][December 22nd_ 2011 at 10_08]
    
    Wow! This post is great. It solved my problem. Thanks.
    
    I just put necessary echo commands into a new script called /etc/ppp/ipv6-up.d/0dhcp-slaac.
    
    Gabor
3.  [Jeff Loughridge][] Says:   
    [February 3rd, 2012 at 11:53][February 3rd_ 2012 at 11_53]
    
    Great post. I couldn’t determine why my linux VM wouldn’t accept RAs until Google led me here. Thanks for the help.
    
    Jeff L.
4.  [Thank Goodness for NAT66][] Says:   
    [February 6th, 2012 at 08:02][February 6th_ 2012 at 08_02]
    
    \[...\] I struggled to figure out why the debian router wouldn’t use SLAAC to configure its external interface. I knew that enabling forwarding would result in the OS ignoring Router Advertisements (RAs). I tried tweaking the IPv6 variables in the /proc filesystem. No luck. Fortunately, I stumbled upon a blog post called Linux, IPv6, Router Advertisements, and Forwarding. \[...\]
5.  Ravi Varma A Says:   
    [February 24th, 2012 at 05:27][February 24th_ 2012 at 05_27]
    
    Very good information. It was very useful and it solved my issue.
6.  [Blog o’ Doom » Native IPv6 On Comcast][Blog o_ Doom _ Native IPv6 On Comcast] Says:   
    [May 30th, 2012 at 08:03][May 30th_ 2012 at 08_03]
    
    \[...\] and 1 on the internal interface and packets will still be forwarded and you will accept RAs. See this blog for more \[...\]
7.  [Gwen L.][] Says:   
    [June 12th, 2012 at 22:49][June 12th_ 2012 at 22_49]
    
    Thanks for some more details than I’ve found elsewhere, especially the semantics of what this mysterious “2″ value I’ve seen prescribed for accept\_ra is.
8.  [Stormy][] Says:   
    [November 2nd, 2012 at 09:24][November 2nd_ 2012 at 09_24]
    
    You’ve captured this perfcelty. Thanks for taking the time!
9.  [Tom MCSE][] Says:   
    [March 10th, 2013 at 10:33][March 10th_ 2013 at 10_33]
    
    Great IPv6 info.
    
    Thanks a lot for this wonderful tutorial about IPv6.
    
    Tom MCSE
10. [l\_bratch][l_bratch] Says:   
    [April 30th, 2013 at 11:58][April 30th_ 2013 at 11_58]
    
    Thanks very much. My ppp0 interface on Arch defaulted to “2″ for accept\_ra, so my IPv6 routes were being messed up continually.
11. Ramkumar N Says:   
    [May 29th, 2013 at 07:26][May 29th_ 2013 at 07_26]
    
    Very good and clear information.Helped me a lot…
12. [IPv6 über DHCP an KVM Gäste verteilen | Sebastian Müller][IPv6 _ber DHCP an KVM G_ste verteilen _ Sebastian M_ller]Says:   
    [January 5th, 2014 at 21:18][January 5th_ 2014 at 21_18]
    
    \[…\] Wenn nicht ::1 genommen wird, muss das gateway im gast entsprechend angepasst werden. ::1 erspart diese Arbeit. Die pre-up echo’s sind ein workaround, da nur entweder accept\_ra ODER forwarding funktioniert. Genaueres findet man hier. \[…\]

[Linux_ IPv6_ router advertisements and forwarding]: http://strugglers.net/~andy/blog/2011/09/04/linux-ipv6-router-advertisements-and-forwarding/
[stateless address autoconfiguration _SLAAC]: http://en.wikipedia.org/wiki/IPv6_address#Stateless_address_autoconfiguration
[ip-sysctl.txt]: http://www.kernel.org/doc/Documentation/networking/ip-sysctl.txt
[fuuuuuuuuuuuuuuuuuuuuuu]: /images/20220824/77513da90ab04138b1e745266070c159.png
[Bj_rn Mork posted about a workaround]: http://lists.debian.org/debian-ipv6/2011/05/msg00046.html
[posted about this]: http://marc.info/?l=linux-kernel&m=123599691025508&w=2
[everything went better than expected]: /images/20220824/18dd337fed3d44d5a1036506eedacada.png
[Debian]: http://strugglers.net/~andy/blog/category/linux/debian/
[IPv6]: http://strugglers.net/~andy/blog/category/internet/ipv6/
[Linux]: http://strugglers.net/~andy/blog/category/linux/
[RSS 2.0]: http://strugglers.net/~andy/blog/2011/09/04/linux-ipv6-router-advertisements-and-forwarding/feed/
[leave a response]: http://strugglers.net/~andy/blog/2011/09/04/linux-ipv6-router-advertisements-and-forwarding/#respond
[trackback]: http://strugglers.net/~andy/blog/2011/09/04/linux-ipv6-router-advertisements-and-forwarding/trackback/
[Wildcard SSL Certificate]: http://www.ssl247.com/
[September 5th_ 2011 at 09_39]: http://strugglers.net/~andy/blog/2011/09/04/linux-ipv6-router-advertisements-and-forwarding/#comment-204760
[icon_sad.gif]: /images/20220824/4db677b1a9e6475e93962257f2977e4c.png
[December 22nd_ 2011 at 10_08]: http://strugglers.net/~andy/blog/2011/09/04/linux-ipv6-router-advertisements-and-forwarding/#comment-228061
[Jeff Loughridge]: http://brooksconsulting-llc.com/
[February 3rd_ 2012 at 11_53]: http://strugglers.net/~andy/blog/2011/09/04/linux-ipv6-router-advertisements-and-forwarding/#comment-233170
[Thank Goodness for NAT66]: http://packetpushers.net/thank-goodness-for-nat66/
[February 6th_ 2012 at 08_02]: http://strugglers.net/~andy/blog/2011/09/04/linux-ipv6-router-advertisements-and-forwarding/#comment-233375
[February 24th_ 2012 at 05_27]: http://strugglers.net/~andy/blog/2011/09/04/linux-ipv6-router-advertisements-and-forwarding/#comment-235170
[Blog o_ Doom _ Native IPv6 On Comcast]: http://www.phildev.net/phil/blog/?p=308
[May 30th_ 2012 at 08_03]: http://strugglers.net/~andy/blog/2011/09/04/linux-ipv6-router-advertisements-and-forwarding/#comment-246797
[Gwen L.]: http://www.ecalevolada.info/
[June 12th_ 2012 at 22_49]: http://strugglers.net/~andy/blog/2011/09/04/linux-ipv6-router-advertisements-and-forwarding/#comment-247830
[Stormy]: http://www.google.com/
[November 2nd_ 2012 at 09_24]: http://strugglers.net/~andy/blog/2011/09/04/linux-ipv6-router-advertisements-and-forwarding/#comment-263047
[Tom MCSE]: http://www.joera.in/
[March 10th_ 2013 at 10_33]: http://strugglers.net/~andy/blog/2011/09/04/linux-ipv6-router-advertisements-and-forwarding/#comment-280196
[l_bratch]: http://www.bratch.co.uk/
[April 30th_ 2013 at 11_58]: http://strugglers.net/~andy/blog/2011/09/04/linux-ipv6-router-advertisements-and-forwarding/#comment-284591
[May 29th_ 2013 at 07_26]: http://strugglers.net/~andy/blog/2011/09/04/linux-ipv6-router-advertisements-and-forwarding/#comment-287238
[IPv6 _ber DHCP an KVM G_ste verteilen _ Sebastian M_ller]: https://www.mueller.mn/2014/01/ipv6-ueber-dhcp-an-kvm-gaeste-verteilen/
[January 5th_ 2014 at 21_18]: http://strugglers.net/~andy/blog/2011/09/04/linux-ipv6-router-advertisements-and-forwarding/#comment-336874