|
osdir.com mailing list archive |
|
Subject: Re: Possible instability of DNS in 2.45 - msg#00052List: network.dns.dnsmasq.general> After running fine for over a week, my router with dnsmasq 2.45 became > very unwilling to answer DNS queries (only a few succeeded). Dumping > the statistics showed that a significant number of upstream queries > had failed. Restarting the router solved the problem. You might also consider restarting only dnsmaaq instead of entire router. (to see if the restart of dnsmasq helps or something else has to be restarted ...) Regards, David Thread at a glance:
Previous Message by Date: click to view message previewRe: Possible instability of DNS in 2.45Rune Kock wrote: > After running fine for over a week, my router with dnsmasq 2.45 became > very unwilling to answer DNS queries (only a few succeeded). Dumping > the statistics showed that a significant number of upstream queries > had failed. Restarting the router solved the problem. > > I realise that this is an incredibly useless bug-report. I'm not even > sure that it is a dnsmasq problem. So please, Simon, don't waste your > time on this yet. I'm only posting this to find out if anyone else > has experienced something similar. > > I have now enabled log-queries, and I hope that it will tell me what > happens, should the problem reappear. I'll report back when I know > more, but as the problem seems to be infrequent, it may take a long > time. Thanks for that: if you see that problem again, running strace -p <process-id of dnsmasq> for a couple of minutes and saving the results may be useful, it will give information helpful in tracing any problems with the port-randomisation code. Cheers, Simon. > > > > Rune > > _______________________________________________ > Dnsmasq-discuss mailing list > Dnsmasq-discuss-YFzxfK+dQ3ZKxzGo0kwUX62ZND6+EDdj@xxxxxxxxxxxxxxxx > http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss > Next Message by Date: click to view message previewRe: Conditional sending of different DHCP-OptionsHi ! Simon Kelley wrote: >>>> Then (stage2) uboot.0 is started an request IP + bootoptions via DHCP. >>>> The vendor class is "DBOX2, EMPTY" (obtained via tcpdump/wireshark) >>>> , so >>>> the line >>>> dhcp-vendorclass=dbox2-kernel,DBOX2 >>>> should match. >>> >>> dnsmasq logs the vendor-class when log-dhcp is on, and it's not doing so >>> here, so the vendor class is not being picked up. That's enough to >>> explain the problems you are having. Could you send me a dump of the >>> packet which has the vendor-class ID in it, so I can check what's >>> happening? >> >> I see. Have a look at http://[...] please. > Got it, thanks. > > The obvious thing there is that the DHCP packets from the client are > subtly wrong, they are messing the "end" option. I think that this is > interacting with a bug in dnsmasq which means that the last option in > the packet does not get recognised. Normally this is the "end" option, > so it doesn't matter, but in this case it's the vendor-class option, so > that is being missed. > > Can you easily upgrade dnsmasq to version 2.45, the latest? I believe > that this bug was fixed in 2.43 and just doing the upgrade should fix > the problem. Upgrading to 2.45 fixes this problem. Thanks. cya Previous Message by Thread: click to view message previewRe: Possible instability of DNS in 2.45Rune Kock wrote: > After running fine for over a week, my router with dnsmasq 2.45 became > very unwilling to answer DNS queries (only a few succeeded). Dumping > the statistics showed that a significant number of upstream queries > had failed. Restarting the router solved the problem. > > I realise that this is an incredibly useless bug-report. I'm not even > sure that it is a dnsmasq problem. So please, Simon, don't waste your > time on this yet. I'm only posting this to find out if anyone else > has experienced something similar. > > I have now enabled log-queries, and I hope that it will tell me what > happens, should the problem reappear. I'll report back when I know > more, but as the problem seems to be infrequent, it may take a long > time. Thanks for that: if you see that problem again, running strace -p <process-id of dnsmasq> for a couple of minutes and saving the results may be useful, it will give information helpful in tracing any problems with the port-randomisation code. Cheers, Simon. > > > > Rune > > _______________________________________________ > Dnsmasq-discuss mailing list > Dnsmasq-discuss-YFzxfK+dQ3ZKxzGo0kwUX62ZND6+EDdj@xxxxxxxxxxxxxxxx > http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss > Next Message by Thread: click to view message previewRe: Possible instability of DNS in 2.45On Wed, Aug 13, 2008 at 02:30, Rune Kock <rune.kock-Re5JQEeQqe8AvxtiuMwx3w@xxxxxxxxxxxxxxxx> wrote: > After running fine for over a week, my router with dnsmasq 2.45 became > very unwilling to answer DNS queries (only a few succeeded). Dumping > the statistics showed that a significant number of upstream queries > had failed. Restarting the router solved the problem. Thanks for the bug-hunting ideas, Simon and David. It turns out that my remote logging was horribly broken. (I wasn't aware that the machine receiving the log-entries would do a reverse dns-lookup to the router for every entry received -- and on the router I had enabled logging of all incoming connections!). With this kind of craziness going on, it seems very unlikely that dnsmasq was the cause of the problems. Really, what puzzles me the most is that things did actually work for some time. So my apologies for wasting your time. I have fixed the logging, and everything seems to be running perfectly now. Rune Loading Comments...
|
|
