On 11/08/2018 09:39 AM, Grant Taylor wrote:
Does Bird 1.x support both IPv4 and IPv6 prefixes being advertised over
the same BGP neighbor session, which happens to be IPv4 connected?
Thank you Ondrej and Toke.
That is an exact answer to my question.
I will look into a different solution, be i
Grant Taylor writes:
> Does Bird 1.x support both IPv4 and IPv6 prefixes being advertised over
> the same BGP neighbor session, which happens to be IPv4 connected?
>
> I've not done any research about this specific question yet and I'm just
> hoping for a "yes it does" or "no it does not" answe
On 08. 11. 18 17:39, Grant Taylor wrote:
Hi!
> Does Bird 1.x support both IPv4 and IPv6 prefixes being advertised
> over the same BGP neighbor session, which happens to be IPv4 connected?
No, this was implemented in 2.0.
Ondrej
>
> I've not done any research about this specific questi
Does Bird 1.x support both IPv4 and IPv6 prefixes being advertised over
the same BGP neighbor session, which happens to be IPv4 connected?
I've not done any research about this specific question yet and I'm just
hoping for a "yes it does" or "no it does not" answer.
Thank you in advance.
Now
It looks like your patch should be able to resolve the issue as well, and is
more succinct.
When we have the environment again to test this, we will verify if your
proposed patch works as expected in our use case.
Thanks again for looking into this.
Asbjorn
On 06.11.18, 18:19, "Ondrej Zajic
Thanks for looking at the patch, Ondrej.
1. Discussing it with an SME here, this seems a fair description of what is
happening.
2. I think that part of the comment might be inaccurate now, since as you say,
the NULL case is already covered above it.
3. They could be removed. During the debuggi