From: "\"Juha Ylönen\"" <ylonen@gmx.net>
To: 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 15:51:51 +0100 [thread overview]
Message-ID: <20100119145151.294630@gmx.net> (raw)
In-Reply-To: <201001192007.38210.lindner_marek@yahoo.de>
[-- Attachment #1: Type: text/plain, Size: 1381 bytes --]
-------- Original-Nachricht --------
> Datum: Tue, 19 Jan 2010 20:07:38 +0800
> Von: Marek Lindner <lindner_marek@yahoo.de>
>
> It confirmed what we saw in the other logs: This device (the laptop?) does
> not
> see the packets from the other side, therefore the protocol correctly
> assumes
> a dead link. There might be 2 reasons: either the wifi layer does not
> really
> work or batman-adv drops the packets without any further warning.
> You can try the latest trunk and/or run batctl/wireshark on the laptop to
> deep-inspect the packets. Feel free to share the logs with us.
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?
-Juha
--
Jetzt kostenlos herunterladen: Internet Explorer 8 und Mozilla Firefox 3.5 -
sicherer, schneller und einfacher! http://portal.gmx.net/de/go/chbrowser
[-- Attachment #2: ARM-adhoc-batman --]
[-- Type: application/octet-stream, Size: 0 bytes --]
next prev parent reply other threads:[~2010-01-19 14:51 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" [this message]
2010-01-19 15:11 ` Sven Eckelmann
[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=20100119145151.294630@gmx.net \
--to=ylonen@gmx.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 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.