Re: [lfs-dev] Got static IPv6 working reliably on LFS-running server
On 12/8/19 3:35 PM, jpb...@westvi.com wrote: Hint created and sent to hints list OK, I got it. It may take a week or two before I can check it out, but I will post it to the hints repo sooner than that. -- Bruce -- http://lists.linuxfromscratch.org/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
Re: [lfs-dev] Got static IPv6 working reliably on LFS-running server
On 12/7/2019 9:51 PM, Bruce Dubbs via lfs-dev wrote: On 12/7/19 9:11 PM, Joel Bion via lfs-dev wrote: Hi - This concerns adding static IPv6 support to Linux From Scratch. I worked on this a bit a few years ago, but life got in the way, and I paused all work on this, but over the Thanksgiving break, I finished things up and and have things working. My LFS machine is now working fine being a 'partially' statically-configured device. "Partially" means the machine is still learning its MTU, Default Gateway, etc. via the IPv6 router it is attached to using IPv6-RA. The caveats and limitations are as follows: 1) Technically, it would be possible to make a machine that ONLY speaks IPv6, but that doesn't interest me, so I didn't modify the scripts to support that possibility. 2) I didn't add (let alone test) the ability to learn your IPv6 address dynamically via IPv6 RA. I assume 'static' addressing is wanted. 3) If someone has done their package and application configuration work properly, (such as not using hard-coded addresses in configurations), then there should be very little configuration changes that would need to be made to make the vast majority of their programs and packages work with IPv6. I am not including any documentation on how to do this; that would be beyond LFS, and extend into BLFS. 4) It's simple: a statically configured address that works with the ifconfig.eth0 file, and with ifup and ifdown. It doesn't do anything fancy - but it DOES allow for the configuration of the address and "prefix" length, with auto-learning of other parameters, such as default gateway. 5) I don't believe in teaching people what IPv6 is. If they are going to use it, there's plenty available on the web to teach them. I've modified a number of files to make this work: /etc/resolv.conf - Shows example of using a Google IPv6 DNS resolver. /etc/sysconfig/ifconfig.eth0 - Shows example of configuring both IPv4 & IPv6 /sbin/ifup & /sbin/ifdown - Obvious changes /lib/services/ipv46-static - An extended form of ipv4-static, which adds in support for IPv6 /etc/hosts - Added in IPv6 addresses Here is a brief description of how, with these changed files, things work: Preparing: 1) created /lib/services/ipv46-static 2) edited /sbin/ifup to handle v6 gateway 3) edited /sbin/ifdown to fix a minor bug Enabling IPv6: 1) edit /etc/sysctl.conf to enable ipv6, and also make it so an address isn't learned with router discovery, making the one statically configured be the only one learned: net.ipv6.conf.eth0.disable_ipv6=0 net.ipv6.conf.eth0.autoconf=0 2) edit /etc/sysconfig/ifconfig.eth0 to use ipv46-static as the file. 3) remove "#" prefix from IP6 and PREFIX6 lines in /etc/sysconfig/ifconfig.eth0 and set them appropriately. 4) For compatibility with some software (I've forgotten which!), also specify NETWORKING_IPV6=yes in /etc/sysconfig/network. 5) Reboot. If upon reboot, you don't get proper IPv6 connectivity, you may need to uncomment and set the GATEWAY6 value. If you do that, reboot again. 6) Optional: Put IPv6 DNS server addresses in /etc/resolv.conf Disabling IPv6: 1) edit /etc/sysctl.conf to disable ipv6 (turn on disabling, really). For good measure, I also restore 'autoconf' to its default. net.ipv6.conf.eth0.disable_ipv6=1 net.ipv6.conf.eth0.autoconf=1 2) edit /etc/sysconfig/ifconfig.eth0 to use ipv4-static 3) add "#" prefix to the start of the IP6 and PREFIX6 lines in /etc/sysconfig/ifconfig.eth0 4) For compatibility with some software (I've forgotten which!), also specify NETWORKING_IPV6=no in /etc/sysconfig/network. 5) If they exist, disable IPv6 DNS server addresses in /etc/resolv.conf 6) Remove any other IPv6-specific configuration you have for various packages and applications (these should be VERY few in number!) 7) Reboot. Monitoring IPv6: 1) Regular 'ipaddr' commands do not work. Use 'ip'. Examples: ip address: returns list of interface addresses ip route: returns IPv4 routing table ip -6 route: returns IPv6 routing table 2) Sometimes firewalls from our ISP can be set with IPv6 filtering. Since I use shorewall6, I disable the ISP firewall altogether. MY BIG QUESTION IS: What is the easiest way to add this back into LFS? Provide the changes and required edits to the pages to reference this? Pull down a copy via SVN and make changes? There are a few places that need editing to tell people about IPv6. I do believe, it DOES make sense to have the 'stock' LFS show how IPv6 can be enabled in an LFS system, and further, that this ability be added as part of the 'core' setup (in LFS instead of BLFS, etc.) This sounds interesting. The best way to start is to write a hint that describes the process in detail. From that, we can determine the best way to roll it into LFS. It doesn't have to be a formal hint http://www.linuxfromscratch.org/hints/howtowrite.html but you can
Re: [lfs-dev] Got static IPv6 working reliably on LFS-running server
Hint created and sent to hints list On 2019-12-07 19:51, Bruce Dubbs via lfs-dev wrote: On 12/7/19 9:11 PM, Joel Bion via lfs-dev wrote: Hi - This concerns adding static IPv6 support to Linux From Scratch. I worked on this a bit a few years ago, but life got in the way, and I paused all work on this, but over the Thanksgiving break, I finished things up and and have things working. My LFS machine is now working fine being a 'partially' statically-configured device. "Partially" means the machine is still learning its MTU, Default Gateway, etc. via the IPv6 router it is attached to using IPv6-RA. The caveats and limitations are as follows: 1) Technically, it would be possible to make a machine that ONLY speaks IPv6, but that doesn't interest me, so I didn't modify the scripts to support that possibility. 2) I didn't add (let alone test) the ability to learn your IPv6 address dynamically via IPv6 RA. I assume 'static' addressing is wanted. 3) If someone has done their package and application configuration work properly, (such as not using hard-coded addresses in configurations), then there should be very little configuration changes that would need to be made to make the vast majority of their programs and packages work with IPv6. I am not including any documentation on how to do this; that would be beyond LFS, and extend into BLFS. 4) It's simple: a statically configured address that works with the ifconfig.eth0 file, and with ifup and ifdown. It doesn't do anything fancy - but it DOES allow for the configuration of the address and "prefix" length, with auto-learning of other parameters, such as default gateway. 5) I don't believe in teaching people what IPv6 is. If they are going to use it, there's plenty available on the web to teach them. I've modified a number of files to make this work: /etc/resolv.conf - Shows example of using a Google IPv6 DNS resolver. /etc/sysconfig/ifconfig.eth0 - Shows example of configuring both IPv4 & IPv6 /sbin/ifup & /sbin/ifdown - Obvious changes /lib/services/ipv46-static - An extended form of ipv4-static, which adds in support for IPv6 /etc/hosts - Added in IPv6 addresses Here is a brief description of how, with these changed files, things work: Preparing: 1) created /lib/services/ipv46-static 2) edited /sbin/ifup to handle v6 gateway 3) edited /sbin/ifdown to fix a minor bug Enabling IPv6: 1) edit /etc/sysctl.conf to enable ipv6, and also make it so an address isn't learned with router discovery, making the one statically configured be the only one learned: net.ipv6.conf.eth0.disable_ipv6=0 net.ipv6.conf.eth0.autoconf=0 2) edit /etc/sysconfig/ifconfig.eth0 to use ipv46-static as the file. 3) remove "#" prefix from IP6 and PREFIX6 lines in /etc/sysconfig/ifconfig.eth0 and set them appropriately. 4) For compatibility with some software (I've forgotten which!), also specify NETWORKING_IPV6=yes in /etc/sysconfig/network. 5) Reboot. If upon reboot, you don't get proper IPv6 connectivity, you may need to uncomment and set the GATEWAY6 value. If you do that, reboot again. 6) Optional: Put IPv6 DNS server addresses in /etc/resolv.conf Disabling IPv6: 1) edit /etc/sysctl.conf to disable ipv6 (turn on disabling, really). For good measure, I also restore 'autoconf' to its default. net.ipv6.conf.eth0.disable_ipv6=1 net.ipv6.conf.eth0.autoconf=1 2) edit /etc/sysconfig/ifconfig.eth0 to use ipv4-static 3) add "#" prefix to the start of the IP6 and PREFIX6 lines in /etc/sysconfig/ifconfig.eth0 4) For compatibility with some software (I've forgotten which!), also specify NETWORKING_IPV6=no in /etc/sysconfig/network. 5) If they exist, disable IPv6 DNS server addresses in /etc/resolv.conf 6) Remove any other IPv6-specific configuration you have for various packages and applications (these should be VERY few in number!) 7) Reboot. Monitoring IPv6: 1) Regular 'ipaddr' commands do not work. Use 'ip'. Examples: ip address: returns list of interface addresses ip route: returns IPv4 routing table ip -6 route: returns IPv6 routing table 2) Sometimes firewalls from our ISP can be set with IPv6 filtering. Since I use shorewall6, I disable the ISP firewall altogether. MY BIG QUESTION IS: What is the easiest way to add this back into LFS? Provide the changes and required edits to the pages to reference this? Pull down a copy via SVN and make changes? There are a few places that need editing to tell people about IPv6. I do believe, it DOES make sense to have the 'stock' LFS show how IPv6 can be enabled in an LFS system, and further, that this ability be added as part of the 'core' setup (in LFS instead of BLFS, etc.) This sounds interesting. The best way to start is to write a hint that describes the process in detail. From that, we can determine the best way to roll it into LFS. It doesn't have to be a formal hint
Re: [lfs-dev] Got static IPv6 working reliably on LFS-running server
On 12/7/19 9:11 PM, Joel Bion via lfs-dev wrote: Hi - This concerns adding static IPv6 support to Linux From Scratch. I worked on this a bit a few years ago, but life got in the way, and I paused all work on this, but over the Thanksgiving break, I finished things up and and have things working. My LFS machine is now working fine being a 'partially' statically-configured device. "Partially" means the machine is still learning its MTU, Default Gateway, etc. via the IPv6 router it is attached to using IPv6-RA. The caveats and limitations are as follows: 1) Technically, it would be possible to make a machine that ONLY speaks IPv6, but that doesn't interest me, so I didn't modify the scripts to support that possibility. 2) I didn't add (let alone test) the ability to learn your IPv6 address dynamically via IPv6 RA. I assume 'static' addressing is wanted. 3) If someone has done their package and application configuration work properly, (such as not using hard-coded addresses in configurations), then there should be very little configuration changes that would need to be made to make the vast majority of their programs and packages work with IPv6. I am not including any documentation on how to do this; that would be beyond LFS, and extend into BLFS. 4) It's simple: a statically configured address that works with the ifconfig.eth0 file, and with ifup and ifdown. It doesn't do anything fancy - but it DOES allow for the configuration of the address and "prefix" length, with auto-learning of other parameters, such as default gateway. 5) I don't believe in teaching people what IPv6 is. If they are going to use it, there's plenty available on the web to teach them. I've modified a number of files to make this work: /etc/resolv.conf - Shows example of using a Google IPv6 DNS resolver. /etc/sysconfig/ifconfig.eth0 - Shows example of configuring both IPv4 & IPv6 /sbin/ifup & /sbin/ifdown - Obvious changes /lib/services/ipv46-static - An extended form of ipv4-static, which adds in support for IPv6 /etc/hosts - Added in IPv6 addresses Here is a brief description of how, with these changed files, things work: Preparing: 1) created /lib/services/ipv46-static 2) edited /sbin/ifup to handle v6 gateway 3) edited /sbin/ifdown to fix a minor bug Enabling IPv6: 1) edit /etc/sysctl.conf to enable ipv6, and also make it so an address isn't learned with router discovery, making the one statically configured be the only one learned: net.ipv6.conf.eth0.disable_ipv6=0 net.ipv6.conf.eth0.autoconf=0 2) edit /etc/sysconfig/ifconfig.eth0 to use ipv46-static as the file. 3) remove "#" prefix from IP6 and PREFIX6 lines in /etc/sysconfig/ifconfig.eth0 and set them appropriately. 4) For compatibility with some software (I've forgotten which!), also specify NETWORKING_IPV6=yes in /etc/sysconfig/network. 5) Reboot. If upon reboot, you don't get proper IPv6 connectivity, you may need to uncomment and set the GATEWAY6 value. If you do that, reboot again. 6) Optional: Put IPv6 DNS server addresses in /etc/resolv.conf Disabling IPv6: 1) edit /etc/sysctl.conf to disable ipv6 (turn on disabling, really). For good measure, I also restore 'autoconf' to its default. net.ipv6.conf.eth0.disable_ipv6=1 net.ipv6.conf.eth0.autoconf=1 2) edit /etc/sysconfig/ifconfig.eth0 to use ipv4-static 3) add "#" prefix to the start of the IP6 and PREFIX6 lines in /etc/sysconfig/ifconfig.eth0 4) For compatibility with some software (I've forgotten which!), also specify NETWORKING_IPV6=no in /etc/sysconfig/network. 5) If they exist, disable IPv6 DNS server addresses in /etc/resolv.conf 6) Remove any other IPv6-specific configuration you have for various packages and applications (these should be VERY few in number!) 7) Reboot. Monitoring IPv6: 1) Regular 'ipaddr' commands do not work. Use 'ip'. Examples: ip address: returns list of interface addresses ip route: returns IPv4 routing table ip -6 route: returns IPv6 routing table 2) Sometimes firewalls from our ISP can be set with IPv6 filtering. Since I use shorewall6, I disable the ISP firewall altogether. MY BIG QUESTION IS: What is the easiest way to add this back into LFS? Provide the changes and required edits to the pages to reference this? Pull down a copy via SVN and make changes? There are a few places that need editing to tell people about IPv6. I do believe, it DOES make sense to have the 'stock' LFS show how IPv6 can be enabled in an LFS system, and further, that this ability be added as part of the 'core' setup (in LFS instead of BLFS, etc.) This sounds interesting. The best way to start is to write a hint that describes the process in detail. From that, we can determine the best way to roll it into LFS. It doesn't have to be a formal hint http://www.linuxfromscratch.org/hints/howtowrite.html but you can do that if you want. The minimum I need is to have enough
