July 2016 - Bird-users - Mailing Lists

[PATCH 2/7] Babel: Immediately send a hello on interface reconfigure.
by Toke Høiland-Jørgensen 19 Jul '16

19 Jul '16

An interface reconfiguration may change the hello interval. Section 3.4.1 of the RFC specifies that either the change shouldn't be applied until the next hello is due, or an additional hello should be sent immediately. This does the latter. Signed-off-by: Toke Høiland-Jørgensen <toke(a)toke.dk> --- proto/babel/babel.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/proto/babel/babel.c b/proto/babel/babel.c index 8e104d6..4b28f69 100644 --- a/proto/babel/babel.c +++ b/proto/babel/babel.c @@ -1539,7 +1539,10 @@ babel_reconfigure_iface(struct babel_proto *p, struct babel_iface *ifa, struct b babel_iface_update_state(ifa); if (ifa->up) + { + babel_send_hello(ifa, 0); babel_iface_kick_timer(ifa); + } return 1; } -- 2.8.0

2 2

selctive route download
by Harish Venkatraman 18 Jul '16

18 Jul '16

Hi, Can someone help me in selective route download using bird?. I did not see any specific configs. Secondly I don't want the routes learnt by bgp peers to be installed in the kernel but only routes that are stored in a file through some application to be downloaded to the kernel how do i do it?. The file can have both prefixes and next-hops or just prefixes? Any help is much appreciated. Thanks,

3 2

BGP communities attached to prefix issue
by Javor Kliachev 07 Jul '16

07 Jul '16

Hello, We use BIRD as route server with the well-known "BGP Community policy based filtering" as in most of all other IXP with the following type: * /Do not announce a prefix to a certain peer: 0:peer-as/ * /Announce a prefix to a certain peer: IXP_AS:peer-as/ * /Do not announce a prefix to any peer: 0:IXP_AS/ * /Announce a prefix to all peers: IXP_AS:IXP_AS/ But recently we came across the following case: A member of our IXP is sending his prefixes with attached a huge count of BGP communities ( ~ 750 pcs ) Each of the attached community has following type: 0:ASN ( peer-as ). We see that BIRD accepts these prefixes from member but it return the following error notification: 2016-06-30 10:06:59 <ERR> R0_248: Attribute list too long, skipping corresponding routes 2016-06-30 10:06:59 <ERR> R0_248: - route *x.x.x.0/24* skipped In the same time I'm able to see the prefixes that are exported fine to all member RIBs(for which there is no prohibiting with 0:ASN) via pipes but in spite of that , the prefix is not advertised to any peer over eBGP protocol. In addition at the same time I'm able to see that the prefixes persist into the RIB and BIRD shows that they're advertised but obviously this is not a true. Here is the output with a brief explanation of our scenario:* *R0_248**- protocol BGP of member that should accept the prefixes R0_132 - protocol BGP of the member that sends the prefixes with the huge count of communities. 10.0.0.132 - the peer from protocol R0_132 T60230 - connected table to R0_248 Prefix: *x.x.x.0/24* - prefix with ~750 communities. /# birdc "show route export R0_248 //*x.x.x.0/24*//all"/ *x.x.x.0/24* via 10.0.0.132 on eth0 [R0_132 10:01:33] * (100) [ASxxxxi] Type: BGP unicast univ BGP.origin: IGP /BGP.as_path: yyyy xxxx/ BGP.next_hop: 10.0.0.132 BGP.med: 1000 BGP.local_pref: 100 BGP.community: (64700,44217) (1,1082) (65400,65400) (65400,0) (0,42) (0,251) (0,286) (0,553) (0,680) (0,702) (0,714) (0,1239) (0,1241) (0,1248) (0,1267) (0,1273) (0,1547) (0,1668) (0,1680) (0,1764) (0,2119) (0,2484) (0,2603) (0,2613) (0,2635) (0,2686) (0,2818) (0,2828) (0,2854) (0,2857) (0,2906) (0,2914) (0,3209) (0,3216) (0,3223) (0,3225) (0,3252) (0,3255) (0,3257) (0,3292) (0,3303) (0,3320) (0,3327) (0,3356) (0,3491) (0,3549) (0,3561) (0,3741) (0,3786) (0,3856) (0,3910) (0,4134) ...................................................................... ...................................................................... ...................................................................... (0,4589) (0,4637) (0,4651) (0,4657) (0,4766) (0,4788) (0,4809) (0,5089) (0,5391) (0,5400) (0,5404) (0,5409) (0,5410) (0,5413) (0,5430) (0,5466) (0,5483) (0,5539) (0,5563) (0,5578) (0,5588) (0,5603) (0,5605) (0,5713) (0,6083) (0,60280) (0,60294) (0,60404) (0,60447) (0,60764) (0,60868) (0,61186) (0,61244) (0,61266) (0,61317) (0,61438) (0,61955) (0,62023) (0,62044) (0,62093) (0,62325) (0,62336) (0,62363) (0,62955) (0,63199) (0,63311) (0,63949) (0,64597) (44217,1039) (44217,1049) (44217,1053) (44217,1064) (44217,1074) (44217,9101) # birdc "show route table T60230 /*x.x.x.0/24*/" /*x.x.x.0/24*/ via 10.0.0.132 on eth0 [R0_132 10:01:33] * (100) [ASxxxxi] Our BIRD version is 1.4.5 We have tried with the latest 1.6.0 but there is no effect. Furthermore during our troubleshooting as a separate issue we have observed that we can't add more than ~505 communities to a given prefix. I hope this information will be useful for resolving this issue. Any ideas or thoughts are highly appreciated! Thanks in advance! -- Javor Kliachev Senior IP Engineer tel: +359 2 975 16 16; fax: +359 2 975 34 36; mob: +359 885 988 495; web: www.neterra.net <https://bg.linkedin.com/pub/javor-kliachev/11/b46/843>

3 3

BGP- bad message length error..
by Harish Venkatraman 07 Jul '16

07 Jul '16

I am using bird 1.6.0 and tried to establish ibgp session iam getting the following error. The local as is 60. when do we get this error? Any help is much appreciated. Jul 06 23:53:46 linux-01 systemd[1]: Started BIRD Internet Routing Daemon (IPv4). Jul 06 23:53:46 linux-01 bird[3625]: Started Jul 06 23:53:46 linux-01 bird[3625]: 2016-07-06 23:53:46 <INFO> Started Jul 06 23:54:08 linux-01 bird[3625]: bgp_60: Error: Bad message length: 0037 Jul 06 23:54:08 linux-01 bird[3625]: 2016-07-06 23:54:08 <RMT> bgp_60: Error: Bad mess...037

3 2

ifname in filters
by Alexander Velkov 04 Jul '16

04 Jul '16

Hello, I would like to configure RIP with different ACLs set on different RIP interfaces. For this purpose I thought I could use the '*ifname*' route attribute in bird filters. The problem I am facing is that when I use it, no RIP routes are announced at all, so maybe I am using a wrong syntax. If I don't use the *ifname = "eth0" *I see the following sent from the bird's RIP instance (10.0.4.1 is configured on eth1 and 172.16.0.4 on eth0). I would like the 10.2.4.1/32 route to be announced through eth0 only. I have also tried to use the *ifname ~ "eth0" *syntax with no luck. *tcpdump:* # tcpdump -i any -vvnn port 520 tcpdump: listening on any, link-type LINUX_SLL (Linux cooked), capture size 65535 bytes 13:02:58.664760 IP (tos 0xc0, ttl 1, id 27713, offset 0, flags [none], proto UDP (17), length 52) *10.0.4.1.520* > 224.0.0.9.520: [udp sum ok] RIPv2, Response, length: 24, routes: 1 or less AFI IPv4, *10.2.4.1/32 <http://10.2.4.1/32>*, tag 0x0000, metric: 1, next-hop: self 0x0000: 0202 0000 0002 0000 0a02 0401 ffff ffff 0x0010: 0000 0000 0000 0001 13:03:14.686163 IP (tos 0xc0, ttl 1, id 27714, offset 0, flags [none], proto UDP (17), length 52) *172.16.0.4.520* > 224.0.0.9.520: [udp sum ok] RIPv2, Response, length: 24, routes: 1 or less AFI IPv4, *10.2.4.1/32 <http://10.2.4.1/32>*, tag 0x0000, metric: 1, next-hop: self 0x0000: 0202 0000 0002 0000 0a02 0401 ffff ffff 0x0010: 0000 0000 0000 0001 *bird config:* 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 learn; device routes; } protocol device { scan time 10; # Scan interfaces every 10 seconds } protocol direct { interface "*"; } filter rip_export { # redistribute connected + RIP + ACL if ( ( source = RTS_DEVICE || source = RTS_RIP ) && ( net ~ 10.2.4.0/24 && *ifname = "eth0"* ) ) then { print "net export accepted: ", net; accept; } reject; } protocol rip RIP { debug all; interface "eth0" {mode multicast; split horizon yes; poison reverse no; }; interface "eth1" {mode multicast; split horizon yes; poison reverse no; }; import all; export filter rip_export; } Any help would be appreciated, thank you. Alex

2 3

Re: ifname in filters
by Alexander Velkov 04 Jul '16

04 Jul '16

Just for clarification, this is what I try to achieve 'translated' for use with quagga (ripd): ... access-list filter1 permit 10.2.4.0/24 access-list filter1 deny 0.0.0.0/0 ! interface eth0 interface eth1 ! router rip network eth0 distribute-list filter1 out eth0 network eth1 redistribute connected ... On Mon, Jul 4, 2016 at 3:49 PM, Alexander Velkov <alvel85(a)googlemail.com> wrote: > Hello, > > I would like to configure RIP with different ACLs set on different RIP > interfaces. For this purpose I thought I could use the '*ifname*' route > attribute in bird filters. The problem I am facing is that when I use it, > no RIP routes are announced at all, so maybe I am using a wrong syntax. > > If I don't use the *ifname = "eth0" *I see the following sent from the > bird's RIP instance (10.0.4.1 is configured on eth1 and 172.16.0.4 on > eth0). I would like the 10.2.4.1/32 route to be announced through eth0 > only. I have also tried to use the *ifname ~ "eth0" *syntax with no luck. > > > > > *tcpdump:* > # tcpdump -i any -vvnn port 520 > tcpdump: listening on any, link-type LINUX_SLL (Linux cooked), capture > size 65535 bytes > 13:02:58.664760 IP (tos 0xc0, ttl 1, id 27713, offset 0, flags [none], > proto UDP (17), length 52) > *10.0.4.1.520* > 224.0.0.9.520: [udp sum ok] > RIPv2, Response, length: 24, routes: 1 or less > AFI IPv4, *10.2.4.1/32 <http://10.2.4.1/32>*, tag > 0x0000, metric: 1, next-hop: self > 0x0000: 0202 0000 0002 0000 0a02 0401 ffff ffff > 0x0010: 0000 0000 0000 0001 > 13:03:14.686163 IP (tos 0xc0, ttl 1, id 27714, offset 0, flags [none], > proto UDP (17), length 52) > *172.16.0.4.520* > 224.0.0.9.520: [udp sum ok] > RIPv2, Response, length: 24, routes: 1 or less > AFI IPv4, *10.2.4.1/32 <http://10.2.4.1/32>*, tag > 0x0000, metric: 1, next-hop: self > 0x0000: 0202 0000 0002 0000 0a02 0401 ffff ffff > 0x0010: 0000 0000 0000 0001 > > *bird config:* > > 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 > learn; > device routes; > } > > protocol device { > scan time 10; # Scan interfaces every 10 seconds > } > > protocol direct { > interface "*"; > } > > filter rip_export { > # redistribute connected + RIP + ACL > if ( ( source = RTS_DEVICE || source = RTS_RIP ) && > ( net ~ 10.2.4.0/24 && *ifname = "eth0"* ) ) then { > print "net export accepted: ", net; > accept; > } > > reject; > } > > protocol rip RIP { > debug all; > > interface "eth0" {mode multicast; split horizon yes; poison reverse no; > }; > interface "eth1" {mode multicast; split horizon yes; poison reverse no; > }; > > import all; > export filter rip_export; > } > > Any help would be appreciated, thank you. > > Alex >

1 0