> > Either run servald in foreground mode;
> > > servald start foreground

> I'm a bit confused. Yesterday I ran servald on the routers, and checked
> with htop that servald is indeed running in the background. Today when I
> ran it like that, in foreground, I saw that it segfaults right away and
> quits. The output is attached in a text file. I don't know what happened,
> maybe yesterday I was dreaming or something, or maybe I changed something
> since then.

> > I'm guessing the routers don't have their interfaces configured
> > correctly, but that's just a guess.
> Do you have any possible mistake on your mind that I may have done?

> > Are your routers immediate neighbours on the adhoc mesh side?
> Yes they are.

> > If you want to test our olsr plugin...
> I have decided to first try using the stand alone servald and only when it
> works I may try with the plugin. Do you suggest otherwise?

> @Paul
> > Please try it and let me know if it works.
> Ok, I will. It may take some time.

> > did you configure servald on the router to monitor the relevant
> interfaces?
> Yes I did. I put it in the config file and exported the environment
> variable.

> > Note that Rhizome doesn't currently correctly limit its space usage, which
> is likely to be an issue on an OpenWRT router with tiny storage.
> As long as I don't use it, it won't take up space, right?

> That segfault is funny. They don't come and go without recompilation in my
> experience so it's most likely that I somehow overlooked it yesterday, and
> that is why it didn't work.

> I'm going to recompile it with your Makefile.

> On Wed, Oct 24, 2012 at 5:56 AM, Jeremy Lakeman <jer...@servalproject.org>wrote:

>> On Wed, Oct 24, 2012 at 12:15 PM, Paul Gardner-Stephen
>> <p...@servalproject.org> wrote:
>> > Hello,

>> > Great work!

>> > We will, however, need to use our bundled version of NaCl, because it
>> > is a hybrid between two different versions in the latest changes to
>> > servald. In the meantime, we have rolled the NaCl build into our
>> > regular makefile, thus resolving the problem at the source.  More on
>> > this in a moment.

>> > Now, onto the issue where the phones:

>> > First, the issue described above is critical, because otherwise the
>> > phones and router servalds will be using incompatible crypto.  I have
>> > made (and attached) a first cut at what I think should work.  Please
>> > try it and let me know if it works.  If it does, we will create a
>> > serval-openwrt repository to keep it in, and track changes from there,
>> > if not, show me the build errors and we will track it down.

>> We don't want to create a new repository that will quickly get out of
>> date.  We need to be able to build for OpenWRT from our master branch,
>> until it's working we can create a new branch to track the changes you
>> two are making.

>> > Second, did you configure servald on the router to monitor the
>> > relevant interfaces?  The following command will do it:
>> > servald config set interfaces=+
>> > (this just puts interfaces=+ into serval.conf, which you can do
>> > manually as part of your install if you wish).
>> > Replace + with +interface if you only want it to chat on a single
>> interface.
>> > Note that Rhizome doesn't currently correctly limit its space usage,
>> > which is likely to be an issue on an OpenWRT router with tiny storage.

>> > Paul.

>> --
>> You received this message because you are subscribed to the Google Groups
>> "Serval Project Developers" group.
>> To post to this group, send email to
>> serval-project-developers@googlegroups.com.
>> To unsubscribe from this group, send email to
>> serval-project-developers+unsubscribe@googlegroups.com.
>> For more options, visit this group at
>> http://groups.google.com/group/serval-project-developers?hl=en.