batman-adv on different archs

Datum: Thu, 21 Jan 2010 18:57:52 +0100
Von: Sven Eckelmann <[email protected]>
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?

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).