- Bird-users - Mailing Lists

OSPF weird behaviour
by Eugene M. Zheganin 30 Jan '14

30 Jan '14

Hi. I'm running bird in a large (well, meaning enterprise large, not ISP large) network. I'm using mostly 1.3.11/1.4.0 versions, and FreeBSD on all of the servers that are running bird. My network consists of several network hubs, that local branche offices are attached to. These hubs reside in large cities, and most of them are running some dynamic routing protocols aside from OSPF (BGP and RIP). Of course I'm writing this post not to share this useless information, but to describe a problem that I have. This problem involves two network sites, lets call them A and B. A consists of several networks and several routers, this is a largest site in my network, and site B consists of two bird routers running FreeBSD with VRRP/CARP (one active in each moment) and two dozens of branch offices, running mostly FreeBSD/quagga (they were deployed before I started using bird), and some of them running Cisco IOS/RIP. Site A and B are connected via a gre tunnel and OSPF in it. The problem is, that in some random moment site A receives a route announce from site B containing a route that clearly belongs to a site A. I know this behavior is typical to distance-vector protocol, not for a link state protocol, and it's kind of an impossible situation, but this is exactly what I'm seeing in birdc. The router at site A indicates that it received a route from router at B via OSPF, but in the same time the B router claims that this route clearly points to A. for instance: A: # birdc BIRD 1.3.11 ready. bird> show route for 192.168.7.0 192.168.7.0/24 via 172.16.0.95 on gre13 [ospfv4 10:08] ! E2 (150/10/10000) [192.168.21.2] via 192.168.3.22 on vlan1 [kernel1 10:17] (10) (I manually deleted a 192.168.7.0/24 route from kernel and added one via 192.168.3.22 to solve this temporarily, so OSPF route is this troubled announce) # ifconfig gre13 gre13: flags=b051<UP,POINTOPOINT,RUNNING,LINK0,LINK1,MULTICAST> metric 0 mtu 1476 tunnel inet 89.250.210.69 --> 94.159.37.114 inet 172.16.0.94 --> 172.16.0.95 netmask 0xffffffff inet6 fe80::21a:64ff:fe21:8e80%gre13 prefixlen 64 scopeid 0x1f nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL> B: [emz@moscow-alpha:~]# birdc BIRD 1.4.0 ready. bird> show route 192.168.7.0/24 192.168.7.0/24 via 172.16.0.94 on gre0 [ospfv4 08:08:30] * E2 (150/20/10000) [192.168.3.22] bird> # ifconfig gre0 gre0: flags=b051<UP,POINTOPOINT,RUNNING,LINK0,LINK1,MULTICAST> metric 0 mtu 1476 tunnel inet 94.159.37.114 --> 89.250.210.69 inet 172.16.0.95 --> 172.16.0.94 netmask 0xffffffff inet6 fe80::21a:64ff:fe21:96d5%gre0 prefixlen 64 tentative scopeid 0x8 nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL> I know that this information isn't enough to diagnose the problem, and I wanted to know what should I get to help diagnose this. I should say also, that at this time I get like 100 megabytes per day of bird logs consisting mostly of 'OSPF: LSA disappeared [...]' messages, and, since I get this issue one or two times per month, running bird with full OSPF debug will produce even more. Thanks. Eugene.

2 2

OSPFv2 causes AXUPD link destruction
by Gustavo Ponza 28 Jan '14

28 Jan '14

Hi all, coming back to the 'bird' operation on my hamradio site after two years, or perhaps more, I noted that the actual bird version(s) and including the today 'git' version cause the destruction of AXUDP links of another hamradio application (XNET) which is running on the same 'linux box'. No problem at all with the very fisrt 1.3.x BIRD releases in the same identical situation. I'm running the OSPFv2 by using the following configuration: protocol ospf { tick 2; # rfc1583compat yes; area 0.0.0.254 { stub no; networks { 44.208.0.0/16; 44.134.32.0/24; 44.134.33.0/24; 10.0.0.0/8; }; interface "ax0" { stub; }; interface "ax1" { stub; }; interface "sl0" { stub; }; interface "tun0" { stub; }; interface "ppp0" { type ptp; }; interface "tap0" { type broadcast; }; interface "eth*" { type broadcast; }; }; } Now, my XNET application, apart the AXUDP links towards other XNET or similar nodes, is liked to the linux 'slip' sl0' interface (SDEV0) and to the AX25 'ax0' interface (SDEV1). SDEV0 : SLIP Driver: 38400 Baud SDEV1 : KISS Driver: 38400 Baud However the OSPFv2 (and probably the RIPv2 not yet running here) seems to run OK on its routing task. gus i0ojj

1 0

Re: OSPF dont import routes from LSAdb
by 曾小小 28 Jan '14

28 Jan '14

hi, everybody I have encountered similar problems. My bird version is 1.3.10 I have three devices R0-2, R0 and R1 establish OSPF connections for instance 1, area 20, R0 and R2 establish OSPF connections for instance 2, area 30. I have the same configuration of R1 and R2, just ip address, route-id different: # About R2 ospf configuration filter export_OSPF { if (net = 0.0.0.0 / 0) then { print "net rejected:", net; ospf_metric2 = 20; reject; } if (net = a.b.c.0/24) then { print "net accepted:", net; ospf_metric2 = 20; accept; } reject; } filter import_OSPF { if (net = 0.0.0.0 / 0) then { print "net accepted:", net; ospf_metric2 = 20; accept; } reject; } protocol ospf ospf_business { router id e.f.g.h; debug all; export filter export_OSPF; import filter import_OSPF; area 0.0.0.30 { interface "vlanx" { hello 10; retransmit 5; cost 10; transmit delay 1; dead count 4; wait 40; # Type pointopoint; type broadcast; # Type pointomultipoint; # Priority 0; authentication cryptographic; password "pass"; }; }; } On R0 distribute the default route, you can receive from R0 default route on R1: R1: bird> show ospf lsadb ospf_business 1017-Global Type LS ID Router Age Sequence Checksum 0005 0.0.0.0 x.y.z.1 774 80000533 bf32 Area 0.0.0.20 Type LS ID Router Age Sequence Checksum 0001 x.y.z.1 x.y.z.1 855 80000554 f760 0001 x.y.z.3 x.y.z.3 837 80000552 9ab0 bird> show route protocol ospf_business 1007-0.0.0.0 / 0 via x.y.z.1 on vlan43 [ospf_business 11:24] * E2 (150/10/20) [1] [x.y.z.1] # I can receive from R0 about default route lsadb in R2's lsadb. bird> show ospf lsadb ospf_business 1017 - Global Type LS ID Router Age Sequence Checksum 0005 0.0.0.0 x.y.z.11 481 8000000d ba52 Area 0.0.0.30 Type LS ID Router Age Sequence Checksum 0001 x.y.z.11 x.y.z.11 481 8000054f 829a 0001 x.y.z.12 x.y.z.12 118 8000054a 25ef However, in the routing table, I can not see the default route. Why? Thanks.

2 2

BIRD crashing when disabled OSPF protocol state is requested
by Ondřej Caletka 23 Jan '14

23 Jan '14

Hi, I think I found a bug in BIRD (tested with versions 1.3.9 and 1.4.0). When OSPF state is requested for a disabled OSPF protocol, the BIRD process segfaults. Steps to reproduce: 1. use this bird.conf: ----cut here---- protocol device { scan time 10; } protocol kernel { persist; } protocol ospf something { disabled; area 0.0.0.0 { interface "dummy*"; }; } ----cut here---- 2. run bird 3. query for protocol state: # birdc show ospf state something 4. BIRD crashes I guess there is some null-pointer dereference in the ospf_sh_state function. Regards, Ondřej Caletka, CESNET

2 1

about per_connection and per_packet
by 曾小小 23 Jan '14

23 Jan '14

hi, My system is Ubuntu 13.04, kernel version is 3.8.0-21-generic, bird version is 1.3.10. In order to achieve two functions in r0: Use ecmp functions to achieve load balancing. Using iptables connmark modules in solving the problem of address overlap. I have two devices r0-1, I used the bird's ospf and ecmp function, r0 can learn from r1 to the twodefault route. As follows: default proto bird nexthop via 192.168.0.1 dev tun1 weight 3 nexthop via 192.168.0.2 dev tun2 weight 1 I use tcpdump, Ethereal found on r0 data is based per_packet forwarded to r1. But I'm on r0 configured conntrack. If I use conntrack, so my data from r0 to r1 will generate about connection problems. How do I solve it. Whether per_connection function can solve this connection problem? How to open per_connection on ubuntu system? Thanks for the help you provided earlier, thanks again ...

1 0

Fwd: BIRD unable to read data from TUN/TAP device
by Cyrill Gössi 17 Jan '14

17 Jan '14

Thank you very much for getting back to me in this matter! As for my scenario: in the long run I need to be able to let a single BIRD process run as many as 10000 OSPF protocol instances, each of which communicating locally over an individual TUN/TAP device. In the end, a single Linux system therefore has to be able to support 10000 TUN/TAP devices. As for your ideas and suggestions to check: Having tap1 and tap2 on one system, I'm able to ping tap2 via tap1. Running OSPF in NBMA mode resulted in no messages received by the tap devices at all. I updated my stackoverflow question and included also a strace()-extract of BIRD. In it you see the setup of a socket for a tap device and the inclusion of the file-descriptor for this socket into the set of descriptors observed by the selcet() system call. But unfortunately select() never notices any data ready to be read by this socket file-descriptor. With the additional information about my scenario and the results of your ideas and suggestions, I kindly ask you to take another look at the updated question on stackoverflow. I'm thankful for all the time you or somebody else will invest into supporting me in this matter! Best, Cyrill 2014/1/15 Ondrej Zajicek <santiago(a)crfreenet.org> > On Mon, Jan 13, 2014 at 02:01:48PM +0100, Cyrill Gössi wrote: > > Hi > > > > I'm trying to let BIRD communicate over virtual network devices created > by > > the Linux TUN/TAP module. > > > > As it seems the tap devices receive the messages from BIRD. However, BIRD > > does not seem to receive the messages sent to it over the tap device. > > > > I described the scenario and the issues I run into in more detail on > > stackoverflow. > > I am not sure if i understand your scenario, but if you run both TUN/TAP > endpoints on one machine, i would be surprised if OS network code wouldn't > be confused by that. If not, you should try ping and try to run OSPF > in NBMA mode (which will use just unicasts). > > > If somebody has some experience with running BIRD over TUN/TAP devices, > > Generally, it works over OpenVPN tunnels, which use TUN/TAP devices, > but in that cases both endpoints are on different machines. > > -- > 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." > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.9 (GNU/Linux) > > iEYEARECAAYFAlLVz2YACgkQw1GB2RHercOUBACgiI8lV1yRxeTp5tCaMVNvZ9hf > 8TkAnjppe/ei6PnHmEiiJ3Fhp6PAEN+Z > =FDol > -----END PGP SIGNATURE----- > >

1 0

OSPFv3 (IPv6) Router ID handling
by arno.odermatt＠ch.schindler.com 15 Jan '14

15 Jan '14

Hi, I am evaluating an OSPF solution with bird for IPv4 and IPv6. Tests are all working fine. For IPv4, there is no explicit configuration regarding the router ID (# Override router ID #router id 198.51.100.1; works find) required, BIRD as other OSPF router simply collects and selects a local IP address (lowest or highest value) out of one of the locally existing NIC's addressing. This is nice, since all of the config's within an OSPF areas might look the same and configuration effort is minimized. Unfortunately, with OSPFv3 for IPv6, this seems not to behave the same, therefore configuration effort an a explicit router ID concept is required , when setting up and deploying further IPv6 OSPF routing instances. Can this be solved somehow? freundlich grüsst, kind regards, _________________________ _________________________ _________________________ _________________________ _________________________ ________________ Arno Odermatt arno.odermatt(a)ch.schindler.com ****************************************************** Notice: The information contained in this message is intended only for use of the individual(s) named above and may contain confidential, proprietary or legally privileged information. No confidentiality or privilege is waived or lost by any mistransmission. If you are not the intended recipient of this message you are hereby notified that you must not use, disseminate , copy it in any form or take any action in reliance of it. If you have received this message in error please delete it and any copies of it and notify the sender immediately. *******************************************************

2 1

BIRD unable to read data from TUN/TAP device
by Cyrill Gössi 14 Jan '14

14 Jan '14

Hi I'm trying to let BIRD communicate over virtual network devices created by the Linux TUN/TAP module. As it seems the tap devices receive the messages from BIRD. However, BIRD does not seem to receive the messages sent to it over the tap device. I described the scenario and the issues I run into in more detail on stackoverflow. If somebody has some experience with running BIRD over TUN/TAP devices, please take a look here: http://stackoverflow.com/questions/21001713/linux-tun-tap-unable-to-read-da… Much thanks to anybody that can provied me with some insights into the issue! Best, Cyrill

2 1

OSPF getting forwarding address wrong
by Tore Anderson 14 Jan '14

14 Jan '14

Hi, My anycast nodes exports the availability of their services by configuring /32s configured on the loopback intefaces. These are in turn exported to the OSPF protocol running on bond0: $ birdc 'show interfaces' BIRD 1.3.11 ready. lo up (index=1) MultiAccess AdminUp LinkUp Loopback Ignored MTU=65536 192.0.2.1/32 (Primary, scope univ) 127.0.0.1/8 (Unselected, scope host) 192.0.2.2/32 (Unselected, scope univ) 192.0.2.5/32 (Unselected, scope univ) 192.0.2.3/32 (Unselected, scope univ) 192.0.2.4/32 (Unselected, scope univ) 192.0.2.6/32 (Unselected, scope univ) [..skipping DOWN ifs...] bond0 up (index=6) MultiAccess Broadcast Multicast AdminUp LinkUp MTU=1500 192.0.2.114/28 (Primary, scope univ) Now, there are something strange going on here. Sometimes, and I have not yet been able to understand when or how or why it happens, the resulting Type-7 LSAs that get sent to the upstream router has a forwarding address that is one of the other service addresses configured on "lo", instead of the actual address on "bond0". The upstream router (running JUNOS) doesn't install these routes in its forwarding table, which means that the anycasted service doesn't attract the traffic as it should. This is what the router sees: tore@rtr> show ospf database lsa-id 192.0.2.1 extensive Area 1.2.3.4 Type ID Adv Rtr Seq Age Opt Cksum Len NSSA 192.0.2.1 192.0.2.114 0x8000122a 1145 0x8 0x90ab 36 mask 255.255.255.255 Topology default (ID 0) Type: 2, Metric: 10000, Fwd addr: 192.0.2.114, Tag: 0.0.0.0 Aging timer 00:40:55 Installed 00:19:04 ago, expires in 00:40:55, sent 00:19:02 ago Last changed 13w5d 21:57:44 ago, Change count: 1 Standby flood status Idle {master:0} tore@rtr> show ospf database lsa-id 192.0.2.2 extensive Area 1.2.3.4 Type ID Adv Rtr Seq Age Opt Cksum Len NSSA 192.0.2.2 192.0.2.114 0x800000e8 1388 0x8 0x51a9 36 mask 255.255.255.255 Topology default (ID 0) Type: 2, Metric: 10000, Fwd addr: 192.0.2.6, Tag: 0.0.0.0 Aging timer 00:36:51 Installed 00:23:07 ago, expires in 00:36:52, sent 00:23:05 ago Last changed 4d 19:56:46 ago, Change count: 1 Standby flood status Idle I have confirmed with tcpdump running on the anycast node that the forwarding address in the LS-Update packets sent by BIRD is indeed 192.0.2.6. So at the time of writing, I have the following: LSA-ID 192.0.2.1: forwarding address 192.0.2.114 (works fine) LSA-ID 192.0.2.2: forwarding address 192.0.2.6 (doesn't work) LSA-ID 192.0.2.3: forwarding address 192.0.2.6 (doesn't work) LSA-ID 192.0.2.4: forwarding address 192.0.2.6 (doesn't work) LSA-ID 192.0.2.5: forwarding address 192.0.2.6 (doesn't work) LSA-ID 192.0.2.6: forwarding address 192.0.2.114 (works fine) The only way I've found to actually fix this is to remove and re-add the address: $ ip address del 87.238.33.2/32 dev lo $ ip address add 87.238.33.2/32 dev lo This causes BIRD to re-send the LS-Update with 192.0.2.114 and now the JUNOS route installs it to its FIB and the anycast service starts receiving traffic. The remaining three addresses remain defective. Question is: Why is this happening? Bug, or am I doing something wrong? Tore

2 1

BIRD unable to read date from TUN/TAP device
by Cyrill Gössi 13 Jan '14

13 Jan '14

Hi I'm trying to let BIRD communicate over virtual network devices created by the Linux TUN/TAP module. As it seems the tap devices receive the messages from BIRD. However, BIRD does not seem to receive the messages sent to it over the tap device. I described the scenario and the issues I run into in more detail on stackoverflow. If somebody has some experience with running BIRD over TUN/TAP devices, please take a look here: http://stackoverflow.com/questions/21001713/linux-tun-tap-unable-to-read-da… Much thanks to anybody that can provied me with some insights into the issue! Best, Cyrill

1 0