There is no way to setup two channels in one protocol definition? Or how
can I do it?
inż. Miłosz Oller
W dniu 17.12.2017 o 21:55, Ondrej Zajicek pisze:
On Sun, Dec 17, 2017 at 01:41:44PM +0100, Miłosz Oller wrote:
Hi
How I must define bgp protocol as case 1?
There can be only one source/
Hello!
On 12/16/2017 04:10 PM, Luis Ressel wrote:
> I've been experimenting with bird 2.0.0 for a few days now. Apart from
> the memory leak (which Ondrej's patch appears to fix), the most serious
> issue I've run into is a spurious bird crash caused by the filter code.
> Twice so far, bird died w
On Sun, Dec 17, 2017 at 01:41:44PM +0100, Miłosz Oller wrote:
> Hi
>
> How I must define bgp protocol as case 1?
>
> There can be only one source/neighbor ip.
In case 1 there is only one BGP session / TCP connection and therefore one
source/neighbor address.
> W dniu 17.12.2017 o 03:26, Ondrej
On Sun, Dec 17, 2017 at 08:00:16PM +0100, Tim Weippert wrote:
> Hi List,
>
> i tried Bird 2.0.0, Kernel 4.14.6, Archlinux, VRF separated BGP Peerings.
>
> I get an Config running, where i had an BGP Peering in Global Space and
> one in a VRF. As the VRF Config seems "complex" i though maybe i do
Hi List,
i tried Bird 2.0.0, Kernel 4.14.6, Archlinux, VRF separated BGP Peerings.
I get an Config running, where i had an BGP Peering in Global Space and
one in a VRF. As the VRF Config seems "complex" i though maybe i do
something wrong or even more complex as really needed.
I had the followi
On Sun, 17 Dec 2017 13:43:03 +0100
Clemens Schrimpe wrote:
> > You can use ‘net.type = NET_IP4', 'net.type = NET_IP6'.
>
> Nice …
>
> And you can also „just“ mix IPv6 and legacy IPv4 matches in
> prefix-lists, etc.:
Thanks to both of you! The mixed sets are a nice trick which will take
care
Hi
How I must define bgp protocol as case 1?
There can be only one source/neighbor ip.
inż. Miłosz Oller
W dniu 17.12.2017 o 03:26, Ondrej Zajicek pisze:
On Sat, Dec 16, 2017 at 04:25:50PM +0100, Miłosz Oller wrote:
Hi
I fix it. Please tell me how I must define ipv6 session. There must be
> You can use ‘net.type = NET_IP4', 'net.type = NET_IP6'.
Nice …
And you can also „just“ mix IPv6 and legacy IPv4 matches in prefix-lists, etc.:
if net ~ [
2001:db8::/32+, # doc
fc00::/15+, # ULAs
fe80::
On 17.12.2017 00:43, Baptiste Jonglez wrote:
> Hi,
Hi!
Thank you, it is fixed now.
Ondrej
>
> Congratulations for the 2.0 release :)
>
> It is nice to have kept the 1.6 documentation online. However, the table
> of contents of the 1.6 doc actually points inside the 2.0 doc.
>
