What's new

[Beta] Asuswrt-Merlin 384.11 Beta is now available

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

Works for me. Can you try again in case the clock got changed in the middle of the traceroute?
Same thing.
traceroute2.jpg
 
upload_2019-5-2_23-57-44.png

this is when i try traceroute
 
What happens if you run it over SSH?

Code:
/usr/sbin/traceroute www.yahoo.com
Code:
/tmp/home/root# /usr/sbin/traceroute www.yahoo.com
traceroute to www.yahoo.com (72.30.35.9), 30 hops max, 60 byte packets
 1  * * *
 2  100.41.218.202 (100.41.218.202)  4.197 ms 100.41.218.204 (100.41.218.204)  3.149 ms  3.108 ms
 3  * * *
 4  * * *
 5  * 140.222.228.141 (140.222.228.141)  -1556856020648.295 ms 140.222.228.143 (140.222.228.143)  -1556856020648.415 ms
 6  152.63.26.2 (152.63.26.2)  12.195 ms 140.222.228.141 (140.222.228.141)  -1556856020650.511 ms 152.63.26.42 (152.63.26.42)  -1556856020650.725 ms
 7  204.148.47.162 (204.148.47.162)  -1556856020651.273 ms  -1556856020661.097 ms  -1556856020661.450 ms
 8  72.30.223.3 (72.30.223.3)  -1556856020740.628 ms 216.115.101.135 (216.115.101.135)  -1556856020663.900 ms  -1556856020742.735 ms
 9  74.6.227.145 (74.6.227.145)  -1556856020664.620 ms  -1556856020674.446 ms 74.6.227.149 (74.6.227.149)  -1556856020753.286 ms
10  74.6.227.147 (74.6.227.147)  -1556856020754.126 ms 74.6.122.37 (74.6.122.37)  -1556856020688.676 ms 74.6.122.59 (74.6.122.59)  -1556856020689.576 ms
11  98.137.192.151 (98.137.192.151)  -1556856020690.054 ms 98.139.128.73 (98.139.128.73)  -1556856020690.270 ms 98.139.128.71 (98.139.128.71)  -1556856020690.744 ms
12  72.30.35.9 (72.30.35.9)  -1556856020767.353 ms 98.137.192.151 (98.137.192.151)  -1556856020699.342 ms 72.30.35.9 (72.30.35.9)  -1556856020699.576 ms
/tmp/home/root#
 
Code:
/tmp/home/root# /usr/sbin/traceroute www.yahoo.com
traceroute to www.yahoo.com (72.30.35.9), 30 hops max, 60 byte packets
 1  * * *
 2  100.41.218.202 (100.41.218.202)  4.197 ms 100.41.218.204 (100.41.218.204)  3.149 ms  3.108 ms
 3  * * *
 4  * * *
 5  * 140.222.228.141 (140.222.228.141)  -1556856020648.295 ms 140.222.228.143 (140.222.228.143)  -1556856020648.415 ms
 6  152.63.26.2 (152.63.26.2)  12.195 ms 140.222.228.141 (140.222.228.141)  -1556856020650.511 ms 152.63.26.42 (152.63.26.42)  -1556856020650.725 ms
 7  204.148.47.162 (204.148.47.162)  -1556856020651.273 ms  -1556856020661.097 ms  -1556856020661.450 ms
 8  72.30.223.3 (72.30.223.3)  -1556856020740.628 ms 216.115.101.135 (216.115.101.135)  -1556856020663.900 ms  -1556856020742.735 ms
 9  74.6.227.145 (74.6.227.145)  -1556856020664.620 ms  -1556856020674.446 ms 74.6.227.149 (74.6.227.149)  -1556856020753.286 ms
10  74.6.227.147 (74.6.227.147)  -1556856020754.126 ms 74.6.122.37 (74.6.122.37)  -1556856020688.676 ms 74.6.122.59 (74.6.122.59)  -1556856020689.576 ms
11  98.137.192.151 (98.137.192.151)  -1556856020690.054 ms 98.139.128.73 (98.139.128.73)  -1556856020690.270 ms 98.139.128.71 (98.139.128.71)  -1556856020690.744 ms
12  72.30.35.9 (72.30.35.9)  -1556856020767.353 ms 98.137.192.151 (98.137.192.151)  -1556856020699.342 ms 72.30.35.9 (72.30.35.9)  -1556856020699.576 ms
gildo@RT-AC68P-4738:/tmp/home/root#

there has to be something behind the scenes causing this conflict -- do you have any scripts running? did you try factory reset?
 
Every time I try to enable the local ntp, regardless of how I have the intercept flag set, I get an ntpd stopped in the logs. In rebooting the router I do see the below log, which is then filled by a stop shortly after.

May 2 22:31:56 ntp: Initial clock set
May 2 22:31:56 rc_service: ntpd_synced 8052:notify_rc restart_stubby
May 2 22:31:56 rc_service: waitting "stop_ntpd" via wanduck ..
 
there has to be something behind the scenes causing this conflict -- do you have any scripts running? did you try factory reset?
It seems DNSFilter Global to router is causing it, when enabled the problem appears. Can you try if you have beta 2?
 
Code:
/tmp/home/root# /usr/sbin/traceroute www.yahoo.com
traceroute to www.yahoo.com (72.30.35.9), 30 hops max, 60 byte packets
 1  * * *
 2  100.41.218.202 (100.41.218.202)  4.197 ms 100.41.218.204 (100.41.218.204)  3.149 ms  3.108 ms
 3  * * *
 4  * * *
 5  * 140.222.228.141 (140.222.228.141)  -1556856020648.295 ms 140.222.228.143 (140.222.228.143)  -1556856020648.415 ms
 6  152.63.26.2 (152.63.26.2)  12.195 ms 140.222.228.141 (140.222.228.141)  -1556856020650.511 ms 152.63.26.42 (152.63.26.42)  -1556856020650.725 ms
 7  204.148.47.162 (204.148.47.162)  -1556856020651.273 ms  -1556856020661.097 ms  -1556856020661.450 ms
 8  72.30.223.3 (72.30.223.3)  -1556856020740.628 ms 216.115.101.135 (216.115.101.135)  -1556856020663.900 ms  -1556856020742.735 ms
 9  74.6.227.145 (74.6.227.145)  -1556856020664.620 ms  -1556856020674.446 ms 74.6.227.149 (74.6.227.149)  -1556856020753.286 ms
10  74.6.227.147 (74.6.227.147)  -1556856020754.126 ms 74.6.122.37 (74.6.122.37)  -1556856020688.676 ms 74.6.122.59 (74.6.122.59)  -1556856020689.576 ms
11  98.137.192.151 (98.137.192.151)  -1556856020690.054 ms 98.139.128.73 (98.139.128.73)  -1556856020690.270 ms 98.139.128.71 (98.139.128.71)  -1556856020690.744 ms
12  72.30.35.9 (72.30.35.9)  -1556856020767.353 ms 98.137.192.151 (98.137.192.151)  -1556856020699.342 ms 72.30.35.9 (72.30.35.9)  -1556856020699.576 ms
/tmp/home/root#

I have never seen traceroute returns such weird values (and this is an actual full-featured traceroute command, not just a cutdown Busybox applet).

Do you have REALLY high latency? Otherwise, since the issue happens after the second hop, I can only think that something at your ISP level is messing with ICMP packets.
 
It seems DNSFilter Global to router is causing it, when enabled the problem appears. Can you try if you have beta 2?
yea mine is set to router but i am not experiencing these issues.
 
enabling local NTP server broke those thing for me
Local NTP server/intercept are enabled on mine also. For now, disabling DNSFilter global to router seems to fix the issue. Maybe, ntpd is also in the mix lets see if Merlin finds something.;)
 
Hmmm.. seeing this traceroute stuff I decided to test some things out. I have DoT enabled with Cloudflare and DNSSEC enabled (strict). When running a traceroute command on the router or Windows command prompt, I always see this in the system.log:

Code:
May  2 23:26:29 dnsmasq[1117]: Insecure DS reply received for 126.100.in-addr.arpa, could be bad domain configuration or lack of DNSSEC support from upstream DNS servers
May  2 23:26:29 dnsmasq[1117]: Insecure DS reply received for 126.100.in-addr.arpa, could be bad domain configuration or lack of DNSSEC support from upstream DNS servers

I guess this explains why: https://dnssec-debugger.verisignlabs.com/ shows:
No DS records found for 126.100.in-addr.arpa in the 100.in-addr.arpa zone
No DNSKEY records found
No NSEC records in response
No RRSIGs found

Also, during this, I noticed a traceroute command on the router would never reach my website markheadrick.com; however, it would doing it from Windows. Are these using different protocols or something?
 

Latest threads

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top