BGP Monitoring Protocol (BMP) support in Bird?

[Emerson Barea]

Hi,

is there BGP Monitoring Protocol support in Bird? I didn't get this
information in Bird docs.

Thank you.

Tocha.

Re: BIRD - Config Support for RFC 3107 - Carrying Label Information in BGP

[Ondrej Zajicek]

On Wed, May 23, 2018 at 07:40:26PM +, Thiruvazhiyan Lakshmanan wrote:
> Hi Ondrej,
> Thanks for the reply! How about incoming labels coming from 3107 neighbor? 
> Can BIRD program the kernel table with mpls label for next-hop loopback?

Yes, incoming routes with labels received from RFC 3107 neighbor can be
programmed to kernel IP table as routes with MPLS label for next-hop
loopback (for outgoing traffic). Unfortunately, BIRD will not insert
corresponding MPLS routes to kernel MPLS table (for incoming labelled
traffic). Although this is probably not a problem for PE router, where
either penultimate hop popping or static decapsulating MPLS routes can
be used.

-- 
Elen sila lumenn' omentielvo

Ondrej 'Santiago' Zajicek (email: santi...@crfreenet.org)
OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net)
"To err is human -- to blame it on a computer is even more so."

RE: BIRD - Config Support for RFC 3107 - Carrying Label Information in BGP

[Thiruvazhiyan Lakshmanan]

Hi Ondrej,
Thanks for the reply! How about incoming labels coming from 3107 neighbor? Can 
BIRD program the kernel table with mpls label for next-hop loopback?

Regards, 
Thiruvazhiyan L


-Original Message-
From: Ondrej Zajicek [mailto:santi...@crfreenet.org] 
Sent: Wednesday, May 23, 2018 3:07 PM
To: LAKSHMANAN, THIRUVAZHIYA; Thiruvazhiyan Lakshmanan
Cc: bird-users@network.cz
Subject: Re: BIRD - Config Support for RFC 3107 - Carrying Label Information in 
BGP

On Wed, May 23, 2018 at 06:02:30PM +, LAKSHMANAN, THIRUVAZHIYA wrote:
> In the BIRD 2.0 user guide, I see the support for RFC 3107 - Carrying
> Label information in BGP. We want to configure a VM with BIRD agent
> working like a PE for adding MPLS labels for IPv4 and IPv6 unicast
> routes. Do we have this configuration supported now, and can I get any
> sample working configuration for this please.

Hi

Unfortunately BIRD support for MPLS is currently limited. Can be used as
a BGP route reflector, or can configure static MPLS routes (with static
labels) and announce them. But no automatic route labeling.

For example, see this config:

https://gitlab.labs.nic.cz/labs/bird/blob/int-new/doc/bird.conf.example2
(although static routes there are VPN routes, it is analogous).

-- 
Elen sila lumenn' omentielvo

Ondrej 'Santiago' Zajicek (email: santi...@crfreenet.org)
OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net)
"To err is human -- to blame it on a computer is even more so."


Disclaimer:  This message and the information contained herein is proprietary 
and confidential and subject to the Tech Mahindra policy statement, you may 
review the policy at http://www.techmahindra.com/Disclaimer.html 
 externally 
http://tim.techmahindra.com/tim/disclaimer.html 
 internally within 
TechMahindra.

RE: [bird-support #899727] RFC 3107 - Carrying Label Information in BGP - Config Support

[Thiruvazhiyan Lakshmanan]

Yes, I emailed to bird-users@network.cz as well, 
I will update you once I get response.

Regards,
Thiruvazhiyan L
NVP – Testing and Certification team
Room - A3 1C-24
Middletown, NJ 07748 USA
Email: tl0041...@techmahindra.com
Office: +1 732 420 8076
Mobile: +1 732 331 3485

From: LINGALA, AVINASH [mailto:ar9...@att.com]
Sent: Wednesday, May 23, 2018 2:18 PM
To: Thiruvazhiyan Lakshmanan
Subject: RE: [bird-support #899727] RFC 3107 - Carrying Label Information in 
BGP - Config Support

I think  you emailed to their support email address.

Trying posting your question here : 
http://bird.network.cz/mailman/listinfo/bird-users>


​
Thanks,
Avinash Lingala
Principal Member Of Technical Staff,
AT Labs
•: 732-420-0809

This communication may contain information that is privileged, or confidential. 
If you are not the intended recipient, please note that any dissemination, 
distribution or copying of this communication is strictly prohibited.  Anyone 
who receives this message in error should notify the sender immediately by 
telephone or by return e-mail and delete it from his or her computer


From: Thiruvazhiyan Lakshmanan 
Sent: Wednesday, May 23, 2018 2:14 PM
To: LINGALA, AVINASH 
Subject: FW: [bird-support #899727] RFC 3107 - Carrying Label Information in 
BGP - Config Support


Hi Avinash,

As per the response from BIRD support, Looks like, this has become paid support 
from 23/03/2018. I still posted in the users forum, let’s see whether anyone 
respond.



[cid:image001.png@01D3F2A1.47B46EE0]



Regards,

Thiruvazhiyan L

NVP – Testing and Certification team

Room - A3 1C-24

Middletown, NJ 07748 USA

Email: tl0041...@techmahindra.com

Office: +1 732 420 8076

Mobile: +1 732 331 3485





-Original Message-
From: Josef Jirasek via RT [mailto:bird-supp...@network.cz]
Sent: Wednesday, May 23, 2018 1:53 PM
To: Thiruvazhiyan Lakshmanan
Subject: [bird-support #899727] RFC 3107 - Carrying Label Information in BGP - 
Config Support



  Dear Sirs,



 this contact address is reserved for members of the paid support program.



  If you are interested in membership that ensures premium customer care at

  guaranteed times, advanced security notifications or priority development

  of your preferred features, let us know in reply to this email. Detailed

  information about the support program and its options 
<​http://bird.network.cz/?support>.



  Otherwise, direct your query to the BIRD user community discussion forum 
<​http://bird.network.cz/mailman/listinfo/bird-users>



  Kind Regards.



Team BIRD, CZ.NIC

--







CZ.NIC, z. s. p. o.

Milesovska 5

130 00

Praha 3

--

Tel.: +420 222 745 111







www.nic.cz

www.mojeID.cz
 - vaše bezpečná webová identita

--

Dne St 23.Květen.2018 19:40:03, 
tl0041...@techmahindra.com napsal(a):

> Dear support-team,

> In the BIRD 2.0 user guide, I see the support for RFC 3107 - Carrying

> Label information in BGP. We want to configure a VM with BIRD agent

> working like a PE for adding MPLS labels for IPv4 and IPv6 unicast

> routes. Do we have this configuration supported now, and can I get

> any sample working configuration for this please.

>

> Regards,

> Thiruvazhiyan L

> Email: 
> tl0041...@techmahindra.com

>

>



>

> Disclaimer: This message and the information contained herein is

> proprietary and confidential and subject to the Tech Mahindra

> policy 

RFC 3107 - Carrying Label Information in BGP - Config Support

[Thiruvazhiyan Lakshmanan]

Dear support-team,
In the BIRD 2.0 user guide, I see the support for RFC 3107 - Carrying Label 
information in BGP. We want to configure a VM with BIRD agent working like a PE 
for adding MPLS labels for IPv4 and IPv6 unicast routes. Do we have this 
configuration supported now, and can I get any sample working configuration for 
this please.

Regards,
Thiruvazhiyan L
Email: tl0041...@techmahindra.com



Disclaimer:  This message and the information contained herein is proprietary 
and confidential and subject to the Tech Mahindra policy statement, you may 
review the policy at http://www.techmahindra.com/Disclaimer.html 
 externally 
http://tim.techmahindra.com/tim/disclaimer.html 
 internally within 
TechMahindra.

Re: Package repositories

[Jonathan Stewart]

Ondrej, thank you for packages!  Sysadmins everywhere appreciate them
greatly (including myself and MBIX).


On Wed, May 23, 2018 at 9:27 AM, Jan Maria Matejka 
wrote:

> I suggest this way:
> 1) rename bird -> bird-legacy and bird-devel -> bird2
> 2) keep this for quite a long time to let users manually change from
> bird-legacy
> to bird2 (one whole release cycle?) and not force them into upgrade
> 3) rename bird2 -> bird
> 4) drop bird-legacy when we stop supporting it
>

This is too complicated, in my view.

Do it like apache.

Leave the bird 1.x package as bird
Add new bird 2.x package as bird2

In future, bird 3.x can bird3

No need to change package names, fewest surprises to sysadmins.

Cheers,
Jonathan

Re: Package repositories

[Toke Høiland-Jørgensen]

Jan Maria Matejka  writes:

> Hello!
>
>> On Wed, May 23, 2018 at 3:05 PM Ondrej Zajicek > > wrote:
>> We plan to have some transition in packages to keep both 1.6 and 2.0 as
>> independent packages in repository without automatic update, similarly to
>> how grub->grub2 transition was done in Debian.
>> 
> On 05/23/2018 03:54 PM, Olivier Cochard-Labbé wrote:
>> 
>> ​Hi,
>> I need to rename the FreeBSD port name too because right now we've got:
>> - net/bird : bird 1.X branch
>> - net/bird-devel: bird 2.X branch
>> 
>> Do you have an idea for the most appropriate port name ?
>> - net/bird1 and net/bird2
>> - Or net/bird-legacy (for 1.X branch) and net/bird (for 2.X branch)
>> - Or other idea ?
>
> I suggest this way:
> 1) rename bird -> bird-legacy and bird-devel -> bird2
> 2) keep this for quite a long time to let users manually change from 
> bird-legacy
> to bird2 (one whole release cycle?) and not force them into upgrade
> 3) rename bird2 -> bird
> 4) drop bird-legacy when we stop supporting it

As a point of reference, we went with bird1/bird2 in openwrt:

https://github.com/openwrt-routing/packages/pull/378

-Toke

Re: Package repositories

[Jan Maria Matejka]

Hello!

> On Wed, May 23, 2018 at 3:05 PM Ondrej Zajicek  > wrote:
> We plan to have some transition in packages to keep both 1.6 and 2.0 as
> independent packages in repository without automatic update, similarly to
> how grub->grub2 transition was done in Debian.
> 
On 05/23/2018 03:54 PM, Olivier Cochard-Labbé wrote:
> 
> ​Hi,
> I need to rename the FreeBSD port name too because right now we've got:
> - net/bird : bird 1.X branch
> - net/bird-devel: bird 2.X branch
> 
> Do you have an idea for the most appropriate port name ?
> - net/bird1 and net/bird2
> - Or net/bird-legacy (for 1.X branch) and net/bird (for 2.X branch)
> - Or other idea ?

I suggest this way:
1) rename bird -> bird-legacy and bird-devel -> bird2
2) keep this for quite a long time to let users manually change from bird-legacy
to bird2 (one whole release cycle?) and not force them into upgrade
3) rename bird2 -> bird
4) drop bird-legacy when we stop supporting it

Maria

Re: Package repositories

[Olivier Cochard-Labbé]

On Wed, May 23, 2018 at 3:05 PM Ondrej Zajicek 
wrote:

>
> Hi
>
> We added Debian packages for 1.6.4 to our repository. Sorry for the
> delay. We are updating our infrastructure to have automatic package
> builds in the future. Packages for BIRD 2.0 will likely be released
> with the next release.
>
> We plan to have some transition in packages to keep both 1.6 and 2.0 as
> independent packages in repository without automatic update, similarly to
> how grub->grub2 transition was done in Debian.
>
>
​Hi,
I need to rename the FreeBSD port name too because right now we've got:
- net/bird : bird 1.X branch
- net/bird-devel: bird 2.X branch

Do you have an idea for the most appropriate port name ?
- net/bird1 and net/bird2
- Or net/bird-legacy (for 1.X branch) and net/bird (for 2.X branch)
- Or other idea ?

Thanks

Re: Package repositories

[Ondrej Zajicek]

On Mon, May 14, 2018 at 09:12:30AM +0200, Jan-Philipp Litza wrote:
> Hi list,
> 
> the prebuilt packages under [1] seem to be a bit outdated. While Fedora
> and CentOS at least have 1.6.4 available, Debian only has 1.6.3, and
> there is not a single package for 2.0.

Hi

We added Debian packages for 1.6.4 to our repository. Sorry for the
delay. We are updating our infrastructure to have automatic package
builds in the future. Packages for BIRD 2.0 will likely be released
with the next release.

We plan to have some transition in packages to keep both 1.6 and 2.0 as
independent packages in repository without automatic update, similarly to
how grub->grub2 transition was done in Debian.

-- 
Elen sila lumenn' omentielvo

Ondrej 'Santiago' Zajicek (email: santi...@crfreenet.org)
OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net)
"To err is human -- to blame it on a computer is even more so."