public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
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: Tue, 19 Jan 2010 18:12:59 +0100	[thread overview]
Message-ID: <201001191813.04466.sven.eckelmann@gmx.de> (raw)
In-Reply-To: <20100119153233.319500@gmx.net>

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

Juha Ylönen wrote:
> > As far as I can see only data from 00:22:fa:dc:9a:ce can be seen (send
> > from us
> > aka laptop?). Have you tested if the adhoc connection between this two
> > devices
> > (arm <-> laptop) is really working (just set up the adhoc network as
> > usual and
> > then give them an ip instead of adding to
> > /proc/net/batman-adv/interfaces. A
> > simple ping test should be sufficient to say that it works(tm)).
> 
> Yes, ad-hoc itself works pretty well. the device boots up to his default
>  ad-hoc, and I've sent the module over with scp and did some configuring
>  over ssh. I did run couple of tests with IP disabled in the interfaces
>  (set up exactly as in the readme) but recently I've just kept them in the
>  default setup with IP's, will it cause problems? The problem existed with
>  non-IP interfaces too.

batman-adv works on a lower level - so it shouldn't be a really problem in 
that situation. Maybe you can "tcpdump -s 0 -w test.dump" on the arm too. I am 
currently not sure why the arm cannot or doesn't send packets at all. The logs 
in 20100118132935.91200@gmx.net say that it was send, but I currently don't 
understand why they don't reach their destination. Maybe a dump from the arm 
reveals the problem - or at least we know if data gets send at all or if the 
data is stopped somewhere else.

Best regards,
	Sven

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

  parent reply	other threads:[~2010-01-19 17:12 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"
2010-01-19 15:11             ` Sven Eckelmann
     [not found]               ` <20100119153233.319500@gmx.net>
2010-01-19 17:12                 ` Sven Eckelmann [this message]
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=201001191813.04466.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