From: Sven Eckelmann <sven.eckelmann@gmx.de>
To: "Juha Ylönen" <ylonen@gmx.net>
Cc: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] batman-adv on different archs
Date: Tue, 19 Jan 2010 16:11:27 +0100 [thread overview]
Message-ID: <201001191611.30799.sven.eckelmann@gmx.de> (raw)
In-Reply-To: <20100119145151.294630@gmx.net>
[-- Attachment #1: Type: Text/Plain, Size: 1486 bytes --]
Juha Ylönen wrote:
> I got the latest trunk up and running, some changes were required to get it
> to crosscompile for ARM (and 2.6.24 kernel). Same behaviour as before,
> device log shows a lot of activity, but laptop batman doesn't seem to be
> doing much anything. I tried the wireshark and got a log ok (which shows a
> lot of multicast traffic from the device until I disabled the service) but
> I'm at loss to decipher possible batman packages. What should they look
> like in wireshark? I only noticed couple of IPX packages from device to
> (broadcast?) but nothing else. I attached the log file, is anyone able to
> say if there are batman packages included?
There is a dissector for wireshark at
http://gitorious.org/wireshark-batman-plugins/wireshark-batman-adv
(compatible with 0.2, but haven't added new code to make it compatible with
new functionality in trunk). I will add support for protocol version 9 after
finishing some other non-paid work.
Your log is for version 9 of the protocol (trunk). So it is harder to read :)
As far as I can see only data from 00:22:fa:dc:9a:ce can be seen (send from us
aka laptop?). Have you tested if the adhoc connection between this two devices
(arm <-> laptop) is really working (just set up the adhoc network as usual and
then give them an ip instead of adding to /proc/net/batman-adv/interfaces. A
simple ping test should be sufficient to say that it works(tm)).
Best regards,
Sven
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2010-01-19 15:11 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-18 11:27 [B.A.T.M.A.N.] batman-adv on different archs "Juha Ylönen"
2010-01-18 11:39 ` Andrew Lunn
2010-01-18 13:29 ` "Juha Ylönen"
2010-01-18 13:38 ` Marek Lindner
2010-01-18 13:51 ` Andrew Lunn
2010-01-19 7:46 ` "Juha Ylönen"
2010-01-19 7:43 ` "Juha Ylönen"
2010-01-19 12:07 ` Marek Lindner
2010-01-19 14:51 ` "Juha Ylönen"
2010-01-19 15:11 ` Sven Eckelmann [this message]
[not found] ` <20100119153233.319500@gmx.net>
2010-01-19 17:12 ` Sven Eckelmann
2010-01-19 19:37 ` Simon Wunderlich
2010-01-20 14:05 ` "Juha Ylönen"
2010-01-20 21:58 ` Marek Lindner
2010-01-18 11:42 ` Marek Lindner
-- strict thread matches above, loose matches on Subject: below --
2010-01-19 14:58 "Juha Ylönen"
2010-01-20 2:15 ` Marek Lindner
2010-01-20 9:29 ` "Juha Ylönen"
2010-01-20 9:42 ` Marek Lindner
2010-01-20 9:49 ` Andrew Lunn
2010-01-20 9:51 ` Sven Eckelmann
2010-01-20 13:12 ` "Juha Ylönen"
2010-01-20 22:32 ` Marek Lindner
2010-01-21 14:12 ` "Juha Ylönen"
2010-01-21 15:29 ` Sven Eckelmann
2010-01-21 17:17 ` Gus Wirth
2010-01-21 18:32 ` Sven Eckelmann
2010-01-22 18:26 ` Simon Wunderlich
2010-01-24 21:19 ` "Juha Ylönen"
2010-01-21 19:02 "Juha Ylönen"
2010-01-22 12:16 ` Sven Eckelmann
2010-01-24 21:17 "Juha Ylönen"
2010-01-24 22:03 ` Sven Eckelmann
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=201001191611.30799.sven.eckelmann@gmx.de \
--to=sven.eckelmann@gmx.de \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=ylonen@gmx.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