From: Sven Eckelmann <sven.eckelmann@gmx.de>
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: Sun, 24 Jan 2010 23:03:48 +0100 [thread overview]
Message-ID: <201001242303.56730.sven.eckelmann@gmx.de> (raw)
In-Reply-To: <20100124211718.37790@gmx.net>
[-- 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 --]
next prev parent reply other threads:[~2010-01-24 22:03 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-24 21:17 [B.A.T.M.A.N.] batman-adv on different archs "Juha Ylönen"
2010-01-24 22:03 ` Sven Eckelmann [this message]
2010-01-26 7:20 ` [B.A.T.M.A.N.] batman-adv mujlticast [WAS: Re: batman-adv on different archs] "Juha Ylönen"
2010-01-26 7:24 ` Marek Lindner
-- strict thread matches above, loose matches on Subject: below --
2010-01-21 19:02 [B.A.T.M.A.N.] batman-adv on different archs "Juha Ylönen"
2010-01-22 12:16 ` 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=201001242303.56730.sven.eckelmann@gmx.de \
--to=sven.eckelmann@gmx.de \
--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