<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel about="http://permalink.gmane.org/gmane.network.quagga.user">
    <title>gmane.network.quagga.user</title>
    <link>http://permalink.gmane.org/gmane.network.quagga.user</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.network.quagga.user/9649"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.network.quagga.user/9648"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.network.quagga.user/9647"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.network.quagga.user/9646"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.network.quagga.user/9645"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.network.quagga.user/9644"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.network.quagga.user/9643"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.network.quagga.user/9642"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.network.quagga.user/9641"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.network.quagga.user/9640"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.network.quagga.user/9639"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.network.quagga.user/9638"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.network.quagga.user/9637"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.network.quagga.user/9636"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.network.quagga.user/9635"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.network.quagga.user/9634"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.network.quagga.user/9633"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.network.quagga.user/9632"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.network.quagga.user/9631"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.network.quagga.user/9630"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://permalink.gmane.org/gmane.network.quagga.user/9649">
    <title>[quagga-users 9975] Re: Disappearing Routes</title>
    <link>http://permalink.gmane.org/gmane.network.quagga.user/9649</link>
    <description>

This possibly may be fixed by Stephan Hemminger's fixes for zebra, in 
0.99.11. Can you retest with it?

regards,
</description>
    <dc:creator>paul-p3WKshh8b8w&lt; at &gt;public.gmane.org</dc:creator>
    <dc:date>2008-10-04T16:00:52</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.network.quagga.user/9648">
    <title>[quagga-users 9974] Re: Quagga 0.99.11 Released</title>
    <link>http://permalink.gmane.org/gmane.network.quagga.user/9648</link>
    <description>


I either wasn't aware of that problem or I've forgotten about it 
(either way). Did you post about it before?

regards,
</description>
    <dc:creator>paul-p3WKshh8b8w&lt; at &gt;public.gmane.org</dc:creator>
    <dc:date>2008-10-04T15:56:52</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.network.quagga.user/9647">
    <title>[quagga-users 9973] Re: Balancing of links</title>
    <link>http://permalink.gmane.org/gmane.network.quagga.user/9647</link>
    <description>
Your routing deamon can't balance them, since it doens't know how much
traffic will be sent over each router.  This has to be a job for your
system.  If you have support for multipath routing, perhaps that could
be setup to try and distribute the traffic better.  I would not expect
it to become perfect though.

</description>
    <dc:creator>Lennart Sorensen</dc:creator>
    <dc:date>2008-10-03T20:22:34</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.network.quagga.user/9646">
    <title>[quagga-users 9972]  Balancing of links</title>
    <link>http://permalink.gmane.org/gmane.network.quagga.user/9646</link>
    <description>_______________________________________________
Quagga-users mailing list
Quagga-users-UOy77sIEA+cAd7ICUelF/Q&lt; at &gt;public.gmane.org
http://lists.quagga.net/mailman/listinfo/quagga-users
</description>
    <dc:creator>Ronaldo Cardoso</dc:creator>
    <dc:date>2008-10-03T19:41:50</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.network.quagga.user/9645">
    <title>[quagga-users 9971] Re: Disappearing Routes</title>
    <link>http://permalink.gmane.org/gmane.network.quagga.user/9645</link>
    <description>
Can you retrieve any useful information from netstat as to why the
interface is going down (errors etc)?

Does the supplier of T1 #2 see anything in their line stats indicating
that the circuit is flapping?

Are the kernel routes decrementing over time when the second T1 appears
to have dropped?

Can you send/receive traffic over the second T1 (ICMP) while Quagga
shows the interface as down (perhaps it is a cosmetic issue)?

Does ifconfig show it as down as well?

Steve
</description>
    <dc:creator>Steve Bertrand</dc:creator>
    <dc:date>2008-10-03T13:03:27</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.network.quagga.user/9644">
    <title>[quagga-users 9970]  Problem with Route Summarisation in OSPF</title>
    <link>http://permalink.gmane.org/gmane.network.quagga.user/9644</link>
    <description>I appear to have a problem with route summarisation on ABR's in OSPF.
Quagga version is 0.99.10

The simplified diagram below shows router R1 in area 0 (the backbone).
R2 and R3 are ABR's with one interface in area 0 and two interfaces each
in area 1; one interface is to a local LAN and the other continues on
round the ring. Routers R4, R5 and R6 are internal routers in area 1.
All interfaces are Ethernet.

Everything works fine as long as I do not summarise routes on the ABR's.
All the subnets in area 1 are injected into the backbone as summary
LSA's. This works well and you get optimised routing between areas, but
the routing table gets rather large and defeats the purpose of using
areas.

If I summarise the subnets in area 1 on the two ABR's, R2 and R3, I get
some bizarre behaviour in that various subnets in area 1 become
unreachable from the backbone - the packets just get dropped somewhere.
The subnets that are reachable and unreachable also change over periods
of 5 to 10 minutes or so. All the area 1 s</description>
    <dc:creator>Hirsch, Stephen</dc:creator>
    <dc:date>2008-10-03T04:39:04</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.network.quagga.user/9643">
    <title>[quagga-users 9969] Re: Quagga 0.99.11 Released</title>
    <link>http://permalink.gmane.org/gmane.network.quagga.user/9643</link>
    <description>I see no mention of fixes for prefix-list editing from vtysh.   Was  
this fixed but not mentioned?

Example:

On Oct 2, 2008, at 4:03 AM, Paul Jakma wrote:

</description>
    <dc:creator>Jo Rhett</dc:creator>
    <dc:date>2008-10-02T17:23:17</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.network.quagga.user/9642">
    <title>[quagga-users 9968]  Disappearing Routes</title>
    <link>http://permalink.gmane.org/gmane.network.quagga.user/9642</link>
    <description>_______________________________________________
Quagga-users mailing list
Quagga-users-UOy77sIEA+cAd7ICUelF/Q&lt; at &gt;public.gmane.org
http://lists.quagga.net/mailman/listinfo/quagga-users
</description>
    <dc:creator>Orbiting Code Inc.</dc:creator>
    <dc:date>2008-10-02T16:47:45</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.network.quagga.user/9641">
    <title>[quagga-users 9967]  Quagga 0.99.11 Released</title>
    <link>http://permalink.gmane.org/gmane.network.quagga.user/9641</link>
    <description>Quagga 0.99.11 has been released, and is available, along with a full 
changelog, in the usual places, e.g.:

 http://www.quagga.net/download/

Thanks to everyone who helped by reporting bugs, contributing and 
testing fixes.

Release notes:

Stable release candidate:
------------------------

Most regressions in 0.99 over 0.98 are now believed to be fixed. This 
release should be considered a release-candidate for a new stable 
series, and we urge any remaining users of 0.98 to test this release 
and report any bugs. A blocker meta-bug exists to track critical 
regressions (http://bugzilla.quagga.net/show_bug.cgi?id=246).


bgpd: Preliminary UI and Linux-IPv4 support for TCP-MD5 merged
--------------------------------------------------------------

Initial support for TCP-MD5 has been merged. This adds the neighbor 
... password command, and some support for setting TCP-MD5 on 
pure-IPv4 connections on Linux. On Linux systems with IPv6 available, 
passing the -l 0.0.0.0 argument to bgpd may allow TCP-MD5 s</description>
    <dc:creator>Paul Jakma</dc:creator>
    <dc:date>2008-10-02T11:03:42</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.network.quagga.user/9640">
    <title>[quagga-users 9966]  Port knocking?</title>
    <link>http://permalink.gmane.org/gmane.network.quagga.user/9640</link>
    <description>Has anyone used port knocking to help secure access to the CLI on a  
production quagga (or Vyatta) box doing at least a few hundred mbps  
traffic? I don't expect serious problems but I wonder if performance  
could be an issue (I wouldn't expect that unless the knocking code is  
badly written, but I haven't read any sources yet).

We're still considering Vyatta so I'm also curious to know how hard or  
easy people have found it to bolt on additional software. I expect in  
this case that I'd have to make sure that the knocking software gets  
to see all the inbound packets before Vyatta's filters discard them;  
other than that I don't forsee much trouble.

Thanks,
/a
</description>
    <dc:creator>Alexis Rosen</dc:creator>
    <dc:date>2008-10-01T23:49:22</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.network.quagga.user/9639">
    <title>[quagga-users 9965] Re: OSPF binding to wrong interface on FreeBSD 7</title>
    <link>http://permalink.gmane.org/gmane.network.quagga.user/9639</link>
    <description>
I probably wouldn't care about display errors.  I've previously talked
about various problems.  Let's just say "it seemed capable of taking 
down even Quagga OSPFD's in other areas that were not directly connected
to the area in question."  Look back for a post called "OSPFD gone wild"
and probably any other recent messages from me on the list.


We've got one router doing RELENG_7+patch.  We've got one server doing it
as well.  Most of our UNIX routing is FreeBSD 4.11, because both 5 and 6
are crap for performance.  Was hoping to flip everything over to 7...

... JG
</description>
    <dc:creator>Joe Greco</dc:creator>
    <dc:date>2008-10-01T22:11:00</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.network.quagga.user/9638">
    <title>[quagga-users 9964] Re: OSPF binding to wrong interface on FreeBSD 7</title>
    <link>http://permalink.gmane.org/gmane.network.quagga.user/9638</link>
    <description>Hello Joe,

Joe Greco wrote:

Can you describe the events you saw? Were they service disrupting
or just display errors?


So, did you stay with RELENG_6 or are you running RELENG_7+patch
in production with some minor issues?

I need to upgrade some routers, so I have to decide what to do.

Markus
</description>
    <dc:creator>Markus Oestreicher</dc:creator>
    <dc:date>2008-10-01T21:57:06</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.network.quagga.user/9637">
    <title>[quagga-users 9963] Re: OSPF binding to wrong interface on FreeBSD 7</title>
    <link>http://permalink.gmane.org/gmane.network.quagga.user/9637</link>
    <description>
It Does Not.  It looks like it appears to under certain circumstances,
such as if you only have one interface advertising (this is based on
observation, not analysis).  It definitely goes to hell if you use it
in an environment with a bunch of interfaces.  We were using Quagga out
of ports originally when we first saw all this.

The sockopt.c.diff patch appears like it might work, except that we're
still seeing a low incidence of OSPF "events" which we haven't isolated.
There was a response, I believe on the FreeBSD lists, that suggested it
wasn't really a correct solution.  

I've refrained from commenting until now since we didn't have a good
feeling for how it was behaving in the long run.  In the short run, it
*appears* to work just like older Quagga on older FreeBSD.

... JG
</description>
    <dc:creator>Joe Greco</dc:creator>
    <dc:date>2008-10-01T20:15:39</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.network.quagga.user/9636">
    <title>[quagga-users 9962] Re: OSPF binding to wrong interface on FreeBSD 7</title>
    <link>http://permalink.gmane.org/gmane.network.quagga.user/9636</link>
    <description>John Lingate schrieb:

Just a question for clarity:

I see that the FreeBSD port contains a small patch from Jan-2008 that adds
three lines to sockopt.c to restore old behaviour:

http://www.freebsd.org/cgi/cvsweb.cgi/ports/net/quagga/files/patch-lib-sockopt.c?rev=1.1

Can anyone confirm that the current quagga port works correctly on RELENG_7?

Thanks!

Markus
</description>
    <dc:creator>Markus Oestreicher</dc:creator>
    <dc:date>2008-10-01T19:29:51</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.network.quagga.user/9635">
    <title>[quagga-users 9961] Re: BGP over IPv6 routing informations notsentin UPDATE message</title>
    <link>http://permalink.gmane.org/gmane.network.quagga.user/9635</link>
    <description>

I have to admit I didn't notice the version Nick was running.  We had  
our (solvable) problems with 0.99.10.

Michael

-----
Michael H. Lambert, GigaPoP Coordinator        Phone: +1 412 268-4960
Pittsburgh Supercomputing Center               FAX:   +1 412 268-5832
300 S Craig St, Pittsburgh, PA  15213 USA      lambert-YUCGctl3KYs&lt; at &gt;public.gmane.org
</description>
    <dc:creator>Michael Lambert</dc:creator>
    <dc:date>2008-10-01T14:09:41</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.network.quagga.user/9634">
    <title>[quagga-users 9960] Re: BGP over IPv6 routing informations not sentin UPDATE message</title>
    <link>http://permalink.gmane.org/gmane.network.quagga.user/9634</link>
    <description>_______________________________________________
Quagga-users mailing list
Quagga-users-UOy77sIEA+cAd7ICUelF/Q&lt; at &gt;public.gmane.org
http://lists.quagga.net/mailman/listinfo/quagga-users
</description>
    <dc:creator>Arnold Nipper</dc:creator>
    <dc:date>2008-10-01T12:01:43</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.network.quagga.user/9633">
    <title>[quagga-users 9959] Re: BGP over IPv6 routing informations not sentin UPDATE message</title>
    <link>http://permalink.gmane.org/gmane.network.quagga.user/9633</link>
    <description>Hi Nick,

On 1 Oct 2008, at 12:16, Nick wrote:


We ran into what sounds like a similar problem.  After several Google  
searches and much poking around we hit upon the 'neighbor override- 
capability' peer option.  The problem would seem to be in RFC 2283 vs  
RFC 2858 multiprotocol extensions.

Michael

-----
Michael H. Lambert, GigaPoP Coordinator        Phone: +1 412 268-4960
Pittsburgh Supercomputing Center               FAX:   +1 412 268-5832
300 S Craig St, Pittsburgh, PA  15213 USA      lambert-YUCGctl3KYs&lt; at &gt;public.gmane.org
</description>
    <dc:creator>Michael Lambert</dc:creator>
    <dc:date>2008-10-01T10:44:56</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.network.quagga.user/9632">
    <title>[quagga-users 9958] Re: BGP over IPv6 routing informations not sentin UPDATE message</title>
    <link>http://permalink.gmane.org/gmane.network.quagga.user/9632</link>
    <description>I would also like to add some more information.

The BGP routers are identified as peers and it shows the neighbor 
information with the command "sh bgp neighbors". The messages sent 
between these two routers are addressed in IPv6 only, but the problem 
lies in the NLRI filed of BGP UPDATE packet where there is no IPV6 
information(only IPV4 info, which I dont want to advertise)

Hope this will give you more info. If you require more info, just sent 
me a mail.

Thanks and Regards,
Nibin Varghese
</description>
    <dc:creator>Nick</dc:creator>
    <dc:date>2008-10-01T16:16:21</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.network.quagga.user/9631">
    <title>[quagga-users 9957]  HELP! Quagga and NAT</title>
    <link>http://permalink.gmane.org/gmane.network.quagga.user/9631</link>
    <description>Hi there.

I have "router-on-a-stick" under linux 2.6 and quagga 0.99.10 with 
following interfaces.
vlan201 - uplink with IP address, say 1.1.1.1
vlan202 - uplink with IP address 2.2.2.2
vlan300 - gateway interface to the DMZ, with IP address, say, 5.5.5.5

vlan101...vlan199 - gateway interfaces to local networks, each having IP 
range 192.168.101.0/24....192.168.199.0/24.
Each local network is SNATted behind its own public IP addresses, say 
5.5.5.101....5.5.5.199.

I set local preference and weight so that all outgoing traffic has to be 
sent via vlan201. Incoming packets, however,
can be received both at vlan201 and vlan202. And if the latter happens, 
NAT gets stuck... I don't receive any packet
on NATted interface, whilst DMZ feels ok.

What can be done about this? I've read LARTC about different routing 
tables, but this would work if I have static
uplink routers, and looks very ambiguous with zebra.

Please heeeeeelp!!!

Yours,
 B.
</description>
    <dc:creator>Billy</dc:creator>
    <dc:date>2008-10-01T10:29:30</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.network.quagga.user/9630">
    <title>[quagga-users 9956] BGP over IPv6 routing informations not sent inUPDATE message</title>
    <link>http://permalink.gmane.org/gmane.network.quagga.user/9630</link>
    <description>Hi,

Recently I was trying to configure two BGP routers with IPv6 
capabalities. I am using quagga (version 0.99.9) and I am running it on 
Ubuntu 8.04 system.

I will detail upon my configurations:

There are three virtual machines(all Ubuntu virtual OS) running on 
Ubuntu base system. The base and one Ubuntu guest (Ubuntu-guest1) are 
acting as the BGP routers. I divided it to have two AS so that

AS 3 includes -&gt; Host Ubuntu(*) + Ubuntu Guest 3
AS 4 includes -&gt; Ubuntu Guset1(*) + Ubuntu guest 2
where * is the BGP routers.

I removed all the irrelevant routes so that it virtually creates dynamic 
routing. I tested this network setup with IPv4 and it worked perfectly 
fine in sharing routes and updating the kernel routes in the BGP routers.

So I wanted to test the same netwotk configuration with IPv6 
capabilities. I changed my interface addresses to have a non-local link 
address (I chose feco::ac10:0/112).  The  network configuration was fine 
but I saw that the UPDATE messages  of BGP is always showing </description>
    <dc:creator>Nick</dc:creator>
    <dc:date>2008-10-01T16:08:56</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.network.quagga.user/9629">
    <title>[quagga-users 9955]   Re: iBGP problem</title>
    <link>http://permalink.gmane.org/gmane.network.quagga.user/9629</link>
    <description>That was included in the original details post. It shows bgpd knows all 
the prefixes and next-hops. Anyway, here is again:

And for your entertainment, while we're at it, the "show ip bgp" from
the cpl.bbq.nl; the one behaving funny:
     Network          Next Hop            Metric LocPrf Weight Path
* i10.0.0.0/24      10.5.0.2                 1    100      0  ?
*&gt;i                 10.5.0.1                 0    100      0  ?
*&gt; 10.2.1.0/24      0.0.0.0                  1         32768  ?
* i10.3.0.0/24      10.0.0.7                 0    100      0  ?
*&gt;i                 10.0.0.7                 0    100      0  ?
* i10.3.1.0/24      10.0.0.6                 0    100      0  ?
*&gt;i                 10.0.0.6                 0    100      0  ?
* i10.3.2.0/24      10.0.0.7                 0    100      0  ?
*&gt;i                 10.0.0.7                 0    100      0  ?
* i10.3.4.0/24      10.0.0.7                 0    100      0  ?
*&gt;i                 10.0.0.7                 0    100      0  ?
* i10.3.16.8/29 </description>
    <dc:creator>Peter van den Heuvel</dc:creator>
    <dc:date>2008-10-01T10:00:02</dc:date>
  </item>
  <textinput about="http://search.gmane.org/?group=$group=gmane.network.quagga.user">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.network.quagga.user</link>
  </textinput>
</rdf:RDF>
