From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.botz.org (thalamus.botz.org [207.210.96.137]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "mail.botz.org", Issuer "mail.botz.org" (not verified)) by huchra.bufferbloat.net (Postfix) with ESMTPS id 2365B21F100 for ; Fri, 16 Aug 2013 07:14:20 -0700 (PDT) Received: from [127.0.0.1] (syzygy.botz.org [127.0.0.1]) (authenticated bits=0) by mail.botz.org (8.13.8/8.13.8) with ESMTP id r7GEGR3T023637 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 16 Aug 2013 10:16:29 -0400 DomainKey-Signature: a=rsa-sha1; s=thaldk; d=botz.org; c=simple; q=dns; b=iYb07a9AX3WNIYpAKDxnoUtYCkHjcQ+igeDKq+y2EYpVg6AUR30hPJ6mr0qrc/tMe mCBDckbVGgCi7ZdQpEqEA== DKIM-Signature: a=rsa-sha1; c=simple/simple; d=botz.org; s=thalamus; t=1376662590; bh=0BkWm0VI1aWrMYoBL38vWiBZfu4=; h=Message-ID:Date: From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To: Content-Type:Content-Transfer-Encoding:X-Scanned-By; b=kdJh0gzxJ5U+ vUKOKY8F/4cbtklGuBdKXNbwX5d7Edo4MD9daNhAc0lP1gj7MIlqAjIXpVpSirwRwP0 1Z12rh7AoCW/tXrLEgWk9a6T5nWJ72mq319KO2eegN2Ei/FfrUlNqCABJcUUlG8a5+W ZYJKoTT4Ag765dqSPc7gYG+i8= Message-ID: <520E33B7.2020008@botz.org> Date: Fri, 16 Aug 2013 11:14:15 -0300 From: Juergen Botz User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130625 Thunderbird/17.0.7 MIME-Version: 1.0 To: Dave Taht References: <520D47AA.8050408@botz.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.62 on 207.210.96.137 Cc: "cerowrt-devel@lists.bufferbloat.net" Subject: Re: [Cerowrt-devel] Meshing broken? X-BeenThere: cerowrt-devel@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: Development issues regarding the cerowrt test router project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Aug 2013 14:14:21 -0000 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