- Bird-users - Mailing Lists

[PATCH] More multipath support for OSPF
by Peter Christensen 23 Apr '14

23 Apr '14

Hi, I noticed that the multipath support in OSPF seems to be fairly limited. Essentially I was only able to make it do multipath if I had two interfaces connecting to the same router. At my company, we need true multipath between multiple routers using a single interface. (If I needed the other, I could use LACP) I am aware of the implications the default multipath implementation in Linux which operates on a per-packet basis, which is why we've patched our kernels to do it per-flow instead. Anyway, I seemed to have managed to make multipath work as expected - at least in our setup. (Patch attached) Essentially, I've hooked my multipath code into ri_install_ext() and ri_install_net(), where I add the equal routes if the routes share the same type, metrics and OSPF area. I realize that my add_nexthops() is /very/ similar to merge_nexthops() in functionality, but it seemed that the top_hash_entry() could be null, so I wrote a new method which did not rely on that - at the cost of more calls to copy_nexthop(), I guess. Any thoughts? Best regard Peter Christensen

2 5

question : broadcast kernel table via OSPF
by bino＠indoakses-online.com 22 Apr '14

22 Apr '14

Dear all I'm trying to learn BIRD4 to do ospf over batman-adv got to router : 1. router A 1.a. OSPF is at interface 'bat0' 1.b. Have 172.16.1.1/24 address at another interface, and have 'external route' 1.c. bird4.conf is at : http://pastebin.com/kin9MEnw 1.d. have birdc4 installed 2. router B 1.a. OSPF is at interface 'bat0' 1.b. bird4.conf is at : http://pastebin.com/XGTuHqfr 1.c. Not enough space to have birdc4 onboard Check from A. Router A using birdc4 : --------- bird> show ospf neighbors ospf1: Router ID Pri State DTime Interface Router IP 10.0.0.2 1 full/dr 00:56 bat0 10.0.0.2 bird> show ospf state area 0.0.0.0 router 10.0.0.1 distance 0 network 10.0.0.0/24 metric 1000 external 172.16.3.0/24 metric 1000 via 10.0.0.3 router 10.0.0.2 distance 1000 network 10.0.0.0/24 metric 1000 network 10.0.0.0/24 dr 10.0.0.2 distance 1000 router 10.0.0.2 router 10.0.0.1 --------- Looks like anything work fine. B. Router B, using terminal console : -------------------- root@OpenWrt:~# route Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface default 192.168.10.1 0.0.0.0 UG 0 0 0 br-lan 10.0.0.0 * 255.255.255.0 U 0 0 0 bat0 172.16.3.0 10.0.0.3 255.255.255.0 UG 0 0 0 bat0 192.168.10.0 * 255.255.255.0 U 0 0 0 br-lan ------------- Looks like : B.1. External route defined at Router-A is broadcasted ... nice B.2. Kernel route table of Router-A is NOT broadcasted. My question is : Why Kernel route table of Router-A is NOT broadcasted ? Kindly please give me any of your enlightenment to fix this problem. Sincerely -bino-

2 6

Importing routes with "strange next-hop" from the kernel
by Baptiste Jonglez 21 Apr '14

21 Apr '14

Hi, To save some IP space, we are playing a lot with /32 routes, which sometimes leads to unusual network setups. Specifically, we've hit this issue with Bird: http://marc.info/?l=bird-users&m=133465758907527&w=2 Basically, bird refuses to import a route from the kernel if the next-hop is not in a directly connected network. For instance, with a routing table like this: XX.XX.XX.32 dev eth1.101 proto static scope link src XX.XX.XX.1 XX.XX.XX.64/28 via 91.216.110.32 dev eth1.101 proto static bird will import the first route, but not the second one, spamming logs with "KRT: Received route XX.XX.XX.64/28 with strange next-hop XX.XX.XX.32". This is probably a good idea in most cases, but there are setups where these kind of routes make sense. The workaround described in the above thread ("ip addr add XX.XX.XX.1 peer XX.XX.XX.32") does not always apply, since we may want to have multiple /32 peers directly reachable on a given interface. We found another workaround (note the "onlink" flag and the "via" part): ip route add XX.XX.XX.32/32 via XX.XX.XX.32 dev eth1.101 onlink proto static This basically tells the kernel that the route we added is indeed in a connected network, so that Bird is happy. Note that subsequent routes using this /32 as next-hop also need the "onlink" flag: ip route add XX.XX.XX.64/28 via XX.XX.XX.32 dev eth1.101 proto static onlink In the hope that it will help someone someday, Baptiste

1 0

Version 1.4.3
by Ondrej Filip 15 Apr '14

15 Apr '14

Hi! We found a bug in IPv6 BGP implementation. So we decided to release 1.4.3. Ondrej

3 4

BFD on 1.4.2
by Kristoffer Egefelt 14 Apr '14

14 Apr '14

Hi, I’m trying BFD with some Force10 S4810 routers, problem is that sessions only come up every 3 or 4 times I restart bird. Also if Force10 routers are restarted, some times the sessions do not come back up. Also I have to restart bird to get it to work - birdc configure does not do it. I tried with the sysctl -w net.ipv4.ip_local_port_range="49152 65535” but this does not help either. I’m not able to get more debug info from the force10 devices than this: working : Apr 14 14:50:07: %STKUNIT0-M:CP %OSPF-5-ADJCHG: Neighbour state changed.OSPF Process 1, Nbr 77.66.22.228 on interface Vl 3000 change state from LOADING to FULL 3d0h48m : OSPFINFO: Quick Enabling BFD for NBRIP 77.66.22.228 RTRID 77.66.22.228 3d0h48m : OSPFINFO: OSPF Enabling BFD for NBRIP 77.66.22.228 Interface Vl 3000 IfIndex 1107528632 3d0h48m : OSPFINFO: Bfd Parameters interval 0 min_rx 0 Mult 0 role 0 3d0h48m : OSPFINFO: Completed Enabling BFD for NBRIP 77.66.22.228 Apr 14 14:50:08: %STKUNIT0-M:CP %BFDMGR-1-BFD_STATE_CHANGE: Changed session state to Up for neighbor 77.66.22.228 on interface Vl 3000 (diag: NO_DIAG) 3d0h48m : OSPFINFO: Ospf got BFD msg 3d0h48m : OSPFINFO: Bfd Msg Type Up for interface Vl 3000 3d0h48m : OSPFINFO: BFD Msg Up for NBRIP 77.66.22.228 RTRID 77.66.22.228, nbr bfd state Init not working : Apr 14 14:49:46: %STKUNIT0-M:CP %OSPF-5-ADJCHG: Neighbour state changed.OSPF Process 1, Nbr 77.66.22.228 on interface Vl 3000 change state from LOADING to FULL 3d0h47m : OSPFINFO: Quick Enabling BFD for NBRIP 77.66.22.228 RTRID 77.66.22.228 3d0h47m : OSPFINFO: OSPF Enabling BFD for NBRIP 77.66.22.228 Interface Vl 3000 IfIndex 1107528632 3d0h47m : OSPFINFO: Bfd Parameters interval 0 min_rx 0 Mult 0 role 0 3d0h47m : OSPFINFO: Completed Enabling BFD for NBRIP 77.66.22.228 Any hints are greatly appreciated. Thanks Regards Kristoffer

2 2

received-routes command
by Jimmy Halim 14 Apr '14

14 Apr '14

Hi guys, I am sorry if I am bringing this question again since I have been away from BIRD community for awhile. Can we show BGP “received-routes” command in BIRD right now? I understand the latest release is v1.4.2. Back in 2012, one suggestion to do it is to build up a table that receives all BGP routes and then do the filtering under pipe as per following which I haven’t tried. I hope we do not need to do this now. <snip> table t; protocol bgp { table t; import all; export all; ... } protocol pipe { peer table t; import < here goes filters for BGP export < here goes filters for BGP } <snip> Thanks, Jimmy

2 3

IPv6 BGP debugging
by Peter Andreev 11 Apr '14

11 Apr '14

Hi everybody, I'm trying to set up bird 1.4.2 on FreeBSD 9.1 and stuck on the following: bird> sh pro name proto table state since info kernel1 Kernel master up 13:10:06 device1 Device master up 13:10:06 NICbr1 BGP master up 13:10:28 Established NICbr2 BGP master up 13:10:29 Established PTTlg BGP master start 13:10:24 Connect Socket: Invalid argument MLPA1 BGP master start 13:10:24 Connect Socket: Operation timed out MLPA2 BGP master start 13:10:24 Connect Socket: Invalid argument MLPA3 BGP master start 13:12:51 OpenConfirm BGP Error: Hold timer expired MLPA4 BGP master start 13:10:24 Connect Socket: Invalid argument STATIC_BGP Static master up 13:10:06 All these BGP protocols are inherited from one template. The only difference is that those are established, use another source address which is configured on virtual interface. However my question is how to find out what's going on and how to detect a problem? Setting "log syslog all;" is not very helpful - it only fills the log file with a lot of "bird6: KRT: Error sending route 2c0f:fb50::/0 to kernel: No such process" messages. -- Is there any problem Exterminatus cannot solve? I have not found one yet.

4 12

bgp route selection
by Thomas Goldberg 10 Apr '14

10 Apr '14

Hello, can yomeone please explain me the following behaviour: There's one eBGP session (b_dtag1) and one iBGP session with one of our RR Servers (b_rr1). The RR redistributes the blackhole prefixes learned from the Spamhouse BGP Feed (BGPf). The prefix 64.112.128.0/18 is supposed to be blackholed. These are the two routes learned from the two peers: bird> show route all 64.112.128.0/18 64.112.128.0/18 via X.X.X.X on eth0 [b_dtag1 Apr06] * (100) [AS3320i] Type: BGP unicast univ BGP.origin: IGP BGP.as_path: 3320 3491 25847 46879 BGP.next_hop: X.X.X.X BGP.local_pref: 100 blackhole [b_rr1 15:36 from Y.Y.Y.Y] (100/-) [AS65535i] Type: BGP unicast univ BGP.origin: IGP BGP.as_path: 65190 BGP.next_hop: 192.168.2.11 BGP.med: 0 BGP.local_pref: 40000 BGP.community: (65190,1000) (65535,65281) As you can see the (older) regular eBGP route is picked over the blackhole route: Based on the Route selection rules from http://bird.network.cz/?get_doc&f=bird-6.html#ss6.2 I expected that the first (Prefer route with the highest Local Preference attribute) and the second (Prefer route with the shortest AS path) rule would result in the blackhole route being picked. Best Regards Thomas Goldberg

4 5

ipv6 ecmp ospf
by Vasiliy Tolstov 10 Apr '14

10 Apr '14

Hi all. I'm try to get working ecmp with ipv6 and bird 1.4. Now i'm not understand why routes to test ip installed and removed after 3-5 seconds. Can somebody helps me? In log i have : Apr 6 15:14:31 rl01 bird6: device1: Scanning interfaces Apr 6 15:14:31 rl01 bird6: kernel1: Scanning routing table Apr 6 15:14:31 rl01 bird6: kernel1: 2001:db8:0:f101:ccde:85ff:fe22:ec43/128: will be updated Apr 6 15:14:31 rl01 bird6: kernel1: 2001:db8:0:f101:ccde:85ff:fe22:ec43/128: already seen Apr 6 15:14:31 rl01 bird6: kernel1: Pruning table master Apr 6 15:14:31 rl01 bird6: kernel1: 2001:db8:0:f101:ccde:85ff:fe22:ec43/128: updating Apr 6 15:14:31 rl01 bird6: Netlink: No such process Apr 6 15:14:31 rl01 bird6: kernel1: Pruning inherited routes Apr 6 15:14:32 rl01 bird6: radv1: Timer fired on eth1 Apr 6 15:14:32 rl01 bird6: radv1: Sending RA via eth1 Apr 6 15:14:32 rl01 bird6: radv1: Timer fired on eth0 Apr 6 15:14:32 rl01 bird6: radv1: Sending RA via eth0 Apr 6 15:14:32 rl01 bird6: ospf1: HELLO packet received from fe80::225:90ff:fe97:a719 via eth1 Apr 6 15:14:32 rl01 bird6: ospf1: HELLO packet received from fe80::225:90ff:fe97:a718 via eth0 Apr 6 15:14:37 rl01 bird6: device1: Scanning interfaces Apr 6 15:14:37 rl01 bird6: kernel1: Scanning routing table Apr 6 15:14:37 rl01 bird6: kernel1: Pruning table master Apr 6 15:14:37 rl01 bird6: kernel1: 2001:db8:0:f101:ccde:85ff:fe22:ec43/128: reinstalling Apr 6 15:14:37 rl01 bird6: kernel1: Pruning inherited routes Apr 6 15:14:37 rl01 bird6: ospf1: HELLO packet sent via eth1 Apr 6 15:14:37 rl01 bird6: ospf1: HELLO packet sent via eth0 Apr 6 15:14:37 rl01 bird6: ospf1: HELLO packet received from fe80::225:90ff:fe97:a719 via eth1 Apr 6 15:14:37 rl01 bird6: ospf1: HELLO packet received from fe80::225:90ff:fe97:a718 via eth0 Apr 6 15:14:42 rl01 bird6: ospf1: HELLO packet sent via eth0 Apr 6 15:14:42 rl01 bird6: ospf1: HELLO packet sent via eth1 Apr 6 15:14:42 rl01 bird6: device1: Scanning interfaces Apr 6 15:14:42 rl01 bird6: kernel1: Scanning routing table Apr 6 15:14:42 rl01 bird6: kernel1: 2001:db8:0:f101:ccde:85ff:fe22:ec43/128: will be updated Apr 6 15:14:42 rl01 bird6: kernel1: 2001:db8:0:f101:ccde:85ff:fe22:ec43/128: already seen Apr 6 15:14:42 rl01 bird6: kernel1: Pruning table master Apr 6 15:14:42 rl01 bird6: kernel1: 2001:db8:0:f101:ccde:85ff:fe22:ec43/128: updating Apr 6 15:14:42 rl01 bird6: Netlink: No such process Apr 6 15:14:42 rl01 bird6: kernel1: Pruning inherited routes Apr 6 15:14:42 rl01 bird6: ospf1: HELLO packet received from fe80::225:90ff:fe97:a719 via eth1 Apr 6 15:14:42 rl01 bird6: ospf1: HELLO packet received from fe80::225:90ff:fe97:a718 via eth0 rl01 bird config: log syslog all; #{error, info}; router id 172.16.250.251; debug protocols all; protocol kernel { learn; scan time 5; # Scan kernel routing table every 20 seconds import all; # Default is import all export all; # Default is export none } protocol direct { interface "eth0", "eth1", "dummy0"; export all; import all; } protocol device { scan time 5; # Scan interfaces every 10 seconds } protocol radv { interface "eth0" { max ra interval 30; link mtu 9000; prefix 2001:db8:0:f102::/64; }; interface "eth1" { max ra interval 30; link mtu 9000; prefix 2001:db8:0:f103::/64; }; } filter ospf_filter { if net ~ [ ::/0 ] then reject; else accept; } protocol ospf { tick 5; ecmp 4; import filter ospf_filter; export all; #filter ospf_filter; area 0 { interface "eth0","eth1" { check link yes; cost 5; hello 5; retransmit 2; wait 10; dead 20; ecmp weight 5; }; interface "dummy0" { stub yes; cost 1; }; stubnet 2001:db8:0:f101::/128; }; } birdc6 show route BIRD 1.4.0 ready. 2001:db8:0:f101:ccde:85ff:fe22:ec43/128 multipath [ospf1 15:14:27] ! I (150/5) [172.16.250.8] via fe80::225:90ff:fe97:a718 on eth0 weight 5 via fe80::225:90ff:fe97:a719 on eth1 weight 5 2001:db8:0:f101:e010:b8ff:feb6:d4a/128 dev dummy0 [direct1 15:14:16] * (240) dev dummy0 [ospf1 15:14:17] I (150/0) [172.16.250.251] 2001:db8:0:f103::/64 dev eth1 [direct1 15:14:16] * (240) dev eth1 [ospf1 15:14:27] I (150/5) [172.16.250.8] 2001:db8:0:f102::/64 dev eth0 [direct1 15:14:16] * (240) dev eth0 [ospf1 15:14:27] I (150/5) [172.16.250.8] birdc6 show ospf top BIRD 1.4.0 ready. area 0.0.0.0 router 172.16.250.8 distance 5 network [172.16.250.8-2] metric 5 network [172.16.250.8-3] metric 5 router 172.16.250.251 distance 0 network [172.16.250.8-2] metric 5 network [172.16.250.8-3] metric 5 network [172.16.250.8-2] distance 5 router 172.16.250.8 router 172.16.250.251 network [172.16.250.8-3] distance 5 router 172.16.250.8 router 172.16.250.251 birdc6 show ospf ne BIRD 1.4.0 ready. ospf1: Router ID Pri State DTime Interface Router IP 172.16.250.8 1 full/dr 00:20 eth0 fe80::225:90ff:fe97:a718 172.16.250.8 1 full/dr 00:20 eth1 fe80::225:90ff:fe97:a719 birdc6 show interfaces BIRD 1.4.0 ready. lo up (index=1) MultiAccess AdminUp LinkUp Loopback Ignored MTU=65536 ::1/128 (Primary, scope host) eth0 up (index=2) MultiAccess Broadcast Multicast AdminUp LinkUp MTU=9000 2001:db8:0:f102:92e2:baff:fe31:44c/64 (Primary, scope univ) fe80::92e2:baff:fe31:44c/64 (Unselected, scope link) eth1 up (index=3) MultiAccess Broadcast Multicast AdminUp LinkUp MTU=9000 2001:db8:0:f103:92e2:baff:fe31:44d/64 (Primary, scope univ) fe80::92e2:baff:fe31:44d/64 (Unselected, scope link) eth2 DOWN (index=4) MultiAccess Broadcast Multicast AdminDown LinkDown MTU=1500 eth3 up (index=5) MultiAccess Broadcast Multicast AdminUp LinkUp MTU=1500 fe80::92e2:baff:fe31:44f/64 (Primary, scope link) eth4 up (index=6) MultiAccess Broadcast Multicast AdminUp LinkUp MTU=1500 fe80::225:90ff:fea1:82a6/64 (Primary, scope link) eth5 DOWN (index=7) MultiAccess Broadcast Multicast AdminDown LinkDown MTU=1500 bond0 DOWN (index=8) MultiAccess Broadcast Multicast AdminDown LinkDown MTU=1500 ovs-system DOWN (index=9) MultiAccess Broadcast Multicast AdminDown LinkDown MTU=1500 ovs-vm up (index=10) MultiAccess Broadcast Multicast AdminUp LinkUp MTU=1500 fe80::b485:3ff:fe6b:e1f5/64 (Primary, scope link) dummy0 up (index=11) MultiAccess Broadcast Multicast AdminUp LinkUp MTU=1500 2001:db8:0:f101:e010:b8ff:feb6:d4a/128 (Primary, scope univ) fe80::94c5:c3ff:fe84:dd26/64 (Unselected, scope link) -- Vasiliy Tolstov,

2 5

BIRD - iBGP between both RS - invalid NEXT-HOP notification.
by Javor Kliachev 08 Apr '14

08 Apr '14

Hello, We use BIRD as route server for a long time without any problems. We have both fully symmetric RS for redundancy. Yesterday we decided to establish "internal BGP session" between both of them. The reason to do this is to achieve prefix symmetric on both RS. Some of our members hold BGP session only with one of our route servers. But after establishing this BGP session we began to see the following message into our logs on both RS for total random prefixes on absolutely random intervals. Here is part of my bird.log: 07-03-2014 14:19:41 R0_29: Invalid NEXT_HOP attribute in route 178.254.232.0/21 07-03-2014 14:19:41 R0_30: Invalid NEXT_HOP attribute in route 178.254.232.0/21 07-03-2014 14:18:52 R0_52: Invalid NEXT_HOP attribute in route 79.140.156.0/22 07-03-2014 14:18:52 R0_52: Invalid NEXT_HOP attribute in route 79.140.148.0/22 07-03-2014 14:18:52 R0_52: Invalid NEXT_HOP attribute in route 79.140.144.0/20 07-03-2014 14:18:52 R0_52: Invalid NEXT_HOP attribute in route 79.140.152.0/22 07-03-2014 14:18:52 R0_52: Invalid NEXT_HOP attribute in route 79.140.144.0/22 07-03-2014 14:18:52 R0_52: Invalid NEXT_HOP attribute in route 79.140.156.0/22 07-03-2014 14:18:52 R0_52: Invalid NEXT_HOP attribute in route 79.140.144.0/20 07-03-2014 14:18:52 R0_52: Invalid NEXT_HOP attribute in route 79.140.148.0/22 07-03-2014 14:18:52 R0_52: Invalid NEXT_HOP attribute in route 79.140.152.0/22 07-03-2014 14:18:52 R0_52: Invalid NEXT_HOP attribute in route 79.140.144.0/22 07-03-2014 14:16:39 R0_29: Invalid NEXT_HOP attribute in route 178.254.232.0/21 07-03-2014 14:16:39 R0_30: Invalid NEXT_HOP attribute in route 178.254.232.0/21 07-03-2014 14:01:39 R0_52: Invalid NEXT_HOP attribute in route 95.168.66.0/23 07-03-2014 14:01:39 R0_52: Invalid NEXT_HOP attribute in route 95.168.68.0/23 07-03-2014 13:52:02 R0_14: Invalid NEXT_HOP attribute in route 151.252.198.0/24 07-03-2014 13:51:57 R0_14: Invalid NEXT_HOP attribute in route 151.252.198.0/24 07-03-2014 13:29:36 R0_87: Invalid NEXT_HOP attribute in route 85.11.144.0/20 07-03-2014 13:29:28 R0_87: Invalid NEXT_HOP attribute in route 85.11.144.0/20 07-03-2014 13:29:15 R0_87: Invalid NEXT_HOP attribute in route 85.11.144.0/20 07-03-2014 13:29:06 R0_87: Invalid NEXT_HOP attribute in route 85.11.144.0/20 07-03-2014 13:28:14 R0_87: Invalid NEXT_HOP attribute in route 85.187.120.0/22 07-03-2014 13:28:14 R0_87: Invalid NEXT_HOP attribute in route 85.187.120.0/22 07-03-2014 13:19:36 R0_87: Invalid NEXT_HOP attribute in route 85.187.120.0/22 07-03-2014 13:19:31 R0_87: Invalid NEXT_HOP attribute in route 85.187.120.0/22 07-03-2014 13:19:31 R0_87: Invalid NEXT_HOP attribute in route 85.11.144.0/20 07-03-2014 13:19:31 R0_87: Invalid NEXT_HOP attribute in route 85.187.120.0/22 07-03-2014 13:19:22 R0_87: Invalid NEXT_HOP attribute in route 85.11.144.0/20 07-03-2014 13:13:43 R0_71: Invalid NEXT_HOP attribute in route 46.229.194.0/24 07-03-2014 13:13:43 R0_71: Invalid NEXT_HOP attribute in route 46.229.192.0/23 07-03-2014 13:13:42 R0_29: Invalid NEXT_HOP attribute in route 46.229.194.0/24 07-03-2014 13:13:42 R0_29: Invalid NEXT_HOP attribute in route 46.229.192.0/23 07-03-2014 13:06:22 R0_60: Invalid NEXT_HOP attribute in route 193.104.73.0/24 07-03-2014 13:03:54 R0_52: Invalid NEXT_HOP attribute in route 178.79.61.0/24 07-03-2014 12:54:56 R0_60: Invalid NEXT_HOP attribute in route 89.35.114.0/24 07-03-2014 12:54:56 R0_60: Invalid NEXT_HOP attribute in route 86.105.150.0/24 07-03-2014 12:54:56 R0_60: Invalid NEXT_HOP attribute in route 46.102.181.0/24 07-03-2014 12:54:56 R0_60: Invalid NEXT_HOP attribute in route 46.102.176.0/24 07-03-2014 12:54:56 R0_60: Invalid NEXT_HOP attribute in route 37.156.69.0/24 07-03-2014 12:54:25 R0_60: Invalid NEXT_HOP attribute in route 188.240.70.0/24 07-03-2014 12:54:25 R0_60: Invalid NEXT_HOP attribute in route 188.212.157.0/24 07-03-2014 12:34:43 R0_52: Invalid NEXT_HOP attribute in route 91.148.106.0/24 07-03-2014 12:27:48 R0_52: Invalid NEXT_HOP attribute in route 91.148.118.0/24 07-03-2014 12:16:33 R0_29: Invalid NEXT_HOP attribute in route 178.254.232.0/21 07-03-2014 12:16:33 R0_30: Invalid NEXT_HOP attribute in route 178.254.232.0/21 07-03-2014 12:09:39 R0_87: Invalid NEXT_HOP attribute in route 85.11.144.0/20 07-03-2014 12:09:10 R0_87: Invalid NEXT_HOP attribute in route 85.11.144.0/20 07-03-2014 12:08:57 R0_87: Invalid NEXT_HOP attribute in route 85.187.120.0/22 07-03-2014 12:08:50 R0_87: Invalid NEXT_HOP attribute in route 85.187.120.0/22 07-03-2014 12:08:49 R0_87: Invalid NEXT_HOP attribute in route 85.187.120.0/22 07-03-2014 12:02:41 R0_52: Invalid NEXT_HOP attribute in route 212.200.0.0/21 07-03-2014 11:47:01 R0_29: Invalid NEXT_HOP attribute in route 178.254.232.0/21 07-03-2014 11:47:01 R0_30: Invalid NEXT_HOP attribute in route 178.254.232.0/21 07-03-2014 10:55:50 R0_60: Invalid NEXT_HOP attribute in route 91.206.209.0/24 I had checked many times and make many tests if the next-hop is correct and everything looks fine but this messages comes permanently :) We managed to troubleshoot the following behavior and relationship and see the following effect: Our scenario: 0.100 0.200 RS1 <- iBGP -> RS2 | | | | TEST.AS ----------- 0.252 TEST.AS announce: 31.13.244.0/24 RS2 learn this prefix as: 31.13.244.0/24 via 10.1.0.252 on eth0 [R0_252 14:44] * (100) [AS60230i] via 10.1.0.252 on eth0 [*R0_100* 15:12 from 10.1.0.100] (100) [AS60230i] As soon as we stop to announce 31.13.244.0/24 from TEST.AS to RS1, in the logs of RS1 begin to come the following message: 07-03-2014 15:10:09R0_252: Invalid NEXT_HOP attribute in route 31.13.244.0/24 But when we try to shutdown (administratively ) the session between TEST.AS and RS1 this behavior does not occur and everything seems normal. I hope this information will be useful for resolving this strange issue. Here is our configuration set on both RS. The real AS number & IPs has been changed for security reason :) # RS2: table T65535 protocol pipe P65535 from iBGP_PIPES { description "RS1"; peer table T65535; export where RS_PIPE_OUT(); } protocol bgp R0_100 from iBGP { description "0.100_iBGP_RS1"; source address 10.1.0.200; neighbor 10.1.0.100 as 65535; import all; export all; passive off; table T65535; route limit 10000; gateway direct; } # RS1: table T65535 protocol pipe P65535 from iBGP_PIPES { description "RS2"; peer table T65535; export where RS_PIPE_OUT(); } protocol bgp R0_200 from iBGP { description "0.200_iBGP_RS1"; source address 10.1.0.100; neighbor 10.1.0.200 as 65535; import all; export all; passive off; table T65535; route limit 10000; gateway direct; } # show bgp summary shows the following: # RS2: ---------------------------------------------------------------- adv / rcv / limit --- 0.100_iBGP_RS1 10.1.0.100 65535 Mar06 Established 4527/3235/10000 -------------------------------------------------------------------------------------- # RS1: ---------------------------------------------------------------- adv / rcv / limit --- 0.200_iBGP_RS2 10.1.0.200 65535 Mar06 Established 3235/4527/10000 -------------------------------------------------------------------------------------- Any ideas or thoughts are highly appreciated! Thanks in advance! -- --- Find out about our new Cloud service - Cloudware.bg <http://cloudware.bg/?utm_source=email&utm_medium=signature&utm_content=link…> Access anywhere. Manage it yourself. Pay as you go. ------------------------------------------------------------------------ *Javor Kliachev* IP Engineer Neterra Ltd. Telephone: +359 2 975 16 16 Fax: +359 2 975 34 36 www.neterra.net <http://www.neterra.net>

4 7