[Olsr-dev] Making easier debug olsrd problems on OpenWRT platform Was: no interfaces detected / 0.6.2 / arch: atheros
ZioPRoTo (Saverio Proto)
Thu Mar 29 19:52:15 CEST 2012
so we have this big discussion about a (trivial) patch that makes the
olsrd binary hash different and this makes a pain for olsrd developers
give proper support on the OpenWRT platform
because we are now all at the battlemesh in person, what about find a
solution for this ?
why is not possible to remove the patch and have olsrd change the
ip_forwarding setting ? thanks !
2012/1/5 Henning Rogge <(spam-protected)>:
> On Thu, Jan 5, 2012 at 10:33, Markus Kittenberger
> <(spam-protected)> wrote:
>> On Wed, Jan 4, 2012 at 4:55 PM, Jo-Philipp Wich <(spam-protected)> wrote:
>>> [and again to the list, sorry Bastian]
>>> I wonder what magic patches you're talking about?
>>> The two patches listed here hardly seem to be related to iface handling:
>> no but they modify the sourcecode, resulting in an hash in olsrd -v that is
>> different than any of our releases, or git commits
>> -> therfore we (olsr folks) can identify such modified olsrd version, and
>> usually like to consider such olsrds as "unsupported"
>> i.e. especially i will never provide any good support for such olsrd's
>> e.g. definietly no on-site debugging, or longer mails on mailing lists,..
> Maybe we can help if someone points us to the specific changes he has
> compared to any version in our git repository.
> I introduced this stuff after we spend a week to look for a severe
> memory overflow problem only to learn that the user had patched his
> OLSRd and caused the problem with this (unknown) code.
> "Wo kämen wir hin, wenn alle sagten, wo kämem wir hin, und niemand
> ginge, um einmal zu schauen, wohin man käme, wenn man ginge." (Kurt
> Olsr-dev mailing list
More information about the Olsr-dev