I was just playing around with my LFS Box (which is going to operate as
a Router/Firewall/A few network services (NTP, SquidProxy, et C) and
wanted to add IPv6 support to it, I got the tunnel to HE electric up and
running, and everything but was looking to add the IPv6 address to the
internal Network Interfaces, this is where I ran into a snag, and
haven't found any information about how others have over come the issue.
To get IPv6 on the internal interfaces I think I've found 3 different
ways to support it, but none of the 3 really look appealing and was
wondering if someone else has done it, and how they did it.
1. Manually use ip add commands every time I boot
Disadvantage - No Automatic at Boot Time
2. Create a Script and tie it into the init.d directories
Advantage - Automatic at Boot Time
Disadvantage - Kinda of messy as the Network
Interfaces are configured by two different mechanisms
3. Add it to the ifconfig.eth0, etc files (I may be wrong with my
understanding of the work here so if I am please correct me)
Advantage - Cleanest Approach, as all boot
network configuration is handled by the same mechanism
Disadvantage (for Single Stack - IPv6 Only) -
Think I would have to add a /lib/services/ipv6-static file which doesn't
look like it would
be all that hard, just copy the
ipv4-static file and make a few small changes to reflect the
ip commands being used for inet6
instead of inet4
Disadvantage (for Dual Stack - IPv6 and IPv4) -
This would take a fair amount of work I believe. I would still have to
create the /lib/services file mentioned in the IPv6 only
Solution, but then from what I can tell the ifup would have to
also be modified to run through the config part twice (or 1,000 times)
to configure more than 1 protocol on an adapter.
Thank You,
Casey
--
http://linuxfromscratch.org/mailman/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
