- Bird-users - Mailing Lists

ospf interoperability problems with cisco and other errors
by Csaba Szép 05 Oct '09

05 Oct '09

Hi All! I'm a very new bird user, but i have some problems with cisco 7200 router. First, the HELLO packet ignored with "Bad OSPF hello packet from 1.0.0.1 received: options mismatch (0x12)." if i use the cisco default ospf configuration. With "ip ospf lls disable" option everything is ok. Second, i advertise some alias IP from the pc to the cisco router, but if i remove the alias address from the interface some OSPF routes still present in the cisco router. Here is the relevant configuration: Cisco 7200 12.2(28)SB5 interface Loopback0 ip address 3.0.0.1 255.255.255.255 ! interface FastEthernet0/0 ip address 1.0.0.1 255.255.255.0 ip ospf message-digest-key 1 md5 benabela ip ospf lls disable duplex full ! router ospf 1 log-adjacency-changes area 0.0.0.0 authentication message-digest network 1.0.0.0 0.0.0.255 area 0.0.0.0 default-information originate ! ip classless ip route 0.0.0.0 0.0.0.0 Loopback0 Bird 1.1.4 protocol kernel { learn; scan time 20; import all; export none; } protocol device { scan time 10; } protocol ospf ospf1 { debug { routes,filters }; export filter { if net ~ 192.0.2.0/24 then accept; reject; }; area 0.0.0.0 { interface "tap1" { authentication cryptographic; password "benabela"; }; }; }; ip addr show output without alias adresses: 22: tap1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast qlen 500 link/ether 00:ff:1a:ea:21:0c brd ff:ff:ff:ff:ff:ff inet 1.0.0.2/24 brd 1.0.0.255 scope global tap1 inet6 fe80::2ff:1aff:feea:210c/64 scope link valid_lft forever preferred_lft forever The tap1 and cisco fa0/0 is bridged. The tap1:0 and tap1:1 alias ip now not present (earlier i up and down the alias interfaces) , but cisco show this: 1.0.0.0/24 is subnetted, 1 subnets C 1.0.0.0 is directly connected, FastEthernet0/0 3.0.0.0/32 is subnetted, 1 subnets C 3.0.0.1 is directly connected, Loopback0 O E2 192.0.2.0/24 [110/10000] via 1.0.0.2, 00:28:35, FastEthernet0/0 S* 0.0.0.0/0 is directly connected, Loopback0 Bird show this: bird> sh route 0.0.0.0/0 via 1.0.0.1 on tap1 [ospf1 17:47] E2 (150/10/1) [1] via 10.1.16.1 on eth0 [kernel1 17:44] (10) 1.0.0.0/24 dev tap1 [direct1 17:44] (240) dev tap1 [ospf1 17:47] I (150/10) 2.0.0.0/24 dev tap2 [direct1 17:44] (240) dev tap2 [ospf2 17:44] I (150/10) 10.1.16.0/20 dev eth0 [direct1 17:44] (240) 127.0.0.0/8 dev lo [direct1 17:44] (240) 192.168.252.0/24 dev vmnet2 [direct1 17:44] (240) 192.168.253.0/24 dev vmnet1 [direct1 17:44] (240) 192.168.254.0/24 dev vmnet8 [direct1 17:44] (240) If i up the tap1:0 and tap1:1 22: tap1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast qlen 500 link/ether 00:ff:1a:ea:21:0c brd ff:ff:ff:ff:ff:ff inet 1.0.0.2/24 brd 1.0.0.255 scope global tap1 inet 192.0.2.1/32 brd 192.0.2.255 scope global tap1:0 inet 192.0.2.2/32 brd 192.0.2.255 scope global tap1:1 inet6 fe80::2ff:1aff:feea:210c/64 scope link valid_lft forever preferred_lft forever bird show this: bird> show route 0.0.0.0/0 via 1.0.0.1 on tap1 [ospf1 17:47] E2 (150/10/1) [1] via 10.1.16.1 on eth0 [kernel1 17:44] (10) 1.0.0.0/24 dev tap1 [direct1 17:44] (240) dev tap1 [ospf1 17:47] I (150/10) 2.0.0.0/24 dev tap2 [direct1 17:44] (240) dev tap2 [ospf2 17:44] I (150/10) 10.1.16.0/20 dev eth0 [direct1 17:44] (240) 127.0.0.0/8 dev lo [direct1 17:44] (240) 192.168.252.0/24 dev vmnet2 [direct1 17:44] (240) 192.168.253.0/24 dev vmnet1 [direct1 17:44] (240) 192.168.254.0/24 dev vmnet8 [direct1 17:44] (240) 192.0.2.1/32 dev tap1 [direct1 18:26] (240) 192.0.2.2/32 dev tap1 [direct1 18:27] (240) cisco show this: 1.0.0.0/24 is subnetted, 1 subnets C 1.0.0.0 is directly connected, FastEthernet0/0 3.0.0.0/32 is subnetted, 1 subnets C 3.0.0.1 is directly connected, Loopback0 192.0.2.0/24 is variably subnetted, 3 subnets, 2 masks O E2 192.0.2.2/32 [110/10000] via 1.0.0.2, 00:00:40, FastEthernet0/0 O E2 192.0.2.0/24 [110/10000] via 1.0.0.2, 00:00:40, FastEthernet0/0 O E2 192.0.2.1/32 [110/10000] via 1.0.0.2, 00:00:40, FastEthernet0/0 S* 0.0.0.0/0 is directly connected, Loopback0 Down the tap alias interfaces: bird> show route 0.0.0.0/0 via 1.0.0.1 on tap1 [ospf1 17:47] E2 (150/10/1) [1] via 10.1.16.1 on eth0 [kernel1 17:44] (10) 1.0.0.0/24 dev tap1 [direct1 17:44] (240) dev tap1 [ospf1 17:47] I (150/10) 2.0.0.0/24 dev tap2 [direct1 17:44] (240) dev tap2 [ospf2 17:44] I (150/10) 10.1.16.0/20 dev eth0 [direct1 17:44] (240) 127.0.0.0/8 dev lo [direct1 17:44] (240) 192.168.252.0/24 dev vmnet2 [direct1 17:44] (240) 192.168.253.0/24 dev vmnet1 [direct1 17:44] (240) 192.168.254.0/24 dev vmnet8 [direct1 17:44] (240) But cisco still present some bad routes: 1.0.0.0/24 is subnetted, 1 subnets C 1.0.0.0 is directly connected, FastEthernet0/0 3.0.0.0/32 is subnetted, 1 subnets C 3.0.0.1 is directly connected, Loopback0 O E2 192.0.2.0/24 [110/10000] via 1.0.0.2, 00:04:18, FastEthernet0/0 S* 0.0.0.0/0 is directly connected, Loopback0 So what is the problem? Some debug output from bird: bird: ospf1 < added 192.0.2.0/24 dev tap1 bird: ospf1 < removed 192.0.2.0/24 dev tap1 bird: ospf1 < added 192.0.2.1/32 dev tap1 bird: ospf1 < removed 192.0.2.1/32 dev tap1 bird: ospf1 < added 192.0.2.0/24 dev tap1 bird: ospf1 < removed 192.0.2.0/24 dev tap1 bird: ospf1 < added 192.0.2.0/24 dev tap1 bird: ospf1 < removed 192.0.2.0/24 dev tap1 bird: ospf1 < added 192.0.2.2/32 dev tap1 bird: ospf1 < removed 192.0.2.1/32 dev tap1 bird: ospf1 < removed 192.0.2.2/32 dev tap1 So why produced bird these lines with /24 prefix?: bird: ospf1 < added 192.0.2.0/24 dev tap1 bird: ospf1 < removed 192.0.2.0/24 dev tap1 Thx Csszep

2 6

Bird, Cisco & OSPF problem
by Jarek 05 Oct '09

05 Oct '09

Hi! I have problem with ospf configuration between Linux and Cisco. We have: LAN 10.200.199.0 | Linux (two public interfaces) | | INTERNET | Cisco (one public interface) | LAN 10.200.200.0 Between Linux and Cisco we have two GRE tunnels. I'd like to setup OSPF so gre tunnels will be redundant. On Linux I have: protocol kernel { persist; learn; scan time 20; export all; import all; } protocol device { scan time 10; } protocol direct { interface "*"; } protocol ospf myOSPF { tick 2; export all; import all; area 0 { interface "tunnel*"; }; } On cisco: router ospf 100 router-id 10.200.200.1 log-adjacency-changes network 10.200.200.0 0.0.0.255 area 0 network 192.168.100.68 0.0.0.3 area 0 network 192.168.101.68 0.0.0.3 area 0 192.168.100 and 192.168.101 are tunnel networks. The problem is that probably Linux doesn't send info about directly connected networks to Cisco. In Linux routing table, I see proper route: 10.200.200.0/24 via 192.168.100.70 dev tunnel0 proto bird But on Cisco side, there are only static routes: 85.0.0.0/29 is subnetted, 1 subnets S 85.*.*.* [1/0] via 79.*.*.* 217.*.*.*/30 is subnetted, 1 subnets S 217.*.*.* [1/0] via 79.*.*.* 10.0.0.0/24 is subnetted, 1 subnets C 10.200.200.0 is directly connected, Ethernet0 79.0.0.0/30 is subnetted, 1 subnets C 79.*.*.* is directly connected, Ethernet1 192.168.100.0/30 is subnetted, 1 subnets C 192.168.100.68 is directly connected, Tunnel0 192.168.101.0/30 is subnetted, 1 subnets C 192.168.101.68 is directly connected, Tunnel1 show ip ospf Routing Process "ospf 100" with ID 10.200.200.1 Supports only single TOS(TOS0) routes Supports opaque LSA SPF schedule delay 5 secs, Hold time between two SPFs 10 secs Minimum LSA interval 5 secs. Minimum LSA arrival 1 secs Number of external LSA 76. Checksum Sum 0x2231B2 Number of opaque AS LSA 0. Checksum Sum 0x0 Number of DCbitless external and opaque AS LSA 76 Number of DoNotAge external and opaque AS LSA 0 Number of areas in this router is 1. 1 normal 0 stub 0 nssa External flood list length 0 Area BACKBONE(0) Number of interfaces in this area is 3 Area has no authentication SPF algorithm executed 51 times Area ranges are Number of LSA 3. Checksum Sum 0x36EE Number of opaque link LSA 0. Checksum Sum 0x0 Number of DCbitless LSA 2 Number of indication LSA 0 Number of DoNotAge LSA 0 Flood list length 0 show ip ospf neighbor Neighbor ID Pri State Dead Time Address Interface 10.209.192.2 1 FULL/ - 00:00:38 192.168.100.69 Tunnel0 10.209.192.2 1 FULL/ - 00:00:38 192.168.101.69 Tunnel1 What is wrong ? best regards -- Jarek <jarek(a)poczta.srv.pl>

2 3

feature request: per protocol instance router id
by Csaba Szép 05 Oct '09

05 Oct '09

Hi! Now the router id is global option, it would be great if that is configurable per (ospf) protocol instance like cisco. router ospf 1 router-id 2.0.0.1 log-adjacency-changes area 0.0.0.0 authentication message-digest redistribute static subnets network 2.0.0.0 0.0.0.255 area 0.0.0.0 default-information originate Any chance? thx csszep

2 1

New release 1.1.4
by Ondrej Filip 02 Oct '09

02 Oct '09

Hello! New version is ready. This version includes some minor enhancements and bugfixes. Version 1.1.4 (2009-10-02) o BGP passive option. o Several minor bugfixes. RPM and Debian packages are on-line. Ondrej

2 1

1.1.3 segfaults on seeing certain routes
by KORN Andras 22 Sep '09

22 Sep '09

Hi, Background: I'm completely new to BIRD. I have five locations connected via OpenVPN in a full mesh, using Linux 2.6 routers, and I thought I'd try dynamic instead of static routing. At first I just wanted to see how/what BIRD would do, so I set it to use kernel routing table 3 which I don't use for policy routing. I copied the contents of my other routing tables into table 3 and fired up bird, which promptly segfaulted. gdb shows: #0 0x00007ffff7901210 in strlen () from /lib/libc.so.6 #1 0x000000000043fe3c in bvsnprintf (buf=0x7fffffffdab0 "via 172.18.68.254 on ", size=999999979, fmt=0x441b2b "s", args=0x7fffffffd960) at printf.c:232 #2 0x000000000044071c in bsprintf (buf=0x7fffffffdab0 "via 172.18.68.254 on ", fmt=0x441b20 "via %I on %s") at printf.c:372 #3 0x0000000000403b67 in rt_format_via (e=0x683300, via=0x7fffffffdab0 "via 172.18.68.254 on ") at /tmp/bird-1.1.3/nest/rt-table.c:1052 #4 0x0000000000401ded in rte_trace (p=0x6771c0, e=0x683300, dir=62, msg=0x4419af "added [best]") at /tmp/bird-1.1.3/nest/rt-table.c:142 #5 0x0000000000402b17 in rte_trace_in (flag=2, p=0x6771c0, e=0x683300, msg=0x4419af "added [best]") at /tmp/bird-1.1.3/nest/rt-table.c:150 #6 0x00000000004027bb in rte_recalculate (table=0x674640, net=0x682118, p=0x6771c0, src=0x6771c0, new=0x683300, tmpa=0x0) at /tmp/bird-1.1.3/nest/rt-table.c:436 #7 0x0000000000402d8a in rte_update (table=0x674640, net=0x682118, p=0x6771c0, src=0x6771c0, new=0x683300) at /tmp/bird-1.1.3/nest/rt-table.c:633 #8 0x0000000000439b61 in krt_learn_announce_update (p=0x6771c0, e=0x6830f0) at krt.c:283 #9 0x000000000043a039 in krt_learn_prune (p=0x6771c0) at krt.c:386 #10 0x000000000043a9ae in krt_prune (p=0x6771c0) at krt.c:677 #11 0x000000000043aaea in krt_scan (t=0x67fa60) at krt.c:729 #12 0x000000000043723e in tm_shot () at io.c:355 #13 0x0000000000438d80 in io_loop () at io.c:1260 #14 0x000000000043c5c3 in main (argc=4, argv=0x7fffffffe008) at main.c:471 The following routes are sufficient (but maybe not all of them necessary) to reproduce the segfault: # ip ro sh table 3 172.18.68.254 dev tap5 scope link src 172.18.32.254 10.10.107.0/24 via 172.18.68.254 dev tap5 src 172.18.32.254 192.168.12.0/22 via 172.18.68.254 dev tap5 src 172.18.32.254 172.18.64.0/20 via 172.18.68.254 dev tap5 src 172.18.32.254 The bird config reads as follows: log stderr all; router id 172.18.32.254; debug protocols all; protocol direct { interface "tap1", "tap2", "tap3", "tap5"; } protocol kernel { learn; # Learn all alien routes from the kernel persist; # Don't remove routes on bird shutdown scan time 10; # Scan kernel routing table every 20 seconds export all; # Default is export none kernel table 3; # Kernel table to synchronize with (default: main) } protocol device { scan time 10; # Scan interfaces every 10 seconds } protocol static { } protocol ospf vpn { tick 2; area 0 { interface "tap1", "tap2", "tap3", "tap5" { password "secretsecretsecr"; dead 20; type pointopoint; authentication cryptographic; }; }; } Additionally, when running with an empty table 3 on one of the neighbours of this router, it logged messages like: 21-09-2009 12:55:08 <WARN> Received HELLO packet address (172.18.32.254) is inconsistent with the primary address of interface tap4. It indeed is inconsistent, because all tap interfaces have the same address on each router (specific to the router, with a /32 mask), and I use host routes to make them visible on the other end; effectively, my tap links are point to point. This works perfectly for static routing; I hope BIRD's warning doesn't mean that it ignores that Hello message...? Andras -- Andras Korn <korn at elan.rulez.org> - <http://chardonnay.math.bme.hu/~korn/> Everybody wants to go to heaven, but nobody wants to die.

2 6

Wired Bird BGP behaviour
by Dr. Christian Riede 22 Sep '09

22 Sep '09

Hello, i have the following setup: ISP-Router | --+----------+----------+----------+ NET-ISP | | | | Quagga1 Quagga2 Quagga3 Quagga4 Test-Quagga1 Bird | | | | | | | | | | | | --+-|--------+-|--------+-|--------+-|--------+-|--------+ | NET-1 ----+----------+----------+----------+----------+----------+ NET-2 <-------official productive AS----------> <-- private test AS--> Quagga1-4 belong to our official AS. The Test-Quagga and the Bird use a private AS. All six BGP-Routers in NET-1 and NET-2 are fully meshed with BGP sessions over NET-1 and NET-2. Only Quagga1 and Quagga2 have BGP sessions to the ISP-Router. On Quagga1 and Quagga2, I see about 290000 accepted prefixes on the BGP-sessions to the ISP router and on the two sessions between Quagga1 and Quagga2. On Bird, I also see about 290000 accepted prefixes on all sessions. On Test-Quagga1, I see only 3 accepted prefixes on the sessions to Bird (the direct attached networks). When I shut down all eBGP sessions on Test-Quagga1, I get the expected ~290000 accepted prefixes on the two sessions to the Bird. The routing table grows very slowly. If I stop Bird and start Quagga on the same system, I see all expected ~290000 prefixes on Test-Quagga1 via iBGP. It seems that Bird does not re-announce routes to Test-Quagga1 that it learnt via eBGP if it also receives those routes from Test-Quagga1 via iBGP. This behaviour is different to Quagga. Is my suspicion correct? Can anyone explain this behaviour? What is Bird doing differently than Quagga? Is this a sensible behaviour of Bird? Should/can it be fixed? Mit freundlichen Grüßen Dr. Christian Riede Teamleiter Technik Besuchen Sie uns vom 30.09. bis 02.10.2009 auf der Fachmesse www.SAFEKON.de auf dem Stand E.08 der Karlsruher IT-Sicherheitsinitiative (www.ka-it-si.de) -- _________________________________________ =C=O=N=N=E=C=T== Karlsruhe GmbH Computer und Netzwerktechnik Gebrüder-Himmelheber-Straße 7 D-76135 Karlsruhe Amtsgericht Mannheim HRB 110258 Geschäftsführer: Stefan Kratzer Telefon: +49 (0) 721 20120-0 Telefax: +49 (0) 721 20120-500 Internet: www.it-connect.de E-Mail: christian.riede(a)it-connect.de _________________________________________

4 8

BIRD 1.1.3 doesn't build with IPv6 enabled
by Frederic Jaeckel 18 Sep '09

18 Sep '09

Hi there, I tried building BIRD with IPv6 support (--enable-ipv6) on NetBSD (sparc64) today and sadly it failed.. Maybe this is a known issue but I also wanted to report it. :) Complete output: http://nopaste.com/p/abckbQBXq regards, Frederic

2 4

bug found: as-path prepending
by Wolfgang Hennerbichler 18 Sep '09

18 Sep '09

Hi Guys, I found a bug which crashes bird; It seems to be sufficient to use this import filter in a pipe: import filter { if source=RTS_BGP then bgp_path.prepend(1); }; this crashes my bird (amd64). Does it crash yours, too? Wolfgang -- www.vix.at | www.aco.net wh(a)univie.ac.at | WH844-RIPE Vienna University Computer Center

2 3

AS-Path prepending in Pipes or Filters
by Wolfgang Hennerbichler 17 Sep '09

17 Sep '09

Dear BIRD-Users, I'm currently investigating if it's possible to do as-path prepending in bird in filters or pipes. What I could find was this: bgppath BGP path is a list of autonomous system numbers. You can't write literals of this type. too bad. The goal would be to be able to do a prepending per peer within a pipe or filter. Does Anybody know if this is possible? Wolfgang -- www.vix.at | www.aco.net wh(a)univie.ac.at | WH844-RIPE Vienna University Computer Center

3 3

New release 1.1.3
by Ondrej Filip 17 Sep '09

17 Sep '09

Hello! New version is ready. This version includes two important bug fixes: Version 1.1.3 (2009-09-11) o Bugfix in core o Bugfix in BGP related to AS2->AS4 conversion. RPM and Debian packages are on-line. Ondrej

4 10