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