Re: [opennhrp-devel] Configuration reloading and/or periodic syslogging problem

[Alex L. <ale...@gm...>]

Hi Timo,

Currently I stop opennhrp modify config and start it again upon a change to
workaround the problem.
I may probably change the required pieces of code to support your
suggestions upon an opportunity.
Is it possible to merge the changes into the mainline?
Thanks,
Alex

On Mon, Jul 23, 2012 at 8:21 AM, Timo Teras <tim...@ik...> wrote:

> On Sun, 22 Jul 2012 14:27:15 +0300 Alex Levit <ale...@gm...>
> wrote:
>
> > I have a setup with 4 mgre interfaces. Only 2 of them could only be
> > actually active at the same time, the other 2 are for backup (and the
> > NHS is not reachable for them until they will be active).
> > I add one mapping entry for each mgre in opennhrp.conf, so my log
> > files (racoon/syslog/etc) will be all the time flooded by continuous
> > periodic retries (e.g. "Peer up script failed").
> > So I thought not to create standby mgre i/f until required, but this
> > adds even more periodic logging ("Cannot send packet to mgre4(0): No
> > such device or address")
>
> I would be OK that opennhrp skipped all attempts if the gre interface
> is down. This should be relatively simple to implement.
>
> > As I understand there is no possibility to reconfigure opennhrp
> > daemon w/o stopping and starting it - this was enabling to modify
> > config file according to dynamic status of the activity.
> >
> > Can you suggest any workaround/solution ?
>
> Configuration reload is a missing feature. It would be nice to have,
> but I'm tied up with other stuff currently.
>
> -Timo
>