Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug
report.
http://bugzilla.quagga.net/show_bug.cgi?id=196
Summary: Zebra's view of routes differs from the kernel's for
IPv6 routes at least
Product: Quagga
Version: 0.98.3
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: High
Component: zebra
AssignedTo: maintainers@quagga.net
ReportedBy: huggie-quagga@earth.li
We've seen issues where route that have been withdrawn from BGP still exist in
the linux routing table despite zebra having the correct route.
i.e. the bgpd shows:
rbi-rt2# sho ipv6 bgp 2001:470:1f01:ffff::876
[..]
2001:668:0:3::4000:1 from 2001:668:0:3::4000:1
Origin IGP, metric 90, localpref 100, valid, external, best
[and some other less preferred routes]
zebra shows:
rbi-rt2> sho ipv6 route 2001:470::/32
Routing entry for 2001:470::/32
Known via "bgp", distance 20, metric 0, best
Last update 00:31:27 ago
* 2001:668:0:3::4000:1, via eth2.1044
Ok so far just as I'd expect.
Yet then when we ask the routing table we see:
huggie@rbi-rt2:~$ ip -6 ro get 2001:470::/32
2001:470:: via fe80::204:28ff:fe0c:4000 dev eth2.995 proto zebra src
2001:7f8:2:1::13 metric 1024 mtu 1500 advmss 1440
Oh also ip -6 ro list 2001:470::/32 gives:
2001:470::/32 via fe80::204:28ff:fe0c:4000 dev eth2.995 proto zebra metric
1024 mtu 1500 advmss 1440
2001:470::/32 via 2001:668:0:3::4000:1 dev eth2.1044 proto zebra metric 1024
mtu 1500 advmss 1440
So the routes are added multiple times or at least the less preferred one isn't
removed.
I believe _hasso_ on #quagga is close to working out what's wrong but thought I
should stick this information somewhere.
I have (sadly) further examples in our live config at the moment.
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
comments should be made in the comments box of this bug
report.
http://bugzilla.quagga.net/show_bug.cgi?id=196
Summary: Zebra's view of routes differs from the kernel's for
IPv6 routes at least
Product: Quagga
Version: 0.98.3
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: High
Component: zebra
AssignedTo: maintainers@quagga.net
ReportedBy: huggie-quagga@earth.li
We've seen issues where route that have been withdrawn from BGP still exist in
the linux routing table despite zebra having the correct route.
i.e. the bgpd shows:
rbi-rt2# sho ipv6 bgp 2001:470:1f01:ffff::876
[..]
2001:668:0:3::4000:1 from 2001:668:0:3::4000:1
Origin IGP, metric 90, localpref 100, valid, external, best
[and some other less preferred routes]
zebra shows:
rbi-rt2> sho ipv6 route 2001:470::/32
Routing entry for 2001:470::/32
Known via "bgp", distance 20, metric 0, best
Last update 00:31:27 ago
* 2001:668:0:3::4000:1, via eth2.1044
Ok so far just as I'd expect.
Yet then when we ask the routing table we see:
huggie@rbi-rt2:~$ ip -6 ro get 2001:470::/32
2001:470:: via fe80::204:28ff:fe0c:4000 dev eth2.995 proto zebra src
2001:7f8:2:1::13 metric 1024 mtu 1500 advmss 1440
Oh also ip -6 ro list 2001:470::/32 gives:
2001:470::/32 via fe80::204:28ff:fe0c:4000 dev eth2.995 proto zebra metric
1024 mtu 1500 advmss 1440
2001:470::/32 via 2001:668:0:3::4000:1 dev eth2.1044 proto zebra metric 1024
mtu 1500 advmss 1440
So the routes are added multiple times or at least the less preferred one isn't
removed.
I believe _hasso_ on #quagga is close to working out what's wrong but thought I
should stick this information somewhere.
I have (sadly) further examples in our live config at the moment.
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.