On 09/05/2011 12:12 PM, Bruce Dubbs wrote: > Does IPv6 run in conjunction with IPv4. I think it does. I don't > really understand all the issues with implementing IPv4. > > I think that we should hold off for now (after LFS-7.0) until we get a > good handle on how it will be used. AFAIK, most internal networks will > still use IPv4/NAT, but the single DHCP from the ISP or static IPs may > well be IPv6. > Nah, it'll probably be dual stack for a few years at least.
As Zachary mentioned above, the local assigned address will be a non-issue, much as it is today for IPv4 dynamic addresses. We only need to concern ourselves with the loopback entry (::1). OT: IPv6 is much different in the way that auto-configuration/default route takes place. Your ISP will likely assign you a /48 or /64, and the router will advertise a /64 on the inside inerface(s) if the internal interface is assigned values. Everything else happens automatically with no additional tools with the exception of DNS. The last 64 bits are based on the MAC address. For instance, I'm currently using a 6to4 tunnel with tunnelbroker.net (my ISP was too slow to take up testing and I got impatient). My assigned address is 2001:470:c5bf::/48 on the tunnel adapter. IPs are automatically assigned to my other 4 interfaces on the router (my other 4 internal networks) based on my selection of a /64 (for which I assigned :1 to my internal network for a /64. My (obfuscated) MAC address on eth0 is 00:xx:8c:44:xx:xx, and my IP address (assembled from the network and MAC addresses) is 2001:470:c5bf:1:2xx:8cff:fe44:xxxx/64. Anyone feel free to poke around a bit at the subnet if you are capable BTW. I could use a sanity check on my routing rules (ICMPv6 is allowed to forward on 1 and 2). Routing rules are no different than in IPv4. The only current use of DHCPv6 is to assign DNS servers, and maybe for control freaks who want sequential addresses internally for some reason. The only problem I had implementing IPv6 was that I couldn't be lazy and rely on DST-NAT and MASQ. I had to assemble actual routing rules for my internal networks (there are about 35 in the IPv6 chain to cover my needlessly complex network vs about 15 when using nat and masq for the IPv4 segments to provide services to both the outside and internal networks). When it was all said and done, I feel like I learned a bit (on a new platform - MikroTik RouterOS), and had to re-learn an awful lot as well, but IMO, sink or swim is the best possible learning method. :-) -- DJ Lucas -- This message has been scanned for viruses and dangerous content, and is believed to be clean. -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
