http://blog.gmane.org/gmane.network.quagga.user hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://comments.gmane.org/gmane.network.quagga.user/12605 <pre> I created a peer-group, but found that it wasn't allowing me to add additional prefix-lists to different neighbors, only the prefix-list that was defined for the peer-group was getting applied. In the below example, I found that the prefix-list called 'peera-allowed-out' was not applied to that peer, only the peer-group prefix-list. First I created a peer-group and set a prefix-list to be applied to every member of that peer-group: ! define an 'upstream' peer-group and set it so the prefix-list ! 'allowed-in' is applied to all of them neighbor upstream peer-group neighbor upstream prefix-list allowed-in in ! !Then I defined a neighbor: ! ! BGP peerA neighbor 192.168.0.1 remote-as 16652 ! then I set a specify prefix-list for outbound: neighbor 192.168.0.1 prefix-list peera-allowed-out out neighbor 192.168.0.1 peer-group upstream neighbor 192.168.0.1 description PeerA neighbor 192.168.0.1 update-source 192.168.0.2 ! ! here is that specific prefix-list: ip prefix-list peera-allowed-out permit 10.0.0.0/24 ip prefix-list peera-allowed-out deny any ! ! and then the prefix-list for the peer-group ip prefix-list allowed-in deny 0.0.0.0/0 ! localhost ip prefix-list allowed-in deny 127.0.0.0/8 ip prefix-list allowed-in deny 10.0.0.0/24 ip prefix-list allowed-in permit any Can someone clue me in to what I dont understand about peer-group configuration? thanks, micah </pre> micah anderson 2012-05-21T15:23:27 http://comments.gmane.org/gmane.network.quagga.user/12604 <pre>Hi, I was checking in VTYSH that the desabiliar any of the daemons, the commands available in the same continues VTYSH. Would have any way to disable it, the compilation, according to the daemons that I'm enabling? Regards, Marco Túlio _______________________________________________ Quagga-users mailing list Quagga-users-UOy77sIEA+cAd7ICUelF/Q&lt; at &gt;public.gmane.org http://lists.quagga.net/mailman/listinfo/quagga-users </pre> Marco Tulio R Braga 2012-05-18T11:52:23 http://comments.gmane.org/gmane.network.quagga.user/12602 <pre>Hi All, We are exercising quagga0.99.20-quagga-ripd.  keychain  configuration commands in the below mentioned scenario leads to quagg-ripd crash. Did anybody observe this ? Please share any patch/fix for this issue. ============== steps to arrive the issue ============ telnet 127.1 2602 &lt;&lt;zebra, login password ripd$enable ripd#conf term .. .. ripd(config-keychain)# do sh run Current configuration: ! hostname ripd password zebra log stdout ! key chain testing key 14  key-string testing  accept-lifetime 09:33:15 May 18 2012 duration 120 ! router rip network eth0 ! line vty ! end ripd(config-keychain)# no ke ripd(config-keychain)# no key 14 ripd(config-keychain)# ke ripd(config-keychain)# key 14 ripd(config-keychain-key)# ac ripd(config-keychain-key)# accept-lifetime 09:33:15 May 18 2012 duration 120 ripd(config-keychain-key)# ke ripd(config-keychain-key)# key-st ripd(config-keychain-key)# key-string st ripd(config-keychain-key)# key-string testing ripd(config-keychain-key)# ripd# conf ter ripd(config)# i interface  ip         ipv6 ripd(config)# in ripd(config)# interface eth0 ripd(config-if)# ip rip au ripd(config-if)# ip rip authentication m ripd(config-if)# ip rip authentication mode m ripd(config-if)# ip rip authentication mode md5 ripd(config-if)# ip ri ripd(config-if)# ip rip au ripd(config-if)# ip rip authentication k ripd(config-if)# ip rip authentication key-chain testing ripd(config-if)# k ripd(config-if)# ip rip sp ripd(config-if)# ip rip split-horizon p ripd(config-if)# ip rip split-horizon poisoned-reverse ripd(config-if)# ip rip ripd(config-if)# ip rip se ripd(config-if)# ip rip send ver ripd(config-if)# ip rip send version 2 ripd(config-if)# ip ri ripd(config-if)# ip rip r ripd(config-if)# ip rip receive ver ripd(config-if)# ip rip receive version 2 ripd(config-if)# exit ripd(config)# ke ripd(config)# key ch ripd(config)# key chain test ripd(config)# do sh ip rip Codes: R - RIP, C - connected, S - Static, O - OSPF, B - BGP Sub-codes:      (n) - normal, (s) - static, (d) - default, (r) - redistribute,      (i) - interface     Network            Next Hop         Metric From            Tag Time C(i) 192.168.1.0/24     0.0.0.0               1 self              0 ripd(config)# ke ripd(config)# key c ripd(config)# key chain testing ripd(config-keychain)# no ke ripd(config-keychain)# no key 14 ripd(config-keychain)# ke ripd(config-keychain)# key 14 ripd(config-keychain-key)# ac ripd(config-keychain-key)# accept-lifetime 09:33:15 May 18 2012 duration 120Connection closed by foreign host. root&lt; at &gt;linux:~# /* Here the ripd got crashed, hence quagga-ripd  shell is closed */ ============== steps to arrive the issue ============ </pre> Ganesh Reddy K 2012-05-17T06:04:08 http://comments.gmane.org/gmane.network.quagga.user/12594 <pre>Hello List. Cisco says that with their OSPF implementation if the route cost are the same they do CEF, Does quagga on Linux 2.6.32 or later do any kind of load balancing if the costs are the same? Thanks for any info. </pre> Steve Clark 2012-05-16T16:15:51 http://comments.gmane.org/gmane.network.quagga.user/12590 <pre>Hello! I've this error during compile with --disable-ipv6 gcc -DHAVE_CONFIG_H -DSYSCONFDIR=\"/etc/quagga/\" -DMULTIPATH_NUM=0 -I. -I.. -I.. -I.. -I../lib -fPIE -Os -fno-omit-frame-pointer -g -std=gnu99 -Wall -Wsign-compare -Wpointer-arith -Wbad-function-cast -Wwrite-strings -Wmissing-prototypes -Wmissing-declarations -Wchar-subscripts -Wcast-qual -MT zebra_rib.o -MD -MP -MF .deps/zebra_rib.Tpo -c -o zebra_rib.o zebra_rib.c mv -f .deps/zebra_rib.Tpo .deps/zebra_rib.Po gcc -DHAVE_CONFIG_H -DSYSCONFDIR=\"/etc/quagga/\" -DMULTIPATH_NUM=0 -I. -I.. -I.. -I.. -I../lib -fPIE -Os -fno-omit-frame-pointer -g -std=gnu99 -Wall -Wsign-compare -Wpointer-arith -Wbad-function-cast -Wwrite-strings -Wmissing-prototypes -Wmissing-declarations -Wchar-subscripts -Wcast-qual -MT interface.o -MD -MP -MF .deps/interface.Tpo -c -o interface.o interface.c In file included from interface.c:37: ../zebra/rtadv.h:33: error: field âprefixâ has incomplete type make[2]: *** [interface.o] Error 1 make[2]: Leaving directory `/usr/local/src/quagga-0.99.21/zebra' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/usr/local/src/quagga-0.99.21' make: *** [all] Error 2 All other version are compiled correctly Thanks --- Sim </pre> Sim 2012-05-15T13:26:58 http://comments.gmane.org/gmane.network.quagga.user/12588 <pre>Hi. I'm using quagga to handle ipv6 routes in my network. I have the following setup: router A &lt;---ethernet---&gt; router B &lt;----WAN gre tunnels----&gt; multiple ospf routers The problem is that quagga on router A reriodically loses (I'd say 'deletes', because in debug mode it's clear that router A quagga does that) routes received by the router B from multiple other routers and announced to the A. The following output will show it more clearly: Router B table: wizard.hq.norma.perm.ru# sh ipv6 route ospf Codes: K - kernel route, C - connected, S - static, R - RIPng, O - OSPFv3, I - ISIS, B - BGP, * - FIB route. O&gt;* 2001:470:1f08:14c0::1/128 [110/1] via fe80::21a:64ff:fec6:a87c, vlan1, 00:21:45 O 2001:470:1f09:14c0::/120 [110/1] via fe80::202:b3ff:fee9:8d0e, vlan1, 07w2d06h O&gt;* 2a00:5cc0:c::/64 [110/2] via fe80::21a:64ff:fe21:9489, gre6, 03:13:14 O&gt;* fd00::/120 [110/2] via fe80::21a:64ff:fe21:910e, gre1, 01w0d03h O fd00::300/120 [110/1] is directly connected, vlan1, 09w5d02h O&gt;* fd00::700/120 [110/1] via fe80::202:b3ff:fee9:8d0e, vlan1, 09w4d18h O&gt;* fd00::d00/120 [110/2] via fe80::21a:64ff:fe21:9489, gre6, 03:10:25 O&gt;* fd00::b400/120 [110/2] via fe80::21a:64ff:fe21:962d, gre2, 2d03h56m Router A table after ospf6d is launched: taiga# sh ipv6 route ospf Codes: K - kernel route, C - connected, S - static, R - RIPng, O - OSPFv3, I - ISIS, B - BGP, * - FIB route. O 2001:470:1f09:14c0::/120 [110/1] via fe80::202:b3ff:fee9:8d0e, vlan1, 00:00:29 O&gt;* 2a00:5cc0:c::/64 [110/2] via fe80::21a:64ff:fe21:8e80, vlan1, 00:00:29 O&gt;* fd00::/120 [110/3] via fe80::21a:64ff:fe21:8e80, vlan1, 00:00:29 O fd00::300/120 [110/1] is directly connected, vlan1, 00:00:30 O fd00::700/120 [110/1] via fe80::202:b3ff:fee9:8d0e, vlan1, 00:00:29 O&gt;* fd00::d00/120 [110/4] via fe80::21a:64ff:fe21:8e80, vlan1, 00:00:29 O&gt;* fd00::b400/120 [110/2] via fe80::21a:64ff:fe21:8e80, vlan1, 00:00:29 O fe80::/64 [110/1] via fe80::21a:64ff:fe21:8e80, vlan1, 00:00:29 Router A table after some time: taiga# sh ipv6 route ospf Codes: K - kernel route, C - connected, S - static, R - RIPng, O - OSPFv3, I - ISIS, B - BGP, * - FIB route. O 2001:470:1f09:14c0::/120 [110/1] via fe80::202:b3ff:fee9:8d0e, vlan1, 00:23:20 O&gt;* fd00::/120 [110/3] via fe80::21a:64ff:fe21:8e80, vlan1, 00:23:20 O fd00::300/120 [110/1] is directly connected, vlan1, 00:23:21 O fd00::700/120 [110/1] via fe80::202:b3ff:fee9:8d0e, vlan1, 00:23:20 O&gt;* fd00::d00/120 [110/4] via fe80::21a:64ff:fe21:8e80, vlan1, 00:23:20 Notice the fd00::b400/120 route is gone. However, it's still present in the router B table. This isn't specific to quagga version. I observed this on like 5 last versions. How can this be solved ? Is this some error in my ospf setup ? By the way, can I use the same OSPF area numbers in OSPF6 as in OSPF4 (I use the same) ? Thanks. Eugene. </pre> Eugene M. Zheganin 2012-05-15T04:32:15 http://comments.gmane.org/gmane.network.quagga.user/12584 <pre>Hello, I cannot get isisd to run with zebra. If I start up an instance on one node, it will stay up but as soon as I start up another neighboring node with isis, the original node aborts with an assertion failure. I am using the latest cloned version from git (after 0.99.21 release). Here is a the run with the assertion failure: bb02-sf% sudo ./isisd -A 127.0.0.1 -f isisd.conf -i /var/run/quagga/isisd.pid 2012/05/08 17:35:18 ISIS: ISIS-Spf: TENT is empty SPF-root:isisd 2012/05/08 17:35:18 ISIS: ISIS-Spf: TENT is empty SPF-root:isisd 2012/05/08 17:35:18 ISIS: ISIS-Spf: TENT is empty SPF-root:isisd 2012/05/08 17:35:18 ISIS: ISIS-Spf: TENT is empty SPF-root:isisd 2012/05/08 17:35:18 ISIS: Quagga-ISISd 0.99.21 starting: vty&lt; at &gt;2608 2012/05/08 17:35:48 ISIS: ISIS-Spf: TENT is empty SPF-root:isisd 2012/05/08 17:36:18 ISIS: ISIS-Spf: TENT is empty SPF-root:isisd 2012/05/08 17:50:29 ISIS: ISIS-Spf: TENT is empty SPF-root:isisd 2012/05/08 17:52:40 ISIS: ISIS-Adj: No usable IP interface addresses in LAN IIH from eth1 2012/05/08 17:52:42 ISIS: Assertion `isis_find_vertex (spftree-&gt;paths, id, vtype) == ((void *)0)' failed in file isis_spf.c, line 515, function isis_spf_add2tent 2012/05/08 17:52:42 ISIS: Backtrace for 17 stack frames: 2012/05/08 17:52:42 ISIS: [bt 0] /home/hasenov/quagga_current/quagga/lib/.libs/libzebra.so.0(zlog_backtrace+0x1f) [0xb782707a] 2012/05/08 17:52:42 ISIS: [bt 1] /home/hasenov/quagga_current/quagga/lib/.libs/libzebra.so.0(_zlog_assert_failed+0x92) [0xb78271dd] 2012/05/08 17:52:42 ISIS: [bt 2] /home/hasenov/quagga_current/quagga/isisd/.libs/lt-isisd(+0x1dbf7) [0xb7884bf7] 2012/05/08 17:52:42 ISIS: [bt 3] /home/hasenov/quagga_current/quagga/isisd/.libs/lt-isisd(+0x1de9f) [0xb7884e9f] 2012/05/08 17:52:42 ISIS: [bt 4] /home/hasenov/quagga_current/quagga/isisd/.libs/lt-isisd(+0x1e7d3) [0xb78857d3] 2012/05/08 17:52:42 ISIS: [bt 5] /home/hasenov/quagga_current/quagga/isisd/.libs/lt-isisd(+0x5b03) [0xb786cb03] 2012/05/08 17:52:42 ISIS: [bt 6] /home/hasenov/quagga_current/quagga/isisd/.libs/lt-isisd(+0x5b3c) [0xb786cb3c] 2012/05/08 17:52:42 ISIS: [bt 7] /home/hasenov/quagga_current/quagga/isisd/.libs/lt-isisd(+0x94ec) [0xb78704ec] 2012/05/08 17:52:42 ISIS: [bt 8] /home/hasenov/quagga_current/quagga/isisd/.libs/lt-isisd(+0x98cc) [0xb78708cc] 2012/05/08 17:52:42 ISIS: [bt 9] /home/hasenov/quagga_current/quagga/isisd/.libs/lt-isisd(+0x1c28d) [0xb788328d] 2012/05/08 17:52:42 ISIS: [bt 10] /home/hasenov/quagga_current/quagga/isisd/.libs/lt-isisd(+0x519d) [0xb786c19d] 2012/05/08 17:52:42 ISIS: [bt 11] /home/hasenov/quagga_current/quagga/isisd/.libs/lt-isisd(+0x1078a) [0xb787778a] 2012/05/08 17:52:42 ISIS: [bt 12] /home/hasenov/quagga_current/quagga/isisd/.libs/lt-isisd(isis_receive+0x1c3) [0xb787a9b3] 2012/05/08 17:52:42 ISIS: [bt 13] /home/hasenov/quagga_current/quagga/lib/.libs/libzebra.so.0(thread_call+0x5b) [0xb781ad50] 2012/05/08 17:52:42 ISIS: [bt 14] /home/hasenov/quagga_current/quagga/isisd/.libs/lt-isisd(main+0x40c) [0xb786b4cb] 2012/05/08 17:52:42 ISIS: [bt 15] /lib/libc.so.6(__libc_start_main+0xe7) [0xb767bce7] 2012/05/08 17:52:42 ISIS: [bt 16] /home/hasenov/quagga_current/quagga/isisd/.libs/lt-isisd(+0x3f51) [0xb786af51] Abort And here is my config: hostname isisd password foo enable password foo log stdout ! interface eth0 ! interface eth1 ip router isis Test1 isis circuit-type level-1 ! interface eth2 ! ip router isis Test1 ! isis circuit-type level-1 ! interface eth3 ! interface lo ! router isis Test1 net 51.0000.0000.0116.00 metric-style wide is-type level-1 ! line vty ! - Hristo_______________________________________________ Quagga-users mailing list Quagga-users-UOy77sIEA+cAd7ICUelF/Q&lt; at &gt;public.gmane.org http://lists.quagga.net/mailman/listinfo/quagga-users </pre> Hristo Asenov 2012-05-14T04:48:06 http://comments.gmane.org/gmane.network.quagga.user/12582 <pre>Hello, I have running ospf6d with other quaggas and ciscos, it working fine. However we also have a Juniper MX80 and when I try to do ospf between quagga (tried a couple of versions including 0.99.21) it crash. quagga# sh ipv6 ospf6 neighbor Neighbor ID Pri DeadTime State/IfState Duration I/F[State] X.X.X.1 1 00:00:38 Full/DR 00:00:48 vlan2000[BDR] X.X.X.2 128 00:00:35 Full/DR 00:00:04 vlan2003[BDR] quagga1# sh ipv6 ospf6 neighbor Warning: closing connection to ospf6d because of an I/O error! quagga# After a a couple of seconds when I add vlan2003 to the area I can see the neighbour for a couple of seconds and then it crash. Any ideas? /Jonas </pre> jb-rtBqxLFAbNU< at >public.gmane.org 2012-05-07T05:08:14 http://comments.gmane.org/gmane.network.quagga.user/12581 <pre>Hi, i wonder if there is any on-job MPLS support on quagga daemons ? Thanks, </pre> Sami Halabi 2012-05-06T06:16:41 http://comments.gmane.org/gmane.network.quagga.user/12580 <pre>Hello. I revealed a regression in OSPF's access list (OS Linux). ospfd.conf: router ospf &lt;skip&gt; distribute-list reject_local_network out kernel ! access-list reject_local_network deny 10.0.0.0/8 access-list reject_local_network deny 192.168.0.0/16 access-list reject_local_network permit any System have static route: # ip r|grep 192.168.111 192.168.111.0/24 via x.x.x.1 dev eth1 This route is not advertised with versions prior to 0.99.21. </pre> Sergey 2012-05-05T16:37:48 http://comments.gmane.org/gmane.network.quagga.user/12576 <pre>Does quagga supports 32 bit ASNs? Thanks, </pre> bolivar-o08fFCl+uX5axL8h6EyKEw< at >public.gmane.org 2012-05-02T03:02:51 http://comments.gmane.org/gmane.network.quagga.user/12572 <pre> Got an odd issue with IPv6 ospf6d. I have a couple quagga routers (0.99.20.1 on linux) that share a network with a Cisco router that is functioning as Area Border Router. The Area is 131.94.128.0 The cisco Area Border Router also connects to area 0. In area 0 is a ASBR that is injecting a default route (::0/0) When I bring up router1 all seems fine. Router1 receives and uses a few routes from area 0, and announces a downstream network as well. But as soon as I bring up router 2, after the DB exchange a LSA is sent from router2 to router1, and this causes router1 to do a SPF calculation. When router1 does this SPF calculation it loses the default route. Well, it discards the default route. router2 comes up fine, and it does use the ASE default route. Until something changes and a SPF calc is done on router2, then it will discard the default route. Any ideas what is happening here? It doesn't make sense to me other than some bug in the SPF calculation. But maybe I am missing something?? E ------- Details available via web in directory http://users.cis.fiu.edu/~esj/quagga-problem-ospf3/ http://users.cis.fiu.edu/~esj/quagga-problem-ospf3/network.png is the picture http://users.cis.fiu.edu/~esj/quagga-problem-ospf3/router1.ospf6d.conf http://users.cis.fiu.edu/~esj/quagga-problem-ospf3/router2.ospf6d.conf are the relevant parts of the config files of the two quagga routers http://users.cis.fiu.edu/~esj/quagga-problem-ospf3/ospf6d.log router1 ospf6d logs with the following set: debug ospf6 message lsupdate debug ospf6 lsa unknown debug ospf6 zebra debug ospf6 spf process debug ospf6 route table debug ospf6 route intra-area debug ospf6 route inter-area debug ospf6 asbr debug ospf6 abr also has some annotation by me and references to packets in the .pcap http://users.cis.fiu.edu/~esj/quagga-problem-ospf3/ospf6-database-before show ospf6 database detail show ospf6 database dump before the LSA arrived and the SPF ran http://users.cis.fiu.edu/~esj/quagga-problem-ospf3/ospf6-database-after show ospf6 database detail show ospf6 database dump after the LSA arrived and the SPF ran and the ASE type 1 with the default route was removed. http://users.cis.fiu.edu/~esj/quagga-problem-ospf3/tcpdump.full.pcap a pcap from the point of view of router1 as all this was happening. </pre> Eric S. Johnson 2012-05-01T17:05:16 http://comments.gmane.org/gmane.network.quagga.user/12567 <pre>Hello! I encounter one strange problem: - FreeBSD 9.0 x64; - Quagga 0.99.20; - DHClient FreeBSD native and ISC-DHCP42-Client. When system starts DHCP client which was put into /sbin instead of dhclient gets address system works or some time normally. But when lease elapses DHCP-Client asks for new lease... At that moment interface loose its IP at all, all sessions go down, connectivity get lost. What do I do? I stop Quagga (nothing else does not help!), I kill dhclient process, I start dhclient again and I start Quagga. All is fine again. But... BGP-sessions - it is not a joke! VPN-tunnels over Internet to remote sites are UP for short time but real connectivity with remote computers appears after rather long time - while Quagga exchanges LSAs via tunnels with another OSPF neighbors. Our ISP's requirement is to lease IP for several hours! Do you understand what it means? Question: what could it be? May you help me? I've changed FreeBSD 7.2 x64 on current 9.0-release, but old problem is still here... :-( I exhausted all my mind. Kind regards, Ellad G. Yatsko </pre> Ellad G. Yatsko 2012-04-24T14:26:43 http://comments.gmane.org/gmane.network.quagga.user/12565 <pre>Hi, Quagga-0.99.20 is allowing v4 and v6 neighbors to be attached to a single peer-group. Is this a valid configuration ? If valid how often this kind of scenario can be seen in real time deployment ? Thanks Sridhar Pothuganti _______________________________________________ Quagga-users mailing list Quagga-users-UOy77sIEA+cAd7ICUelF/Q&lt; at &gt;public.gmane.org http://lists.quagga.net/mailman/listinfo/quagga-users </pre> Sridhar Pothuganti 2012-04-24T06:47:20 http://comments.gmane.org/gmane.network.quagga.user/12563 <pre>Dear Everybody, I'm new on this list because until now I was just a happy user of quagga, I had no problem with it. But now I need some really urgent help with quagga. I'm installed a new machine with pfsense 2.0.1 on amd64. I'm installed the quagga from the pfsense package manager. It installed the version quagga-0.99.20_3. I'm trying to run zebra only to manage some static routes. (pfsense builtin routes not an option because the destination interfaces are not up at boot time) Here is the zebra conf, with only one rule for testing: log syslog ip route 172.20.71.0/24 172.30.253.12 If I'm adding this rule from console with route add command then everything works perfectly and I'm getting the following output on the route monitor command: got message of size 192 on Wed Apr 18 10:03:41 2012 RTM_ADD: Add Route: len 192, pid: 41494, seq 1, errno 0, flags:&lt;UP,GATEWAY,DONE,STATIC&gt; locks: inits: sockaddrs: &lt;DST,GATEWAY,NETMASK&gt; 172.20.71.0 172.30.253.12 (0) 0 ffff ff If I'm starting zebra it sends some error to the error log: zebra[47974]: kernel_rtm_ipv4: 172.20.71.0/24: rtm_write() unexpectedly returned -5 for command RTM_ADD zebra[47974]: rtm_write: write : Invalid argument (22) and the route monitor sends the following output: got message of size 140 on Wed Apr 18 10:12:23 2012 RTM_ADD: Add Route: len 140, pid: 0, seq 0, errno 0, flags:&lt;UP,GATEWAY,PROTO1&gt; locks: inits: sockaddrs: &lt;DST,GATEWAY,NETMASK&gt; 172.20.71.0 172.30.253.12 (255) ffff ffff ff Have anybody any idea what can be the problem? What I can see that the end of the command (the netmask) differs but I don't know why it is 0 or 255, the commands are the same. Thank you in advance. Best Regards: Gabor Debreczeni-Kis </pre> Gabor Debreczeni-Kis 2012-04-18T08:22:07 http://comments.gmane.org/gmane.network.quagga.user/12562 <pre>In testing I discovered this bug is affecting me: http://www.vyatta.org/forum/viewtopic.php?t=4326&amp;sid=5466ad49da1d7d6eaf56cc34b0f3faad This is, IPv6 Null0 blackhole routes are inactive, while IPv4 ones work. ip route 10.0.0.0/24 Null0 250 ipv6 route fe80::/64 Null0 250 However: show ip route static S 10.0.0.0/24 [250/0] is directly connected, Null0, bh show ipv6 route static S fe80::/64 [250/0] is directly connected, Null0 inactive Is this a bug, and what is the workaround? Must I configure null routes in the host OS directly? Regards, Tyler </pre> Tyler J. Wagner 2012-04-15T21:59:16 http://comments.gmane.org/gmane.network.quagga.user/12560 <pre>Dear all, When I set this first, all is OK, and both servers announce the external routes (VIPs) out with a "Forwarding address" of *Router ID* However, while by testing the failover of the interfaces per server by shutting down one interface and keeping the other interface one is UP,the external OSPF route is advertised by the dns servers with forwarding address of the physical interface ,since the interface is down the next hop IP is not valid and hence all the traffic destined to this VIP will be blackhole.By restarting NIC interfaces"service network restart" the scenario becomes normal and the forward address getting the router ID. Can you assist us why this scenario happed on quagga and not in zebra. Regards, _______________________________________________ Quagga-users mailing list Quagga-users-UOy77sIEA+cAd7ICUelF/Q&lt; at &gt;public.gmane.org http://lists.quagga.net/mailman/listinfo/quagga-users </pre> Naser Al Hattab 2012-04-15T05:07:35 http://comments.gmane.org/gmane.network.quagga.user/12556 <pre>Dear all, *Checked OSPF Database, and found something interesting. The external OSPF routes (NSSA type-7) is advertised by the DNS servers with forwarding address of the physical interface instead of router ID. Now, Since the interface is down, the next hop IP ( which is the forwarding address) is not valid and hence all traffic destined to this VIP will be black hole.* *Your support is appreciated.* *Regards, Naser Al Hattab. *** _______________________________________________ Quagga-users mailing list Quagga-users-UOy77sIEA+cAd7ICUelF/Q&lt; at &gt;public.gmane.org http://lists.quagga.net/mailman/listinfo/quagga-users </pre> Naser Al Hattab 2012-04-12T11:05:38 http://comments.gmane.org/gmane.network.quagga.user/12552 <pre>Yes. This was the reason. Thanks Scott. -Rohan ________________________________________ From: quagga-users-bounces-UOy77sIEA+cAd7ICUelF/Q&lt; at &gt;public.gmane.org [quagga-users-bounces-UOy77sIEA+cAd7ICUelF/Q&lt; at &gt;public.gmane.org] On Behalf Of quagga-users-request-UOy77sIEA+cAd7ICUelF/Q&lt; at &gt;public.gmane.org [quagga-users-request-UOy77sIEA+cAd7ICUelF/Q&lt; at &gt;public.gmane.org] Sent: Thursday, April 05, 2012 4:30 PM To: quagga-users-UOy77sIEA+cAd7ICUelF/Q&lt; at &gt;public.gmane.org Subject: Quagga-users Digest, Vol 105, Issue 4 Send Quagga-users mailing list submissions to quagga-users-UOy77sIEA+cAd7ICUelF/Q&lt; at &gt;public.gmane.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.quagga.net/mailman/listinfo/quagga-users or, via email, send a message with subject or body 'help' to quagga-users-request-UOy77sIEA+cAd7ICUelF/Q&lt; at &gt;public.gmane.org You can reach the person managing the list at quagga-users-owner-UOy77sIEA+cAd7ICUelF/Q&lt; at &gt;public.gmane.org When replying, please edit your Subject line so it is more specific than "Re: Contents of Quagga-users digest..." Today's Topics: 1. [quagga-users 12846] OSPFv2 adjacencies per node (Rohan Mahale) 2. [quagga-users 12847] Re: OSPFv2 adjacencies per node (Scott Feldman) ---------------------------------------------------------------------- Message: 1 Date: Thu, 5 Apr 2012 11:12:35 +0530 From: Rohan Mahale &lt;Rohan_Mahale-cj8gakGGFqhBDgjK7y7TUQ&lt; at &gt;public.gmane.org&gt; To: "quagga-users-UOy77sIEA+cAd7ICUelF/Q&lt; at &gt;public.gmane.org" &lt;quagga-users-UOy77sIEA+cAd7ICUelF/Q&lt; at &gt;public.gmane.org&gt; Subject: [quagga-users 12846] OSPFv2 adjacencies per node Message-ID: &lt;AFF3CD28B1CA804AA40043457A6012A2453275DB6C-8puAfXTIdtW/+Uwtb8U0qy7MsEZMiIJY0E9HWUfgJXw&lt; at &gt;public.gmane.org&gt; Content-Type: text/plain; charset="us-ascii" Is there any limitation on number of OSPFv2 adjacencies allowed per quagga node ? In my test a quagga node is taking only 20 adjacencies on different interfaces. Thanks, Rohan **************** CAUTION - Disclaimer ***************** This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solely for the use of the addressee(s). If you are not the intended recipient, please notify the sender by e-mail and delete the original message. Further, you are not to copy, disclose, or distribute this e-mail or its contents to any other person and any such actions are unlawful. This e-mail may contain viruses. Infosys has taken every reasonable precaution to minimize this risk, but is not liable for any damage you may sustain as a result of any virus in this e-mail. You should carry out your own virus checks before opening the e-mail or attachment. Infosys reserves the right to monitor and review the content of all messages sent to or from this e-mail address. Messages sent to or from this e-mail address may be stored on the Infosys e-mail system. ***INFOSYS******** End of Disclaimer ********INFOSYS*** ------------------------------ Message: 2 Date: Thu, 5 Apr 2012 00:03:13 -0700 From: Scott Feldman &lt;sfeldma-qUQiAmfTcIp+XZJcv9eMoEEOCMrvLtNR&lt; at &gt;public.gmane.org&gt; To: Quagga Users Lists &lt;quagga-users-UOy77sIEA+cAd7ICUelF/Q&lt; at &gt;public.gmane.org&gt; Subject: [quagga-users 12847] Re: OSPFv2 adjacencies per node Message-ID: &lt;D8A04EE5-C3B3-48F7-B6A9-FB8EF9E83DC1-qUQiAmfTcIp+XZJcv9eMoEEOCMrvLtNR&lt; at &gt;public.gmane.org&gt; Content-Type: text/plain; charset=us-ascii On Apr 4, 2012, at 10:42 PM, Rohan Mahale wrote: Just a guess, but are you hitting IGMP mcast limit perhaps? $ cat /proc/sys/net/ipv4/igmp_max_memberships 20 Add net.ipv4.igmp_max_memberships = XX to /etc/sysctl.conf. -scott ------------------------------ _______________________________________________ Quagga-users mailing list Quagga-users-UOy77sIEA+cAd7ICUelF/Q&lt; at &gt;public.gmane.org http://lists.quagga.net/mailman/listinfo/quagga-users End of Quagga-users Digest, Vol 105, Issue 4 ******************************************** </pre> Rohan Mahale 2012-04-09T02:59:01 http://comments.gmane.org/gmane.network.quagga.user/12548 <pre>-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all, I'm facing some issues dealing with route-maps and bgp. I'm trying to redistribute conected networks to ibgp, I have something like this: router bgp NNNN bgp router-id 123.45.67.1 bgp log-neighbor-changes network xxx.yyy.zzz.www/NN route-map EBGP_DIST ... redistribute connected metric 1010 route-map INTERFACES_REDISTRIBUTE_BGP ... and the route-map route-map INTERFACES_REDISTRIBUTE_BGP permit 10 match interface vlan111 ! route-map INTERFACES_REDISTRIBUTE_BGP permit 15 match interface vlan112 ! And the bad surprise... # show ip bgp neighbors 123.45.67.2 advertised-routes ... Network Next Hop Metric LocPrf Weight Path ... *&gt; 123.45.48.246/32 123.45.67.1 1010 100 32768 ? *&gt; 123.45.49.248/29 123.45.67.1 1010 100 32768 ? *&gt; 123.45.55.128/28 123.45.67.1 1010 100 32768 ? VL111 *&gt; 123.45.55.240/28 123.45.67.1 1010 100 32768 ? VL112 ... Okay, I can see the networks of my VLAN111 and VLAN112 over there... but it seems the route-map is being ignored, since other routes are being sent with metric 1010 as well (only this redistribution / route-map changes the metric to 1010). Another simtom is... if I remove some match interface... let's say, vlan112, the given network persists on advertised-routes. Am I missing / messing something? Thanks in advance, - -- André Gustavo N. Lopes -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJPfbNDAAoJED/ohHvKzwrPDUAIAOCrOsT8Fg+ygREgQbGSHpIv jLaL0a06DT2arj34e6eg1J2kmLd3P8ak2n7zELOfksDRyHfaAXtpuv5OkwAcW+dy 4UF5I7qymGIzhEWe/NGuB2F3K8tXP6o2vnfzi1XzVR8nXw7cmd2xgQPnglKnUttr yDF9LHD8tFI6UviMaWEjrqCi3jkZAPRku3MYKMcbREOkl+9L35ehZQDpbBWCALWv QZ4fEGVEHvIOeWTyBmnycwyrvq8cMG6U9UESe8yohhbdVqfrTa/moahT04uoqucU JmY45WgpaTJb4Aa/hS/Z9bCSvc74ZakTsYDZeLF78zkP0HdWH2aMp7LOEjQ2kWs= =vbuk -----END PGP SIGNATURE----- </pre> André Gustavo N. Lopes 2012-04-05T14:59:16 http://comments.gmane.org/gmane.network.quagga.user/12547 <pre>Hi, All. Any recommendations for configuring ripd to listen on all active interfaces would be greatly appreciated. An example of our current ripd.conf is as follows: ------ ! -*- rip -*- ! hostname ripd ! !debug rip events !debug rip packet !debug rip zebra ! interface eth0 no ip rip authentication mode ! router rip network eth0 passive-interface default ! log file /var/log/quagga/ripd.log ! ------ This works great for a system with eth0 as the single active network interface. However, it obviously needs to be updated for a system with additional or different active interfaces. I have not yet found a ripd.conf that tells ripd to listen for rip advertisements on all active interfaces. Any suggestions for updating our rip configuration would be greatly appreciated. Many thanks, Devin </pre> Devin Bougie 2012-04-05T14:52:45 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.network.quagga.user