[Commotion-dev] dynamic runtime config of olsrd

[Hans-Christoph Steiner]

I also brought this up on olsr-dev, and Henning and others confirmed that there is little dynamic config currently possible.  Here's Henning's email:


On 04/12/2012 04:26 AM, Hans-Christoph Steiner wrote:
> 
> I'm wondering what's the best example for dynamic configuration of
> olsrd? The only example I could find is the httpinfo ADMIN_INTERFACE,
> which  seems to have been abandoned years ago.
Yes, the HTTPINFO plugin in general and especially the admin interface is in a really bad shape because nobody used it for years. It cannot handle multiple concurrent accesses well, it consumes quite a lot of memory and the its not that useful.

> Is anyone doing dynamic configuration of olsrd at runtime?  Is this
> not at all useful?
At the moment OLSRd (neither stable nor development branch) is prepared
for any kind of configuration change during runtime. The only thing that
is dynamic is the IPs of the interfaces, which are scanned by OLSRd
during runtime.

The new OLSRd (v2) I am working on should resolve the problem, but doing
it for the current one will be quite a lot of work.

Henning Rogge




On Apr 12, 2012, at 1:39 PM, Josh King wrote:

> Oops, sorry, premature send ;-)
> 
> I had always assumed that sending a HUP to the daemon would at least
> cause it to re-read its config file; going to test to see if that's the
> case. I know that having a much more dynamic framework for this sort of
> thing is part of the roadmap for OLSRv2, but that's still in relatively
> early stages as far as I know. I've been meaning to send a message to
> Henning (OLSRv2 lead developer) about some other questions, so I'll see
> if I can pull him into this conversation in the hopes that he can shed
> some light on the issue.
> 
> On 04/12/2012 01:37 PM, Josh King wrote:
>> Hmm, I had alwa
>> 
>> On 04/12/2012 11:57 AM, Ben West wrote:
>>> In my practice, I've only just restarted the olsrd daemon after changing
>>> olsrd.conf and let a minute or so transpire while it rebuilds the
>>> routing table.
>>> 
>>> The disruption of any actively routed traffic wasn't that long (e.g. a
>>> minute or less), and I think it would only be noticeable on continuous
>>> TCP streams (aka streaming media) and maybe SSH sessions.
>>> 
>>> Also, you could try manually setting a default route with a higher
>>> metric (aka lower priority) as a fallback for the period while olsrd
>>> restarts.
>>> 
>>> On Wed, Apr 11, 2012 at 9:26 PM, Hans-Christoph Steiner
>>> <hans at guardianproject.info <mailto:hans at guardianproject.info>> wrote:
>>> 
>>> 
>>>    I'm wondering what's the best example for dynamic configuration of
>>>    olsrd?  The only example I could find is the httpinfo
>>>    ADMIN_INTERFACE, which seems to have been abandoned years ago.
>>> 
>>>    Is anyone doing dynamic configuration of olsrd at runtime?  Is this
>>>    not at all useful?
>>> 
>>>    .hc
>>> 
>>> 
>>>    _______________________________________________
>>>    Commotion-dev mailing list
>>>    Commotion-dev at lists.chambana.net
>>>    <mailto:Commotion-dev at lists.chambana.net>
>>>    http://lists.chambana.net/mailman/listinfo/commotion-dev
>>> 
>>> 
>>> 
>>> 
>>> -- 
>>> Ben West
>>> me at benwest.name <mailto:me at benwest.name>
>>> 
>>> 
>>> 
>>> _______________________________________________
>>> Commotion-dev mailing list
>>> Commotion-dev at lists.chambana.net
>>> http://lists.chambana.net/mailman/listinfo/commotion-dev
>> 
>> 
>> 
>> _______________________________________________
>> Commotion-dev mailing list
>> Commotion-dev at lists.chambana.net
>> http://lists.chambana.net/mailman/listinfo/commotion-dev
> 
> -- 
> Josh King
> 
> "I am an Anarchist not because I believe Anarchism is the final goal,
> but because there is no such thing as a final goal." -Rudolf Rocker
> 
> _______________________________________________
> Commotion-dev mailing list
> Commotion-dev at lists.chambana.net
> http://lists.chambana.net/mailman/listinfo/commotion-dev