Quagga 1.2.0: проблема с добавлением маршрутов

[ne-vlezay80]

Установил из исходников свежую версию quagga'и. IPv4 маршруты с BGP добавляются нормально, хотя IPv6 маршруты в BGP видны, но почиму-то zebra их не видит. В чём может быть дело?

 

root@servl:~# vtysh -c "sh ipv6 bgp"
BGP table version is 0, local router ID is 91.219.5.247
Status codes: s suppressed, d damped, h history, * valid, > best, = multipath,
             i internal, r RIB-failure, S Stale, R Removed
Origin codes: i - IGP, e - EGP, ? - incomplete

  Network          Next Hop            Metric LocPrf Weight Path
*> ::/0             ::                       0         32768 i
*> 2001:470:78b7::/54
                   ::                       0         32768 i
*> 2a01:d0:c353::/50
                   ::                       0         32768 i
  2a01:d0:c353:fd::/64
                   fd00:1002:1288:fd::1
                                            0             0 65503 i
  2a01:d0:c353:170::/60
                   fd00:1002:1289:10::4
                                                          0 65301 i
*> fd00:1002:1288::/48
                   ::                       0         32768 i
*> fd00:1002:1289::/48
                   ::                       0         32768 i

Displayed  7 out of 7 total prefixes

root@servl:~# vtysh -c "sh ipv6 route"
Codes: K - kernel route, C - connected, S - static, R - RIPng,
      O - OSPFv6, I - IS-IS, B - BGP, A - Babel, N - NHRP,
      > - selected route, * - FIB route

S>* ::/0 [1/0] via fd00:1002:1288:fd::1, tun0
C>* ::1/128 is directly connected, lo
S>* 2001:470:78b7::/54 [1/0] is directly connected, lo
S>* 2001:470:c3de::/48 [1/0] is directly connected, lo
S>  2001:470:c3de:80::2/128 [1/0] is directly connected, etherlan0 inactive
 *                               via fd00:1002:1288:1::10, eth2
C>* 2a01:d0:c353:3fff::fffd/128 is directly connected, tun0
C>* fd00:1002:1288:1::/64 is directly connected, eth2
C>* fd00:1002:1288:2::/64 is directly connected, br0
C>* fd00:1002:1288:fd::/126 is directly connected, tun0
C>* fd00:1002:1289:10::/64 is directly connected, br-vlan0
C>* fd00:1002:1289:20::/64 is directly connected, tun10
C * fe80::/64 is directly connected, vlan101
C * fe80::/64 is directly connected, vlan100
C * fe80::/64 is directly connected, ns0
C * fe80::/64 is directly connected, br0
C * fe80::/64 is directly connected, br-vlan0
C * fe80::/64 is directly connected, eth2
C>* fe80::/64 is directly connected, eth0
root@servl:~#

Edited February 20, 2017 by ne-vlezay80