From: Jan Hetges <tran@ms20.net>
To: b.a.t.m.a.n@open-mesh.net
Subject: [B.A.T.M.A.N.] freifunk 1.6.8/1.6.9
Date: Mon, 15 Oct 2007 20:02:42 -0600 [thread overview]
Message-ID: <20071016020242.GA4608@apoderado.ometepe.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 305 bytes --]
Hi
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 ?
cheers
--Jan
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2007-10-16 2:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-16 2:02 Jan Hetges [this message]
2007-10-16 6:23 ` [B.A.T.M.A.N.] freifunk 1.6.8/1.6.9 a.anselmi
2007-10-16 7:23 ` Jan Hetges
2007-10-16 8:28 ` Axel Neumann
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=20071016020242.GA4608@apoderado.ometepe.net \
--to=tran@ms20.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