1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.
Dismiss Notice

Welcome To SNBForums

SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.

If you'd like to post a question, simply register and have at it!

While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!

Asus RT -Ac 58U after upgrade to firmware:3.0.0.4.382_51939

Discussion in 'ASUSWRT - Official' started by adam1, Jan 19, 2020.

Tags:
  1. adam1

    adam1 New Around Here

    Joined:
    Jan 19, 2020
    Messages:
    5
    Hello and welcome. I am new and my knowledge in this subject is small
    From several days I have had the same error in loop. looks below

    Jan 19 17:24:37 dnsmasq[14322]: Maximum number of concurrent DNS queries reached (max: 150)
    Jan 19 17:24:43 dnsmasq[14322]: Maximum number of concurrent DNS queries reached (max: 150)
    Jan 19 17:24:53 dnsmasq[14322]: Maximum number of concurrent DNS queries reached (max: 150)
    Jan 19 17:24:59 dnsmasq[14322]: Maximum number of concurrent DNS queries reached (max: 150)
    Jan 19 17:25:06 dnsmasq[14322]: Maximum number of concurrent DNS queries reached (max: 150)
    Jan 19 17:25:12 dnsmasq[14322]: Maximum number of concurrent DNS queries reached (max: 150)
    Jan 19 17:25:30 dnsmasq[14322]: Maximum number of concurrent DNS queries reached (max: 150)
    Jan 19 17:26:00 dnsmasq[14322]: Maximum number of concurrent DNS queries reached (max: 150)
    Jan 19 17:26:06 dnsmasq[14322]: Maximum number of concurrent DNS queries reached (max: 150)
    Jan 19 17:26:13 dnsmasq[14322]: Maximum number of concurrent DNS queries reached (max: 150)
    Jan 19 17:26:27 dnsmasq[14322]: Maximum number of concurrent DNS queries reached (max: 150)
    Jan 19 17:26:34 dnsmasq[14322]: Maximum number of concurrent DNS queries reached (max: 150)
    Jan 19 17:26:48 dnsmasq[14322]: Maximum number of concurrent DNS queries reached (max: 150)
    Jan 19 17:26:54 dnsmasq[14322]: Maximum number of concurrent DNS queries reached (max: 150)
    Jan 19 17:27:03 dnsmasq[14322]: Maximum number of concurrent DNS queries reached (max: 150)
    Jan 19 17:27:09 dnsmasq[14322]: Maximum number of concurrent DNS queries reached (max: 150)
    Jan 19 17:27:15 dnsmasq[14322]: Maximum number of concurrent DNS queries reached (max: 150)
    Jan 19 17:27:41 dnsmasq[14322]: Maximum number of concurrent DNS queries reached (max: 150)
    Jan 19 17:27:54 dnsmasq[14322]: Maximum number of concurrent DNS queries reached (max: 150)
    Jan 19 17:28:14 dnsmasq[14322]: Maximum number of concurrent DNS queries reached (max: 150)
    Jan 19 17:29:00 dnsmasq[14322]: Maximum number of concurrent DNS queries reached (max: 150)
    Jan 19 17:29:12 dnsmasq[14322]: Maximum number of concurrent DNS queries reached (max: 150)
    Jan 19 17:29:18 dnsmasq[14322]: Maximum number of concurrent DNS queries reached (max: 150)
    Jan 19 17:29:24 dnsmasq[14322]: Maximum number of concurrent DNS queries reached (max: 150)
    Jan 19 17:29:30 dnsmasq[14322]: Maximum number of concurrent DNS queries reached (max: 150)
    Jan 19 17:29:37 dnsmasq[14322]: Maximum number of concurrent DNS queries reached (max: 150)
    Jan 19 17:29:46 dnsmasq[14322]: Maximum number of concurrent DNS queries reached (max: 150)
    Jan 19 17:30:00 dnsmasq[14322]: Maximum number of concurrent DNS queries reached (max: 150)
    Jan 19 17:30:06 dnsmasq[14322]: Maximum number of concurrent DNS queries reached (max: 150)
    Jan 19 17:30:12 dnsmasq[14322]: Maximum number of concurrent DNS queries reached (max: 150)
    Jan 19 17:30:18 dnsmasq[14322]: Maximum number of concurrent DNS queries reached (max: 150)
    Jan 19 17:30:24 dnsmasq[14322]: Maximum number of concurrent DNS queries reached (max: 150)
    Jan 19 17:30:33 dnsmasq[14322]: Maximum number of concurrent DNS queries reached (max: 150)
    Jan 19 17:30:39 dnsmasq[14322]: Maximum number of concurrent DNS queries reached (max: 150)
    Jan 19 17:30:45 dnsmasq[14322]: Maximum number of concurrent DNS queries reached (max: 150)
    Jan 19 17:30:51 dnsmasq[14322]: Maximum number of concurrent DNS queries reached (max: 150)
    Jan 19 17:31:04 dnsmasq[14322]: Maximum number of concurrent DNS queries reached (max: 150)
    Jan 19 17:31:10 dnsmasq[14322]: Maximum number of concurrent DNS queries reached (max: 150)
    Jan 19 17:31:16 dnsmasq[14322]: Maximum number of concurrent DNS queries reached (max: 150)
    Jan 19 17:31:22 dnsmasq[14322]: Maximum number of concurrent DNS queries reached (max: 150)
    Jan 19 17:31:28 dnsmasq[14322]: Maximum number of concurrent DNS queries reached (max: 150)

    Dnsmasq.conf file looks

    [email protected]:/tmp/etc# cat dnsmasq.conf
    pid-file=/var/run/dnsmasq.pid
    user=admin2
    bind-dynamic
    interface=br0
    interface=pptp*
    no-dhcp-interface=pptp*
    no-resolv
    servers-file=/tmp/resolv.dnsmasq
    no-poll
    no-negcache
    cache-size=1500
    min-port=4096
    dhcp-range=lan,192.168.1.2,192.168.1.254,255.255.255.0,86400s
    dhcp-option=lan,3,192.168.1.1
    dhcp-option=lan,252,"\n"
    dhcp-authoritative
    address=/findasus.local/192.168.1.1
    [email protected]:/tmp/etc#

    I need Help, what should I do?
     
  2. EmeraldDeer

    EmeraldDeer Very Senior Member

    Joined:
    Dec 22, 2017
    Messages:
    601
    Location:
    Massachusetts
    Is there a way to modify dnsmasq.conf on stock firmware?

    I would change to this:
    cache-size=2500

    I would delete this:
    no-negcache
     
    adam1 likes this.
  3. RMerlin

    RMerlin Super Moderator

    Joined:
    Apr 14, 2012
    Messages:
    32,159
    Location:
    Canada
    No.

    That error has nothing to do with caching. In fact when a few of us tested this a few years ago, nobody ever reported an instance where the 1500 entries cache was too small.

    This error indicates that something on his network is trying to generate over 150 *concurrent* dns queries. Could be a misbehaving client, could be a problem with the upstream DNS causing requests to pile up, could be a software generating an abnormal number of concurrent requests (web server log analyzer doing reverse lookups, for example).
     
    adam1 likes this.
  4. EmeraldDeer

    EmeraldDeer Very Senior Member

    Joined:
    Dec 22, 2017
    Messages:
    601
    Location:
    Massachusetts
    I agree, but to really get to the bottom of this, one would need to tcpdump on the router filtering for DNS, transfer the capture file, bring it up in something like Wireshark and analyze the output. Stock firmware probably does not provide a way to tcpdump.
     
    adam1 likes this.
  5. RMerlin

    RMerlin Super Moderator

    Joined:
    Apr 14, 2012
    Messages:
    32,159
    Location:
    Canada
    No need for that. Just stop dnsmasq, enable query logging, and manually launch dnsmasq.
     
    adam1 and L&LD like this.
  6. adam1

    adam1 New Around Here

    Joined:
    Jan 19, 2020
    Messages:
    5
    I changed cache-size=2500 with diffrent values and nothing solved the problem
    The same with add dns-forward-max=<queries>
    "
    Just stop dnsmasq, enable query logging, and manually launch dnsmasq"

    IT sound interesting but how to stop dsnmasq and enable query logging? Do somebody write commands, please?
     
  7. EmeraldDeer

    EmeraldDeer Very Senior Member

    Joined:
    Dec 22, 2017
    Messages:
    601
    Location:
    Massachusetts
    My guess is:

    Add the following lines to /etc/dnsmasq.conf:
    Code:
    log-async=25
    log-queries=extra
    log-facility=/opt/var/log/dnsmasq.log
    
    Restart dnsmasq:
    Code:
    service restart_dnsmasq
    
     
    adam1 likes this.
  8. ColinTaylor

    ColinTaylor Part of the Furniture

    Joined:
    Mar 31, 2014
    Messages:
    10,688
    Location:
    UK
    Or you could just disconnect each of your clients one by one until you find the device that is spamming the DNS server.
     
    adam1 likes this.
  9. RMerlin

    RMerlin Super Moderator

    Joined:
    Apr 14, 2012
    Messages:
    32,159
    Location:
    Canada
    That will cause the firmware to overwrite it. You have to manually kill it (killall dnsmasq), then run it (dnsmasq --log-async).
     
    adam1 likes this.
  10. adam1

    adam1 New Around Here

    Joined:
    Jan 19, 2020
    Messages:
    5
    First I used
    [email protected]:/tmp/etc# killall dnsmasq
    [email protected]:/tmp/etc# dnsmasq --log-async

    Replay from log
    Jan 20 16:41:02 rc_service: service 5573:notify_rc restart_dnsmasq
    Jan 20 16:41:02 dnsmasq[5576]: Maximum number of concurrent DNS queries reached (max: 150)
    Jan 20 16:41:08 dnsmasq[5576]: Maximum number of concurrent DNS queries reached (max: 150)
    Jan 20 16:42:06 dnsmasq[5576]: Maximum number of concurrent DNS queries reached (max: 150)
    Jan 20 16:42:54 dnsmasq[5576]: Maximum number of concurrent DNS queries reached (max: 150)


    Then I read dsnmasq.conf

    [email protected]:/tmp/etc# cat dnsmasq.conf
    pid-file=/var/run/dnsmasq.pid
    user=admin2
    bind-dynamic
    interface=br0
    interface=pptp*
    no-dhcp-interface=pptp*
    no-resolv
    servers-file=/tmp/resolv.dnsmasq
    no-poll
    no-negcache
    cache-size=1500
    min-port=4096
    dhcp-range=lan,192.168.1.2,192.168.1.254,255.255.255.0,86400s
    dhcp-option=lan,3,192.168.1.1
    dhcp-option=lan,252,"\n"
    dhcp-authoritative
    address=/findasus.local/192.168.1.1
    [email protected]:/tmp/etc#

    and add lines


    [email protected]:/tmp/etc# vi dnsmasq.conf
    pid-file=/var/run/dnsmasq.pid
    user=admin2
    bind-dynamic
    interface=br0
    interface=pptp*
    no-dhcp-interface=pptp*
    no-resolv
    servers-file=/tmp/resolv.dnsmasq
    no-poll
    no-negcache
    cache-size=1500
    min-port=4096
    dhcp-range=lan,192.168.1.2,192.168.1.254,255.255.255.0,86400s
    dhcp-option=lan,3,192.168.1.1
    dhcp-option=lan,252,"\n"
    dhcp-authoritative
    address=/findasus.local/192.168.1.1
    log-async=25
    log-queries=extra
    log-facility=/opt/var/log/dnsmasq.log
    ~
    ~
    esc
    :wq
    and restart

    [email protected]:/tmp/etc# service restart_dnsmasq
    Done.

    and the same like above

    Did I use correctly the commands?

    Why after save dnsmasq.conf with new lines and restart it the File has the same settings and lines. Should it have got a new lines? I suppose "yes
     
    Last edited: Jan 20, 2020
  11. adam1

    adam1 New Around Here

    Joined:
    Jan 19, 2020
    Messages:
    5
    OK I used command
    dnsmasq --no-daemon --log-queries --log-facility=/var/log/dnsmasq.log
    and I know just now, what device is spamming:D
    Now I have to blocked it

    Amazing, it stopped completely.
    I have nothing replay in log but router it is often lose connection

    I need to test it yet

    Where do I find the logs files for the router and all run daemons ?
     
    Last edited: Jan 20, 2020
    maxbraketorque likes this.
  12. adam1

    adam1 New Around Here

    Joined:
    Jan 19, 2020
    Messages:
    5
    Thank you all for help me. You are amazing and great.:)
    Issue is solved