On Tue, 20 Jul 2004 [EMAIL PROTECTED] wrote:
Hello all, I have been "playing" with ipv6 for a while now (mostly on Linux and osX) and I have started to turn my thoughts to networking and servers. The easy one I guess is servers. Presumably a static ipaddress is best to use because of DNS etc. If a static address is allocated, radvd will not be required because there is no ipv4 DHCP type requirement. Is this a correct assumption?
I would recommend using static addresses for servers, probably next to the autoconfigured addresses. You can add as much address as you want to an interface easily in IPv6. You can easily define a well know address for a particular address (another level of indirection and flexibility next to CNAMEs).
Second, networks. On an ipv4 based ip network, it is usual on wan links (unless they are unnumbered serial lines) to use a .252 or /30 mask with 4 addresses in the subnet (net, ip1, ip2, broadcast). Is this wise to implement in ipv6? eg use a /126 mask to allow four valid ipv6 addresses. In that case, if I get a /48, I would need to use the first allowed block (/49 mask?) carved up into much smaller chunks, ultimately down to the /126's for wan lines.
For WAN links, even if they are Ethernet, you can rely on link-local address. You don't have to to add prefix to them unless you have a host that will be also connected to that network and must be reachable globally. The link-local address is /64 and very much automatic... If you need a globally reachable address, allocate /64 for subnets and /128 for loopbacks.
Given a working ipv4 network where each remote site has a /24 ipv4 allocation (and is more than enough given the number of pc's there), would it be sensible to use a /120 for each site or perhaps be profligate(!) and use /118 to allow for all the ipv6 toasters we are likely to be able to buy next year?
Allocate between /48 - /64 for that network. Count the number of subnets - taking into account the future extension and allocate accordingly. If you have to delegate the reverse DNS zone then on nibble boundary: /48, /52, /56, /60 or /64.
Regards,
Janos Mohacsi Network Engineer, Research Associate NIIF/HUNGARNET, HUNGARY Key 00F9AF98: 8645 1312 D249 471B DBAE 21A2 9F52 0D1F 00F9 AF98
--------------------------------------------------------------------- The IPv6 Users Mailing List Unsubscribe by sending "unsubscribe users" to [EMAIL PROTECTED]
