Recently Joel Bion sent us a hint that addresses setting static
ipv6 addresses in LFS.
http://www.linuxfromscratch.org/hints/downloads/files/IPv6-in-LFS.txt
I've been looking at this trying to decide if/how to incorporate this
into LFS.
When I look at ipv6, my first question is why? In the case of the user
that gets an ipv4 address from his ISP, the use of private addresses
10.x, 172.16-31.x, 192.168.x makes ipv6 unneeded. Only in the case that
the ISP does not have any ipv4 addresses available is it really needed.
I don't know how common that is.
I do know that ipv4 and ipv6 can be run at the same time, but I can't
think of a valid reason unless there are two connections to the internet
with different routes. In this case the ipv6 route would be to an ISP
that does not have any ipv4 addresses available. I would think this
would be extremely rare and not just for LFS users.
The most common reason for ipv6 would be for those that do not have ipv4
available at all. I have not heard of that from any LFS user, but I
don't hear from everyone.
I have tried to do some ipv6 testing and I can get ping6 to work between
systems and my router. The problem is that I can't seem to get my
router to actually route ipv6 packets to the internet, so my testing is
really insufficient. This seems to be a router/ISP problem that is
beyond the scope of LFS/BLFS.
If another editor who can do ipv6 testing can validate ipv6
instructions, I'm not opposed to adding those, but it may just be better
to reference the ipv6 hint in Section 7.5. General Network Configuration.
I'll also note that the hint only addresses the System V book. systemd
is another matter. Also opening up ipv6 in LFS would probably mean that
we would need to address it in several BLFS packages (ntp, nfs, Network
Manager, dhco, wireless tools, etc).
-- Bruce
--
http://lists.linuxfromscratch.org/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
