public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: "Jay Brussels" <jay@dslx.net>
To: 'The list for a Better Approach To Mobile Ad-hoc Networking'
	<b.a.t.m.a.n@lists.open-mesh.org>
Subject: Re: [B.A.T.M.A.N.] Current OpenWrt build
Date: Thu, 13 Nov 2014 10:30:14 -0500	[thread overview]
Message-ID: <019301cfff56$b8cb3830$2a61a890$@dslx.net> (raw)
In-Reply-To: <20141112135424.GV9205@medion.lan>

Hello Bastian,

I was referring to the BATMAN patches, not OpenWRT.  The bugtraker does have
162 BATMAN issues, most closed and none that are open that will affect my
application.

I have seen some patches on the listserver  that states certain mesh traffic
can cause a crash.  This is my primary concern.

Jay
 

-----Original Message-----
From: B.A.T.M.A.N [mailto:b.a.t.m.a.n-bounces@lists.open-mesh.org] On Behalf
Of Bastian Bittorf
Sent: Wednesday, November 12, 2014 8:54 AM
To: The list for a Better Approach To Mobile Ad-hoc Networking
Subject: Re: [B.A.T.M.A.N.] Current OpenWrt build

* Jay Brussels <jay@dslx.net> [12.11.2014 14:50]:
> Is the current OpenWrt release stable enough for deployment or are there
some "must have" patches requiring a build from scratch for a successful
deployment?

Hi Mr. President,

Define 'stable'.
There are >2700 open issues in the bugtracker:
https://dev.openwrt.org/report/1

bye, bastian


  reply	other threads:[~2014-11-13 15:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-12 12:47 [B.A.T.M.A.N.] Current OpenWrt build Jay Brussels
2014-11-12 13:54 ` Bastian Bittorf
2014-11-13 15:30   ` Jay Brussels [this message]
2014-11-15 18:58     ` Sven Eckelmann
2014-11-16  6:28       ` Linus Lüssing
2014-11-16  8:50         ` Sven Eckelmann
2014-11-16  9:14           ` Sven Eckelmann
2014-11-16 10:19             ` Linus Lüssing
2014-11-16  6:51 ` Linus Lüssing

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='019301cfff56$b8cb3830$2a61a890$@dslx.net' \
    --to=jay@dslx.net \
    --cc=b.a.t.m.a.n@lists.open-mesh.org \
    /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