public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Marek Lindner <lindner_marek@yahoo.de>
To: The list for a Better Approach To Mobile Ad-hoc Networking
	<b.a.t.m.a.n@open-mesh.net>
Subject: Re: [B.A.T.M.A.N.] Problem with B.A.T.M.A.N. 0.3.1 rv1206 (compatibility version 5)
Date: Fri, 20 Mar 2009 20:47:30 +0800	[thread overview]
Message-ID: <200903202047.30861.lindner_marek@yahoo.de> (raw)
In-Reply-To: <3ebdcf0a0903190638p583bababq7891e21413b4f4e@mail.gmail.com>

On Thursday 19 March 2009 21:38:14 Max wrote:
> Now I'm able to ping every originator in the network. The problem is
> derived from some iptables filters that stop the ping. Executing the
> following command I remove the filters solving the problem:

Glad to hear that.


> When I launch the daemon in normal mode, using the command "batmand ath0",
> no error is displayed but no OGMs is observed to be travelling in the
> network using Wireshark. The only message displayed is:
> "Interface activated: ath0
> Using interface ath0 with address 10.0.0.1 and broadcast address
> 10.255.255.255"

Could you please run 
batmand -c -d 4
after you started the daemon ? This command will make batman start a "client" 
that connects to the running daemon that outputs error messages. Feel free to 
share these messages with us.  :-)


> And finally another question...
> Is it normal to observe 3 different processes named batmand using the shell
> command ps?

Batman uses threads to parallelize certain tasks (basically 2 threads). Older 
kernel versions / different thread implementations don't offer "real" threads 
but use processes instead. Usually, they create a control process that syncs 
the other "threads" (processes in this case), hence 2 + 1 processes in "ps".

Regards,
Marek


  reply	other threads:[~2009-03-20 12:47 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-18 14:43 [B.A.T.M.A.N.] Problem with B.A.T.M.A.N. 0.3.1 rv1206 (compatibility version 5) Max
2009-03-19  2:55 ` Marek Lindner
2009-03-19 13:38   ` Max
2009-03-20 12:47     ` Marek Lindner [this message]
2009-03-20 13:03       ` Max
2009-03-21  1:13         ` Marek Lindner
2009-03-21 13:07           ` Max
2009-03-23 17:13             ` Marek Lindner
2009-03-23 22:05               ` Sven Eckelmann
2009-03-24 19:17                 ` Sven Eckelmann
2009-03-25  2:44                   ` Marek Lindner
2009-03-26 12:59                     ` [B.A.T.M.A.N.] [PATCH] Don't detach batmand to background by default Sven Eckelmann
2009-03-31 18:26                       ` Marek Lindner
2009-04-01 10:28                         ` Sven Eckelmann
2009-04-01 10:31                           ` [B.A.T.M.A.N.] [PATCH 1/2] Add parameter to disable fork to background Sven Eckelmann
2009-04-01 10:31                           ` [B.A.T.M.A.N.] [PATCH 2/2] Sanitise batmand process by reexecuting it Sven Eckelmann
2009-04-01 22:20                             ` [B.A.T.M.A.N.] [PATCHv2 " Sven Eckelmann
2009-03-24 12:45               ` [B.A.T.M.A.N.] Problem with B.A.T.M.A.N. 0.3.1 rv1206 (compatibility version 5) P. Mazart
2009-04-11  0:54 ` Marek Lindner
  -- strict thread matches above, loose matches on Subject: below --
2009-03-19 12:55 Marco Tozzini

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=200903202047.30861.lindner_marek@yahoo.de \
    --to=lindner_marek@yahoo.de \
    --cc=b.a.t.m.a.n@open-mesh.net \
    /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