From: Robert Bradley <robert.bradley1@gmail.com>
To: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] Fwd: 3.3.6-2
Date: Thu, 24 May 2012 19:58:12 +0100 [thread overview]
Message-ID: <4FBE84C4.80607@gmail.com> (raw)
In-Reply-To: <4FBE7AAB.5080307@freedesktop.org>
On 24/05/12 19:15, Jim Gettys wrote:
> On 05/24/2012 02:12 PM, Sebastian Moeller wrote:
>> Hi Jim,
>>
>> good point, I will go and see whether that is the cause for my crashes… Will return to this post if/when I have new data in either direction…
> If you do, see if you can grab the babeld.conf file and add it to:
> https://www.bufferbloat.net/issues/392
>
I don't know if it helps at all, but it looks like Babel's failing to
obtain channel information for the guest interfaces (gw00 and gw10).
Are these disabled on your routers at the moment? I suppose in the
worst case you could try setting an explicit channel for both of the
non-mesh guest interfaces and see if the logs clear up (or somehow pass
"-L /dev/null" to babeld).
I'm assuming the ad-hoc mesh links are working fine, since gw01/gw11
aren't present in the log fragment.
--
Robert Bradley
next prev parent reply other threads:[~2012-05-24 18:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <00404BC8-3761-409D-A1C8-9213D7D9A3DF@gmx.de>
2012-05-24 3:48 ` Sebastian Moeller
2012-05-24 15:44 ` Robert Bradley
2012-05-24 16:18 ` Sebastian Moeller
2012-05-24 16:32 ` Jim Gettys
2012-05-24 18:12 ` Sebastian Moeller
2012-05-24 18:15 ` Jim Gettys
2012-05-24 18:58 ` Robert Bradley [this message]
2012-05-25 6:41 ` [Cerowrt-devel] 3.3.6-2 Sebastian Moeller
2012-05-25 7:02 ` Dave Taht
2012-05-25 11:11 ` Robert Bradley
2012-05-25 18:25 ` Sebastian Moeller
2012-05-25 22:38 ` Robert Bradley
2012-06-02 7:03 ` Sebastian Moeller
2012-06-03 22:24 ` Robert Bradley
2012-06-06 23:03 ` Sebastian Moeller
2012-05-25 0:04 ` [Cerowrt-devel] Fwd: 3.3.6-2 Sebastian Moeller
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
List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4FBE84C4.80607@gmail.com \
--to=robert.bradley1@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.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