public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Axel Neumann <axel@open-mesh.net>
To: The list for a Better Approach To Mobile Ad-hoc Networking
	<b.a.t.m.a.n@open-mesh.net>
Subject: Re: [B.A.T.M.A.N.] freifunk 1.6.8/1.6.9
Date: Tue, 16 Oct 2007 10:28:04 +0200	[thread overview]
Message-ID: <200710161028.04217.axel@open-mesh.net> (raw)
In-Reply-To: <20071016072328.GC10100@apoderado.ometepe.net>

Hi,

On Dienstag 16 Oktober 2007, Jan Hetges wrote:
> Hi
>
> On Tue, Oct 16, 2007 at 08:23:59AM +0200, a.anselmi@oltrelinux.com wrote:
> > > is anyone using this on wrt54g ?
> > > i just tried both and batmand_0.3-beta-rv674 gives a segmenation fault
> > > and batmand_0.2-rv502 doesn't start (probably segfault as well).
> > > can someone confirm/deny this?
> > > has someone a link for a working (with batmand)
> > > openwrt-g-freifunk-1.6.x-x.bin/trx ?
> >
> if one reboots the box after the batman installation everything
> is fine (i fell over that before... but didn't remember ;)
>
If you start the daemon with -r, -g, or -p (any GW functionality), then it
might be related to the tun module (kmod-tun). I remember that when installing 
that module it is not loaded automatically. But after the next restart its 
loaded. 

ciao, 
/ axel


> cheers
>
>   --Jan



  reply	other threads:[~2007-10-16  8:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-16  2:02 [B.A.T.M.A.N.] freifunk 1.6.8/1.6.9 Jan Hetges
2007-10-16  6:23 ` a.anselmi
2007-10-16  7:23   ` Jan Hetges
2007-10-16  8:28     ` Axel Neumann [this message]
2007-10-16 13:13 ` Marek Lindner
2007-10-16 17:25   ` [B.A.T.M.A.N.] batmand_0.3-beta-rv724 segmentation fault Jan Hetges
2007-10-16 18:52     ` Jan Hetges
2007-10-16 19:48       ` [B.A.T.M.A.N.] batmand_0.3 " Jan Hetges
2007-10-17  9:09         ` Axel Neumann
2007-10-17 16:04           ` Jan Hetges

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200710161028.04217.axel@open-mesh.net \
    --to=axel@open-mesh.net \
    --cc=b.a.t.m.a.n@open-mesh.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox