From: x@muc.ccc.de
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: [B.A.T.M.A.N.] batman-adv 0.2 on openwrt
Date: Sun, 07 Feb 2010 21:54:38 +0100 [thread overview]
Message-ID: <4B6F288E.8050406@muc.ccc.de> (raw)
hi!
as openwrt 8.09.2 still ships with an old batman-adv 0.1 module, i tried to compile a batman-adv 0.2 module.
the compile worked, the module loads, originators see each other, but on the openwrt box on bat0 tx packets stays 0 while tx dropped obviously increases with each packet to be transmitted.
the setup:
laptop debian squeeze amd64 2.6.31.12 batman-adv 0.2
laptop debian sid x86 2.6.32 batman-adv 0.2
ap openwrt 8.09.2 ixp4xx/armeb (cambria) 2.6.26.8 batman-adv 0.2
the facts:
all bridges and iptables switched off.
with plain ip on the wlan interfaces, pinging between all nodes works fine (when within reach).
all three nodes have the respective two other nodes listed as originators, and if all are within reach of each other, with originator=nexthop.
pinging via bat0 works between the two laptops.
pinging the laptops via bat0 from the ap results in no packets seen on the laptops' bat0.
pinging the ap via bat0 from a laptop results in incoming arp-requests and outgoing arp-replies seen on the ap's bat0 - but again, the arp-replies aren't seen on the laptops' bat0 (nor on the laptops' wlan interfaces).
on the ap's bat0, the tx packets counter stays at 0, while the tx dropped counter seems to increase with each packet that should be sent over it.
i enabled all logging (15) on the ap and the laptops, but found no hint in there...
the only interesting messages seem to be in dmesg, saying:
protocol 4305 is buggy, dev ath1
so to me it seems like all tx packets on bat0 on the ap are dropped, while everything else seems to work as it's supposed to.
i then tried to compile the current (r1568) version from svn for the ap. again, the compile worked, but the ap just freezes immediately when i try to load it.
i thought about trying a newer kernel for the ap, but from openwrt there's a special cambria kernel and i haven't found its config and also don't know what patches might have been applied, so i haven't had much hope for any helpful result along this path...
regards,
Chris
next reply other threads:[~2010-02-07 20:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-07 20:54 x [this message]
2010-02-10 1:15 ` [B.A.T.M.A.N.] batman-adv 0.2 on openwrt Linus Lüssing
2010-02-12 21:59 ` Linus Lüssing
2010-02-10 2:43 ` Linus Lüssing
2010-02-10 18:58 ` x
2010-02-11 2:39 ` Linus Lüssing
2010-02-11 9:00 ` Marek Lindner
2010-02-11 14:00 ` x
2010-02-12 11:09 ` Marek Lindner
2010-02-12 18:36 ` x
2010-02-12 23:45 ` Linus Lüssing
2010-02-13 5:47 ` x
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=4B6F288E.8050406@muc.ccc.de \
--to=x@muc.ccc.de \
--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