- Bird-users - Mailing Lists

View prefixes advertised to BGP peer
by Anand Buddhdev 18 May '15

18 May '15

Dear bird users, Do you know if, in bird version 1.4.5, there is a way to view the prefixes being advertised to a specific BGP peer? Apologies of this is covered in the manual, but I can't seem to find it. Regards, Anand

2 1

bird1.5.0 and MyOSPF: Bad packet from 192.168.0.XX via eth0 - my own router ID (0)
by Arkadiusz Miśkiewicz 18 May '15

18 May '15

On various machines with OSPF bird 1.5.0 reports bad packets. It doesn't get its own ID right? It is configured with: router id 192.168.0.164; May 18 13:42:34 rhea bird: ... May 18 13:42:35 rhea bird: MyOSPF: Bad packet from 192.168.0.44 via eth0 - my own router ID (0) May 18 13:42:35 rhea bird: ... May 18 13:42:36 rhea bird: MyOSPF: Bad packet from 192.168.0.9 via eth0 - my own router ID (0) May 18 13:42:36 rhea bird: ... May 18 13:42:37 rhea bird: MyOSPF: Bad packet from 192.168.0.26 via eth0 - my own router ID (0) May 18 13:42:37 rhea bird: ... May 18 13:42:38 rhea bird: MyOSPF: Bad packet from 192.168.0.9 via eth0 - my own router ID (0) May 18 13:42:38 rhea bird: ... May 18 13:42:38 rhea bird: MyOSPF: Bad packet from 192.168.0.26 via eth0 - my own router ID (0) May 18 13:42:38 rhea bird: ... May 18 13:42:39 rhea bird: MyOSPF: Bad packet from 192.168.0.26 via eth0 - my own router ID (0) May 18 13:42:39 rhea bird: ... May 18 13:42:40 rhea bird: MyOSPF: Bad packet from 192.168.0.26 via eth0 - my own router ID (0) May 18 13:42:40 rhea bird: ... May 18 13:42:42 rhea bird: MyOSPF: Bad packet from 192.168.0.9 via eth0 - my own router ID (0) May 18 13:42:42 rhea bird: ... May 18 13:42:42 rhea bird: MyOSPF: Bad packet from 192.168.0.44 via eth0 - my own router ID (0) May 18 13:42:42 rhea bird: ... May 18 13:42:44 rhea bird: MyOSPF: Bad packet from 192.168.0.44 via eth0 - my own router ID (0) May 18 13:42:44 rhea bird: ... May 18 13:42:45 rhea bird: MyOSPF: Bad packet from 192.168.0.44 via eth0 - my own router ID (0) May 18 13:42:45 rhea bird: ... May 18 13:42:46 rhea bird: MyOSPF: Bad packet from 192.168.0.44 via eth0 - my own router ID (0) May 18 13:42:46 rhea bird: ... May 18 13:42:47 rhea bird: MyOSPF: Bad packet from 192.168.0.26 via eth0 - my own router ID (0) May 18 13:42:47 rhea bird: ... May 18 13:42:48 rhea bird: MyOSPF: Bad packet from 193.239.45.164 via eth0 - my own router ID (0) May 18 13:42:48 rhea bird: ... May 18 13:42:49 rhea bird: MyOSPF: Bad packet from 193.239.45.164 via eth0 - my own router ID (0) May 18 13:42:49 rhea bird: ... May 18 13:42:50 rhea bird: MyOSPF: Bad packet from 192.168.0.26 via eth0 - my own router ID (0) -- Arkadiusz Miśkiewicz, arekm / ( maven.pl | pld-linux.org )

2 1

BIRD ripng default gateway route strange behavior
by olivier a 11 May '15

11 May '15

Hello all ^^ I'm puzzled with a really weird RIPng default gateway propagation problem. I don't quite understand what's happening. Here is what happens ... Network topology : PC1---Router1---Router2----InternetGateway---z RIPng enabled on PC1, Router1, Router2 Router2 has a static IPv6 DG ( Default Gateway ) to InternetGateway Router1 has no static IPv6 DG, and no kernel{learn} directive. Router2=Ubuntu14.04 LTS, Router1=raspbian Wheezy, bird = last version, compiled from sources link-local addresses replaces with symbolic names ( ie [fe80::Router1] ) Something really strange seems to happen : . Router2 gets this routing table : default via InternetGateway dev eth0 proto static metric 1 default via [fe80::Router1] dev eth1 proto bird metric 1024 But Router1 isn't announcing any IPv6 DefaultGateway, just ::/0 metric 16 ( ie it is poisoning the route ). ( I checked using Wireshark ). Is there a bug that transforms a received "::/0 metric 16" into a "default via [fe80::Router1] dev eth1 proto bird metric 1024" route ? Here is Router2 bird6.conf file : ------------------------------------------------- log syslog all; debug protocols all; #log stderr all; #log "tmp" all; router id 192.168.4.1; protocol kernel { learn; scan time 20; export all; import all; } protocol direct { #interface "eth0"; } protocol device { scan time 10; } protocol rip { debug all; port 521; interface "*" { mode multicast; ttl security on; }; honor neighbor; authentication none; import all; export all; } ------------------------------------------------------------- I managed to solve the problem, by having Router2 drop incomming ::/0 announcements : --------------------------------------------------------- import filter { # This block filters ::/0 in if net ~ [ ::/0+ ] then reject "ripng:rejected:DG"; else accept "ripng:accepted:not-DG"; }; export all; --------------------------------------------------------- the problem is solved, yet it puzzles me. This is really strange. Does anybody understand what is happening ??

3 6

key/value structure
by Pavlos Parissis 09 May '15

09 May '15

Hi, For each ip_prefix I advertize I need to add a BGP community in the form of (ASN,<RouterID>). I have the following mapping between IPs and RouterIDs ip_prefix, RouterID 10.10.10.1, 1 10.10.10.2, 2 10.10.10.3, 3 10.10.10.4, 1 10.10.10.5, 2 10.10.10.6, 3 ..... So, inside a function I need to express the following lookup_community_router_id() { return some_kind_of_dict_structure(net.ip) } and the use it in a filter/function filter { bgp.community((1111, lookup_community_router_id(net))); accept; } Is this possible? Thanks, Pavlos

2 2

Re: Bird IRC channel
by Hans van Kranenburg 04 May '15

04 May '15

Hi, On 05/04/2015 08:06 PM, Tom Wesley wrote: > > As noone piped up saying what a bad idea this I've made all three of > your channel founders so you can set the channel up as you wish. Thank you, Tom! Hans van Kranenburg

1 0

no rc files with bird on ubuntu ?
by Kai 03 May '15

03 May '15

Hello everybody! We are running bird and bird6 on an ubuntu server. I just noticed that /etc/init.d/bird and .../bird6 are not linked to any of the /etc/rc?.d directories on our three systems. Furthermore update-rc.d wouldn't create the links but just fail silently (that is with a succinct "System start/stop links for /etc/init.d/bird do not exist."). I'm stuck right now. Does anyone else observe the same behaviour? Am I mistaken in thinking there should be rd.c-files? Best regards, Kai -- "Das ist Demokratie, wenn man sich aussuchen darf, wer einen verarscht." (Hagen Rether) D-55118 Meenz fast: kai_pf (aT] web(dot)de ++ PGP Key fingerprint B567 C43E 99D1 7709 7D64 3BF8 2DE8 1092 0EEF D58E ++ -----BEGIN GEEK CODE BLOCK----- VERSION: 3.12 GCS/IT/CM d- s:- a+>-----(?) C++$ UL++(++++$) P+++ L++ E-(+) W--(+) N !w---($) !O !M V? PS+ PE-() Y+ PGP(+) t R*@ tv--@ b+>++ DI++ G e+++(*) h? y? ------END GEEK CODE BLOCK------

3 3

Version 1.5.0 in Ubuntu PPA
by Clint Armstrong 28 Apr '15

28 Apr '15

Will packages be going into the official Ubuntu PPA soon? https://launchpad.net/~cz.nic-labs/+archive/ubuntu/bird

1 0

bird6 1.4.5 OSPFv3 LSA checksum failures
by Chris Boot 28 Apr '15

28 Apr '15

Hi folks, I’m running bird6 1.4.5-1 (from Debian jessie) on my home network. Quite regularly I see floods of "Received bad lsa checksum” message in my syslog on the two routers that run BIRD, which causes connectivity interruptions. The network is made up of a variety of devices running different OSPF stacks. The network is fully dual-stacked with the same devices running OSPFv2 and OSPFv3 with a mostly identical configuration. The network contains two Quagga (0.99.23.1-1 from Debian Jessie) routers, one Dell PowerConnect 8024F (fw 5.1.7.5), and several MikroTik RouterOS (6.28) routers. The problem *only* occurs on OSPFv3; OSPFv2 is unaffected. The messages always follow a very specific pattern. Here are the last 10 received on one of my routers: Apr 25 16:17:36 clemens bird6: Received bad lsa checksum from fe80::290:7fff:fe3c:502a: de00 deff Apr 25 16:17:37 clemens bird6: Received bad lsa checksum from fe80::5e26:aff:feb8:34ad: de00 deff Apr 25 16:17:41 clemens bird6: Received bad lsa checksum from fe80::290:7fff:fe3c:502a: de00 deff Apr 25 16:17:42 clemens bird6: Received bad lsa checksum from fe80::5e26:aff:feb8:34ad: de00 deff Apr 25 16:17:46 clemens bird6: Received bad lsa checksum from fe80::290:7fff:fe3c:502a: de00 deff Apr 25 16:17:47 clemens bird6: Received bad lsa checksum from fe80::5e26:aff:feb8:34ad: de00 deff Apr 25 16:17:51 clemens bird6: Received bad lsa checksum from fe80::290:7fff:fe3c:502a: de00 deff Apr 25 16:17:52 clemens bird6: Received bad lsa checksum from fe80::5e26:aff:feb8:34ad: de00 deff Apr 25 16:17:56 clemens bird6: Received bad lsa checksum from fe80::290:7fff:fe3c:502a: de00 deff Apr 25 16:18:01 clemens bird6: Received bad lsa checksum from fe80::290:7fff:fe3c:502a: de00 deff If I grep my logs looking for unique entries, I see the following: Received bad lsa checksum from $PEER: 1800 18ff Received bad lsa checksum from $PEER: 30 ff30 Received bad lsa checksum from $PEER: 3500 35ff Received bad lsa checksum from $PEER: 40 ff40 Received bad lsa checksum from $PEER: 5000 50ff Received bad lsa checksum from $PEER: 6600 66ff Received bad lsa checksum from $PEER: 6e00 6eff Received bad lsa checksum from $PEER: 86 ff86 Received bad lsa checksum from $PEER: 9800 98ff Received bad lsa checksum from $PEER: 9c00 9cff Received bad lsa checksum from $PEER: 9e ff9e Received bad lsa checksum from $PEER: 9f ff9f Received bad lsa checksum from $PEER: bc ffbc Received bad lsa checksum from $PEER: cc ffcc Received bad lsa checksum from $PEER: cd ffcd Received bad lsa checksum from $PEER: cf00 cfff Received bad lsa checksum from $PEER: dc ffdc Received bad lsa checksum from $PEER: dd ffdd Received bad lsa checksum from $PEER: de00 deff Received bad lsa checksum from $PEER: e600 e6ff Received bad lsa checksum from $PEER: ee00 eeff Received bad lsa checksum from $PEER: fe fffe Thus, the problem occurs when (AIUI) the checksum sent by the peer has a zero octet, which doesn’t agree with how lsasum_check() calculates the checksum where the octet is always 0xff instead. This happens either when the first octet is zero or the second octet is zero. Looking through my logs, it seems I have yet to run into a situation where the values are reversed, e.g. the checksum in the LSA always includes a zero octet and BIRD always calculates 0xff, never the other way around. I have yet to look in much detail whether the problem is likely to be in BIRD’s lsasum_check() implementation or in the checksum generated by one of my other devices, and I don’t yet know which device(s) generate the LSAs that BIRD complains about. Has anyone here run into this before? Thanks, Chris -- Chris Boot bootc(a)bootc.net

2 4

Bird IRC channel
by Hans van Kranenburg 26 Apr '15

26 Apr '15

Hi all, As you might probably, or more probably not know, a sub-official bird IRC channel exists, which is #bird on freenode. The current inhabitants have no idea who ever started the channel, or how to be able to change any attributes of the channel, like setting topic or anything... Cycling the channel is not really an option, since 99% of the inhabitants seem just to be lurking around, never saying anything. (Yeah, if you're reading this, say something! :D ) 00:24 <Knorrie> access #bird list 00:24 -ChanServ(ChanServ@services.)- Entry Nickname/Host Flags 00:24 -ChanServ(ChanServ@services.)- ----- ---------------------- ----- 00:24 -ChanServ(ChanServ@services.)- 1 freenode-staff +AFRefiorstv [modified 2y 44w 5d ago] 00:24 -ChanServ(ChanServ@services.)- ----- ---------------------- ----- 00:24 -ChanServ(ChanServ@services.)- End of #bird FLAGS listing. 00:27 <Knorrie> flags #bird 00:27 -ChanServ(ChanServ@services.)- You are not authorized to perform this operation. From time to time we have really interesting conversations on this IRC channel, and I would really like it to become a little more active. Let's hang around and just share a bit about what we're doing with bird in an informal way. If you have ever started this channel, or have any idea how to get control of it back again, join! -- Hans van Kranenburg - System / Network Engineer T +31 (0)10 2760434 | hans.van.kranenburg(a)mendix.com | www.mendix.com

1 1

password for BGP in clear-text in bird.conf file?
by Christopher Jay Manders 25 Apr '15

25 Apr '15

Hi, I am not sure if this has been brought up before, but it is very sad that the password for BGP AUTH is in clear-text. Is there anything in progress to rectify or discussion about this? Encoding or encryption of the password would be a very welcome thing. Thanks! Christopher

5 5