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: Thu, 21 Jan 2010 20:02:51 +0100 [thread overview]
Message-ID: <20100121190251.179780@gmx.net> (raw)
-------- Original-Nachricht --------
> Datum: Thu, 21 Jan 2010 18:57:52 +0100
> Von: Sven Eckelmann <sven.eckelmann@gmx.de>
> Yes, but doesn't explain why there is no batman-adv packet from ARM
> reaching
> the laptop and the other way around. batman-adv is a layer bellow and has
> nearly nothing to do with the stuff which runs over it (the only thing
> which
> accesses the layer over it should be the gateway stuff).
>
> @Juha, I found time and looked a little bit at the stuff which came from
> the
> ARM in the last log. Wireshark means that it is a Raw ethernet packet. And
> thinks that the stuff attached is a IPX packet.... but reading the raw
> data
> reveals that it should be the batman-packet.... with extra data between
> the
> ethernet header and the actual batman-adv packet. So the problem looks to
> me a
> little bit like hardware of the arm does something very stupid to our
> packets.
>
> I've attach a small picture to explain what I mean. The green part it the
> normal receiver and sender stuff for ethernet. The orange part is not
> explainable for me... Have we forgot some alignment stuff? Is your card
> adding
> some extra data? I am not sure what that could mean right now.
> The red thing is the ethernet type for batman-adv, pink the type of
> batman-adv
> packet, yellow the protocol version and light blue the flags for that
> packet.
> I don't know more color - so just marked the rest of the packet blue. The
> amount of bytes are correct and it looks fine to me.
>
> As anyone a good idea? Maybe a small capture of a normal ping test and a
> rawsend test between the both could help to understand the problem better.
> And
> can you maybe tell us what kind of hardware is used inside the arm for the
> eth1 device?
Hi,
This looks interesting, I've had problems with the wlan driver before but it has been quite stable for a while. Wlan chip in use is CSR UniFi 1050, with driver compiled from CSR supplied sources.
I'll try your rawsend and ping capturing during the weekend. Sorry for the bother in advance if this turns out to be due the crappy wlan driver (as said, it has been giving problems earlier, though I haven't seen any packet mangling before).
-Juha
--
Haiti-Nothilfe! Helfen Sie per SMS: Sende UIHAITI an die Nummer 81190.
Von 5 Euro je SMS (zzgl. SMS-Gebühr) gehen 4,83 Euro an UNICEF.
next reply other threads:[~2010-01-21 19:02 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-21 19:02 "Juha Ylönen" [this message]
2010-01-22 12:16 ` [B.A.T.M.A.N.] batman-adv on different archs Sven Eckelmann
-- strict thread matches above, loose matches on Subject: below --
2010-01-24 21:17 "Juha Ylönen"
2010-01-24 22:03 ` Sven Eckelmann
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-18 11:27 "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
[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
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=20100121190251.179780@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox