Modify

Opened 5 years ago

Closed 5 years ago

Last modified 4 years ago

#13014 closed defect (fixed)

dnsmasq spam in logread about assigned nameservers..

Reported by: dani@… Owned by: developers
Priority: normal Milestone: Chaos Calmer 15.05
Component: base system Version: Trunk
Keywords: dnsmasq, dhcp Cc:

Description

hello,
just installed r35642 on a tp-link wr1043nd v1.8 and configured it for pppoe access (dual stack) and i see the logread is spammed with these like each minute..

Feb 17 18:54:55 wr1043nd daemon.info dnsmasq[1901]: reading /tmp/resolv.conf.auto
Feb 17 18:54:55 wr1043nd daemon.info dnsmasq[1901]: using nameserver 2a02:2f01:30:2:0:405:465:1#53
Feb 17 18:54:55 wr1043nd daemon.info dnsmasq[1901]: using nameserver 2a02:2f01:30:201:0:405:465:1#53
Feb 17 18:54:55 wr1043nd daemon.info dnsmasq[1901]: using nameserver 213.154.124.1#53
Feb 17 18:54:55 wr1043nd daemon.info dnsmasq[1901]: using nameserver 193.231.252.1#53
Feb 17 18:54:55 wr1043nd daemon.info dnsmasq[1901]: using nameserver 213.154.124.1#53
Feb 17 18:54:55 wr1043nd daemon.info dnsmasq[1901]: using nameserver 193.231.252.1#53
Feb 17 18:54:55 wr1043nd daemon.info dnsmasq[1901]: using local addresses only for domain lan
Feb 17 18:55:55 wr1043nd daemon.info dnsmasq[1901]: reading /tmp/resolv.conf.auto
Feb 17 18:55:55 wr1043nd daemon.info dnsmasq[1901]: using nameserver 2a02:2f01:30:2:0:405:465:1#53
Feb 17 18:55:55 wr1043nd daemon.info dnsmasq[1901]: using nameserver 2a02:2f01:30:201:0:405:465:1#53
Feb 17 18:55:55 wr1043nd daemon.info dnsmasq[1901]: using nameserver 213.154.124.1#53
Feb 17 18:55:55 wr1043nd daemon.info dnsmasq[1901]: using nameserver 193.231.252.1#53
Feb 17 18:55:55 wr1043nd daemon.info dnsmasq[1901]: using nameserver 213.154.124.1#53
Feb 17 18:55:55 wr1043nd daemon.info dnsmasq[1901]: using nameserver 193.231.252.1#53
Feb 17 18:55:55 wr1043nd daemon.info dnsmasq[1901]: using local addresses only for domain lan
Feb 17 18:56:53 wr1043nd daemon.info dnsmasq[1901]: reading /tmp/resolv.conf.auto
Feb 17 18:56:53 wr1043nd daemon.info dnsmasq[1901]: using nameserver 2a02:2f01:30:2:0:405:465:1#53
Feb 17 18:56:53 wr1043nd daemon.info dnsmasq[1901]: using nameserver 2a02:2f01:30:201:0:405:465:1#53
Feb 17 18:56:53 wr1043nd daemon.info dnsmasq[1901]: using nameserver 213.154.124.1#53
Feb 17 18:56:53 wr1043nd daemon.info dnsmasq[1901]: using nameserver 193.231.252.1#53
Feb 17 18:56:53 wr1043nd daemon.info dnsmasq[1901]: using nameserver 213.154.124.1#53
Feb 17 18:56:53 wr1043nd daemon.info dnsmasq[1901]: using nameserver 193.231.252.1#53
Feb 17 18:56:53 wr1043nd daemon.info dnsmasq[1901]: using local addresses only for domain lan

root@wr1043nd:~# cat /etc/config/dhcp
config dnsmasq

option domainneeded 1
option boguspriv 1
option filterwin2k 0 # enable for dial on demand
option localise_queries 1
option rebind_protection 1 # disable if upstream must serve RFC1918 addresses
option rebind_localhost 1 # enable for RBL checking and similar services
#list rebind_domain example.lan # whitelist RFC1918 responses for domains
option local '/lan/'
option domain 'lan'
option expandhosts 1
option nonegcache 1
option cachesize 0
option authoritative 1
option readethers 1
option leasefile '/tmp/dhcp.leases'
option resolvfile '/tmp/resolv.conf.auto'
#list server '/mycompany.local/1.2.3.4'
#option nonwildcard 1
#list interface br-lan
list notinterface 'eth0.2'
#list bogusnxdomain '64.94.110.11'

config dhcp lan

option interface lan
option start 10
option limit 250
option leasetime 72h

config dhcp wan

option interface wan
option ignore 1

Attachments (0)

Change History (7)

comment:1 Changed 5 years ago by jeff@…

Logs every 2 seconds here. See also ticket #12942 . Rebuilding a dnsmasq now with "return 0;" in my_syslog as an attempted workaround. Appears to keep log from getting spammed, though of course, it also prevents any logging to /var/log/messages.

comment:2 Changed 5 years ago by cyrus

It would be interesting to know why you get Router Advertisements from your ISP so often.
Anyway I cured the symptom with r35743.

comment:3 Changed 5 years ago by cyrus

  • Resolution set to fixed
  • Status changed from new to closed

comment:4 Changed 5 years ago by lkraav <leho@…>

I am also having this problem on AA, every ~2 minutes syslog is getting:

...
Jul 26 10:45:28 plaza-gw netifd: wan (610): Sending renew...
Jul 26 10:45:28 plaza-gw netifd: wan (610): Lease of 1.2.3.4 obtained, lease time 300
Jul 26 10:46:24 plaza-gw dnsmasq[2453]: reading /tmp/resolv.conf.auto
Jul 26 10:46:24 plaza-gw dnsmasq[2453]: using nameserver 4.3.2.1#53
Jul 26 10:46:24 plaza-gw dnsmasq[2453]: using nameserver 4.3.2.2#53
Jul 26 10:46:24 plaza-gw dnsmasq[2453]: using local addresses only for domain domain.com
Jul 26 10:47:58 plaza-gw netifd: wan (610): Sending renew...
Jul 26 10:47:58 plaza-gw netifd: wan (610): Lease of 1.2.3.4 obtained, lease time 300
Jul 26 10:48:09 plaza-gw dnsmasq[2453]: reading /tmp/resolv.conf.auto
Jul 26 10:48:09 plaza-gw dnsmasq[2453]: using nameserver 4.3.2.1#53
Jul 26 10:48:09 plaza-gw dnsmasq[2453]: using nameserver 4.3.2.2#53
Jul 26 10:48:09 plaza-gw dnsmasq[2453]: using local addresses only for domain domain.com
...

This did not come through on latest Backfire.

I'm wondering about the above changeset r35743 - is it the correct one? It seems to have no changes other than some package date and checksum.

Is there a way to stop dnsmasq from spinning wheels like this?

comment:5 Changed 4 years ago by lkraav <leho@…>

I understand now. You just specify a newer commit hash to pull.

comment:6 Changed 4 years ago by lkraav <leho@…>

Some discussion in #12649 pointed me to understand that renew can actually take place earlier than the lease expiration time and default is indeed 0.5 * T1.

But I'm not sure then why I'm still getting the logspam, even though I'm running AA release, which is much later than r35743. I'm looking at netifd commit 486aa7, it seems only about the file rotation and dnsmasq functionality still gets triggered. How does this reduce logspam?

comment:7 Changed 4 years ago by lkraav <leho@…>

Some discussion in #12649 pointed me to understand that renew can actually take place earlier than the lease expiration time and default is indeed 0.5 * T1.

But I'm not sure then why I'm still getting the logspam, even though I'm running AA release, which is much later than r35743. I'm looking at netifd commit 486aa7, it seems only about the file rotation and dnsmasq functionality still gets triggered. How does this reduce logspam?

Add Comment

Modify Ticket

Action
as closed .
The resolution will be deleted. Next status will be 'reopened'.
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.