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 <[email protected]> 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<[email protected]>
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<[email protected]>
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<[email protected]>
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
[email protected]
https://lists.bufferbloat.net/listinfo/cerowrt-devel
_______________________________________________
Cerowrt-devel mailing list
[email protected]
https://lists.bufferbloat.net/listinfo/cerowrt-devel
_______________________________________________
Dnsmasq-discuss mailing list
[email protected]
http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
_______________________________________________
Cerowrt-devel mailing list
[email protected]
https://lists.bufferbloat.net/listinfo/cerowrt-devel
