From: Dave Taht <dave.taht@gmail.com>
To: Juergen Botz <jurgen@botz.org>
Cc: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] Meshing broken?
Date: Thu, 15 Aug 2013 15:48:58 -0700 [thread overview]
Message-ID: <CAA93jw5E+yxXKQ+PbGHH2yuFh2cQy8Rfaj8+-WnozOOz6EjH9w@mail.gmail.com> (raw)
In-Reply-To: <520D47AA.8050408@botz.org>
[-- Attachment #1: Type: text/plain, Size: 1420 bytes --]
ahcpd is enabled in client mode by default in this test series. So either
you need to have an ahcpd server or two on the mesh running, or to assign
ips manually in /etc/config/network for gw11 and gw01.
See the differences between /etc/config/ahcpd prior to 3.10 for how to
setup a server version of ahcpd
It's nice to know someone is playing with and actually dependent on the
meshy stuff.
I can revert back to server mode if you like but I had a reason for
switching to ahcpd client mode by default. 33 machines in the lab are
clients, and accidentally ending up with a rogue ahcp server on that caused
me serious headaches. Several times. I could, I guess, leave the static ips
up....
On Thu, Aug 15, 2013 at 2:27 PM, Juergen Botz <jurgen@botz.org> wrote:
> In the whole 3.10.x series (2-6 so far) meshing appears to be
> broken... my routers come up without an address on either of
> the babel interfaces. Reverting to 3.7.5 makes it work again.
>
> All the relevant processes (babeld, zebra, watchquagga) seem
> to be running, and there are no obvious error messages I can
> find...
>
> :j
>
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>
--
Dave Täht
Fixing bufferbloat with cerowrt:
http://www.teklibre.com/cerowrt/subscribe.html
[-- Attachment #2: Type: text/html, Size: 2041 bytes --]
next prev parent reply other threads:[~2013-08-15 22:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-15 21:27 Juergen Botz
2013-08-15 22:48 ` Dave Taht [this message]
2013-08-16 14:14 ` Juergen Botz
2013-08-16 17:59 ` Juergen Botz
[not found] ` <CAA93jw6LpjABPwe02NhKJYpXaoZz3i4ivshj7Rus-k+yENyzYQ@mail.gmail.com>
2013-08-16 18:13 ` Juergen Botz
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=CAA93jw5E+yxXKQ+PbGHH2yuFh2cQy8Rfaj8+-WnozOOz6EjH9w@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=jurgen@botz.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