[Cerowrt-devel] Names not resolved on Wireless

[Cerowrt-devel] Names not resolved on Wireless

[Fred Stratton]

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?

Re: [Cerowrt-devel] Names not resolved on Wireless

[David Personette]

[-- Attachment #1: Type: text/plain, Size: 584 bytes --]

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
>

[-- Attachment #2: Type: text/html, Size: 1079 bytes --]

Re: [Cerowrt-devel] Names not resolved on Wireless

[David Personette]

[-- Attachment #1: Type: text/plain, Size: 959 bytes --]

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
>>
>
>

[-- Attachment #2: Type: text/html, Size: 1954 bytes --]

Re: [Cerowrt-devel] Names not resolved on Wireless

[Dave Taht]

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
>



-- 
Dave Täht

Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html

Re: [Cerowrt-devel] Names not resolved on Wireless

[Fred Stratton]

With the last three builds, there is no ipv4 connection to OS X 10.7.5 or Ubuntu 12.04.3 clients. ipv6 works, but that is not the responsibility of DNSMasq yet, IIRC. Attempts at ipv4  lease renewal fail on both clients.

Have reverted from 3.10.15-2 to 3.10.11-3 again, awaiting another build of DNSMasq.


On 10 Oct 2013, at 15:43, Dave Taht <dave.taht@gmail.com> 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
>> 
> 
> 
> 
> -- 
> Dave Täht
> 
> Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html

Re: [Cerowrt-devel] [Dnsmasq-discuss] Names not resolved on Wireless

[Dave Taht]

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

Re: [Cerowrt-devel] [Dnsmasq-discuss] Names not resolved on Wireless

[Simon Kelley]

I'm not sure that's the problem, but it's worth a try.


Another thing to do is add a a line to log if bindtodevice() in 
src/dhcp-common.c actually sets the SO_BINDTODEVICE sockopt. It's not 
supposed to even is there's currently exactly one interface, if there's 
a possibility that more will appear. This could be relevant in this 
case, but I'm not sure where the regression could come from.

Hmm, are you using --listen-address or --interface to configure dnsmasq 
to server particular interfaces? Or maybe --except-interface? Now 
there's a thought.....

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
>
>
>

Re: [Cerowrt-devel] [Dnsmasq-discuss] Names not resolved on Wireless

[Simon Kelley]

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
>
>
>

Re: [Cerowrt-devel] [Dnsmasq-discuss] Names not resolved on Wireless

[Dave Taht]

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

Re: [Cerowrt-devel] [Dnsmasq-discuss] Names not resolved on Wireless

[David Personette]

[-- Attachment #1: Type: text/plain, Size: 5751 bytes --]

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
>

[-- Attachment #2: Type: text/html, Size: 9798 bytes --]

Re: [Cerowrt-devel] [Dnsmasq-discuss] Names not resolved on Wireless

[Fred Stratton]

[-- Attachment #1: Type: text/plain, Size: 6002 bytes --]

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


[-- Attachment #2: Type: text/html, Size: 10419 bytes --]

Re: [Cerowrt-devel] [Dnsmasq-discuss] Names not resolved on Wireless

[Dave Taht]

[-- Attachment #1: Type: text/plain, Size: 6271 bytes --]

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=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
>
>

[-- Attachment #2: Type: text/html, Size: 11378 bytes --]

Re: [Cerowrt-devel] [Dnsmasq-discuss] Names not resolved on Wireless

[Simon Kelley]

On 11/10/13 15:30, Dave Taht wrote:
> 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 just pushed to git code to log at startup if dnsmasq deploys the 
SO_BINDTODEVICE hack. The compile-time and run-time dependencies to do 
that were frightening. Given that this can and has silently bitten 
people, it's good to be informed.

If you see something like

dnsmasq-dhcp: DHCP, sockets bound exclusively to interface br0

then there's a problem.


I'll try and learn how to flash the router Dave gave me so I can test 
this stuff myself.

Cheers,

Simon.

>
> 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=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
>>
>>
>

Re: [Cerowrt-devel] [Dnsmasq-discuss] Names not resolved on Wireless

[Richard E. Brown]

Simon,

> I'll try and learn how to flash the router Dave gave me so I can test this stuff myself.

For anyone interested in trying to do this at home, Dave wrote a *very* good procedure for flashing the ...xxx-squashfs-factory.img firmware via tftp at:

http://www.bufferbloat.net/projects/cerowrt/wiki/CeroWrt_flashing_instructions

As noted on that page, the tftp process always works. You'll also need:

- bent paper clip
- Ethernet cable
- tftp client on your computer
- and of course, a WNDR3700v2 or WNDR3800 router

It takes longer to read the steps than to flash the firmware. :-)

Rich Brown
Hanover, NH USA

Re: [Cerowrt-devel] [Dnsmasq-discuss] Names not resolved on Wireless

[Simon Kelley]

On 11/10/13 18:52, Richard E. Brown wrote:
> Simon,
>
>> I'll try and learn how to flash the router Dave gave me so I can test this stuff myself.
>
> For anyone interested in trying to do this at home, Dave wrote a *very* good procedure for flashing the ...xxx-squashfs-factory.img firmware via tftp at:
>
> http://www.bufferbloat.net/projects/cerowrt/wiki/CeroWrt_flashing_instructions
>
> As noted on that page, the tftp process always works. You'll also need:
>
> - bent paper clip
> - Ethernet cable
> - tftp client on your computer
> - and of course, a WNDR3700v2 or WNDR3800 router
>
> It takes longer to read the steps than to flash the firmware. :-)
>
> Rich Brown
> Hanover, NH USA
>

Indeed. Being located in a nautical, rather than office, environment I 
used a split-pin instead of a paperclip. I also had to find the firmware 
for the ethernet port in the ship's computer, which is not supported 
out-of-the-box by Ubuntu :-( That done, it went fine.

Poking around my newly flashed router, I find.

1) The dnsmasq config does indeed use --except-interface and no 
--interface statements, so the SO_BINDTODEVICE bug a talked about before 
may have caused the problem if exactly one interface is up when dnsmasq 
starts. The code I committed yesterday which logs setting 
SO_BINDTODEVICE is the final arbiter of this, but I think that bug 
should be fixed anyway. It may have been the original source of the problem.

2) This is an out-of-the-box router, I've not changed the config at all. 
I can see a single --dhcp-range, 
172.30.42.2,172.30.42.27,255.255.255.224,24h which corresponds to the 
wired interface. I can't see anything for the wireless interfaces. When 
I go to the GUI for the wireless interface, I see it has address 
172.30.42.65/26 and the DHCP service is enabled, but for start address 2 
and 26 leases. Since 2 isn't in the 64-96 range, could that be the 
problem, or am I missing something obvious?

Cheers,

Simon.

Re: [Cerowrt-devel] [Dnsmasq-discuss] Names not resolved on Wireless

[Fred Stratton]

[-- Attachment #1: Type: text/plain, Size: 7025 bytes --]

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:

> 
> 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=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


[-- Attachment #2: Type: text/html, Size: 12111 bytes --]

Re: [Cerowrt-devel] Names not resolved on Wireless

[Richard E. Brown]

Dave,

On Oct 10, 2013, at 10:43 AM, Dave Taht <dave.taht@gmail.com> wrote:

> Hot, fresh, firmware can be had at:
> 
> http://snapon.lab.bufferbloat.net/~cero2/cerowrt/wndr/

Uh oh… It looks as if 3.10.15-2 is identical to 3.10.15-3 on the download pages. 

http://snapon.lab.bufferbloat.net/~cero2/cerowrt/wndr/3.10.15-3/

I downloaded both (…15-2 and…15-3) and they're the exact same length, and the firmware that's identified as the -3 version displays "-2" in luci...

Best,

Rich

Re: [Cerowrt-devel] Names not resolved on Wireless

[Fred Stratton]

You are correct.

3.10.15-3 does not remedy the issue with wireless dhcp clients.

On 10 Oct 2013, at 19:42, Richard E. Brown wrote:

> Dave,
> 
> On Oct 10, 2013, at 10:43 AM, Dave Taht <dave.taht@gmail.com> wrote:
> 
>> Hot, fresh, firmware can be had at:
>> 
>> http://snapon.lab.bufferbloat.net/~cero2/cerowrt/wndr/
> 
> Uh oh… It looks as if 3.10.15-2 is identical to 3.10.15-3 on the download pages. 
> 
> http://snapon.lab.bufferbloat.net/~cero2/cerowrt/wndr/3.10.15-3/
> 
> I downloaded both (…15-2 and…15-3) and they're the exact same length, and the firmware that's identified as the -3 version displays "-2" in luci...
> 
> Best,
> 
> Rich
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel