Re: [B.A.T.M.A.N.] batman-adv on different archs

Sven Eckelmann
2010-01-24T22:03:48Z

[-- Attachment #1: Type: Text/Plain, Size: 1268 bytes --]

Juha Ylönen wrote:
> > So please test and capture
> > * rawsend from ARM
> > * ping between laptop and arm
> > * a "ping -s 1" between laptop and arm
> >
> > I hope that tests help to see were the problem really is. If the ping -s
> > 1 works, can you please also capture a some packets of batman-adv 0.2?
>
> Logs for all cases attached. I pinged from arm to laptop, would you have
> liked it in the other direction too?

No, one direction is ok. What we can see here is that we have a < 50 bytes
packet and it is seems to be send correctly. So maybe the problem is not
related to "small" packets.

> Rawsend from arm->laptop didn't work, the packets end up in the laptop as
> llc packets, so apparently they were mangled by the driver. rawsend from
> laptop->arm worked fine, which is included in the rawsend.log file.

Ok, so we have a real simple example here. We see that we have a "large"
ethernet frame (unlike batman-adv) and a "unnormal" ethernet type. So maybe
you could forward rawsend.log and rawsend.c to the driver developers. They
should be able to find and fix the problem with such a real small example. Or
does anyone see a related problem in rawsend.c?

What is the batmand stuff for?

Best regards,
Sven

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]