Pedro Ribeiro | 21 May 19:12 2015
Picon

[quagga-users 13999] OSPFv3 daemon inconsistencies between Quagga versions (and problems!)

Hello,

Sorry for the long email, I'm trying to send all the information that seems important for the problem analysts.

I'm using a few PCs working as routers with Quagga in a mixed vendor scenario.
After upgrading Quagga in one of the routers, a Cisco router became inaccessible over IPv6.
After analysis I've found the route to the Cisco's loopback interface was missing in the upgraded Quagga.
With some testing I've concluded that changing the address prefix from /128 to /127 changed the behaviour
of the newer Quagga and made the route appear in the table (with an undesired prefix but that's a minor problem).

Following I'm presenting a few command outputs from 3 of the equipments.
The Cisco that become inaccessible, an old Quagga (0.99.22.4) and the newer (0.99.24.1).

The loopback interface of the Cisco router is configured this way:

interface Loopback6
 no ip address
 ipv6 address 2001:690:2008::1003/128
 ipv6 ospf network point-to-point
 ipv6 ospf 1 area 0
end
The state of the Cisco database regarding the prefix LSAs
C1841#sh ipv6 ospf database prefix self-originate

            OSPFv3 Router with ID (193.137.220.250) (Process ID 1)

        Intra Area Prefix Link States (Area 0)

  Routing Bit Set on this LSA
  LS age: 7
  LS Type: Intra-Area-Prefix-LSA
  Link State ID: 0
  Advertising Router: 193.137.220.250
  LS Seq Number: 80003C5D
  Checksum: 0x58C1
  Length: 64
  Referenced LSA Type: 2001
  Referenced Link State ID: 0
  Referenced Advertising Router: 193.137.220.250
  Number of Prefixes: 2
  Prefix Address: 2001:690:2008::1003
  Prefix Length: 128, Options: LA , Metric: 0
  Prefix Address: 2001:690:2009:EFE0::
  Prefix Length: 64, Options: None, Metric: 400
In the new Quagga (named scratchy):
scratchy# sh version
Quagga 0.99.24.1 ().
Copyright 1996-2005 Kunihiro Ishiguro, et al.
configured with:
    --prefix=/usr --build=x86_64-pc-linux-gnu --host=x86_64-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --disable-dependency-tracking --disable-silent-rules --libdir=/usr/lib64 --docdir=/usr/share/doc/quagga-0.99.24.1 --enable-user=quagga --enable-group=quagga --enable-vty-group=quagga --with-cflags=-O2 -pipe -march=native -mtune=native -fno-strict-aliasing --sysconfdir=/etc/quagga --enable-exampledir=/usr/share/doc/quagga-0.99.24.1/samples --localstatedir=/run/quagga --disable-static --disable-pie --disable-capabilities --disable-pcreposix --disable-tcp-zebra --disable-doc --disable-ripngd --enable-multipath=0 --enable-vtysh --without-libpam --enable-ipv6 --enable-babeld --enable-ospf6d --enable-rtadv

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

scratchy# sh ipv6 ospf6 database adv-router 193.137.220.250

        Area Scoped Link State Database (Area 0.0.0.0)

Type LSId           AdvRouter       Age   SeqNum                        Payload
Rtr  0.0.0.0        193.137.220.250  32 80003d02       193.137.220.222/0.0.0.30
INP  0.0.0.0        193.137.220.250  39 80003c5d        2001:690:2008::1003/128
INP  0.0.0.0        193.137.220.250  39 80003c5d        2001:690:2009:efe0::/64
INP  0.0.0.0        193.137.220.250  39 80003c5d        2001:690:2009:efe0::/64

        I/F Scoped Link State Database (I/F bond0 in Area 0.0.0.0)

Type LSId           AdvRouter       Age   SeqNum                        Payload

        I/F Scoped Link State Database (I/F outs1dmz in Area 0.0.0.0)

Type LSId           AdvRouter       Age   SeqNum                        Payload
Lnk  0.0.0.12       193.137.220.2501039 80003c43       fe80::211:21ff:fe85:d2e2

        I/F Scoped Link State Database (I/F dummy0 in Area 0.0.0.0)

Type LSId           AdvRouter       Age   SeqNum                        Payload

        I/F Scoped Link State Database (I/F dummy1 in Area 0.0.0.0)

Type LSId           AdvRouter       Age   SeqNum                        Payload

        AS Scoped Link State Database

Type LSId           AdvRouter       Age   SeqNum                        Payload

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

scratchy# sh ipv6 ospf6 database intra-prefix adv-router 193.137.220.250

        Area Scoped Link State Database (Area 0.0.0.0)

Type LSId           AdvRouter       Age   SeqNum                        Payload
INP  0.0.0.0        193.137.220.250  63 80003c5d        2001:690:2008::1003/128
INP  0.0.0.0        193.137.220.250  63 80003c5d        2001:690:2009:efe0::/64
INP  0.0.0.0        193.137.220.250  63 80003c5d        2001:690:2009:efe0::/64

Are this 3 LSAs Ok? the 2nd and the 3rd seem duplicates, the older Quagga only has 1 (see below)
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

scratchy# sh ipv6 ospf6 database intra-prefix adv-router 193.137.220.250 detail

        Area Scoped Link State Database (Area 0.0.0.0)

Age:   78 Type: Intra-Prefix
Link State ID: 0.0.0.0
Advertising Router: 193.137.220.250
LS Sequence Number: 0x80003c5d
CheckSum: 0x58c1 Length: 64
Duration: 00:01:16
     Number of Prefix: 2
     Reference: Router Id: 0.0.0.0 Adv: 193.137.220.250
     Prefix Options: --|--|LA|--
     Prefix: 2001:690:2008::1003/128
     Prefix Options: --|--|--|--
     Prefix: 2001:690:2009:efe0::/64

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
The route isn't in the table, only the static blackhole route to our entire IPv6 block
scratchy# sh ipv6 route 2001:690:2008::1003
Routing entry for 2001:690:2008::/47
  Known via "static", distance 250, metric 0, reject
    directly connected, null0 inactive


In the older Quagga (named itchy)
itchy# sh version  
Quagga 0.99.22.4 ().
Copyright 1996-2005 Kunihiro Ishiguro, et al.

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

itchy# sh ipv6 ospf6 database adv-router 193.137.220.250

        Area Scoped Link State Database (Area 0.0.0.0)

Type         LSId            AdvRouter        Age   SeqNum Cksm  Len Duration
Router       0.0.0.0         193.137.220.250  101 80003d02 36a5   40 00:01:40
Intra-Prefix 0.0.0.0         193.137.220.250  109 80003c5d 58c1   64 00:01:47

        I/F Scoped Link State Database (I/F bond0 in Area 0.0.0.0)

Type         LSId            AdvRouter        Age   SeqNum Cksm  Len Duration

        I/F Scoped Link State Database (I/F outs1 in Area 0.0.0.0)

Type         LSId            AdvRouter        Age   SeqNum Cksm  Len Duration
Link         0.0.0.12        193.137.220.250 1109 80003c43 6515   44 00:18:27

        I/F Scoped Link State Database (I/F dummy0 in Area 0.0.0.0)

Type         LSId            AdvRouter        Age   SeqNum Cksm  Len Duration

        I/F Scoped Link State Database (I/F dummy1 in Area 0.0.0.0)

Type         LSId            AdvRouter        Age   SeqNum Cksm  Len Duration

        AS Scoped Link State Database

Type         LSId            AdvRouter        Age   SeqNum Cksm  Len Duration

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

itchy# sh ipv6 ospf6 database intra-prefix adv-router 193.137.220.250

        Area Scoped Link State Database (Area 0.0.0.0)

Type         LSId            AdvRouter        Age   SeqNum Cksm  Len Duration
Intra-Prefix 0.0.0.0         193.137.220.250  132 80003c5d 58c1   64 00:02:10

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

itchy# sh ipv6 ospf6 database intra-prefix adv-router 193.137.220.250 detail  

        Area Scoped Link State Database (Area 0.0.0.0)

Age:  150 Type: Intra-Prefix
Link State ID: 0.0.0.0
Advertising Router: 193.137.220.250
LS Sequence Number: 0x80003c5d
CheckSum: 0x58c1 Length: 64
     Number of Prefix: 2
     Reference: Router Id: 0.0.0.0 Adv: 193.137.220.250
     Prefix Options: --|--|LA|--
     Prefix: 2001:690:2008::1003/128
     Prefix Options: --|--|--|--
     Prefix: 2001:690:2009:efe0::/64

The route is in the route table of this equipment !!!

itchy# sh ipv6 route 2001:690:2008::1003
Routing entry for 2001:690:2008::1003/128
  Known via "ospf6", distance 110, metric 230, best
  Last update 00:03:40 ago
  * fe80::461e:a1ff:fe53:1250, via bond0

Ok, now I've changed the prefix in the address and repeated some commands.

interface Loopback6
 no ip address
 ipv6 address 2001:690:2008::1003/127
 ipv6 ospf network point-to-point
 ipv6 ospf 1 area 0
end

C1841#sh ipv6 ospf database prefix self-originate

            OSPFv3 Router with ID (193.137.220.250) (Process ID 1)

        Intra Area Prefix Link States (Area 0)

  Routing Bit Set on this LSA
  LS age: 500
  LS Type: Intra-Area-Prefix-LSA
  Link State ID: 0
  Advertising Router: 193.137.220.250
  LS Seq Number: 80003C5C
  Checksum: 0x1B03
  Length: 64
  Referenced LSA Type: 2001
  Referenced Link State ID: 0
  Referenced Advertising Router: 193.137.220.250
  Number of Prefixes: 2
  Prefix Address: 2001:690:2008::1002
  Prefix Length: 127, Options: None, Metric: 1
  Prefix Address: 2001:690:2009:EFE0::
  Prefix Length: 64, Options: None, Metric: 400

In the newer Quagga the LSAs seem similar, with the prefix changed
scratchy# sh ipv6 ospf6 database adv-router 193.137.220.250

        Area Scoped Link State Database (Area 0.0.0.0)

Type LSId           AdvRouter       Age   SeqNum                        Payload
Rtr  0.0.0.0        193.137.220.250 421 80003d00       193.137.220.222/0.0.0.30
INP  0.0.0.0        193.137.220.250 421 80003c5c        2001:690:2008::1002/127
INP  0.0.0.0        193.137.220.250 421 80003c5c        2001:690:2009:efe0::/64
INP  0.0.0.0        193.137.220.250 421 80003c5c        2001:690:2009:efe0::/64

        I/F Scoped Link State Database (I/F bond0 in Area 0.0.0.0)

Type LSId           AdvRouter       Age   SeqNum                        Payload

        I/F Scoped Link State Database (I/F outs1dmz in Area 0.0.0.0)

Type LSId           AdvRouter       Age   SeqNum                        Payload
Lnk  0.0.0.12       193.137.220.250 788 80003c43       fe80::211:21ff:fe85:d2e2

        I/F Scoped Link State Database (I/F dummy0 in Area 0.0.0.0)

Type LSId           AdvRouter       Age   SeqNum                        Payload

        I/F Scoped Link State Database (I/F dummy1 in Area 0.0.0.0)

Type LSId           AdvRouter       Age   SeqNum                        Payload

        AS Scoped Link State Database

Type LSId           AdvRouter       Age   SeqNum                        Payload

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

scratchy# sh ipv6 ospf6 database intra-prefix adv-router 193.137.220.250        

        Area Scoped Link State Database (Area 0.0.0.0)

Type LSId           AdvRouter       Age   SeqNum                        Payload
INP  0.0.0.0        193.137.220.250 446 80003c5c        2001:690:2008::1002/127
INP  0.0.0.0        193.137.220.250 446 80003c5c        2001:690:2009:efe0::/64
INP  0.0.0.0        193.137.220.250 446 80003c5c        2001:690:2009:efe0::/64

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

scratchy# sh ipv6 ospf6 database intra-prefix adv-router 193.137.220.250 detail

        Area Scoped Link State Database (Area 0.0.0.0)

Age:  463 Type: Intra-Prefix
Link State ID: 0.0.0.0
Advertising Router: 193.137.220.250
LS Sequence Number: 0x80003c5c
CheckSum: 0x1b03 Length: 64
Duration: 00:07:41
     Number of Prefix: 2
     Reference: Router Id: 0.0.0.0 Adv: 193.137.220.250
     Prefix Options: --|--|--|--
     Prefix: 2001:690:2008::1002/127
     Prefix Options: --|--|--|--
     Prefix: 2001:690:2009:efe0::/64
Now, the route is in the table
scratchy# sh ipv6 route 2001:690:2008::1003
Routing entry for 2001:690:2008::1002/127
  Known via "ospf6", distance 110, metric 201, best
  Last update 00:02:55 ago
  * fe80::211:21ff:fe85:d2e2, via outs1dmz

I'm I doing some mistake? It's the expected behaviour or a bug?
I hope this could help the developers.

regards. thanks for the excellent work in this project!
-- Best regards, =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Pedro Ribeiro IPLNet, Redes de dados e comunicações Departamento de Sistemas de Informação e Comunicações Instituto Politécnico de Lisboa Telefone: +351 210 464 701 VoIP: sip:80101-eNdSyHewRMXQUPosyRRdSA@public.gmane.org =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
_______________________________________________
Quagga-users mailing list
Quagga-users@...
https://lists.quagga.net/mailman/listinfo/quagga-users
Andrew Gideon | 20 May 23:23 2015

[quagga-users 13998] Re: SPEC file broken since 0.99.24

> thanks a lot! Works fine for me

That's good to know; thanks.

	- Andrew
Ana Lobo | 19 May 20:46 2015
Picon

[quagga-users 13996] Trying to run zebra daemon

Hi all!
I´m new in Quagga and I´ve just compiled and installed it successfully.
I´ve installed in the default directories (/usr/local/sbin and /usr/local/etc).
I´m tryin to start zebra daemon using this command line:

$ zebra --daemon -A 127.0.0.1

First of all, it didn´t succeed because it was trying to use the default user and group quagga/quagga. Therefore, I´ve configured again changing the user and group to my own user alobo/alobo, using this comand line:

$ ./configure --enable-user=alobo --enable-group=alobo -enable-vty-group=alobo

After this I compile and install quagga correctly, using these commands:
$ make
$ sudo make install

Now, when I try to start zebra daemon with this command:

$ zebra --daemon -A 127.0.0.1

I get the following error message:

privs_init: could not setgroups, Operation not permitted

Can you please help me?

Thanks in advance and best regards,
Ana



_______________________________________________
Quagga-users mailing list
Quagga-users@...
https://lists.quagga.net/mailman/listinfo/quagga-users
Pavel Odintsov | 15 May 09:52 2015
Picon

[quagga-users 13993] Support for BGP Flow Spec

Hello, folks!

Do you have any plans about support for RFC 5575/BGP Flow Spec?

I have BGP Flow Spec implemented with ExaBGP in my network for
internal tasks of traffic filtration
(https://github.com/FastVPSEestiOu/fastnetmon/blob/master/docs/EXABGP_INTEGRATION.md)
and I want to use it with my uplink.

But I can't because Quagga haven't support for flow spec and can't
propagate my flow spec announces from internal router to uplinks.

Could you recommend anything in this case?

--

-- 
Sincerely yours, Pavel Odintsov
David Ganor | 10 May 10:33 2015

[quagga-users 13988] How to deploy quagga-0.99.24 on Ubuntu12.04

Hi all,
I'm pretty new to quagga, so I hope I'm not asking an RTFM question ;-)

I've successfully downloaded the sources of quagga-0.99.24 and built a working soft-router running zebra and isisd daemons.
(all done inside an Oracle's VirtualBox4.3.26 virtual machine running Ubuntu12.04-32bit Linux)

Now I wish to pack this new quagga and install it on another VM used for lab testing (not a development VM, so there's no 'gcc', 'build-essential' and other required packages...)
This "lab" VM is already installed (using apt-get) with an older quagga (0.99.15).

I've tried just to copy the newly created zebra and isisd binaries, but they don't seem to work

Thank you for any help/suggestion
-- Best regards, David Ganor ||||||||||||||||||||||||||||||||||| Cell: +972-54-3090299 Tel: +972-74-7028642 Fax: +972-153-74-7028642 SW developer www.oliver-solutions.com |||||||||||||||||||||||||||||||||||
_______________________________________________
Quagga-users mailing list
Quagga-users@...
https://lists.quagga.net/mailman/listinfo/quagga-users
Dmitry Melekhov | 8 May 07:26 2015

[quagga-users 13984] ospf route is not installed ...

Hello!

I run quagga 0.99.22  on Centos 5.11 x86-64,
today I found that on of routes is not installed in server routing table,
it receives it, it announces it, but no route:

sh ip ospf database
10.1.200.72     10.3.2.10       1224 0x80001c87 0x8423 E2 10.1.200.72/30 
[0x0]

sh ip ospf route
N E2 10.1.200.72/30        [20/20] tag: 0
                            via 10.5.3.18, gre6

ip route | grep 10.1.200.72
shows nothing.

Could you tell me is this bug? Or how can I find what is problem cause?

Right now I added static route as workaround.

Thank you!
Andreas Schultz | 6 May 18:10 2015
Picon

[quagga-users 13983] Metric not honored when import default route from OSPF

Hi,

I have a router that gets it default route from OSPF from two different
routers. Both send different metrics, but ospfd is always importing
both routes. I've tried playing with different metrics and metric-type
without success.

As far as I can tell the metric are received correctly
(show ip ospf database external contains the correct metrics), but they
are not applied.

Any idea????

The routes originate from two vyos boxes (using quagga 0.99.20.1), the
other router is running quagga 0.99.23.

RT4# show ip route
Codes: K - kernel route, C - connected, S - static, R - RIP,
       O - OSPF, I - IS-IS, B - BGP, A - Babel,
       > - selected route, * - FIB route

O>* 0.0.0.0/0 [110/70] via 172.29.0.9, vnf-xe1p1, 00:22:13
  *                    via 172.29.0.10, vnf-xe1p1, 00:22:13

RT4# show ip ospf database  external 

       OSPF Router with ID (172.29.0.1)

                AS External Link States 

  LS age: 8
  Options: 0x2  : *|-|-|-|-|-|E|*
  LS Flags: 0x6  
  LS Type: AS-external-LSA
  Link State ID: 0.0.0.0 (External Network Number)
  Advertising Router: 172.20.16.49
  LS Seq Number: 80000202
  Checksum: 0x3e0c
  Length: 36
  Network Mask: /0
        Metric Type: 1
        TOS: 0
        Metric: 50
        Forward Address: 172.20.16.1
        External Route Tag: 0

  LS age: 8
  Options: 0x2  : *|-|-|-|-|-|E|*
  LS Flags: 0x6  
  LS Type: AS-external-LSA
  Link State ID: 0.0.0.0 (External Network Number)
  Advertising Router: 172.20.16.50
  LS Seq Number: 800001f9
  Checksum: 0x41de
  Length: 36
  Network Mask: /0
        Metric Type: 1
        TOS: 0
        Metric: 100
        Forward Address: 172.20.16.1
        External Route Tag: 0

RT4 config:

interface vnf-xe1p0
 ip ospf authentication message-digest
 ip ospf message-digest-key 1 md5 kowp4ButMo
 ipv6 nd suppress-ra
!
interface vnf-xe1p1
 ip ospf authentication message-digest
 ip ospf message-digest-key 1 md5 kowp4ButMo
 ipv6 nd suppress-ra
!
router ospf
 network 0.0.0.0/0 area 0.0.0.0
 area 0.0.0.0 authentication message-digest
 default-information originate metric 100
!
ip forwarding

vyos config:

interface eth1
 ip ospf authentication message-digest
 ip ospf message-digest-key 1 md5 kowp4ButMo
 ipv6 nd suppress-ra
 link-detect
!
interface lo
!
router ospf
 network 0.0.0.0/0 area 0.0.0.0
 area 0 authentication message-digest
 default-metric 100
 default-information originate metric 100 metric-type 1
!
ip route 0.0.0.0/0 172.20.16.1

Thanks
Andreas
-- 
--

-- 
Dipl. Inform.
Andreas Schultz
Kaz Nishimura | 5 May 14:56 2015

[quagga-users 13982] ospf6d no longer update routes in Debian GNU/Linux 8

I have used Quagga ospf6d for routing IPv6 between two isolated networks linked by a SIT tunnel on Debian GNU/Linux 7.  After upgrading to Debian 8, ospf6d no longer updates its internal routing table.

Debian 7 used Quagga 0.99.22.4 and Debian 8 now uses 0.99.23.1.  I guess it was caused by changes made to ospf6d in version 0.99.23 but I have a very little time to examine what is going wrong.  Where should I check first?

I have already sent a bug report to Debian, but the package maintainer is not an expert in OSPFv3, so I am asking here.
_______________________________________________
Quagga-users mailing list
Quagga-users@...
https://lists.quagga.net/mailman/listinfo/quagga-users
Qin, Xiaohong | 4 May 19:54 2015

[quagga-users 13979] netconf in quagga

Hi All,

 

Does Quagga support netconf? If yes, how to enable and configure it?

 

Thanks.

 

Dennis Qin (aka Xiaohong Qin)

_______________________________________________
Quagga-users mailing list
Quagga-users@...
https://lists.quagga.net/mailman/listinfo/quagga-users
Nilton Gabriel Bueno Pires | 2 May 20:02 2015
Picon

[quagga-users 13978] BGP multipath

Hello,

I`m trying to setup a multipath environment with quagga bgp and mikrotik. The network scenario as follows:

Quagga Router A ====Ethernet===== Mikrotik BGP
Quagga Router B ====Ethernet===== Mikrotik BGP
Quagga Router A ====Ethernet===== Quagga Router B

So i have a network on mikrotik 186.251.121.0/28
and i annouce via bgp to Quagga Router A and Quagga Router B
and based on the metric i want to send this network through the Router B that go through Router A to the internet, and if the Router B fails I want to send the network directly to router A and to the internet.

So i have configured the 3 routers, and via filters on the mikrotik set the metric of that network to 50 when it goes to Router B and 100 when it goes through Router A, but Router A that is receiving the route sets the mikrotik as the next-hop to the network, and even if i don’t announce the network to Router A, it continues to set the route gateway to the mikrotik, even if it receives the route from Router B, i’ve tried several different configurations to no avail, if anyone knows how to configure this scenario, or tips, anything that helps, i would apreciate very much. Thanks.


The config I am using on Router A
router bgp 262831
 bgp deterministic-med
 network 186.251.120.0/22
 neighbor 186.251.122.18 remote-as 262831
 neighbor 186.251.122.18 prefix-list bpout out
 neighbor 186.251.122.18 route-map rteste in
 neighbor 186.251.122.210 remote-as 262831
 neighbor 186.251.122.210 description ccrlocal
 neighbor 186.251.122.210 default-originate
 neighbor 186.251.122.210 prefix-list interno in
 neighbor 186.251.122.210 prefix-list interno out
!
ip prefix-list bpout seq 10 permit 186.251.120.0/22 le 23
ip prefix-list interno seq 5 deny 186.251.122.192/28
ip prefix-list interno seq 10 permit 186.251.120.0/22 ge 23
ip prefix-list interno seq 65000 deny any
!
route-map rteste permit 1000
 set originator-id 186.251.122.18

The config I am using on Router B
router bgp 262831
 bgp router-id 186.251.122.18
 redistribute kernel
 redistribute connected
 redistribute static
 neighbor 186.251.122.17 remote-as 262831
 neighbor 186.251.122.17 route-reflector-client
 neighbor 186.251.122.17 prefix-list bpout out
 neighbor 186.251.122.17 route-map r100 out
 neighbor 186.251.122.194 remote-as 262831
 neighbor 186.251.122.194 description ccrlocal
 neighbor 186.251.122.194 default-originate
 neighbor 186.251.122.194 prefix-list bpout out
 neighbor 186.251.122.196 remote-as 262831
 neighbor 186.251.122.196 description cabo
 neighbor 186.251.122.196 default-originate
 neighbor 186.251.122.196 prefix-list bpout out
 neighbor 186.251.122.197 remote-as 262831
 neighbor 186.251.122.197 description saae
 neighbor 186.251.122.197 default-originate
 neighbor 186.251.122.197 prefix-list bpout out
 neighbor 186.251.122.198 remote-as 262831
 neighbor 186.251.122.198 description prm
 neighbor 186.251.122.198 default-originate
 neighbor 186.251.122.198 prefix-list bpout out
 neighbor 186.251.122.199 remote-as 262831
 neighbor 186.251.122.199 description rancho
 neighbor 186.251.122.199 default-originate
 neighbor 186.251.122.199 prefix-list bpout out
 neighbor 186.251.122.200 remote-as 262831
 neighbor 186.251.122.200 description rancho58
 neighbor 186.251.122.200 default-originate
 neighbor 186.251.122.200 prefix-list bpout out
 neighbor 186.251.122.201 remote-as 262831
 neighbor 186.251.122.201 description ibiaci
 neighbor 186.251.122.201 default-originate
 neighbor 186.251.122.201 prefix-list bpout out
!
access-list 10 permit 186.251.121.243
!
ip prefix-list bgnone seq 10 deny any
ip prefix-list bpout seq 10 permit 186.251.120.0/22 ge 23
ip prefix-list bpout seq 65000 deny any
ip prefix-list redethunder seq 10 permit 186.251.122.192/28
ip prefix-list teste seq 100 permit 186.251.121.243/32
!
route-map r100 permit 5
 match ip address prefix-list redethunder
 set metric 10
 set weight 1
 on-match goto 10000
!
route-map r100 permit 10
 match ip address 10
 set originator-id 186.251.122.18
 set metric 10
 on-match goto 10000
!
route-map r100 permit 100
 set metric +30
 set originator-id 186.251.122.18

Nilton Gabriel Bueno Pires <gabriel-3ZsmRO42UTI39yzSjRtAkw@public.gmane.org>
+55 43 3232 1627
+55 43 9117 7672








_______________________________________________
Quagga-users mailing list
Quagga-users@...
https://lists.quagga.net/mailman/listinfo/quagga-users
Andrew Gideon | 30 Apr 03:09 2015

[quagga-users 13976] Re: SPEC file broken since 0.99.24

Timo:

I'm surprised you got as far as you did, but I've only actually built
this - as opposed to using RPMs built by others - a couple of times.  

I found the same issue you did regarding "with_pimd".  I solved this
(differently than you; more details below), but then I hit a dependency
issue.  As of RHEL/CentOS 6, the tetex RPM has disappeared.  It appears
that texlive replaces it.

I've now successfully built RPMs using both CentOS 6.6 and 7.1.1503.

Here are my changes to the spec file for you to try:

[tagonline <at> CentOS7GuestC quagga]$ diff -u /tmp/0.99.24.1-quagga.spec.in /tmp/0.99.24.1-andrew-quagga.spec.in
--- /tmp/0.99.24.1-quagga.spec.in	2015-04-29 20:42:23.004388941 -0400
+++ /tmp/0.99.24.1-andrew-quagga.spec.in	2015-04-29 20:42:46.795315014 -0400
 <at>  <at>  -20,6 +20,7  <at>  <at> 
 %{!?with_irdp:		%define	with_irdp	1 }
 %{!?with_rtadv:		%define	with_rtadv	1 }
 %{!?with_isisd:		%define	with_isisd	1 }
+%{!?with_pimd:		%define	with_pimd	1 }
 %{!?with_shared:	%define	with_shared	1 }
 %{!?with_multipath:	%define	with_multipath	64 }
 %{!?quagga_user:	%define	quagga_user	quagga }
 <at>  <at>  -44,7 +45,7  <at>  <at> 
 %{!?dist:		%define		dist	%{default_dist}}

 # as distros change packages we depend on, our Requires have to change, sadly.
-%define quagga_buildreqs texi2html texinfo tetex autoconf pam-devel
+%define quagga_buildreqs texi2html texinfo autoconf pam-devel
 %define quagga_buildreqs %{quagga_buildreqs} patch libcap-devel

 # FC4 and 5 split texi2html out of tetex package.
 <at>  <at>  -52,6 +53,16  <at>  <at> 
 %define  quagga_buildreqs %{quagga_buildreqs} texi2html
 %endif

+# Redhat 6 & 7 don't include tetex - There are probably Fedora versions
+# for which this needs to be done as well.  This code presumes that 
+# something other than rhel uses tetex.  That's likely not always
+# correct.
+%if 0%{rhel} < 6
+%define  quagga_buildreqs %{quagga_buildreqs} tetex
+%else
+%define  quagga_buildreqs %{quagga_buildreqs} texlive
+%endif
+
 # pam_stack is deprecated in FC5
 # default to pam_stack, default should be changed later.
 %if "%dist" == "fc4" || "%dist" == "fc3"
 <at>  <at>  -103,7 +114,18  <at>  <at> 
 BuildRequires:	readline readline-devel ncurses ncurses-devel
 Requires(pre):		ncurses
 %endif
-BuildRequires:	texinfo tetex autoconf pam-devel patch libcap-devel tetex
+BuildRequires:	texinfo autoconf pam-devel patch libcap-devel
+
+# Redhat 6 & 7 don't include tetex - There are probably Fedora versions
+# for which this needs to be done as well.  This code presumes that 
+# something other than rhel uses tetex.  That's likely not always
+# correct.
+%if 0%{rhel} < 6
+BuildRequires:	tetex
+%else
+BuildRequires:	texlive
+%endif
+
 # Initscripts > 5.60 is required for IPv6 support
 Requires(pre):		initscripts >= 5.60
 Requires(pre):		ncurses pam
[tagonline <at> CentOS7GuestC quagga]$ 

This is built from changes to quagga.spec.in in git using the defined
release procedure.  This is still only in my local copy of the
repository, of course.  If and when this works for you, I'll post to the
dev list for review.

	- Andrew

Gmane