From: Axel Neumann <axel@open-mesh.net>
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.] Rev 972: batmand -c -d n hangs sometimes
Date: Tue, 12 Feb 2008 20:34:21 +0100 [thread overview]
Message-ID: <200802122034.21957.axel@open-mesh.net> (raw)
In-Reply-To: <20080212094759.vx84kym5c0oowok0@webmail.ddmesh.de>
Hello,
On Dienstag 12 Februar 2008, Freifunk Dresden wrote:
> I have also disabled this "logging" completely and let only run batmand to
> build up the net. I can not say if the access to the debug output leads to
> blocking the batmand faster.I also have seen that batmand blocks after
> awhile if it is only running for building the network.
Ok, then it does not strictly depend on the logging.
>
> I have put a logfile on my webpage.
> http://www.ddmesh.de/batmand-hanglog.txt
>
> In one of the previous threads someone had a problem with "batmand
> going crazy".
> I'm not sure to remember right. But I think that it had to do with
> sequence number that's wrapping around.
> The logfile ends at the time batmand stopps. At the end of this log you
> will find something like "prevRxSeqno: 0, currRxSeqno-prevRxSeqno 0,"
> perhabs it is the same reason.
I checked the log file.
the "prevRxSeqno: 0..." line is no problem. The "0" comes from a bad debug
statement. If you search your debug log you'll see many of these lines.
The "going crazy..." thing was related to overlapping uptime - thats also
another story.
>
> batmand is currently started with two interfaces eth1 and tbb. eth1 is
> the wireless interface and tbb is a tun/tap device that is used by vpn
> tincd.
> tincd has got invalid hostnames, so it never creates a connection.
> Perhabs batmand has a problem with this kind of "dead" interfaces.
> I have tried to remove this tbb interface when starting batmand.
> batmand was running at least for two days. But the "dead" interface
> may also have no influence to this problem.
> Currently batmand is running since 10 hours with eth1 and tbb (dead
> interface).
Can you verify if the problem also occures if batmand is started without any
tap devices?
Can you check for other syslog messages that might be related to the stopping
batmand? What does logread say ?
The strange thing is that the debug-level-4 output stops in the middle of an
action. Can you also check for the number of batmand processes before and
after the stopped batmand process?
Have you ever tried what happens if you connect the tap interface to a bridge
and bind batmand to the bridge device instead?
Last but not least: have you observed (or explicitly not observed) this
phenomenon also with previous revisions in the same scenario ?
>
> I never have seen this problem with the WRT54GS, only with GL.
Is the batmand on the WRT54GS also bound to a tinc interface ?
ciao,
axel
>
> /Stephan
>
>
>
>
> _______________________________________________
> B.A.T.M.A.N mailing list
> B.A.T.M.A.N@open-mesh.net
> https://list.open-mesh.net/mm/listinfo/b.a.t.m.a.n
next prev parent reply other threads:[~2008-02-12 19:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-03 11:50 [B.A.T.M.A.N.] Rev 972: batmand -c -d n hangs sometimes Freifunk Dresden
2008-02-03 18:27 ` elektra
2008-02-12 8:27 ` Freifunk Dresden
2008-02-11 12:04 ` Axel Neumann
2008-02-12 8:47 ` Freifunk Dresden
2008-02-12 19:34 ` Axel Neumann [this message]
2008-02-13 16:48 ` Freifunk Dresden
2008-02-14 9:19 ` Axel Neumann
-- strict thread matches above, loose matches on Subject: below --
2008-02-14 20:15 Freifunk Dresden
2008-02-15 18:27 ` Axel Neumann
2008-02-17 20:48 Freifunk Dresden
2008-02-25 11:00 ` Axel Neumann
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=200802122034.21957.axel@open-mesh.net \
--to=axel@open-mesh.net \
--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