[quagga-dev 9039] quagga-0.99.20mr2.1 release

An updated version of Quagga with extensions for mobile routing is available from:
http://downloads.pf.itd.nrl.navy.mil/ospf-manet/quagga-0.99.20mr2.1/ .

This release contains several bug fixes and other improvements including better alignment with RFC 5614. 
http://downloads.pf.itd.nrl.navy.mil/ospf-manet/quagga-0.99.20mr2.1/RELEASE_NOTES.MobileRouting
includes a more detailed list of changes.

  Tom

[quagga-dev 9040] Re: quagga-0.99.20mr2.1 release

2012/2/6 Goff, Thomas <Thomas.Goff <at> boeing.com>:
> An updated version of Quagga with extensions for mobile routing is available from:
http://downloads.pf.itd.nrl.navy.mil/ospf-manet/quagga-0.99.20mr2.1/ .
>
> This release contains several bug fixes and other improvements including better alignment with RFC
5614.
 http://downloads.pf.itd.nrl.navy.mil/ospf-manet/quagga-0.99.20mr2.1/RELEASE_NOTES.MobileRouting
includes a more detailed list of changes.
>
>  Tom
>
>
> _______________________________________________
> Quagga-dev mailing list
> Quagga-dev <at> lists.quagga.net
> http://lists.quagga.net/mailman/listinfo/quagga-dev

Hi Thomas,

Thanks for your effort on keeping this project alive. Could you
provide a git repo so I can track your patches more easily?

Best Regards,
Renato.

--

-- 
Renato Westphal

[quagga-dev 9041] Committing New Features to Master Branch?

Quagga maintainers,

Would it be possible to commit new features to the master branch at the 
same time as (or before) committing them to the RE-testing branch? 
Having new features initially only in RE-testing limits their testing 
exposure and may keep people who run the master branch from discovering 
bugs earlier, before releases. I understand that maintainer time is 
limited, but if a patch for RE-testing also applies cleanly to master, 
can it just be committed to both branches?

Part of the reason I am asking is that I also use some extensions to 
Quagga that are developed externally:
  - OSPFv3 MDR (http://cs.itd.nrl.navy.mil/work/ospf-manet/)
  - PIM SM (http://www.nongnu.org/qpimd/)

These external branches are based off of master, not RE-testing, which 
makes sense as they are experimental in nature. As a researcher, I would 
like to be able to, for example, try out the Babel routing protocol 
alongside OSPFv3 MDR in wireless networks. However, Babel is in 
RE-testing and not master, and trying to integrate the code bases in 
order to build one copy of Quagga gets unnecessarily difficult because 
of this.

(Of course, it would be ideal if the above extensions could make their 
way into the mainline Quagga at some point... I'm not sure what the 
right timing or process would be for something like that, and I am not 
their maintainer.)

At the moment, the following patch groups have been applied to 
RE-testing-0.99 but not to master:

[quagga-dev 9042] Re: Google changes to Quagga now available on code.google.com

01.02.2012, 13:52, "Subbaiah Venkata" <svenkata <at> google.com>:
> Hi All,
>
> New ISIS branch is pushed to google public repository.
> http://code.google.com/p/google-quagga/source/browse/?name=is-is
>
> This branch has support for new features and bug fixes.Please let me know if you have any questions.

Hello, Subbaiah.

Thank you for publishing this work. This is the second publication in the name of Google, and the final goal,
as far as I take it, is to converge the branches in foreseeable future. It will require some work on the
project's side as well.

I have briefly studied the contents of commits b1b73b9 and f17b498. First of all, proofreading is hard,
because changes are not isolated from each other, the change to IS-IS, BGP, library functions, zserv and
indentation are mixed together. Just in case the changes were originally made and verified in some
ordered way and later joined in a single commit for the sole purpose of publication, discussing the
original isolated changes one at a time would help making through the merge. Is it possible?

Then, there is a series of IS-IS commits, which noone was able to verify so far:

d83bf5a
30a7558
dfafeae
b775c38
9632e3e

The commit IDs belong to quagga-RE repo only. Do you have the time and will to review these? They seem to be
very closely related.

[quagga-dev 9043] Re: Committing New Features to Master Branch?

On Thu, Feb 09, 2012 at 01:31:22PM -0500, Ward, David - 0663 - MITLL wrote:
> Part of the reason I am asking is that I also use some extensions to 
> Quagga that are developed externally:
>   - OSPFv3 MDR (http://cs.itd.nrl.navy.mil/work/ospf-manet/)
>   - PIM SM (http://www.nongnu.org/qpimd/)

I'm currently merging pimd to master. I've been ill the last week, so
it's a bit delayed, but I hope to push it in a few days.

(pimd is PIM-"SSM" only btw, no ASM features)

-David

[quagga-dev 9044] Re: Google changes to Quagga now available on code.google.com

On Fri, Feb 10, 2012 at 06:57:36PM +0400, Denis Ovsienko wrote:
> 01.02.2012, 13:52, "Subbaiah Venkata" <svenkata <at> google.com>:
> > Hi All,
> >
> > New ISIS branch is pushed to google public repository.
> > http://code.google.com/p/google-quagga/source/browse/?name=is-is
> >
> > This branch has support for new features and bug fixes.Please let me know if you have any questions.
> 
> Then, there is a series of IS-IS commits, which noone was able to verify so far:

Considering that isisd is still "experimental", i would merge these with
"doesn't let hell break loose" as merge criterium.

-David

[quagga-dev 9045] Re: Committing New Features to Master Branch?

>
> On Thu, Feb 09, 2012 at 01:31:22PM -0500, Ward, David - 0663 - MITLL wrote:
> > Part of the reason I am asking is that I also use some extensions to
> > Quagga that are developed externally:
> >   - OSPFv3 MDR (http://cs.itd.nrl.navy.mil/work/ospf-manet/)
> >   - PIM SM (http://www.nongnu.org/qpimd/)
>
> I'm currently merging pimd to master. I've been ill the last week, so
> it's a bit delayed, but I hope to push it in a few days.

While merging new code/protocols is fun, I had the impression you would start
merging the old patches that has been sent in over the last years which are
sitting in the mail archive or your own patch work?

 Jocke

[quagga-dev 9046] Re: Committing New Features to Master Branch?

On Fri, Feb 10, 2012 at 04:50:46PM +0100, Joakim Tjernlund wrote:
> >
> > On Thu, Feb 09, 2012 at 01:31:22PM -0500, Ward, David - 0663 - MITLL wrote:
> > > Part of the reason I am asking is that I also use some extensions to
> > > Quagga that are developed externally:
> > >   - OSPFv3 MDR (http://cs.itd.nrl.navy.mil/work/ospf-manet/)
> > >   - PIM SM (http://www.nongnu.org/qpimd/)
> >
> > I'm currently merging pimd to master. I've been ill the last week, so
> > it's a bit delayed, but I hope to push it in a few days.
> 
> While merging new code/protocols is fun, I had the impression you would start
> merging the old patches that has been sent in over the last years which are
> sitting in the mail archive or your own patch work?

I've been carrying pimd in my trees for quite a while, it's simply the
next thing on my randomly-ordered list of things to tackle. Also, I have
a better understanding of PIM than of OSPF or BGP, having written a
(partial) PIM implementation before. Plus, Balaji's SAFI code is in and
needs testing.

And, yeah, it's more fun, and since I'm doing this out of pure altruism
(I don't even need quagga for my workplace or anything) that's a huge
point...

(Oh, if anyone wants to hire someone to work on quagga, I'm available.
And we desperately need a _dedicated_paid_maintainer_ in my opinion.
With no other obligations. Hell, even a 10hr/week job would do. I'm a
student, I'm cheap :P...)

[quagga-dev 9047] Regarding about isisd

[quagga-dev 9048] Re: Regarding about isisd

On Sat, 11 Feb 2012 00:47:14 +0500
Syed Muhammad Mohsin Kazmi <08beesmmkazmi <at> seecs.edu.pk> wrote:

> Hi all,
>           I am trying to port TRILL in Linux. Can isisd for solaris in
> SUNWquagga work for linux-quagga, if we port it. If yes, what kind of
> changes required?
>           Thanks in advance.
> 
> 
> Regards,
> Mohsin Kazmi

Linux doesn't have the AF_TRILL, you will need to either do a tunnel
driver or do encapsulation in userspace.