- Bird-users - Mailing Lists

MTU mismatch with nbr
by Derek Andrew 24 Sep '17

24 Sep '17

We are running BIRD and BIRD6 to manage our BFD and OSPF relationship on our DNS servers. We moved the DNS servers onto a Fortigate firewall. I was able to get the BIRD daemon running, but BIRD6 is complaining about an MTU mismatch with the neighbour. Is there any way to tell BIRD to ignore the MTU? The OSPF status is showing the neighbour is in the Exchange state. Thanks. d -- Copyright 2017 Derek Andrew (excluding quotations) +1 306 966 4808 Communication and Network Services Information and Communications Technology Infrastructure Services *University of Saskatchewan*Peterson 120; 54 Innovation Boulevard Saskatoon,Saskatchewan,Canada. S7N 2V3 Timezone GMT-6 Typed but not read.

2 1

Static routing
by Александра Урошевска 24 Sep '17

24 Sep '17

Hi all bird users, I have started with fresh configuration of BIRD. And I want to use a default routing table with static routing. Is there any template for configuration of protocol static, protocol kernel, protocol direct? Thank you very much. Kind regards, Aleksandra

2 1

Agregator protocol
by Luk 21 Sep '17

21 Sep '17

Hi, I'm trying to use aggregator protocol (patch from Alexander Chernikov). Can someone explain if I can use this patch to aggregate routes to upstream providers ? My goal is to not use "route x.x.x.x/xy reject;" syntax to announce routes to the internet, but rather use aggregation, which will be used only if there will be one or more more-specific-route within particular prefix from iBGP session. -- Regards, Luk

1 0

TCP md5 authentication failures for almost on all the server's BGP peering
by Harish Shetty 21 Sep '17

21 Sep '17

Hi All I am using bird-1.4.5-1.el6, we are getting alerted for TCP md5 authentication failures for almost on all the server's BGP peering with switches. Error we are seeing as mentioned below. Jul 17 17:15:29 lca1-s1-csw02.nw.linkedin.com 2017 Jul 17 17:15:29 UTC: %NETSTACK-3-TCP_MD5_AUTH_FAILURE: netstack [3617] MD5_DIGEST_INVALID:Dropping packets from src:x.x.x.x.34987,dst:y.y.y.yy.179 Jul 17 07:24:28 lca1-e1-csw01-lo0.nw.linkedin.com 2017 Jul 17 07:24:28 UTC: %NETSTACK-3-TCP_MD5_AUTH_FAILURE: netstack [3640] MD5_DIGEST_INVALID:Dropping packets from src:yyyy.yyyy.yyyy.35088,dst:xxxx.xxxx.xxx.179 lca1-s1-csw01.nw.linkedin.com 2017 Jul 17 05:01:25 UTC: %NETSTACK-3-TCP_MD5_AUTH_FAILURE: netstack [3617] MD5_DIGEST_INVALID:Dropping packets from src:x.x.x.xx.55220,dst:1y.y.y.yy.179 we have raised a Case with Cisco and they are saying possible cause would be " If received packet has got modified in transit, so hash computed at origin is not matching at the destination". Does anyone have seen this type of error before? Is bird causing something to corrupt the packet? Any solution / way to check and confirm everything fine at bird is appreciated. Regards Harish Shetty

3 2

Set interfaces in BIRD
by Александра Урошевска 21 Sep '17

21 Sep '17

Hello everybody, I am a student from Macedonia at FINKI <https://www.finki.ukim.mk/en>. I am 24 years old. I just installed BIRD on a VM and I want to know how to set up interfaces and protocols. I am very new at this, want to try how it works. Can anybody help me? Thank you very much. Best regards, Aleksandra

2 1

Ignoring bogus route 240.0.0.0/4
by Alexander Demenshin 20 Sep '17

20 Sep '17

Hi, Any reason why 240.0.0.0/4+ routes are ignored by bird (1.6.3)? I have tried to blackhole this range in static protocol, but got this message. Attempts to manually add any kernel route from this range were silently ignored. -- With best regards, Alexander.

4 6

[RFC,PATCH 1/2] BGP: Implement iebgp_peer mode.
by Lennert Buytenhek 20 Sep '17

20 Sep '17

Implement an 'internal eBGP' peer mode, where the remote peer uses a different AS number than we do, as if it were an eBGP peer, but we treat the peer as if were an AS-internal peer. This enables implementing a network setup according to the model documented in RFC7938. This makes two changes to the BGP route propagation logic: * When we are propagating a route to or from an internal eBGP peer, we will avoid resetting the MED attribute. * When comparing BGP-learned routes, we will consider routes learned from an 'internal eBGP' peer as iBGP routes as far as the RFC 4271 9.1.2.2. d) check (Prefer external peers) is concerned. --- proto/bgp/attrs.c | 22 ++++++++++++++++------ proto/bgp/bgp.h | 1 + proto/bgp/config.Y | 4 +++- 3 files changed, 20 insertions(+), 7 deletions(-) diff --git a/proto/bgp/attrs.c b/proto/bgp/attrs.c index b9e2490d..478c805c 100644 --- a/proto/bgp/attrs.c +++ b/proto/bgp/attrs.c @@ -1100,15 +1100,21 @@ bgp_update_attrs(struct bgp_proto *p, rte *e, ea_list **attrs, struct linpool *p if (!p->is_internal && !p->rs_client) { + struct bgp_proto *new_bgp = (e->attrs->src->proto->proto == &proto_bgp) ? + (struct bgp_proto *) e->attrs->src->proto : NULL; + bgp_path_prepend(e, attrs, pool, p->local_as); /* The MULTI_EXIT_DISC attribute received from a neighboring AS MUST NOT be * propagated to other neighboring ASes. * Perhaps it would be better to undefine it. */ - a = ea_find(e->attrs->eattrs, EA_CODE(EAP_BGP, BA_MULTI_EXIT_DISC)); - if (a) - bgp_attach_attr(attrs, pool, BA_MULTI_EXIT_DISC, 0); + if (!p->cf->iebgp_peer && (new_bgp == NULL || !new_bgp->cf->iebgp_peer)) + { + a = ea_find(e->attrs->eattrs, EA_CODE(EAP_BGP, BA_MULTI_EXIT_DISC)); + if (a) + bgp_attach_attr(attrs, pool, BA_MULTI_EXIT_DISC, 0); + } } /* iBGP -> keep next_hop, eBGP multi-hop -> use source_addr, @@ -1317,9 +1323,11 @@ bgp_rte_better(rte *new, rte *old) } /* RFC 4271 9.1.2.2. d) Prefer external peers */ - if (new_bgp->is_internal > old_bgp->is_internal) + n = !!(new_bgp->is_internal || new_bgp->cf->iebgp_peer); + o = !!(old_bgp->is_internal || old_bgp->cf->iebgp_peer); + if (n > o) return 0; - if (new_bgp->is_internal < old_bgp->is_internal) + if (n < o) return 1; /* RFC 4271 9.1.2.2. e) Compare IGP metrics */ @@ -1424,7 +1432,9 @@ bgp_rte_mergable(rte *pri, rte *sec) } /* RFC 4271 9.1.2.2. d) Prefer external peers */ - if (pri_bgp->is_internal != sec_bgp->is_internal) + p = !!(pri_bgp->is_internal || pri_bgp->cf->iebgp_peer); + s = !!(sec_bgp->is_internal || sec_bgp->cf->iebgp_peer); + if (p != s) return 0; /* RFC 4271 9.1.2.2. e) Compare IGP metrics */ diff --git a/proto/bgp/bgp.h b/proto/bgp/bgp.h index e47a0eb1..8652fae8 100644 --- a/proto/bgp/bgp.h +++ b/proto/bgp/bgp.h @@ -51,6 +51,7 @@ struct bgp_config { int add_path; /* Use ADD-PATH extension [RFC7911] */ int allow_local_as; /* Allow that number of local ASNs in incoming AS_PATHs */ int allow_local_pref; /* Allow LOCAL_PREF in EBGP sessions */ + int iebgp_peer; /* Peer has different AS but should be treated as internal peer */ int gr_mode; /* Graceful restart mode (BGP_GR_*) */ int setkey; /* Set MD5 password to system SA/SP database */ unsigned gr_time; /* Graceful restart timeout */ diff --git a/proto/bgp/config.Y b/proto/bgp/config.Y index 55c602f1..f01a6fb6 100644 --- a/proto/bgp/config.Y +++ b/proto/bgp/config.Y @@ -27,7 +27,8 @@ CF_KEYWORDS(BGP, LOCAL, NEIGHBOR, AS, HOLD, TIME, CONNECT, RETRY, INTERPRET, COMMUNITIES, BGP_ORIGINATOR_ID, BGP_CLUSTER_LIST, IGP, TABLE, GATEWAY, DIRECT, RECURSIVE, MED, TTL, SECURITY, DETERMINISTIC, SECONDARY, ALLOW, BFD, ADD, PATHS, RX, TX, GRACEFUL, RESTART, AWARE, - CHECK, LINK, PORT, EXTENDED, MESSAGES, SETKEY, BGP_LARGE_COMMUNITY) + CHECK, LINK, PORT, EXTENDED, MESSAGES, SETKEY, BGP_LARGE_COMMUNITY, + IEBGP_PEER) CF_GRAMMAR @@ -129,6 +130,7 @@ bgp_proto: | bgp_proto ALLOW BGP_LOCAL_PREF bool ';' { BGP_CFG->allow_local_pref = $4; } | bgp_proto ALLOW LOCAL AS ';' { BGP_CFG->allow_local_as = -1; } | bgp_proto ALLOW LOCAL AS expr ';' { BGP_CFG->allow_local_as = $5; } + | bgp_proto IEBGP_PEER bool ';' { BGP_CFG->iebgp_peer = $3; } | bgp_proto GRACEFUL RESTART bool ';' { BGP_CFG->gr_mode = $4; } | bgp_proto GRACEFUL RESTART AWARE ';' { BGP_CFG->gr_mode = BGP_GR_AWARE; } | bgp_proto GRACEFUL RESTART TIME expr ';' { BGP_CFG->gr_time = $5; } -- 2.13.4

3 3

Bird v2, MPLS and LDP
by Maximilian Wilhelm 19 Sep '17

19 Sep '17

Hi folks, I've just seen in the NEWS for bird 2.0.0-pre1 that there are many MPLS related things coming. Kudos for that! Forgive me if this has been answered recently, I didn't find anything in my list archive: As of the available support for MPLS forwarding in the Linux kernel, I'm wondering if there is any rough roadmap the next releases? Are there any plans on integrating some LDP module (maybe also borrowing from the openldpd as FRR did? ;)) into bird? Thanks for your great work! Will someone of you folks at DENOG9? Best Max -- "Kunst ist Besessenheit. Du willst etwas unter Kontrolle bringen bevor es Dich kontrolliert." -- O

2 3

FreeBSD 11.1 OSPF multicast broken?
by Aragon Gouveia 19 Sep '17

19 Sep '17

Good day, There seems to be a multicast related bug with FreeBSD 11.1 and Bird 1.6.3. In summary: Two problems: * Ethernet interfaces configured as "broadcast" do not emit any OSPF packets, as observed by tcpdump. * Above interfaces receive OSPF packets from Linux neighbours (as seen by tcpdump), but Bird does not receive them (nothing logged in debug mode). Two workarounds: * Enabling "real broadcast" solves both problems above, but it must be enabled on all peers' configs so that everyone broadcasts. * Configuring interfaces as nbma on all peers also solves both problems. While Bird is running, there seem to be no OSPF multicast memberships reported by ifmcstat(8), eg. # ifmcstat -i vtnet1 -v vtnet1: inet 192.168.102.16 igmpv3 rv 2 qi 125 qri 10 uri 3 group 224.0.0.1 mode exclude mcast-macaddr 01:00:5e:00:00:01 link 52:54:00:85:d7:51 group 01:00:5e:00:00:01 I have also tried disabling firewalls, and have not seen any "Permission denied" socket errors logged by Bird in debug mode. I'd be delighted to help test/find a fix with my lab setup, but for now I'm a bit lost for digging into code and kernel APIs, which is where I suspect the problem lies. Any ideas where to start? Thanks, Aragon

3 9

BIRD export reject not working
by Marek Królikowski 19 Sep '17

19 Sep '17

Hello guys, I got strange problem with BGP i share data to Collector but i put to reject some bgp path.... This is how look configuration of BGP session of Collector: protocol bgp Collector { description "Collector"; local as MY-ASN; source address IPv61; neighbor IPV62 as SOMEONE-ASN; multihop; import none; export filter { if bgp_path.first = 64515 then reject; if bgp_path = 64515 then reject; if bgp_path.last = 64515 then reject; include "export.conf"; }; } But: root@pl-bgp:~# birdc6 show route export Collector all 2a0b:e206::/32 BIRD 1.6.3 ready. 2a0b:e206::/32 via 2a06:1287:330e:16::2 on bgp-fr [France 2017-09-18] * (100) [AS21430i] Type: BGP unicast univ BGP.origin: IGP BGP.as_path: MY-ASN 64515 20473 1299 21430 BGP.next_hop: 2a07:XXXX.XXXX.XXXX BGP.local_pref: 100 BGP.community: (64515,44) Like You see in BGP path there is 64515. How i export this to Collector if i put reject on export? What is wrong? I use BIRD 1.6.3. Best Regards Marek Krolikowski

4 4