- Bird-users - Mailing Lists

Re[2]: Problem with redistribute static routes from venet (openvz pseudointerface)
by Łukasz Chrustek 21 Mar '11

21 Mar '11

Witam, > On Sun, Mar 20, 2011 at 10:33:12PM +0100, Łukasz Chrustek wrote: >> Hello, >> >> I would like to import routes (ips exactly, with netmask /32) added by >> openvz virtualization to main ruting kernel table, when the >> virtualization system starts. I don't want to be misunderstand, but in >> quagga it works :), and I would like to test (and switch to) bird. >> Unfortunetly in bird I can't see the routes(ips) from venet0, see >> below. My configuration (most important parts, if You think You will >> need more, please let me now): > Handling device routes in BIRD is a bit tricky - there are two sides > of the problem - import to the BIRD table and export to the kernel table. > (so first is to see the routes in 'show route'). > So i understand it correctly that you want to import the routes from > one kernel table and export them to another? (as i see that they already > are in 'ip route ls t 254'). I want to see routes from venet0 in main kernel ruting table # ip route ls t 254 X.Y.10.61 dev venet0 scope link X.Y.10.60 dev venet0 scope link 192.168.1.51 dev venet0 scope link 192.168.1.140 dev venet0 scope link X.Y.10.64 dev venet0 scope link X.Y.10.65 dev venet0 scope link X.Y.11.0/29 dev eth0 proto kernel scope link src X.Y.11.3 10.1.1.0/24 dev eth1 proto kernel scope link src 10.1.1.0 default via X.Y.11.1 dev eth0 onlink in ruting table in bird (to use them to redistribute to ospf latly), but in bird I see only those routes: bird> show route 0.0.0.0/0 via X.Y.11.1 on eth0 [kernel1 22:10] * (10) 10.1.1.0/24 dev eth1 [MyOSPF 22:10] * I (150/10) [X.Y.11.3] X.Y.11.0/29 dev eth0 [MyOSPF 22:10] * I (150/10) [X.Y.11.3] >> protocol direct { >> interface "-eth*", "venet*"; # Restrict network interfaces it works with >> } > Direct would not generate these routes, because they are not addresses assigned > to the iface (in output 'ip a l') Ok, I understand and I figure this out by bringing up another iface on this server (eth1), the 10.1.1.0/24 route shows up in bird routing table. >> protocol kernel { >> learn; # Learn all alien routes from the kernel >> persist; # Don't remove routes on bird shutdown >> scan time 20; # Scan kernel routing table every 20 seconds >> # import none; # Default is import all >> import all; >> export all; # Default is export none >> # kernel table 5; # Kernel table to synchronize with (default: main) >> kernel table 254; >> } > Kernel protocol with learn may generate these routes, but there is an > exception for device routes in sysdep/linux/netlink/netlink.c:848 : > /* > * In Linux IPv6, 'native' device routes have proto > * RTPROT_BOOT and not RTPROT_KERNEL (which they have in > * IPv4 and which is expected). We cannot distinguish > * 'native' and user defined device routes, so we ignore all > * such device routes and for consistency, we have the same > * behavior in IPv4. Anyway, users should use RTPROT_STATIC > * for their 'alien' routes. > */ > if (i->rtm_protocol == RTPROT_BOOT) > src = KRT_SRC_KERNEL; > If you remove these two lines and recompile BIRD, you could probably > be able to import device routes. OK, if there won't be any other solution I will check it, thank You. >> protocol static { >> import all; >> #route X.Y.10.61/32 via "venet0"; >> #route X.Y.10.60/32 via "venet0"; >> #route 192.168.1.51/32 via "venet0"; >> #route 192.168.1.140/32 via "venet0"; >> #route X.Y.10.64/32 via "venet0"; >> #route X.Y.10.65/32 via "venet0"; >> } > This should work (if they are uncommented). Unfortunetly, it doesn't work either. > Second thing is to export the routes to the kernel table. > If the routes are from something different than static, > you should use 'device routes' option of kernel protocol > to really allow export of device routes. OK, I will try this in a moment. -- Regards, Łukasz Chrustek

1 1

Problem with redistribute static routes from venet (openvz pseudointerface)
by Łukasz Chrustek 21 Mar '11

21 Mar '11

Hello, I would like to import routes (ips exactly, with netmask /32) added by openvz virtualization to main ruting kernel table, when the virtualization system starts. I don't want to be misunderstand, but in quagga it works :), and I would like to test (and switch to) bird. Unfortunetly in bird I can't see the routes(ips) from venet0, see below. My configuration (most important parts, if You think You will need more, please let me now): protocol direct { interface "-eth*", "venet*"; # Restrict network interfaces it works with } protocol kernel { learn; # Learn all alien routes from the kernel persist; # Don't remove routes on bird shutdown scan time 20; # Scan kernel routing table every 20 seconds # import none; # Default is import all import all; export all; # Default is export none # kernel table 5; # Kernel table to synchronize with (default: main) kernel table 254; } protocol static { import all; #route X.Y.10.61/32 via "venet0"; #route X.Y.10.60/32 via "venet0"; #route 192.168.1.51/32 via "venet0"; #route 192.168.1.140/32 via "venet0"; #route X.Y.10.64/32 via "venet0"; #route X.Y.10.65/32 via "venet0"; } Above configuration (with route) doesn't work either, so I commented this out. protocol ospf MyOSPF { tick 2; import all; export all; # export filter { # ospf_metric1 = 1000; # if source = RTS_STATIC then accept; else reject; # }; # rfc1583compat yes; area 0.0.0.0 { #networks { # X.Y.10.65/32; #}; }; As You can see, I tried some configuration, none worked. The main table looks like this: # ip route ls t 254 X.Y.10.61 dev venet0 scope link X.Y.10.60 dev venet0 scope link 192.168.1.51 dev venet0 scope link 192.168.1.140 dev venet0 scope link X.Y.10.64 dev venet0 scope link X.Y.10.65 dev venet0 scope link X.Y.11.0/29 dev eth0 proto kernel scope link src X.Y.11.3 10.1.1.0/24 dev eth1 proto kernel scope link src 10.1.1.0 default via X.Y.11.1 dev eth0 onlink and in birdc: bird> show route 0.0.0.0/0 via X.Y.11.1 on eth0 [kernel1 22:10] * (10) 10.1.1.0/24 dev eth1 [MyOSPF 22:10] * I (150/10) [X.Y.11.3] X.Y.11.0/29 dev eth0 [MyOSPF 22:10] * I (150/10) [X.Y.11.3] # ip a l 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc sfq state UP qlen 1000 link/ether 00:21:85:3c:f5:76 brd ff:ff:ff:ff:ff:ff inet X.Y.11.3/29 brd X.Y.11.7 scope global eth0 inet6 fe80::221:85ff:fe3c:f576/64 scope link valid_lft forever preferred_lft forever 3: eth1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN qlen 1000 link/ether 00:21:85:3c:f5:77 brd ff:ff:ff:ff:ff:ff inet 10.1.1.0/24 scope global eth1 5: venet0: <BROADCAST,POINTOPOINT,NOARP,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN link/void inet6 fe80::1/128 scope link valid_lft forever preferred_lft forever -- greets from Poland, Łukasz Chrustek

3 2

Re: Peering group
by Ondrej Zajicek 20 Mar '11

20 Mar '11

On Thu, Mar 17, 2011 at 11:54:21AM +0100, Anibe Onuche wrote: > Hello All, > > > > I want to implement a peer group in Bird. > > Some peers have the same configuration and template, they only differ on > their IP address. BIRD does not implement peer groups. You could define parametric functions for import/export filters, but you have to use for example shell to generate config based on templates. -- 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."

1 0

Peering group
by Anibe Onuche 17 Mar '11

17 Mar '11

Hello All, I want to implement a peer group in Bird. Some peers have the same configuration and template, they only differ on their IP address. The configuration and implementation would be highly appreciated Warm Regards Anibe O.

1 0

RPKI extension
by Matthias Waehlisch 14 Mar '11

14 Mar '11

Hi folks, is anyone working on an extension of BIRD to allow for RPKI? Thanks matthias -- Matthias Waehlisch . Freie Universitaet Berlin, Inst. fuer Informatik, AG CST . Takustr. 9, D-14195 Berlin, Germany .. mailto:waehlisch@ieee.org .. http://www.inf.fu-berlin.de/~waehl :. Also: http://inet.cpt.haw-hamburg.de .. http://www.link-lab.net

2 1

PI addresses and BIRD
by Виталий Сергеевич 13 Mar '11

13 Mar '11

Hello, tell me please, to which interface I need to bind PI address? lo? eth0? I have 91.XXX.XXX.0/23 network and local address 172.11.22.1 (eth0). Can I make an alias on eth0 (ip addr add 91.XXX.XXX.1/23 dev eth0)? Or the right thing to do somehow different?

2 1

BIRD Wiki
by Ondrej Zajicek 10 Mar '11

10 Mar '11

Hello I found that there is already one running (empty) wiki as a part of Redmine project management webapp used for BIRD. I added some examples and FAQs for a start: https://git.nic.cz/redmine/projects/bird/wiki You could try to register and edit it. -- 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."

3 10

dynamic export filter based on interface/peering partner
by Arjan Filius 10 Mar '11

10 Mar '11

Hello bird users, i'd like to do some traffic engineering incoming traffic perferred in a central function/filter like the "filter bgp_out {} " i'm using On every peering partner i'd like to have that same export bgp_out filter, and basically i tried some things, but it didn't work out. What i tried is: filter bgp_out { <snip> if ( ( proto = "JointTransit_IPv4_177_NIKHEF" ) || ( proto = "JointTransit_IPv4_178_Telecity2" ) ) then { bgp_path.prepend(OURAS); } <snip> } extra prepend based on proto didn't work (for me). Selection on neighbor AS isn't the most suitable for me as at least one neighbor AS comes trough an "expensive" bgp proto and a "cheap" one. How does one do this, or how would i do this? Currently i needed to get the job done, and created multiple bgp_out_?? filters, and used them in the bgp proto definitions. Thanks in advance, Regards, -- Arjan Filius mailto:iafilius@xs4all.nl

2 1

Socket Error on OpenBSD 4.8
by bird＠hkbsd.com 09 Mar '11

09 Mar '11

Dear all, Any one see the error before? It keep generate from bird and bird6 Tried to reboot but this message is come again once the ospf is up. bird: OSPF: Socket error: No buffer space available Rgds Derek

1 1

Bird and loopback addresses
by Ruben Laban 08 Mar '11

08 Mar '11

(resending with proper from address) Hello, It seems that bird ignores any interfaces / ip addresses which have a subnet mask of 255.255.255.255. This seems to apply to both BGP as OSPF. An interface configured with A.B.C.D/E (E<32) seems to be picked up just fine, whereas configuring it A.B.C.D/32 and a route to A.B.C.D/E does not result in the interface to be picked. I'm quite sure I'm missing something trivial here, but I can't seem to figure out what exactly. Regards, Ruben Laban

2 2