[Olsr-dev] new minor release

[Henning Rogge]

Hi,

the current patch broke the default behavior, which might break countless
of installations out there... so we either need to revert the patch or need
to fix it with a parameter.

Luckily the problem doesn't happen with OLSRv2 ^^

Henning


On Thu, Aug 21, 2014 at 6:21 PM, Philipp Borgers <(spam-protected)>
wrote:

> On Thu, Aug 21, 2014 at 06:09:20PM +0200, Ferry Huberts wrote:
> >
> >
> > On 21/08/14 18:07, Philipp Borgers wrote:
> > >On Thu, Aug 21, 2014 at 04:52:49PM +0200, Ferry Huberts wrote:
> > >>
> > >>
> > >>On 21/08/14 16:49, Saverio Proto wrote:
> > >>>Hello,
> > >>>
> > >>>I mean the branch release-0.6.6 in the olsrd git repository.
> > >>>
> > >>>I had a look now at these two commits.
> > >>>
> > >>>This is a change in default behaviour. I am not really happy with
> > >>>these two commits.
> > >>>
> > >>>In Ninux we have a configuration that uses txtinfo on port 2006 for
> > >>>IPv4 and 2007 for IPv6.
> > >>>It is important to be able to connect to these ports both in IPv4 and
> > >>>IPv6. For example if I am troubleshooting IPv6 it is very nice to be
> > >>>able to connect to that node on IPv4 port 2007 and understand what's
> > >>>wrong with IPv6.
> > >>>
> > >>>If I understand this patch makes impossible to query the txtinfo of
> > >>>the IPv6 olsrd instance if connecting with IPv4.
> > >>>
> > >>>If you want to make this change it is okay, but make it with a config
> > >>>option, and do not change the default behaviour.
> > >>>
> > >>>What do you think about this ?
> > >>>
> > >>
> > >>
> > >>I think you're right Saverio.
> > >>I missed that it changes default behaviour.
> > >>
> > >>There should be a config parameter for this, something like 'IPv6Only'
> which
> > >>defaults to false.
> > >
> > >What is the purpose of the -ipv6 option?
> >
> > Which option are you referring to?
> >
>
> To quote the manual page of olsrd:
>
> "-ipv6       This option instructs olsrd to use the Internet Protocol
> version
>              6. The default is version 4."
>
> Reading this I would expect that olsrd listens only on one type of socket.
> And I
> would expect that plugins do so as well.
>
> Give this information I don't see why we need another option.
> > >
> > >>
> > >>Anyone care to post patches?
> > >>
> > >>>Saverio
> > >>>
> > >>>
> > >>>
> > >>>2014-08-21 16:01 GMT+02:00 Philipp Borgers <(spam-protected)>:
> > >>>>Hi,
> > >>>>
> > >>>>the patches we are inparticular inntrested in are applied in the
> master branch:
> > >>>>
> > >>>>*
> http://olsr.org/git/?p=olsrd.git;a=commit;h=01c1ea452ec3de303be2ee6a351cc56485274970
> > >>>>*
> http://olsr.org/git/?p=olsrd.git;a=commit;h=efcbe5ac8d34cca8ad3e70f80e2e826164b1bcf1
> > >>>>
> > >>>>What do you mean by release branch?
> > >>>>
> > >>>>Best Regards
> > >>>>Philipp
> > >>>>
> > >>>>On Thu, Aug 21, 2014 at 11:05:56AM +0200, Saverio Proto wrote:
> > >>>>>Hello,
> > >>>>>
> > >>>>>are your patches already in the release branch ?
> > >>>>>
> > >>>>>what patches are we talking about ?
> > >>>>>
> > >>>>>thanks
> > >>>>>
> > >>>>>Saverio
> > >>>>>
> > >>>>>
> > >>>>>2014-08-20 22:40 GMT+02:00 Philipp Borgers <(spam-protected)
> >:
> > >>>>>>Hi,
> > >>>>>>
> > >>>>>>at freifunk berlin we are working on a new firmware. We would
> profit from a new
> > >>>>>>minor release of olsr so we could update the openwrt routing feed
> and use it
> > >>>>>>without any patches. As far as I know we are not the only project
> that would
> > >>>>>>profit from a new release.
> > >>>>>>
> > >>>>>>Is there anything I can do to help prepare a release?
> > >>>>>>
> > >>>>>>Thanks a lot.
> > >>>>>>
> > >>>>>>Best Regards
> > >>>>>>Philipp
> > >>>>>>
> > >>>>>>--
> > >>>>>>Olsr-dev mailing list
> > >>>>>>(spam-protected)
> > >>>>>>https://lists.olsr.org/mailman/listinfo/olsr-dev
> > >>>>
> > >>>>--
> > >>>>Olsr-dev mailing list
> > >>>>(spam-protected)
> > >>>>https://lists.olsr.org/mailman/listinfo/olsr-dev
> > >>>
> > >>
> > >>--
> > >>Ferry Huberts
> > >>
> > >>
> >
> > --
> > Ferry Huberts
>
> --
> Olsr-dev mailing list
> (spam-protected)
> https://lists.olsr.org/mailman/listinfo/olsr-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.olsr.org/pipermail/olsr-dev/attachments/20140821/703224ae/attachment.html>