Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Juergen Botz <jurgen@botz.org>
To: Dave Taht <dave.taht@gmail.com>
Cc: "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] Meshing broken?
Date: Fri, 16 Aug 2013 11:14:15 -0300	[thread overview]
Message-ID: <520E33B7.2020008@botz.org> (raw)
In-Reply-To: <CAA93jw5E+yxXKQ+PbGHH2yuFh2cQy8Rfaj8+-WnozOOz6EjH9w@mail.gmail.com>

On 08/15/2013 07:48 PM, Dave Taht wrote:
> 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

Well I had been doing sysupgrades, so my config didn't change,
and I had one router as server and one as client in my config
regardless of what you made the default.  But first in 3.10.x
ahcpd wasn't even coming up... this part I figured out, it was
because I had the two 'list interface gwXX' lines in
/etc/config/ahcpd commented out; up through 3.7.x ahcpd came up
and did its thing regardless, but as of 3.10.x those lines are
needed for ahcpd to start.

Now ahcpd starts up, but the gw{01,11} interfaces still
don't seem to get an address even though /etc/config/network
does list them with 'proto ahcp'.

So something is still different... any ideas?

:j



  reply	other threads:[~2013-08-16 14:14 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
2013-08-16 14:14   ` Juergen Botz [this message]
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=520E33B7.2020008@botz.org \
    --to=jurgen@botz.org \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=dave.taht@gmail.com \
    /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