From Fedora Project Wiki
(basic SLAAC)
 
No edit summary
Line 1: Line 1:
NetworkManager supports the IPv6 protocol. IPv6 is typically used in one of the following configurations:
NetworkManager supports the IPv6 protocol. IPv6 is typically used in one of the following configurations. Network
setup is typically done by the local router and, if necessary, DHCP server.


== SLAAC in dual stack
In the following examples, we assume that radvd resides on the router and DHCP is on the local network (possibly
also on the router).
 
== Static configuration
 
== SLAAC without DNS configuration


/etc/radvd.conf:
/etc/radvd.conf:
Line 8: Line 14:
interface eth0 {
interface eth0 {
     AdvSendAdvert on;
     AdvSendAdvert on;
     prefix 2001:db8:1:2::/64 {
     prefix 2001:db8:1:2::/64 {};
    }
};
}
</pre>
</pre>


In this configuration, DNS is done with IPv4.
DNS queries typically use IPv4.
 
== SLAAC with RDNSS and DNSSL ==
 
/etc/radvd.conf:
 
<pre>
interface eth0 {
    AdvSendAdvert on;
    prefix 2001:db8:1:2::/64 {};
    RDNSS 2001:db8:1:2::ab {};
    DNSSL example.net {};
};
</pre>
 
The contents of host's /etc/resolv.conf is filled in by NetworkManager.
 
== SLAAC with DHCPv6 Information Request
 
/etc/radvd.conf:
 
<pre>
interface eth0 {
    AdvSendAdvert on;
    AdvOtherConfigFlag on;
    prefix 2001:db8:1:2::/64 {};
};
</pre>


== SLAAC with RDNSS and DNSSL
This is often used to supply DNS information to hosts that don't support
RDNSS/DNSSL in Router Advertisements. NetworkManager currently supports
RDNSS but not DNSSL.

Revision as of 12:57, 18 May 2012

NetworkManager supports the IPv6 protocol. IPv6 is typically used in one of the following configurations. Network setup is typically done by the local router and, if necessary, DHCP server.

In the following examples, we assume that radvd resides on the router and DHCP is on the local network (possibly also on the router).

== Static configuration

== SLAAC without DNS configuration

/etc/radvd.conf:

interface eth0 {
    AdvSendAdvert on;
    prefix 2001:db8:1:2::/64 {};
};

DNS queries typically use IPv4.

SLAAC with RDNSS and DNSSL

/etc/radvd.conf:

interface eth0 {
    AdvSendAdvert on;
    prefix 2001:db8:1:2::/64 {};
    RDNSS 2001:db8:1:2::ab {};
    DNSSL example.net {};
};

The contents of host's /etc/resolv.conf is filled in by NetworkManager.

== SLAAC with DHCPv6 Information Request

/etc/radvd.conf:

interface eth0 {
    AdvSendAdvert on;
    AdvOtherConfigFlag on;
    prefix 2001:db8:1:2::/64 {};
};

This is often used to supply DNS information to hosts that don't support RDNSS/DNSSL in Router Advertisements. NetworkManager currently supports RDNSS but not DNSSL.