From: cmsv <cmsv@wirelesspt.net>
To: Gui Iribarren <gui@altermundi.net>
Cc: OpenWrt Development List <openwrt-devel@lists.openwrt.org>,
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.] [OpenWrt-Devel] Kernel panic & Process batadv.sh - Fatal
Date: Tue, 13 Aug 2013 22:48:15 -0400 [thread overview]
Message-ID: <520AEFEF.8050403@wirelesspt.net> (raw)
In-Reply-To: <520984DC.7040401@altermundi.net>
[-- Attachment #1.1: Type: text/plain, Size: 921 bytes --]
The problem has now been solved with the needed patch that was
backported to AA. It is now available in r37768 and the images with
batman-adv are not affected by this problem.
Patch is at: target/linux/generic/patches-3.3/721-phy_packets.patch
On 08/12/2013 08:59 PM, Gui Iribarren wrote:
> On 08/12/2013 09:43 PM, cmsv wrote:
>> OpenWrt version: Attitude Adjustment (r37747)
>>
>> Recently there was someone (Lucaspost) on #batman with a problem caused
>> by mixing the latest AA and Batman-adv 2013.3.0 and while i can't be
>> sure the problem is exactly this one; here goes my testing with a D-link
>> 615C1
>>
>
> maybe you're mixing module and kernel versions?
>
> try to "make dirclean" and rebuild
>
> batadv.sh only does this
>
> echo "$mesh" > "/sys/class/net/$iface/batman_adv/mesh_iface"
>
> where $iface is something like "wlan0" and $mesh is "bat0"
>
> HTH,
>
> Gui
>
[-- Attachment #1.2: 0x782BF73E.asc --]
[-- Type: application/pgp-keys, Size: 36799 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 901 bytes --]
next prev parent reply other threads:[~2013-08-14 2:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-13 0:43 [B.A.T.M.A.N.] Kernel panic & Process batadv.sh - Fatal cmsv
2013-08-13 0:59 ` [B.A.T.M.A.N.] [OpenWrt-Devel] " Gui Iribarren
2013-08-14 2:48 ` cmsv [this message]
2013-08-14 10:33 ` Antonio Quartulli
2013-08-17 0:24 ` cmsv
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=520AEFEF.8050403@wirelesspt.net \
--to=cmsv@wirelesspt.net \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=gui@altermundi.net \
--cc=openwrt-devel@lists.openwrt.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.