FireBrick 2700 Configuration run-through: Difference between revisions
m (→Native IPv6) |
|||
|
</config>
</syntaxhighlight>
DNS auto-config:
( since release V0.02.039 )
The previous config will allow your IPv6-enabled clinets to auto-configure an IP address, and default route. To configure IPv6 DNS server addresses ( DNS servers that are to be queried over IPv6 ), then there are a couple of options. Very recent clients may be RFC6106 aware, and be able to recieve DNS server addresses along with the other config in the same Router Announcement form the FB. To enable this, set the ra-dns option to point to your IPv6 Recursive DNS Server ( in this example, I've added a static IPv6 address 2001:8B0:B7:1::2 to my DNS server box, obviously point it to your own! ):
<syntaxhighlight>
<subnet ip="2001:8B0:B7:1::1/64" ra="true" ra-dns="2001:8B0:B7:1::2"/>
</syntaxhighlight>
This will make the FB include the RDNSS option in the Router Announcements.
If the client is smart enough, this is all it will take.
Most clients are not currently able to recieve this option.
So we must use the more traditional method:
Setting the 'O' flag in the RA, telling the client to do DHCPv6 and ask for 'Other' config data, ie DNS.
<syntaxhighlight>
<subnet ip="2001:8B0:B7:1::1/64" ra="true" ra-other="true"/>
</syntaxhighlight>
Now, the FB will set the O flag, and your clients will query another DHCPv6 server for Other ( DNS ) config data. You must provision an external DHCPv6 server in this case.
The FB can be configured to run a mini-DHCPv6 server to respond to these queries, too.
To enable the O flag AND the mini-DHCPv6, set the ra-other option to 'dhcpv6', and also specify the DNS server address to be doled out in the rd-dns option:
<syntaxhighlight>
<subnet ip="2001:8B0:B7:1::1/64" ra="true" ra-other="dhcpv6" ra-dns="2001:8B0:B7:1::2"/>
</syntaxhighlight>
Now, the clients are instructed to do DHCPv6, ant this FB will respond with the addresses listed.
Tested with: Win 7, Win Vista
= Next Steps, Bonding a Second Line =
| |||