---------- Forwarded message ----------
From: Kaz Nishimura <kazs...@vx68k.org>
Date: Tue, May 5, 2015 at 9:21 PM
Subject: Re: Bug#784292: quagga: ospf6d no loner updates route after
upgrade to Jessie
To: Christian Brunotte <c...@lathspell.de>
I upgraded to 0.99.24-2 from testing but it was not resolved.
This is the output of 'show ipv6 ospf6 database' command on vtysh (backbone
end):
--
Area Scoped Link State Database (Area 0.0.0.0)
Type LSId AdvRouter Age SeqNum
Payload
INP 0.0.0.0 172.20.240.2 153 8000003c
2002:b4eb:feac:fff0::/64
INP 0.0.0.0 172.20.240.2 153 8000003c
240d:0:860a:6600::/64
INP 0.0.0.0 180.235.254.172 495 8000003b
2002:b4eb:feac:fff0::/64
I/F Scoped Link State Database (I/F eth0 in Area 0.0.0.0)
Type LSId AdvRouter Age SeqNum
Payload
Lnk 0.0.0.2 172.20.240.2 159 80000001
fe80::210:c6ff:fe0d:d306
I/F Scoped Link State Database (I/F sit2 in Area 0.0.0.0)
Type LSId AdvRouter Age SeqNum
Payload
Lnk 0.0.0.5 172.20.240.2 153 8000003b
fe80::ac14:f002
Lnk 0.0.0.4 180.235.254.172 495 8000003b
fe80::ac14:1
AS Scoped Link State Database
Type LSId AdvRouter Age SeqNum
Payload
ASE 0.0.0.0 172.20.240.2 153 8000003b
2002:b4eb:feac:fff0::/64
ASE 0.0.0.1 172.20.240.2 153 8000003b
240d:0:860a:6600::/64
ASE 0.0.0.0 180.235.254.172 495 8000003b
2002:b4eb:feac:ff00::/64
ASE 0.0.0.1 180.235.254.172 495 8000003b
2002:b4eb:feac:fff0::/64
--
Note that the leaf end router (180.235.254.172) and the corresponding
destination address (2002:b4eb:feac:ff00::/64) appears in the database.
This is the output of 'show ipv6 ospf6 route' command on vtysh (backbone
end):
--
*N IA 2002:b4eb:feac:fff0::/64 :: sit2
00:05:00
*N IA 240d:0:860a:6600::/64 :: eth0
00:05:00
--
Note that the routing table only has local routes.
As ospf6d is in "beta" state according to Quagga's release announcements,
it could become broken in version 0.99.23. If I could have free time, I
would examine what were changed in ospf6d in 0.99.23.
On Tue, May 5, 2015 at 9:02 PM, Kaz Nishimura <kazs...@vx68k.org> wrote:
> These are my Quagga configurations, which are almost the same as the ones
> before the upgrade (I added interface sit2 and multicast to zebra.conf).
>
> zebra.conf (backbone end, non-essential comments deleted):
> --
> log file /var/log/quagga/zebra.log
>
> access-list private permit 172.20.0.0/16
> access-list private deny any
>
> route-map all deny 90
>
> route-map authorized permit 10
> match ip address private
>
> interface sit2
> multicast
>
> ip route 172.20.0.0/20 172.20.240.1
> ip route 172.20.247.0/24 dummy0
> #ipv6 route 2002:b4eb:feac:ff00::/56 sit2
>
> ip protocol rip route-map authorized
> ip protocol ospf route-map authorized
> --
>
> ospf6d.conf (backbone end, non-essential comments deleted):
> --
> log file /var/log/quagga/ospf6d.log
>
> router ospf6
> router-id 172.20.240.2
>
> interface eth0 area 0.0.0.0
> #interface sit2 area 172.20.0.1
> interface sit2 area 0.0.0.0
>
> redistribute connected
> redistribute static
> --
>
> zebra.conf (leaf end, non-essential comments deleted):
> --
> log file /var/log/quagga/zebra.log
>
> access-list private permit 172.20.0.0/16
> access-list private deny any
>
> route-map all deny 90
>
> route-map authorized permit 10
> match ip address private
>
> interface macvlan0
> no ipv6 nd suppress-ra
> ipv6 nd prefix 2002:b4eb:feac:ff00::/64
>
> interface sit2
> multicast
>
> ip route 172.20.240.0/20 172.20.0.254
> --
>
> ospf6d.conf (leaf end, non-essential comments deleted):
> --
> log file /var/log/quagga/ospf6d.log
>
> router ospf6
> router-id 180.235.254.172
>
> #interface sit2 area 172.20.0.1
> interface sit2 area 0.0.0.0
>
> redistribute connected
> redistribute static
> --
>
>
> On Tue, May 5, 2015 at 5:24 PM, Christian Brunotte <c...@lathspell.de>
> wrote:
>
>> Hello
>>
>> Can you please explain the problem on the Quagga users mailing list
>> (https://lists.quagga.net/mailman/listinfo/quagga-users) and attach
>> the (anonymized) config files? My IPv6 & OSPF knowledge is not
>> good enough to help you myself :)
>>
>> It would be helpful if you could give 0.99.24.2 from Debian testing a try,
>> the .deb package should currently be installable fine on Jessie as Testing
>> still has the same library versions as Jessie:
>> https://packages.debian.org/stretch/quagga
>>
>> Best regards,
>>
>> -christian-
>>
>> Am Tue, 05 May 2015 09:36:09 +0900
>> schrieb Kaz Nishimura <kazs...@vx68k.org>:
>>
>> > Package: quagga
>> > Version: 0.99.23.1-1
>> > Severity: normal
>> > Tags: ipv6
>> >
>> > Dear Maintainer,
>> >
>> > After upgrade to Jessie, ospf6d does not update IPv6 route for a SIT
>> tunnel
>> > (that is the only route I used ospf6d for). Before the upgrade, it just
>> > worked.
>> >
>> > As I see the state of ospf6d by vtysh, it seems it updates its internal
>> > database (show ipv6 ospf6 database) but does not reflect it to its
>> internal
>> > routing table (show ipv6 ospf6 route).
>> >
>> > According to the release announcement, many changes have been made in
>> > version 0.99.23, so they could affect the behavior, IMO. I do not know
>> > if version 0.99.24 has a fix for it.
>> >
>> > As ospf6d is not working for me now, I am using ripngd as a backup, and
>> it
>> > works fine.
>> >
>> > -- System Information:
>> > Debian Release: 8.0
>> > APT prefers stable-updates
>> > APT policy: (500, 'stable-updates'), (500, 'stable')
>> > Architecture: i386 (i686)
>> >
>> > Kernel: Linux 3.16.0-4-686-pae (SMP w/1 CPU core)
>> > Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
>> > Shell: /bin/sh linked to /bin/dash
>> > Init: systemd (via /run/systemd/system)
>> >
>> > Versions of packages quagga depends on:
>> > ii adduser 3.113+nmu3
>> > ii debconf [debconf-2.0] 1.5.56
>> > ii iproute2 3.16.0-2
>> > ii libc6 2.19-18
>> > ii libcap2 1:2.24-8
>> > ii libpam0g 1.1.8-3.1
>> > ii libreadline6 6.3-8+b3
>> > ii libtinfo5 5.9+20140913-1+b1
>> > ii logrotate 3.8.7-1+b1
>> >
>> > quagga recommends no packages.
>> >
>> > Versions of packages quagga suggests:
>> > pn snmpd <none>
>> >
>> > -- Configuration Files:
>> > /etc/quagga/daemons changed:
>> > zebra=yes
>> > bgpd=no
>> > ospfd=no
>> > ospf6d=yes
>> > ripd=yes
>> > ripngd=yes
>> > isisd=no
>> > babeld=no
>> >
>> >
>> > -- debconf information:
>> > * quagga/really_stop: true
>>
>>
>> --
>> Content Delivery Server & Dienste
>> _________________________________________________________________________
>> NETCOLOGNE Gesellschaft für Telekommunikation mbH
>> Am Coloneum 9 | 50829 Köln
>> Tel: 0221 2222-8711 | Fax: 0221 2222-78711
>>
>> www.netcologne.de
>>
>> Geschäftsführer:
>> Jost Hermanns
>> Mario Wilhelm
>> Vorsitzender des Aufsichtsrates:
>> Dr. Andreas Cerbe
>> HRB 25580, AG Köln
>>
>> Diese Nachricht (inklusive aller Anhänge) ist vertraulich. Sollten Sie
>> diese
>> Nachricht versehentlich erhalten haben, bitten wir, den Absender (durch
>> Antwort-E-Mail) hiervon unverzüglich zu informieren und die Nachricht zu
>> löschen. Die E-Mail darf in diesem Fall weder vervielfältigt noch in
>> anderer
>> Weise verwendet werden.
>>
>
>
