- Bird-users - Mailing Lists

Bird reconfiguration without loosing the routes
by Vonlanthen, Elmar 14 Feb '09

14 Feb '09

Hello I have the following configuration: /etc/bird.conf: log syslog all; debug protocols all; router id 172.16.10.1; filter ospf_networks { if net = 172.16.10.0/24 then accept; else reject; } filter ospf_proto { if source ~ [ RTS_OSPF_EXT2 ] then accept; else reject; } protocol direct { interface "*"; } protocol kernel k_master { kernel table 254; learn; persist; scan time 10; import all; export filter ospf_proto; } protocol device { scan time 10; } protocol static { } protocol ospf { tick 2; rfc1583compat yes; import all; export filter ospf_networks; area 0.0.0.0 { interface "gre1" { type pointopoint; authentication none; cost 15; hello 10; dead 40; }; }; } This is working fine. "gre1" is the GRE interface with a point-to-point connection to a remote site (with similar configuration). Now I would like to add a second interface for a new remote site. This here would be the new ospf configuration: protocol ospf { tick 2; rfc1583compat yes; import all; export filter ospf_networks; area 0.0.0.0 { interface "gre1" { type pointopoint; authentication none; cost 15; hello 10; dead 40; }; interface "gre2" { <== new type pointopoint; authentication none; cost 15; hello 10; dead 40; }; }; } Now, how can I reload the configuration, without loosing the routes from the first remote site in the kernel table? When a use "configure" in birdc the routes are going away for a few seconds. I have the keyword "persist" in protocol kernel. If I stop bird, the routes are still there, but when I start bird again, I loose the routes for a few seconds. Many thanks for any help. Best regards Elmar

2 1

bgp export filters?
by Harald Michl 14 Feb '09

14 Feb '09

Hi! I've two questions regarding filtering of bgp announcements. One simple and one more complicated :-) The simple one: I do not want to announce prefixes that have the community 0:64003 attached, but all other prefixes. What I did is: export filter { if (0,64003) ~ bgp_community then { reject; } accept; }; The peer receives no prefixes at all. Any hints? The other question is more interesting/complicated. Is it possible to include some kind of macros in outbound filters? What I would like would be: export macro XYZ { if (0,<remote-as>) ~ bgp_community then { reject; } accept; }; and in the per bgp peering section I'd only write: export filter XYZ; Does that feature exist? If not, would somebody else need something? regards, Harald -- Harald Michl <harald.michl(a)univie.ac.at> Vienna University - ACOnet www.ACO.net - VIX www.VIX.at Universitaetsstrasse 7, A-1010 Vienna, Austria, Europe Tel: +43 1 4277 - 14078 (Fax: - 9140) HM3550-RIPE

2 1

RE: Bird to quagga interoperation
by Vonlanthen, Elmar 10 Feb '09

10 Feb '09

Hello Ondrej In the thread "BIRD <-> Quagga Compatiblity" (started in May, 2007) I have already posted some informations. If you haven't access to the old thread, I could post the mails/infos again. Is possible that Quagga does something wrong? Best regards Elmar -----Original Message----- From: Ondrej Zajicek [mailto:santiago@crfreenet.org] Sent: Mittwoch, 4. Februar 2009 23:43 To: Vonlanthen, Elmar Cc: bird-users(a)network.cz Subject: Re: Bird to quagga interoperation (WARNING!!! PGP with incorrect signature) On Wed, Feb 04, 2009 at 11:30:52AM +0100, Vonlanthen, Elmar wrote: > Hello > > We still have some hosts with the quagga routing daemon in a bird > environment. > > With the bird releases 1.0.11 and 1.0.12 it is not working. Bird gets > the routes, but quagga doesn't. Can you provide a better description of your network setting? The current code seems to me being fully RFC-compliant. I will look at it. The LSA generating code needs some review, but this is an issue i don't know about. -- Elen sila lumenn' omentielvo Ondrej 'SanTiago' Zajicek (email: santiago(a)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."

2 4

Bird to quagga interoperation
by Vonlanthen, Elmar 04 Feb '09

04 Feb '09

Hello We still have some hosts with the quagga routing daemon in a bird environment. With the bird releases 1.0.11 and 1.0.12 it is not working. Bird gets the routes, but quagga doesn't. With the following patch, which Ondrej gave me, it is working (with both releases). Is there any reason, why this patch is not in the current bird release? --- bird-1.0.11.old/proto/ospf/topology.c 2005-02-21 11:05:22.000000000 +0100 +++ bird-1.0.11/proto/ospf/topology.c 2008-09-30 14:32:45.000000000 +0200 @@ -90,14 +90,7 @@ ln->id = neigh->rid; ln->metric = ifa->cost; ln->notos = 0; - if (ifa->iface->addr->flags & IA_UNNUMBERED) - { - ln->data = ifa->iface->index; - } - else - { - ln->data = ipa_to_u32(ifa->iface->addr->ip); - } + ln->data = ipa_to_u32(ifa->iface->addr->ip); } else { Best regards Elmar

2 1

Bird 1.0.22 and FreeBSD
by Xavier Beaudouin 23 Jan '09

23 Jan '09

Hello, I am trying to make run Bird on FreeBSD (1.0.11 was running on it, with the port that has being done), but it seems that tcp md5 features are not really supported as the same way it is on Linux. Until I figure how to adapt that on it, is there any good way to desactivate it during compilation? Thanks, /Xavier

3 2

bird as route-server
by Harald Michl 23 Jan '09

23 Jan '09

Hi! I'm new to the list and new to bird, but know a little bit about bgp and what i want: I want to use bird as a route-server in an ixp environment. If I configure a peer as rc client, i get a syntax-error at "rs client;". The config command should exist according to the documentation... I append the peer-config. Has anyone a hint? I use Version 1.0.11-4. thanks for your answers, Harald protocol bgp AS64002 { local as 64000; neighbor 10.203.0.2 as 64002; rs client; hold time 240; startup hold time 240; connect retry time 120; keepalive time 80; # defaults to hold time / 3 start delay time 5; # How long do we wait before initial connect error wait time 60, 300;# Minimum and maximum time we wait after an error (when consecutive # errors occur, we increase the delay exponentially ... error forget time 300; # ... until this timeout expires) next hop self; # Disable next hop processing and always advertise our local address as nexthop path metric 1; # Prefer routes with shorter paths (like Cisco does) default bgp_med 0; # MED value we use for comparison when none is defined default bgp_local_pref 100; # The same for local preference source address 10.203.0.254; # What local address we use for the TCP connection export all; } -- Harald Michl <harald.michl(a)univie.ac.at> Vienna University - ACOnet www.ACO.net - VIX www.VIX.at Universitaetsstrasse 7, A-1010 Vienna, Austria, Europe Tel: +43 1 4277 - 14078 (Fax: - 9140) HM3550-RIPE

4 5

problem with route server
by Valentin Rosic 23 Jan '09

23 Jan '09

hello, I'm trying to build simple route server but I'm having difficulties. Here are my configurations and debug. Where did I do wrong? bird.conf : ------------------------------------------------- log syslog { debug, trace, info, remote, warning, error, auth, fatal, bug }; log stderr all; log "tmp" all; router id 192.168.55.7; filter test_filter { if net ~ 192.168.55.0/28 then accept; else reject; } protocol direct { interface "eth0"; # Restrict network interfaces it works with } protocol device { scan time 10; # Scan interfaces every 10 seconds } protocol bgp { debug all; local as 999; neighbor 192.168.55.1 as 100; rs client; export all; } ------------------------------------------------- debug: ------------------------------------------------- 23-01-2009 15:43:28 <TRACE> bgp1: Connect delayed by 5 seconds 23-01-2009 15:43:33 <TRACE> bgp1: Connecting to 192.168.55.1 from local address 192.168.55.7 23-01-2009 15:43:33 <TRACE> bgp1: Connected 23-01-2009 15:43:33 <TRACE> bgp1: Sending OPEN(ver=4,as=999,hold=240,id=c0a83707) 23-01-2009 15:43:33 <RMT> bgp1: Received error notification: Required capability missing 23-01-2009 15:44:18 <TRACE> bgp1: Incoming connection from 192.168.55.1 port 15968 23-01-2009 15:44:18 <TRACE> bgp1: Sending OPEN(ver=4,as=999,hold=240,id=c0a83707) 23-01-2009 15:44:18 <TRACE> bgp1: Got OPEN(as=100,hold=180,id=01010101) 23-01-2009 15:44:18 <TRACE> bgp1: Sending KEEPALIVE 23-01-2009 15:44:18 <RMT> bgp1: Received error notification: Required capability missing ------------------------------------------------- cisco 2600 : ------------------------------------------------- router bgp 100 no synchronization bgp router-id 1.1.1.1 bgp log-neighbor-changes network 192.168.1.0 neighbor 192.168.55.7 remote-as 999 neighbor 192.168.55.7 soft-reconfiguration inbound no auto-summary ------------------------------------------------- debug: ------------------------------------------------- Jan 23 15:45:39.216 MET: BGP: Import timer expired. Walking from 1 to 1 Jan 23 15:45:54.216 MET: BGP: Performing BGP general scanning Jan 23 15:45:54.216 MET: BGP(0): scanning IPv4 Unicast routing tables Jan 23 15:45:54.228 MET: BGP(1): scanning VPNv4 Unicast routing tables Jan 23 15:45:54.228 MET: BGP(2): scanning IPv4 Multicast routing tables Jan 23 15:45:59.964 MET: %BGP-3-NOTIFICATION: sent to neighbor 192.168.55.7 2/7 (unsupported/disjoint capability) 0 bytes FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF 0025 0104 03E7 07 Jan 23 15:46:01.072 MET: BGP: service reset requests ------------------------------------------------- -- srdacan pozdrav/regards, Valentin ------------------------------------------------ Valentin Rosic SRCE - Sveucilisni racunski centar J. Marohnica 5, 10000 Zagreb, Croatia email: valentin.rosic @ srce.hr web: http://www.srce.hr tel: +385/1/6165 303 fax: +385/1/6165 559 ------------------------------------------------

2 2

Re: Syntax error on BIRD Configuratrion
by Mo Shivji 16 Jan '09

16 Jan '09

Ondrej Zajicek wrote: > On Fri, Jan 16, 2009 at 03:10:37PM +0000, Mo Shivji wrote: >> Hi >> >> I am in the process of testing BIRD and am having a problem with >> starting BIRD with a simple BGP peering configuration >> >> I get this error when I load the configuration, >> >> $bird# /sbin/bird -c bird.conf >> bird: bird.conf, line 21: syntax error > > I can load given configuration without problems. Perhaps you compiled > bird with IPv6 support and in that case it expect IPv6 address there. > Bird compiled with IPv6 support does not have IPv4 support - for both > protocols you have to have two instances of Bird. > Hi Thanks for the quick response. That's seems to have solved it. Thanks for your help. Mo

1 0

Syntax error on BIRD Configuratrion
by Mo Shivji 16 Jan '09

16 Jan '09

Hi I am in the process of testing BIRD and am having a problem with starting BIRD with a simple BGP peering configuration I get this error when I load the configuration, $bird# /sbin/bird -c bird.conf bird: bird.conf, line 21: syntax error This is my configuration, --------------------------------------- $bird # more bird.conf router id 192.168.253.5; protocol kernel { persist; # Don't remove routes on BIRD shutdown scan time 20; # Scan kernel routing table every 20 seconds export all; # Default is export none } protocol device { scan time 20; # Scan interfaces every 10 seconds } protocol direct { interface "*"; } protocol bgp { local as 8714; neighbor 10.0.0.1 as 1234; source address 10.0.0.254; import all; } --------------------------------------- The errors says there is a a systax error where I I specify the neighbor that my server peers with. I can not see anything wrong here. Am I missing something ? Mo

2 1

ospf: bird stuck in R state
by Yury Shevchuk 22 Dec '08

22 Dec '08

Hi :) The following is a bird bug with some investigation but no good solution yet. Could bird developers please take a look and advise? Thanks, -- sizif We are running ospf with bird 1.0.12 and from time to time discover bird stuck in R state: # ps auxw | grep bird root 14269 56.9 0.0 3088 2064 ? Rs Dec16 690:56 /usr/sbin/bird I have approached the process with gdb and have found the following: 0x0807b742 in s_merge (from=0x80e0e54, to=0x80d118c) at slists.c:35 (gdb) bt #0 0x0807b742 in s_merge (from=0x80e0e54, to=0x80d118c) at slists.c:35 #1 0x0807b6e3 in s_rem_node (n=0x80e0e54) at slists.c:125 #2 0x08066fdb in lsa_install_new (lsa=0xbf983c80, body=0x80c8fc0, oa=0x8096340) at /home/sizif/bird/./proto/ospf/lsalib.c:459 #3 0x0806568a in ospf_lsupd_receive (ps=0x80b56e4, ifa=0x8099570, n=0x80b3bf8) at /home/sizif/bird/./proto/ospf/lsupd.c:487 #4 0x08060553 in ospf_rx_hook (sk=0x80b4310, size=64) at /home/sizif/bird/./proto/ospf/packet.c:346 #5 0x08074c27 in sk_read (s=0x80b4310) at io.c:1212 #6 0x080751af in io_loop () at io.c:1378 #7 0x080779eb in main (argc=3, argv=0xbf983fd4) at main.c:458 Here is the spot in s_merge where we cycle: /* Really merging */ while (g->next) > g = g->next; (gdb) p /x *g $1 = {prev = 0x80e0e54, null = 0x0, next = 0x80ab1d0, node = 0x0} (gdb) display /x g $2 = 0x80ab1d0 That is, the list of slist readers is trivially cycled. 0x80ab1d0 is the address of n->dbsi field of one of the neighbors: (gdb) p /x *(struct ospf_neighbor *)0x80ab190 $31 = {n = {next = 0x80abc38, prev = 0x80aa6e8}, pool = 0x80ab160, ifa = 0x8099570, state = 0x4, inactim = 0x80ab848, imms = {byte = 0x2, bit = {ms = 0x0, m = 0x1, i = 0x0, padding = 0x0}}, dds = 0xcf4d0c79, ddr = 0xb846f866, myimms = {byte = 0x7, bit = {ms = 0x1, m = 0x1, i = 0x1, padding = 0x0}}, rid = 0xc0a84909, ip = 0xc0a84909, priority = 0xa, options = 0x2, dr = 0xc0a8491e, bdr = 0xc0a84930, adj = 0x0, dbsi = { prev = 0x80e0e54, null = 0x0, next = 0x80ab1d0, node = 0x0}, lsrql = { head = 0x80ab1e4, null = 0x0, tail = 0x80ab1e0, tail_readers = 0x80ab1f4}, lsrqh = 0x80ab8b8, lsrqi = {prev = 0x80ab1e4, null = 0x0, next = 0x0, node = 0x80ab1e4}, lsrtl = {head = 0x80e9f8c, null = 0x0, tail = 0x80e9e4c, tail_readers = 0x80ab214}, lsrti = { prev = 0x80ab208, null = 0x0, next = 0x0, node = 0x80ab208}, lsrth = 0x80aba50, ldbdes = 0x80ab268, rxmt_timer = 0x80ab878, ackl = {{ head = 0x80ab234, null = 0x0, tail = 0x80ab230}, {head = 0x80ab240, null = 0x0, tail = 0x80ab23c}}, ackd_timer = 0x80abbd8, csn = 0x0} Another interesing observation is that both nodes given as arguments to s_merge have identical readers field: #1 0x0807b6e3 in s_rem_node (n=0x80e0e54) at slists.c:125 (gdb) p /x *n $38 = {next = 0x80d118c, prev = 0x809a7b4, readers = 0x80ab1d0} (gdb) p /x *(snode *)0x80d118c $40 = {next = 0x80e0f44, prev = 0x809a7b4, readers = 0x80ab1d0} (gdb) p /x *(snode *)0x80e0f44 $41 = {next = 0x80bcdec, prev = 0x80d118c, readers = 0x0} (gdb) p /x *(snode *)0x80bcdec $42 = {next = 0x80b6db4, prev = 0x80e0f44, readers = 0x0} (gdb) p /x *(snode *)0x80b6db4 $43 = {next = 0x80e1174, prev = 0x80bcdec, readers = 0x0} (gdb) p /x *n $44 = {next = 0x80d118c, prev = 0x809a7b4, readers = 0x80ab1d0} (gdb) p /x *(snode *)0x809a7b4 $45 = {next = 0x80d118c, prev = 0x809a764, readers = 0x0} (gdb) p /x *(snode *)0x809a764 $46 = {next = 0x809a7b4, prev = 0x809a714, readers = 0x0} How can an iterator be referenced by more than one slist node? It looks like someone did s_put(&(n->dbsi), ...) while the previous iteration has not been completed. The s_get...s_put pair in ospf_dbdes_send seems sound and safe. I think the culprit is ospf_neigh_sm who does s_init(&(n->dbsi)) when entering NEIGHBOR_EXCHANGE: case INM_NEGDONE: if (n->state == NEIGHBOR_EXSTART) { neigh_chstate(n, NEIGHBOR_EXCHANGE); s_init(&(n->dbsi), &po->lsal); The s_init does good when the neighbor enters NEIGHBOR_EXCHANGE for the first time. But if the neighbor enters NEIGHBOR_EXCHANGE again without finishing the n->dbsi run through po->lsal, we will get exactly the effect we observe: n->dbsi relinked to the head node of po->lsal without unlinking it from the node it currently points to. And a neighbor can indeed leave NEIGHBOR_EXCHANGE with unfinished run through po->lsal for a number of reasons, with INM_SEQMIS or INM_BADLSREQ. One solution I can think of is to keep n->dbsi in s_put state *always*, except for a short s_get...s_put fragment in ospf_dbdes_send where there are no state transitions. Do initial s_init(&(n->dbsi)) in ospf_neighbor_new. Do s_get before s_init in the ospf_neigh_sm fragment cited above. Do s_put unconditionally in ospf_dbdes_send. Your thoughts?

2 2