Compiling from source with --enable-ipv6
I'm trying to build BIRD from sources. If I build without any options, then I end up with a binary called "bird" and its associated control programs, "bird" and "birdcl". This build is only capable of IPv4. So far I understand it. If I configure with the option --enable-ipv6, and build it, I end up with the binary "bird6", and the control programs, "birdc6" and "birdcl6". My question is: is bird6 only able to handle IPv6, or will it also handle IPv4? If it will only handle IPv6, then I would need both bird and bird6. Is there any way to get the build process to build both bird and bird6 without having to "make clean" and reconfigure? Is there any reason why a single bird binary won't just handle both IPv4 and IPv6? The documentation isn't clear about any of this, and could do with some improvement. Regards, Anand
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 8.3.2015 19:49, Anand Buddhdev wrote: Hi Anand! Yes, you are right. Bird is just for IPv4 and bird6 is just for IPv6. We are currently working on integrated version of bird as this is necessary for IS-IS implementation. But this is planned for version 2.0. (And we hope to release it quite soon as majority of the work is done.) Ondrej
I'm trying to build BIRD from sources. If I build without any options, then I end up with a binary called "bird" and its associated control programs, "bird" and "birdcl". This build is only capable of IPv4. So far I understand it.
If I configure with the option --enable-ipv6, and build it, I end up with the binary "bird6", and the control programs, "birdc6" and "birdcl6".
My question is: is bird6 only able to handle IPv6, or will it also handle IPv4?
If it will only handle IPv6, then I would need both bird and bird6. Is there any way to get the build process to build both bird and bird6 without having to "make clean" and reconfigure?
Is there any reason why a single bird binary won't just handle both IPv4 and IPv6?
The documentation isn't clear about any of this, and could do with some improvement.
Regards,
Anand
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBAgAGBQJU/J/0AAoJED82D4RIDoWPnEkP/R+cqiugiFCQ9XqZetq9kxC8 y2NlJ4AD436xm1KuzGGd4e9KecLIaSXUJzwRdNa9Fh09Fnt5nYdvx/UHaZRUlHw+ V+9BPuhiaqJWZGE97rSQP5qLtiFlEXqj0lH6oTnynHwNzz0xadeSHiFjZml9OFwE 1AJLn7PJRlokUW6jAGmX/VtlMW0HwjgiOdbGUk01XJV4VlFK7oiXN9EXjLWLkkdo lP+Fjt96+/WpNejdf1a8jZTvBv3ybs51ffRXiBUrRJf9gyG4hXmlkbChOhaCgykI 1nHx+XwH8D5/fpYlnRcglAHXBL7Zn8PA8lfWYd4AR+XLSuWjZwNJN4ZTLjv3anTK atlDHiDXWrt5H2+qR5MdDx9Z9zFw3+1DbyuDnaGNbBKEnp3GyxIfoKTeh7L/wnbt scwpdbHItLLCFAUF2ERoI3wvKq/TnGumPuC69nKGxsfaESSkz++YbQLGk7oYfMR4 8ULwY5qe6RyeyP7zVyPfJ5iR0Gw/nQSltSuCOpwlzB9xn39R9SGYY8w+g5P9YnBC wN/BcYa7cvkYaITdeiKw6sOelNMGyZKDlW8adBpVo1dCx3zbswEP6ea4XP9XySTA qIssD00seQOXkCZvouZuKMzNPValAi4jrMNARGElCy2cwfTwYz9PO2aOZUy+mvee TXGMAmbiBB53tpiufBTG =Q63N -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 03/08/2015 02:49 PM, Anand Buddhdev wrote: [snip]
The documentation isn't clear about any of this, and could do with some improvement.
You're going to need both binaries and to configure both bird.conf and bird6.conf. There are both positives and negatives to this design implementation, but the ability to separately configure and control the two protocols has a lot of upside. https://gitlab.labs.nic.cz/labs/bird/wikis/FAQ#how-bird-handles-ipv6 - - jkt - -- Jay Turner, Director, CloudRouter DevOps, IIX Inc. ✉ jturner@iix.net ☎: +1-919-633-0619 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAlT8oMoACgkQA/BpaFGKSrywGgCfdSeF5b7R5Ds0AW9udug+SoHW 93QAnRzwAipdJqA2t4meKZW2BNRddvjW =LXmN -----END PGP SIGNATURE-----
participants (3)
-
Anand Buddhdev -
Jay Turner -
Ondrej Filip