From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by huchra.bufferbloat.net (Postfix) with ESMTPS id AFD9021F200 for ; Fri, 11 Oct 2013 12:46:19 -0700 (PDT) Received: from compute3.internal (compute3.nyi.mail.srv.osa [10.202.2.43]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 6E50A219D5; Fri, 11 Oct 2013 15:46:17 -0400 (EDT) Received: from frontend2 ([10.202.2.161]) by compute3.internal (MEProxy); Fri, 11 Oct 2013 15:46:17 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=imap.cc; h=from :mime-version:content-type:subject:date:in-reply-to:to :references:message-id; s=mesmtp; bh=6mF+3FtP4bTOemMjTbN7HyQDt1E =; b=EqRi5Qgrghq6DJkIMz1zRuCbpdc3f/glfcHocN3e+UAtUJ74edhTB7eTHXe 9t2uI/Dz3HtPBc+bYr2oWcCcjfZbX1PNqXDCniCKGNqPitiknhAe771H+qeyXhNq EhmM2elNvNL7KBegn5pg34ytt5QO34iLgSgfWmyP8pgG0sZQ= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=from:mime-version:content-type:subject :date:in-reply-to:to:references:message-id; s=smtpout; bh=6mF+3F tP4bTOemMjTbN7HyQDt1E=; b=hGuij1PaU1fBQ0xmaZMaoU94VWBBzwuuNM93dr TYsr0WS7a6Awdt3ucMHm+I6JvV93gldHM8uNdsPj6+VMxV/QcVKJF/0YWwn6WVZo ObwMbIbMGO579PHRs77OQxjhGZM4nEXj64en20bcDP/2JYaPwwlspyKrGydbA4k/ V67BE= X-Sasl-enc: kxDbCyZQN5WSh4sgh8mQMA66ANbXF+AHnxJ6N9SXgfHV 1381520776 Received: from [172.30.42.27] (unknown [78.147.115.206]) by mail.messagingengine.com (Postfix) with ESMTPA id A269668011D for ; Fri, 11 Oct 2013 15:46:16 -0400 (EDT) From: Fred Stratton Mime-Version: 1.0 (Apple Message framework v1283) Content-Type: multipart/alternative; boundary="Apple-Mail=_460F72D6-8563-4CF1-93A1-A0EAE568ECE2" Date: Fri, 11 Oct 2013 20:46:14 +0100 In-Reply-To: To: cerowrt-devel@lists.bufferbloat.net References: <9A9AF30E-7F5A-41DF-AE94-0C92AD7BBED9@imap.cc> <5256DBB1.50707@thekelleys.org.uk> <52570CC6.4080508@thekelleys.org.uk> Message-Id: X-Mailer: Apple Mail (2.1283) Subject: Re: [Cerowrt-devel] [Dnsmasq-discuss] Names not resolved on Wireless 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, 11 Oct 2013 19:46:20 -0000 --Apple-Mail=_460F72D6-8563-4CF1-93A1-A0EAE568ECE2 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=iso-8859-1 Reverted DNSmasq to 2.67test10* as suggested. Still no ipv4 addresses. = Reverted to 3.10.11-3 again. Checked settings. Renewed leases. Rebooted = everything. On 11 Oct 2013, at 15:30, Dave Taht wrote: >=20 > On Oct 11, 2013 4:02 AM, "David Personette" wrote: > > > > Sorry, it's still behaving the same for me. Failed back to 3.10.11-3 = once more. >=20 > OK I will set aside time Sunday and Monday to poke deeply into this. >=20 > I note you probably needent revert all the way back to this version. = You can wget the version of DNSmasq from this versions packages and = forcibly apply it on top of 3.10.15-4 using opkg. >=20 > > -- > > David P. > > > > > > On Thu, Oct 10, 2013 at 8:01 PM, Dave Taht = wrote: > >> > >> 3.10.15-4 is now out there, containing sufficient patches to get > >> dnsmasq to the current head of tree, and including the patch below. > >> > >> http://snapon.lab.bufferbloat.net/~cero2/cerowrt/wndr/3.10.15-4/ > >> > >> On Thu, Oct 10, 2013 at 1:23 PM, Simon Kelley = wrote: > >> > Having thought about this more, this patch is necessary > >> > > >> > = http://thekelleys.org.uk/gitweb/?p=3Ddnsmasq.git;a=3Dcommit;h=3D8584c502d3= 7627d8abe18213771b5f4f98cb4aa3 > >> > > >> > and should fix the bug iff > >> > > >> > 1) Dnsmasq is configured using --except-interface=3D and > >> > there are no --interface=3D config > >> > lines. > >> > > >> > 2) Exactly one interface that dnsmasq should be listening on is = around when > >> > it starts, but others arrive later. > >> > > >> > I can't explain why it just broke though, this bug has been = around forever. > >> > > >> > > >> > > >> > Simon. > >> > > >> > > >> > > >> > > >> > > >> > On 10/10/13 19:30, Dave Taht wrote: > >> >> > >> >> On Thu, Oct 10, 2013 at 9:54 AM, Simon = Kelley > >> >> wrote: > >> >>> > >> >>> > >> >>> Does reverting > >> >>> > >> >>> > >> >>> = http://thekelleys.org.uk/gitweb/?p=3Ddnsmasq.git;a=3Dcommit;h=3D397542b213= ab4071734f1cdf4cc914d87100456f > >> >>> > >> >>> fix the issue? I fear it might. > >> >> > >> >> > >> >> Seems likely. > >> >> > >> >> I reverted that patch and put it in this build > >> >> > >> >> http://snapon.lab.bufferbloat.net/~cero2/cerowrt/wndr/3.10.15-3/ > >> >> > >> >> I won't be in a position to test stuff myself til sunday but = cero's > >> >> devoted userbase seems to be hoovering over the reload button = and will > >> >> probably beat me to it.... > >> >> > >> >> > >> >>> > >> >>> Cheers, > >> >>> > >> >>> Simon. > >> >>> > >> >>> > >> >>> > >> >>> On 10/10/13 15:43, Dave Taht wrote: > >> >>>> > >> >>>> > >> >>>> Dear Dr. Dnsmasq: > >> >>>> > >> >>>> When cerowrt made the jump between dnsmasq-2.67-test10 and > >> >>>> dnsmasq-2.67-test17, detection of interfaces other than the = first > >> >>>> started failing. It seems to be related to interfaces that = come up > >> >>>> after dnsmasq starts, as restarting it after the device is = fully > >> >>>> booted works. Have moved forward to 2.67-rc3 to no avail. > >> >>>> > >> >>>> (along the way we migrated from kernel 3.10.11 to 3.10.13 to = 3.10.15 > >> >>>> but I doubt that's the issue) > >> >>>> > >> >>>> Hot, fresh, firmware can be had at: > >> >>>> > >> >>>> http://snapon.lab.bufferbloat.net/~cero2/cerowrt/wndr/ > >> >>>> > >> >>>> > >> >>>> [10:39:25] has anyone had IPv4 DHCP problems in the = last two > >> >>>> 3.10.x > >> >>>> builds? currently running 3.10.11-3 and it works flawlessly. > >> >>>> upgraded to 3.10.13-2 and 3.10.15-1 and both present me with = an > >> >>>> identical issue. upon reboot after upgrading, DHCP leases are = no > >> >>>> longer handed out on the wireless interfaces. disabling and > >> >>>> re-enabling DHCP on the wireless interfaces will fix the = problem, but > >> >>>> the problem > >> >>>> [10:39:26] returns after a reboot. = disable/reenable DHCP on > >> >>>> the > >> >>>> interface will again temporarily fix it. > >> >>>> [10:42:03] also tried a fresh install (using reset = to > >> >>>> defaults > >> >>>> option) to avoid anything not properly interpreted from the = config of > >> >>>> the previous version, but still get the same issue. > >> >>>> > >> >>>> > >> >>>> On Thu, Oct 10, 2013 at 5:30 AM, David = Personette > >> >>>> wrote: > >> >>>>> > >> >>>>> > >> >>>>> Just tested again with 3.10.15-2. My OSX (10.8.5) laptop = worked, > >> >>>>> neither > >> >>>>> my > >> >>>>> Nexus 7 (2013 w/CM10.2) or my Fedora 19 laptop could resolve = DNS over > >> >>>>> wireless. My wired Linux server (Ubuntu 12.04.3) was working = fine as > >> >>>>> well. > >> >>>>> Reverted to 3.10.11-3 once more. > >> >>>>> > >> >>>>> -- > >> >>>>> David P. > >> >>>>> > >> >>>>> > >> >>>>> On Mon, Oct 7, 2013 at 7:40 PM, David = Personette > >> >>>>> wrote: > >> >>>>>> > >> >>>>>> > >> >>>>>> > >> >>>>>> I can confirm it as well. I wiped my config back to = defaults, and it > >> >>>>>> wasn't fixed. Reinstalled the 3.10.11-3 build, and restored = my configs > >> >>>>>> and > >> >>>>>> all is well. > >> >>>>>> > >> >>>>>> -- > >> >>>>>> David P. > >> >>>>>> > >> >>>>>> > >> >>>>>> On Mon, Oct 7, 2013 at 7:07 PM, Fred = Stratton > >> >>>>>> wrote: > >> >>>>>>> > >> >>>>>>> > >> >>>>>>> > >> >>>>>>> True for the last two builds. Wired works as expected. > >> >>>>>>> > >> >>>>>>> Is this a problem with the development version of DNSMasq? = What is > >> >>>>>>> the > >> >>>>>>> recommended workaround? > >> >>>>>>> > >> >>>>>>> _______________________________________________ > >> >>>>>>> Cerowrt-devel mailing list > >> >>>>>>> Cerowrt-devel@lists.bufferbloat.net > >> >>>>>>> https://lists.bufferbloat.net/listinfo/cerowrt-devel > >> >>>>>> > >> >>>>>> > >> >>>>>> > >> >>>>>> > >> >>>>> > >> >>>>> > >> >>>>> _______________________________________________ > >> >>>>> Cerowrt-devel mailing list > >> >>>>> Cerowrt-devel@lists.bufferbloat.net > >> >>>>> https://lists.bufferbloat.net/listinfo/cerowrt-devel > >> >>>>> > >> >>>> > >> >>>> > >> >>>> > >> >>> > >> >>> > >> >>> _______________________________________________ > >> >>> Dnsmasq-discuss mailing list > >> >>> Dnsmasq-discuss@lists.thekelleys.org.uk > >> >>> http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss > >> >> > >> >> > >> >> > >> >> > >> > > >> > >> > >> > >> -- > >> Dave T=E4ht > >> > >> Fixing bufferbloat with cerowrt: = http://www.teklibre.com/cerowrt/subscribe.html > >> _______________________________________________ > >> Cerowrt-devel mailing list > >> Cerowrt-devel@lists.bufferbloat.net > >> https://lists.bufferbloat.net/listinfo/cerowrt-devel > > > > > _______________________________________________ > Cerowrt-devel mailing list > Cerowrt-devel@lists.bufferbloat.net > https://lists.bufferbloat.net/listinfo/cerowrt-devel --Apple-Mail=_460F72D6-8563-4CF1-93A1-A0EAE568ECE2 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=iso-8859-1


On Oct 11, 2013 4:02 AM, "David Personette" <dperson@gmail.com> wrote:
>
> Sorry, it's still behaving the same for me. Failed back to = 3.10.11-3 once more.

OK I will set aside time = Sunday and Monday to poke deeply into this.

I note you = probably needent revert all the way back to this version. You can wget = the version of DNSmasq from this versions packages and forcibly apply it = on top of 3.10.15-4 using opkg.

> --
> David P.
>
>
> On Thu, Oct 10, 2013 at 8:01 PM, Dave Taht <dave.taht@gmail.com> = wrote:
>>
>> 3.10.15-4 is now out there, containing sufficient patches to = get
>> dnsmasq to the current head of tree, and including the patch = below.
>>
>> = http://snapon.lab.bufferbloat.net/~cero2/cerowrt/wndr/3.10.15-4/
>>
>> On Thu, Oct 10, 2013 at 1:23 PM, Simon Kelley <simon@thekelleys.org.uk> = wrote:
>> > Having thought about this more, this patch is = necessary
>> >
>> > http://thekelleys.org.uk/gitweb/?p= =3Ddnsmasq.git;a=3Dcommit;h=3D8584c502d37627d8abe18213771b5f4f98cb4aa3=
>> >
>> > and should fix the bug iff
>> >
>> > 1) Dnsmasq is configured using = --except-interface=3D<upstream interface> and
>> > there are no --interface=3D<interface we want to = provide service on> config
>> > lines.
>> >
>> > 2) Exactly one interface that dnsmasq should be listening = on is around when
>> > it starts, but others arrive later.
>> >
>> > I can't explain why it just broke though, this bug has = been around forever.
>> >
>> >
>> >
>> > Simon.
>> >
>> >
>> >
>> >
>> >
>> > On 10/10/13 19:30, Dave Taht wrote:
>> >>
>> >> On Thu, Oct 10, 2013 at 9:54 AM, Simon Kelley<simon@thekelleys.org.uk> >> >> wrote:
>> >>>
>> >>>
>> >>> Does reverting
>> >>>
>> >>>
>> >>> http://thekelleys.org.uk/gitweb/?p= =3Ddnsmasq.git;a=3Dcommit;h=3D397542b213ab4071734f1cdf4cc914d87100456f=
>> >>>
>> >>> fix the issue? I fear it might.
>> >>
>> >>
>> >> Seems likely.
>> >>
>> >> I reverted that patch and put it in this build
>> >>
>> >> = http://snapon.lab.bufferbloat.net/~cero2/cerowrt/wndr/3.10.15-3/
>> >>
>> >> I won't be in a position to test stuff myself til = sunday but cero's
>> >> devoted userbase seems to be hoovering over the reload = button and will
>> >> probably beat me to it....
>> >>
>> >>
>> >>>
>> >>> Cheers,
>> >>>
>> >>> Simon.
>> >>>
>> >>>
>> >>>
>> >>> On 10/10/13 15:43, Dave Taht wrote:
>> >>>>
>> >>>>
>> >>>> Dear Dr. Dnsmasq:
>> >>>>
>> >>>> When cerowrt made the jump between = dnsmasq-2.67-test10 and
>> >>>> dnsmasq-2.67-test17, detection of interfaces = other than the first
>> >>>> started failing. It seems to be related to = interfaces that come up
>> >>>> after dnsmasq starts, as restarting it after = the device is fully
>> >>>> booted works. Have moved forward to 2.67-rc3 = to no avail.
>> >>>>
>> >>>> (along the way we migrated from kernel 3.10.11 = to 3.10.13 to 3.10.15
>> >>>> but I doubt that's the issue)
>> >>>>
>> >>>> Hot, fresh, firmware can be had at:
>> >>>>
>> >>>> http://sna= pon.lab.bufferbloat.net/~cero2/cerowrt/wndr/
>> >>>>
>> >>>>
>> >>>> <knacky>   [10:39:25] has anyone = had IPv4 DHCP problems in the last two
>> >>>> 3.10.x
>> >>>> builds?  currently running 3.10.11-3 and = it works flawlessly.
>> >>>> upgraded to 3.10.13-2 and 3.10.15-1 and both = present me with an
>> >>>> identical issue.  upon reboot after = upgrading, DHCP leases are no
>> >>>> longer handed out on the wireless interfaces. =  disabling and
>> >>>> re-enabling DHCP on the wireless interfaces = will fix the problem, but
>> >>>> the problem
>> >>>> <knacky>   [10:39:26] returns after = a reboot.  disable/reenable DHCP on
>> >>>> the
>> >>>> interface will again temporarily fix it.
>> >>>> <knacky>   [10:42:03] also tried a = fresh install (using reset to
>> >>>> defaults
>> >>>> option) to avoid anything not properly = interpreted from the config of
>> >>>> the previous version, but still get the same = issue.
>> >>>>
>> >>>>
>> >>>> On Thu, Oct 10, 2013 at 5:30 AM, David = Personette<dperson@gmail.com>
>> >>>> wrote:
>> >>>>>
>> >>>>>
>> >>>>> Just tested again with 3.10.15-2. My OSX = (10.8.5) laptop worked,
>> >>>>> neither
>> >>>>> my
>> >>>>> Nexus 7 (2013 w/CM10.2) or my Fedora 19 = laptop could resolve DNS over
>> >>>>> wireless. My wired Linux server (Ubuntu = 12.04.3) was working fine as
>> >>>>> well.
>> >>>>> Reverted to 3.10.11-3 once more.
>> >>>>>
>> >>>>> --
>> >>>>> David P.
>> >>>>>
>> >>>>>
>> >>>>> On Mon, Oct 7, 2013 at 7:40 PM, David = Personette<dperson@gmail.com>
>> >>>>> wrote:
>> >>>>>>
>> >>>>>>
>> >>>>>>
>> >>>>>> I can confirm it as well. I wiped my = config back to defaults, and it
>> >>>>>> wasn't fixed. Reinstalled the = 3.10.11-3 build, and restored my configs
>> >>>>>> and
>> >>>>>> all is well.
>> >>>>>>
>> >>>>>> --
>> >>>>>> David P.
>> >>>>>>
>> >>>>>>
>> >>>>>> On Mon, Oct 7, 2013 at 7:07 PM, Fred = Stratton<fredstratton@imap.cc>
>> >>>>>> wrote:
>> >>>>>>>
>> >>>>>>>
>> >>>>>>>
>> >>>>>>> True for the last two builds. = Wired works as expected.
>> >>>>>>>
>> >>>>>>> Is this a problem with the = development version of DNSMasq? What is
>> >>>>>>> the
>> >>>>>>> recommended workaround?
>> >>>>>>>
>> >>>>>>> = _______________________________________________
>> >>>>>>> Cerowrt-devel mailing list
>> >>>>>>> Cerowrt-devel@lists.bu= fferbloat.net
>> >>>>>>> https://list= s.bufferbloat.net/listinfo/cerowrt-devel
>> >>>>>>
>> >>>>>>
>> >>>>>>
>> >>>>>>
>> >>>>>
>> >>>>>
>> >>>>> = _______________________________________________
>> >>>>> Cerowrt-devel mailing list
>> >>>>> Cerowrt-devel@lists.bu= fferbloat.net
>> >>>>> https://list= s.bufferbloat.net/listinfo/cerowrt-devel
>> >>>>>
>> >>>>
>> >>>>
>> >>>>
>> >>>
>> >>>
>> >>> = _______________________________________________
>> >>> Dnsmasq-discuss mailing list
>> >>> Dnsmasq-discuss@li= sts.thekelleys.org.uk
>> >>> h= ttp://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
>> >>
>> >>
>> >>
>> >>
>> >
>>
>>
>>
>> --
>> Dave T=E4ht
>>
>> Fixing bufferbloat with cerowrt: http://www.teklibr= e.com/cerowrt/subscribe.html
>> _______________________________________________
>> Cerowrt-devel mailing list
>> Cerowrt-devel@lists.bu= fferbloat.net
>> https://list= s.bufferbloat.net/listinfo/cerowrt-devel
>
>

_______________________________________________
Cerowrt-devel mailing = list
Cerowrt-devel@lists.bu= fferbloat.net
https://lists.bufferbloat.net/listinfo/cerowrt-devel<= br>

= --Apple-Mail=_460F72D6-8563-4CF1-93A1-A0EAE568ECE2--