Bug#713005: RFA: miredo -- Teredo IPv6 tunneling through NATs
Hi guys,
On 28/06/13 10:52, Axel Beckert wrote:
> Hi,
>
> Rémi Denis-Courmont wrote:
> > On Fri, 28 Jun 2013 09:44:12 +0200, Axel Beckert <abe@debian.org> wrote:
> > >> But then again, not much as happened on development side in the
> > >> last few years.
> > >
> > > IMHO miredo works fine for years now and I don't miss anything. So
> > > from my point of viewthere's no need for new features. :-)
> > >
> > > If "not much happened" is just bug fixing where necessary, that should
> > > be fine if it continues that way.
> >
> > Hmm well, the whole link-local multicast thing in the development branch
> > that has never really been tested (that I'd know of) or released. Also
> > there are quite a few extensions from the Microsoft/IETF Teredo protocol
> > update that have not been implemented.
>
> I see. (Reasons why I can't take over any upstream development. ;-)
>
> > And then, integration with the
> > network manager and init could be better.
>
> I usually prefer wicd over NM, but I can imagine that this would of be
> use for some people.
>
> > There should be a few fixes in my miredo-debian.git that never hit Debian.
> > If you don't take them, we should probably clear the pending tag on the
> > corresponding bugs.
>
> From the bug reports marked as pending, I'd definitely include them.
> Together with harding build flags and the 1.2.6 upstream version the
> package should be back in shape.
Yes. Working on that. I want first to switch to debhelper. Few questions
here:
* why do you compile miredo statically? shouldn't you compile dynamically
and provide libmiredo or something?
* I noticed that the test suite sometimes fails (rarely and randomly);
the test name is libteredo-list; was testing a part of a cdbs build before?
Cheers,
Tomasz
>
> Tomasz: Please tell me if you need or want any help with the above.
>
> Regards, Axel
> --
> ,''`. | Axel Beckert <abe@debian.org>, http://people.debian.org/~abe/
> : :' : | Debian Developer, ftp.ch.debian.org Admin
> `. `' | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
> `- | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5
Reply to: