Same here. Reverting again.


On 11 Oct 2013, at 12:02, David Personette wrote:

> Sorry, it's still behaving the same for me. Failed back to 3.10.11-3 once more.
> 
> --
> 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=dnsmasq.git;a=commit;h=8584c502d37627d8abe18213771b5f4f98cb4aa3
> >
> > and should fix the bug iff
> >
> > 1) Dnsmasq is configured using --except-interface=<upstream interface> and
> > there are no --interface=<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=dnsmasq.git;a=commit;h=397542b213ab4071734f1cdf4cc914d87100456f
> >>>
> >>> 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/
> >>>>
> >>>>
> >>>> <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.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äht
> 
> 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