You are not logged in.

#26 2013-04-30 21:10:54

ub1quit33
Member
Registered: 2013-04-30
Posts: 58

Re: DNS problem - lookup latency

DNS only uses TCP for AXFER (typically server to server only)... Typical DNS queries are done over UDP. So a tcpdump on port 53 is not likely to produce anything useful.

matone wrote:

you should check with tcpdump what's going on.
run on a shell:

sudo tcpdump -i eth0 port 53

and then in another one query a bunch of dns servers and see what happen on the net.

Offline

#27 2013-04-30 21:16:32

matone
Member
Registered: 2012-06-25
Posts: 7

Re: DNS problem - lookup latency

thanks for the explanation but tcpdump by default shows both tcp and udp connections. Don't get fooled by the name.

 man tcpdump 

Offline

#28 2013-04-30 21:22:26

ub1quit33
Member
Registered: 2013-04-30
Posts: 58

Re: DNS problem - lookup latency

matone wrote:

thanks for the explanation but tcpdump by default shows both tcp and udp connections. Don't get fooled by the name.

 man tcpdump 

Touche! That'll teach me to comment on tools I haven't used smile

Offline

#29 2013-05-01 18:27:53

5ulo
Member
From: Slovakia
Registered: 2012-05-04
Posts: 77

Re: DNS problem - lookup latency

PING one by one

enjoy@arch ~ $ ping -c 5 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=43 time=19.0 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=43 time=18.8 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=43 time=18.6 ms
64 bytes from 8.8.8.8: icmp_seq=4 ttl=43 time=18.9 ms
64 bytes from 8.8.8.8: icmp_seq=5 ttl=43 time=19.2 ms

--- 8.8.8.8 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4006ms
rtt min/avg/max/mdev = 18.696/18.972/19.256/0.253 ms
enjoy@arch ~ $ ping -c 5 8.8.4.4
PING 8.8.4.4 (8.8.4.4) 56(84) bytes of data.

--- 8.8.4.4 ping statistics ---
5 packets transmitted, 0 received, 100% packet loss, time 3999ms

enjoy@arch ~ $ ping -c 5 8.8.4.4
PING 8.8.4.4 (8.8.4.4) 56(84) bytes of data.

--- 8.8.4.4 ping statistics ---
5 packets transmitted, 0 received, 100% packet loss, time 4007ms

enjoy@arch ~ $ ping -c 5 8.8.4.4
PING 8.8.4.4 (8.8.4.4) 56(84) bytes of data.
64 bytes from 8.8.4.4: icmp_seq=1 ttl=43 time=19.0 ms
64 bytes from 8.8.4.4: icmp_seq=2 ttl=43 time=18.6 ms
64 bytes from 8.8.4.4: icmp_seq=3 ttl=43 time=18.9 ms
64 bytes from 8.8.4.4: icmp_seq=4 ttl=43 time=19.0 ms
64 bytes from 8.8.4.4: icmp_seq=5 ttl=43 time=19.2 ms

--- 8.8.4.4 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4005ms
rtt min/avg/max/mdev = 18.661/18.998/19.249/0.228 ms

enjoy@arch ~ $ ping -c 5 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.

--- 8.8.8.8 ping statistics ---
5 packets transmitted, 0 received, 100% packet loss, time 3999ms

8.8.8.8 successfull, 8.8.4.4 two times timeout and then 8.8.8.8 timeout.. wtf?

enjoy@arch ~ $ ip -s link show eth0
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT qlen 1000
    link/ether aa:bb:cc:dd:ee:ff brd ff:ff:ff:ff:ff:ff
    RX: bytes  packets  errors  dropped overrun mcast   
    2563502    5186     0       0       0       0      
    TX: bytes  packets  errors  dropped carrier collsns 
    1047827    6808     0       0       0       0    

Last edited by 5ulo (2013-05-01 18:29:13)

Offline

#30 2013-05-01 23:18:46

ub1quit33
Member
Registered: 2013-04-30
Posts: 58

Re: DNS problem - lookup latency

Let's get some traceroutes to those IPs.
If you haven't already, grab traceroute.

# pacman -S traceroute

Then run a few traceroutes to those IPs to see if you get differing results as you did with ping.

$ i=0; while [[ $i -lt 3 ]]; do traceroute 8.8.8.8; (( i++ )); done
$ i=0; while [[ $i -lt 3 ]]; do traceroute 8.8.4.4; (( i++ )); done

What are you using for interface management? netctl? wicd? NetworkManager? Something else?

Last edited by ub1quit33 (2013-05-01 23:19:55)

Offline

#31 2013-05-02 08:06:36

scar
Member
From: Hungary
Registered: 2009-10-01
Posts: 411

Re: DNS problem - lookup latency

Do you have iperf on your router?
Try to test your raw troughput power first...
You can try tcp and udp separately.

Last edited by scar (2013-05-02 08:06:49)


“The future has already arrived. It's just not evenly distributed yet.”
― William Gibson

Offline

#32 2013-05-02 10:22:48

5ulo
Member
From: Slovakia
Registered: 2012-05-04
Posts: 77

Re: DNS problem - lookup latency

I'm using NetworkManager.
tracert on wlan0

enjoy@arch ~ $ i=0; while [[ $i -lt 3 ]]; do traceroute 8.8.8.8; (( i++ )); done
traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets
 1  192.168.1.1 (192.168.1.1)  0.914 ms  1.594 ms  1.584 ms
 2  ttxc129.ttx-net.sk (62.197.206.129)  3.836 ms  3.850 ms  3.848 ms
 3  ttx00.ttx-net.sk (193.110.186.1)  3.844 ms  3.840 ms  3.831 ms
 4  217.75.70.4 (217.75.70.4)  5.125 ms  5.142 ms  6.368 ms
 5  xe3.inet-ba-interoute-gw1.swan.sk (217.75.72.30)  6.381 ms  6.387 ms  6.379 ms
 6  xe-5-2-0-0.bts-001-score-1-re0.interoute.net (89.202.153.121)  74.198 ms  71.969 ms  71.850 ms
 7  ae0-0.bts-001-score-2-re1.interoute.net (84.233.147.2)  20.853 ms  19.438 ms  19.344 ms
 8  ae1-0.bud-001-score-2-re0.interoute.net (84.233.147.113)  19.723 ms  19.722 ms  19.717 ms
 9  ae0-0.bud-001-score-1-re0.interoute.net (84.233.147.109)  19.708 ms  19.699 ms  19.687 ms
10  74.125.50.125 (74.125.50.125)  290.362 ms  290.396 ms  290.384 ms
11  209.85.243.121 (209.85.243.121)  228.706 ms  228.745 ms  233.139 ms
12  72.14.234.11 (72.14.234.11)  20.077 ms 209.85.241.212 (209.85.241.212)  55.992 ms 72.14.234.11 (72.14.234.11)  20.077 ms
13  209.85.254.116 (209.85.254.116)  233.038 ms  231.644 ms  232.332 ms
14  * * *
15  google-public-dns-a.google.com (8.8.8.8)  22.067 ms  22.049 ms  22.059 ms
traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets
 1  192.168.1.1 (192.168.1.1)  1.296 ms  1.255 ms  2.037 ms
 2  ttxc129.ttx-net.sk (62.197.206.129)  4.159 ms  4.181 ms  4.197 ms
 3  ttx00.ttx-net.sk (193.110.186.1)  4.199 ms  4.208 ms  4.211 ms
 4  217.75.70.4 (217.75.70.4)  4.215 ms  5.375 ms  5.372 ms
 5  xe3.inet-ba-interoute-gw1.swan.sk (217.75.72.30)  5.359 ms  5.355 ms  5.351 ms
 6  xe-5-2-0-0.bts-001-score-1-re0.interoute.net (89.202.153.121)  22.340 ms  19.114 ms  18.983 ms
 7  ae0-0.bts-001-score-2-re1.interoute.net (84.233.147.2)  20.431 ms  19.572 ms  19.669 ms
 8  ae1-0.bud-001-score-2-re0.interoute.net (84.233.147.113)  19.587 ms  19.579 ms  19.564 ms
 9  ae0-0.bud-001-score-1-re0.interoute.net (84.233.147.109)  19.551 ms  19.544 ms  19.066 ms
10  74.125.50.125 (74.125.50.125)  305.813 ms  305.834 ms  305.845 ms
11  209.85.243.121 (209.85.243.121)  233.496 ms  218.093 ms  219.263 ms
12  72.14.234.11 (72.14.234.11)  20.784 ms  32.929 ms  32.933 ms
13  209.85.254.116 (209.85.254.116)  217.900 ms 209.85.254.112 (209.85.254.112)  19.094 ms 209.85.254.116 (209.85.254.116)  218.774 ms
14  * * *
15  google-public-dns-a.google.com (8.8.8.8)  20.315 ms  19.836 ms  19.289 ms
traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets
 1  192.168.1.1 (192.168.1.1)  1.145 ms  1.105 ms  2.166 ms
 2  ttxc129.ttx-net.sk (62.197.206.129)  3.955 ms  3.967 ms  3.944 ms
 3  ttx00.ttx-net.sk (193.110.186.1)  3.929 ms  3.922 ms  3.926 ms
 4  217.75.70.4 (217.75.70.4)  4.786 ms  4.789 ms  5.828 ms
 5  xe3.inet-ba-interoute-gw1.swan.sk (217.75.72.30)  6.356 ms  6.363 ms  6.352 ms
 6  xe-5-2-0-0.bts-001-score-1-re0.interoute.net (89.202.153.121)  22.941 ms  19.899 ms  19.840 ms
 7  ae0-0.bts-001-score-2-re1.interoute.net (84.233.147.2)  19.735 ms  19.120 ms  18.914 ms
 8  ae1-0.bud-001-score-2-re0.interoute.net (84.233.147.113)  19.518 ms  22.812 ms  20.338 ms
 9  ae0-0.bud-001-score-1-re0.interoute.net (84.233.147.109)  20.216 ms  19.751 ms  19.717 ms
10  74.125.50.125 (74.125.50.125)  270.042 ms  269.166 ms  269.032 ms
11  209.85.243.121 (209.85.243.121)  218.725 ms 209.85.243.119 (209.85.243.119)  20.761 ms 209.85.243.121 (209.85.243.121)  221.567 ms
12  72.14.234.11 (72.14.234.11)  20.570 ms 209.85.241.212 (209.85.241.212)  39.054 ms 72.14.234.11 (72.14.234.11)  20.171 ms
13  209.85.254.112 (209.85.254.112)  20.651 ms 209.85.254.116 (209.85.254.116)  222.459 ms  222.278 ms
14  * * *
15  google-public-dns-a.google.com (8.8.8.8)  19.379 ms  20.050 ms  19.994 ms
enjoy@arch ~ $ i=0; while [[ $i -lt 3 ]]; do traceroute 8.8.4.4; (( i++ )); done
traceroute to 8.8.4.4 (8.8.4.4), 30 hops max, 60 byte packets
 1  192.168.1.1 (192.168.1.1)  2.503 ms  2.519 ms  2.527 ms
 2  ttxc129.ttx-net.sk (62.197.206.129)  2.533 ms  2.536 ms  2.540 ms
 3  ttx00.ttx-net.sk (193.110.186.1)  5.313 ms  5.341 ms  5.353 ms
 4  217.75.70.4 (217.75.70.4)  5.359 ms  5.366 ms  5.381 ms
 5  xe3.inet-ba-interoute-gw1.swan.sk (217.75.72.30)  5.394 ms  5.406 ms  5.418 ms
 6  xe-5-2-0-0.bts-001-score-1-re0.interoute.net (89.202.153.121)  86.695 ms  82.479 ms  84.256 ms
 7  ae0-0.bts-001-score-2-re1.interoute.net (84.233.147.2)  19.646 ms  19.698 ms  19.638 ms
 8  ae1-0.bud-001-score-2-re0.interoute.net (84.233.147.113)  27.410 ms  26.622 ms  25.591 ms
 9  ae0-0.bud-001-score-1-re0.interoute.net (84.233.147.109)  19.452 ms  19.474 ms  19.469 ms
10  74.125.50.125 (74.125.50.125)  297.188 ms  297.197 ms  297.189 ms
11  209.85.243.119 (209.85.243.119)  20.170 ms  19.730 ms  32.051 ms
12  209.85.241.212 (209.85.241.212)  22.051 ms 72.14.234.11 (72.14.234.11)  20.573 ms  20.524 ms
13  209.85.254.116 (209.85.254.116)  271.381 ms  270.647 ms 209.85.254.112 (209.85.254.112)  19.372 ms
14  * * *
15  google-public-dns-b.google.com (8.8.4.4)  20.493 ms  20.480 ms  20.443 ms
traceroute to 8.8.4.4 (8.8.4.4), 30 hops max, 60 byte packets
 1  192.168.1.1 (192.168.1.1)  1.003 ms  1.600 ms  1.577 ms
 2  ttxc129.ttx-net.sk (62.197.206.129)  2.950 ms  2.953 ms  2.934 ms
 3  ttx00.ttx-net.sk (193.110.186.1)  3.671 ms  3.669 ms  5.233 ms
 4  217.75.70.4 (217.75.70.4)  5.247 ms  5.233 ms  5.215 ms
 5  xe3.inet-ba-interoute-gw1.swan.sk (217.75.72.30)  7.944 ms  7.959 ms  7.942 ms
 6  xe-5-2-0-0.bts-001-score-1-re0.interoute.net (89.202.153.121)  24.802 ms  21.974 ms  21.315 ms
 7  ae0-0.bts-001-score-2-re1.interoute.net (84.233.147.2)  30.295 ms  30.321 ms  26.007 ms
 8  ae1-0.bud-001-score-2-re0.interoute.net (84.233.147.113)  21.323 ms  20.782 ms  20.880 ms
 9  ae0-0.bud-001-score-1-re0.interoute.net (84.233.147.109)  19.793 ms  19.136 ms  19.102 ms
10  74.125.50.125 (74.125.50.125)  286.271 ms  285.639 ms  285.520 ms
11  209.85.243.121 (209.85.243.121)  226.443 ms 209.85.243.119 (209.85.243.119)  19.550 ms  31.327 ms
12  209.85.241.212 (209.85.241.212)  27.005 ms  27.036 ms  26.996 ms
13  209.85.254.116 (209.85.254.116)  228.657 ms 209.85.254.112 (209.85.254.112)  20.853 ms  20.775 ms
14  * * *
15  google-public-dns-b.google.com (8.8.4.4)  20.030 ms  20.047 ms  20.051 ms
traceroute to 8.8.4.4 (8.8.4.4), 30 hops max, 60 byte packets
 1  192.168.1.1 (192.168.1.1)  1.674 ms  1.661 ms  2.896 ms
 2  ttxc129.ttx-net.sk (62.197.206.129)  2.895 ms  2.884 ms  2.872 ms
 3  ttx00.ttx-net.sk (193.110.186.1)  4.088 ms  4.106 ms  4.147 ms
 4  217.75.70.4 (217.75.70.4)  4.848 ms  4.852 ms  4.843 ms
 5  xe3.inet-ba-interoute-gw1.swan.sk (217.75.72.30)  5.531 ms  5.550 ms  5.558 ms
 6  xe-5-2-0-0.bts-001-score-1-re0.interoute.net (89.202.153.121)  20.981 ms  18.882 ms  19.175 ms
 7  ae0-0.bts-001-score-2-re1.interoute.net (84.233.147.2)  19.526 ms  20.132 ms  20.173 ms
 8  ae1-0.bud-001-score-2-re0.interoute.net (84.233.147.113)  20.128 ms  20.218 ms  20.134 ms
 9  ae0-0.bud-001-score-1-re0.interoute.net (84.233.147.109)  21.214 ms  20.740 ms  20.646 ms
10  74.125.50.125 (74.125.50.125)  338.544 ms  337.540 ms  337.467 ms
11  209.85.243.121 (209.85.243.121)  259.630 ms 209.85.243.119 (209.85.243.119)  20.574 ms  19.956 ms
12  209.85.241.212 (209.85.241.212)  46.171 ms  45.699 ms 72.14.234.11 (72.14.234.11)  18.948 ms
13  209.85.254.112 (209.85.254.112)  20.012 ms 209.85.254.116 (209.85.254.116)  240.376 ms  240.207 ms
14  * * *
15  google-public-dns-b.google.com (8.8.4.4)  20.356 ms  19.549 ms  21.502 ms

tracert on eth0

enjoy@arch ~ $ i=0; while [[ $i -lt 3 ]]; do traceroute 8.8.8.8; (( i++ )); done
traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets
 1  * * *
 2  * * *
 3  * * *
 4  * * *
 5  * * *
 6  * * *
 7  * * *
 8  * * *
 9  * * *
10  * * *
11  * * *
12  * * *
13  * * *
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *
traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets
 1  192.168.1.1 (192.168.1.1)  60.123 ms  60.149 ms  60.155 ms
 2  * * *
 3  * * *
 4  * * *
 5  * * *
 6  * * *
 7  * ae0-0.bts-001-score-2-re1.interoute.net (84.233.147.2)  17.865 ms  17.895 ms
 8  ae1-0.bud-001-score-2-re0.interoute.net (84.233.147.113)  18.068 ms  18.290 ms  18.437 ms
 9  ae0-0.bud-001-score-1-re0.interoute.net (84.233.147.109)  18.064 ms  18.307 ms  18.276 ms
10  74.125.50.125 (74.125.50.125)  305.161 ms  305.606 ms  305.631 ms
11  209.85.243.119 (209.85.243.119)  19.677 ms 209.85.243.121 (209.85.243.121)  222.673 ms  222.623 ms
12  209.85.241.212 (209.85.241.212)  30.531 ms 72.14.234.11 (72.14.234.11)  21.127 ms  18.637 ms
13  209.85.254.112 (209.85.254.112)  18.606 ms 209.85.254.116 (209.85.254.116)  222.388 ms  222.372 ms
14  * * *
15  google-public-dns-a.google.com (8.8.8.8)  19.263 ms  19.009 ms  18.768 ms
traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets
 1  * * *
 2  ttxc129.ttx-net.sk (62.197.206.129)  2.508 ms  2.545 ms  2.550 ms
 3  ttx00.ttx-net.sk (193.110.186.1)  2.599 ms  2.788 ms  2.821 ms
 4  217.75.70.4 (217.75.70.4)  3.133 ms  3.182 ms  3.922 ms
 5  xe3.inet-ba-interoute-gw1.swan.sk (217.75.72.30)  4.281 ms  4.312 ms  4.316 ms
 6  xe-5-2-0-0.bts-001-score-1-re0.interoute.net (89.202.153.121)  19.471 ms  17.298 ms  17.763 ms
 7  ae0-0.bts-001-score-2-re1.interoute.net (84.233.147.2)  18.486 ms  18.479 ms  29.112 ms
 8  ae1-0.bud-001-score-2-re0.interoute.net (84.233.147.113)  18.583 ms  18.481 ms  18.667 ms
 9  ae0-0.bud-001-score-1-re0.interoute.net (84.233.147.109)  18.007 ms  17.924 ms  17.897 ms
10  74.125.50.125 (74.125.50.125)  281.996 ms  281.369 ms  281.489 ms
11  209.85.243.121 (209.85.243.121)  225.843 ms  225.789 ms  225.928 ms
12  72.14.234.11 (72.14.234.11)  19.161 ms  19.088 ms  18.702 ms
13  209.85.254.112 (209.85.254.112)  18.743 ms 209.85.254.116 (209.85.254.116)  225.455 ms 209.85.254.112 (209.85.254.112)  35.881 ms
14  * * *
15  google-public-dns-a.google.com (8.8.8.8)  19.131 ms  19.133 ms  18.149 ms
enjoy@arch ~ $ i=0; while [[ $i -lt 3 ]]; do traceroute 8.8.4.4; (( i++ )); done
traceroute to 8.8.4.4 (8.8.4.4), 30 hops max, 60 byte packets
 1  192.168.1.1 (192.168.1.1)  48.073 ms  48.092 ms  48.099 ms
 2  * * *
 3  * * *
 4  * * *
 5  * * *
 6  * * *
 7  * * *
 8  * * *
 9  * * *
10  * * *
11  * * *
12  * * *
13  * * *
14  * * *
15  * * *
16  * * *
17  * * *
18  google-public-dns-b.google.com (8.8.4.4)  18.965 ms  18.755 ms  18.717 ms
traceroute to 8.8.4.4 (8.8.4.4), 30 hops max, 60 byte packets
 1  * * *
 2  ttxc129.ttx-net.sk (62.197.206.129)  2.673 ms  2.686 ms  2.824 ms
 3  ttx00.ttx-net.sk (193.110.186.1)  2.826 ms  2.936 ms  2.931 ms
 4  217.75.70.4 (217.75.70.4)  3.986 ms  3.993 ms  4.139 ms
 5  xe3.inet-ba-interoute-gw1.swan.sk (217.75.72.30)  4.141 ms  4.797 ms  4.799 ms
 6  xe-5-2-0-0.bts-001-score-1-re0.interoute.net (89.202.153.121)  20.250 ms  17.765 ms  18.225 ms
 7  ae0-0.bts-001-score-2-re1.interoute.net (84.233.147.2)  18.682 ms  18.670 ms  19.839 ms
 8  ae1-0.bud-001-score-2-re0.interoute.net (84.233.147.113)  18.686 ms  17.777 ms  17.613 ms
 9  ae0-0.bud-001-score-1-re0.interoute.net (84.233.147.109)  33.031 ms  33.034 ms  32.382 ms
10  74.125.50.125 (74.125.50.125)  312.115 ms  311.175 ms  311.140 ms
11  209.85.243.119 (209.85.243.119)  18.625 ms  18.938 ms  19.771 ms
12  209.85.241.212 (209.85.241.212)  20.814 ms 72.14.234.11 (72.14.234.11)  19.153 ms 209.85.241.212 (209.85.241.212)  22.322 ms
13  209.85.254.112 (209.85.254.112)  19.791 ms 209.85.254.116 (209.85.254.116)  206.335 ms 209.85.254.112 (209.85.254.112)  19.332 ms
14  * * *
15  google-public-dns-b.google.com (8.8.4.4)  18.602 ms  18.934 ms  19.152 ms
traceroute to 8.8.4.4 (8.8.4.4), 30 hops max, 60 byte packets
 1  * * *
 2  ttxc129.ttx-net.sk (62.197.206.129)  2.451 ms  2.454 ms  2.439 ms
 3  ttx00.ttx-net.sk (193.110.186.1)  2.519 ms  2.628 ms  2.635 ms
 4  217.75.70.4 (217.75.70.4)  3.531 ms  3.522 ms  3.676 ms
 5  xe3.inet-ba-interoute-gw1.swan.sk (217.75.72.30)  3.676 ms  3.659 ms  3.931 ms
 6  xe-5-2-0-0.bts-001-score-1-re0.interoute.net (89.202.153.121)  19.095 ms  17.424 ms  17.526 ms
 7  ae0-0.bts-001-score-2-re1.interoute.net (84.233.147.2)  18.005 ms  18.248 ms  18.147 ms
 8  ae1-0.bud-001-score-2-re0.interoute.net (84.233.147.113)  18.422 ms  18.684 ms  18.946 ms
 9  ae0-0.bud-001-score-1-re0.interoute.net (84.233.147.109)  18.435 ms  18.546 ms  18.521 ms
10  74.125.50.125 (74.125.50.125)  319.828 ms  316.378 ms  316.573 ms
11  209.85.243.121 (209.85.243.121)  211.302 ms  211.317 ms 209.85.243.119 (209.85.243.119)  19.204 ms
12  72.14.234.11 (72.14.234.11)  19.535 ms  20.018 ms 209.85.241.212 (209.85.241.212)  37.031 ms
13  209.85.254.112 (209.85.254.112)  20.127 ms 209.85.254.116 (209.85.254.116)  211.044 ms  211.038 ms
14  * * *
15  google-public-dns-b.google.com (8.8.4.4)  18.272 ms  18.296 ms  18.404 ms

this is directly from my router via ssh

root@DD-WRT:~# traceroute 8.8.8.8
traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 38 byte packets
 1  ttxc129.ttx-net.sk (62.197.206.129)  0.251 ms  0.280 ms  0.249 ms
 2  ttx00.ttx-net.sk (193.110.186.1)  1.052 ms  0.817 ms  1.369 ms
 3  217.75.70.4 (217.75.70.4)  1.627 ms  1.780 ms  1.780 ms
 4  xe3.inet-ba-interoute-gw1.swan.sk (217.75.72.30)  1.724 ms  2.118 ms  2.225 ms
 5  xe-5-2-0-0.bts-001-score-1-re0.interoute.net (89.202.153.121)  17.552 ms  17.372 ms  16.752 ms
 6  ae0-0.bts-001-score-2-re1.interoute.net (84.233.147.2)  17.952 ms  17.714 ms  40.548 ms
 7  ae1-0.bud-001-score-2-re0.interoute.net (84.233.147.113)  51.906 ms  17.488 ms  17.299 ms
 8  ae0-0.bud-001-score-1-re0.interoute.net (84.233.147.109)  17.054 ms  17.119 ms  17.658 ms
 9  74.125.50.125 (74.125.50.125)  276.593 ms  258.899 ms  263.012 ms
10  209.85.243.121 (209.85.243.121)  162.363 ms  209.85.243.119 (209.85.243.119)  18.185 ms  209.85.243.121 (209.85.243.121)  159.919 ms
11  209.85.241.212 (209.85.241.212)  18.584 ms  72.14.234.11 (72.14.234.11)  17.951 ms  18.632 ms
12  209.85.254.112 (209.85.254.112)  18.585 ms  19.456 ms  19.468 ms
13  *  *  *
14  google-public-dns-a.google.com (8.8.8.8)  18.483 ms  18.288 ms  18.164 ms
root@DD-WRT:~# traceroute 8.8.4.4
traceroute to 8.8.4.4 (8.8.4.4), 30 hops max, 38 byte packets
 1  ttxc129.ttx-net.sk (62.197.206.129)  0.411 ms  0.276 ms  0.294 ms
 2  ttx00.ttx-net.sk (193.110.186.1)  0.465 ms  1.144 ms  0.798 ms
 3  217.75.70.4 (217.75.70.4)  1.490 ms  1.421 ms  1.562 ms
 4  xe3.inet-ba-interoute-gw1.swan.sk (217.75.72.30)  1.733 ms  2.229 ms  1.590 ms
 5  xe-5-2-0-0.bts-001-score-1-re0.interoute.net (89.202.153.121)  16.895 ms  46.209 ms  17.017 ms
 6  ae0-0.bts-001-score-2-re1.interoute.net (84.233.147.2)  17.613 ms  17.694 ms  18.055 ms
 7  ae1-0.bud-001-score-2-re0.interoute.net (84.233.147.113)  17.943 ms  17.414 ms  18.324 ms
 8  ae0-0.bud-001-score-1-re0.interoute.net (84.233.147.109)  16.942 ms  17.176 ms  17.318 ms
 9  74.125.50.125 (74.125.50.125)  277.524 ms  271.655 ms  287.470 ms
10  209.85.243.121 (209.85.243.121)  175.844 ms  209.85.243.119 (209.85.243.119)  19.983 ms  209.85.243.121 (209.85.243.121)  185.550 ms
11  209.85.241.212 (209.85.241.212)  20.273 ms  72.14.234.11 (72.14.234.11)  17.886 ms  18.134 ms
12  209.85.254.116 (209.85.254.116)  181.213 ms  161.008 ms  168.847 ms
13  *  *  *
14  google-public-dns-b.google.com (8.8.4.4)  18.485 ms  18.307 ms  18.425 ms

I haven't installed any plugins in my router so I don't have iperf (or haven't found yet)

Offline

#33 2013-05-02 15:21:16

ub1quit33
Member
Registered: 2013-04-30
Posts: 58

Re: DNS problem - lookup latency

Interesting. Are you noticing the issues on your eth0 connection only, or are you experiencing issues on your wlan connection as well? At any rate, it looks like the current most likely culprit is one or both of your interfaces. Try pinging your router on both interfaces, and another device on your LAN on both interfaces, and see if you experience packet loss in either or both of those cases as well. Once we narrow that down, we'll consider our options to blast away this pesky problem smile

Offline

#34 2013-05-02 16:38:50

5ulo
Member
From: Slovakia
Registered: 2012-05-04
Posts: 77

Re: DNS problem - lookup latency

this is ONLY eth0 problem. NOT wlan0

ping another device in my network
while on wlan0

enjoy@arch ~ $ ping -c 10 192.168.1.2
PING 192.168.1.2 (192.168.1.2) 56(84) bytes of data.
64 bytes from 192.168.1.2: icmp_seq=1 ttl=128 time=3.28 ms
64 bytes from 192.168.1.2: icmp_seq=2 ttl=128 time=3.21 ms
64 bytes from 192.168.1.2: icmp_seq=3 ttl=128 time=3.33 ms
64 bytes from 192.168.1.2: icmp_seq=4 ttl=128 time=3.22 ms
64 bytes from 192.168.1.2: icmp_seq=5 ttl=128 time=3.28 ms
64 bytes from 192.168.1.2: icmp_seq=6 ttl=128 time=3.45 ms
64 bytes from 192.168.1.2: icmp_seq=7 ttl=128 time=1.25 ms
64 bytes from 192.168.1.2: icmp_seq=8 ttl=128 time=5.09 ms
64 bytes from 192.168.1.2: icmp_seq=9 ttl=128 time=3.28 ms
64 bytes from 192.168.1.2: icmp_seq=10 ttl=128 time=3.28 ms

--- 192.168.1.2 ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9012ms
rtt min/avg/max/mdev = 1.254/3.271/5.098/0.864 ms

on eth0

enjoy@arch ~ $ ping -c 10 192.168.1.2
PING 192.168.1.2 (192.168.1.2) 56(84) bytes of data.
64 bytes from 192.168.1.2: icmp_seq=1 ttl=128 time=3.40 ms
64 bytes from 192.168.1.2: icmp_seq=2 ttl=128 time=3.29 ms
64 bytes from 192.168.1.2: icmp_seq=3 ttl=128 time=3.26 ms
64 bytes from 192.168.1.2: icmp_seq=4 ttl=128 time=3.29 ms
64 bytes from 192.168.1.2: icmp_seq=5 ttl=128 time=3.37 ms
64 bytes from 192.168.1.2: icmp_seq=6 ttl=128 time=4.73 ms
64 bytes from 192.168.1.2: icmp_seq=7 ttl=128 time=3.34 ms
64 bytes from 192.168.1.2: icmp_seq=8 ttl=128 time=3.13 ms
64 bytes from 192.168.1.2: icmp_seq=9 ttl=128 time=3.01 ms
64 bytes from 192.168.1.2: icmp_seq=10 ttl=128 time=3.25 ms

--- 192.168.1.2 ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9012ms
rtt min/avg/max/mdev = 3.017/3.411/4.732/0.457 ms

connected to openVPN network and pinging device in VPN network
on wlan0

enjoy@arch ~ $ ping -c 10 10.0.0.2
PING 10.0.0.2 (10.0.0.2) 56(84) bytes of data.
64 bytes from 10.0.0.2: icmp_seq=1 ttl=64 time=14.3 ms
64 bytes from 10.0.0.2: icmp_seq=2 ttl=64 time=4.93 ms
64 bytes from 10.0.0.2: icmp_seq=3 ttl=64 time=4.99 ms
64 bytes from 10.0.0.2: icmp_seq=4 ttl=64 time=4.85 ms
64 bytes from 10.0.0.2: icmp_seq=5 ttl=64 time=4.83 ms
64 bytes from 10.0.0.2: icmp_seq=6 ttl=64 time=5.25 ms
64 bytes from 10.0.0.2: icmp_seq=7 ttl=64 time=6.34 ms
64 bytes from 10.0.0.2: icmp_seq=8 ttl=64 time=4.85 ms
64 bytes from 10.0.0.2: icmp_seq=9 ttl=64 time=5.02 ms
64 bytes from 10.0.0.2: icmp_seq=10 ttl=64 time=4.76 ms

--- 10.0.0.2 ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9006ms
rtt min/avg/max/mdev = 4.761/6.020/14.357/2.813 ms

on eth0

enjoy@arch ~ $ ping -c 10 10.0.0.2
PING 10.0.0.2 (10.0.0.2) 56(84) bytes of data.
64 bytes from 10.0.0.2: icmp_seq=1 ttl=64 time=6.14 ms
64 bytes from 10.0.0.2: icmp_seq=2 ttl=64 time=5.40 ms
64 bytes from 10.0.0.2: icmp_seq=3 ttl=64 time=4.55 ms
64 bytes from 10.0.0.2: icmp_seq=4 ttl=64 time=5.97 ms
64 bytes from 10.0.0.2: icmp_seq=5 ttl=64 time=5.67 ms
64 bytes from 10.0.0.2: icmp_seq=6 ttl=64 time=5.46 ms
64 bytes from 10.0.0.2: icmp_seq=7 ttl=64 time=5.31 ms
64 bytes from 10.0.0.2: icmp_seq=8 ttl=64 time=4.56 ms
64 bytes from 10.0.0.2: icmp_seq=9 ttl=64 time=5.15 ms
64 bytes from 10.0.0.2: icmp_seq=10 ttl=64 time=5.14 ms

--- 10.0.0.2 ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9013ms
rtt min/avg/max/mdev = 4.559/5.340/6.143/0.504 ms

When I turn on "Switchable LAN/WLAN" in my notebook bios, eth0 works good BUT this is not a solution. Both interfaces were working few weeks ago together.

edit: ping eth0 and wlan0 from another device in the network was successfull

Last edited by 5ulo (2013-05-02 16:47:11)

Offline

#35 2013-05-03 01:43:54

ub1quit33
Member
Registered: 2013-04-30
Posts: 58

Re: DNS problem - lookup latency

Let's see if we can pinpoint any notable events ocurring on eth0. Ping around on eth0 until you see some packet loss and then run

# journalctl --since=today | grep eth0

Offline

#36 2013-05-03 09:12:54

5ulo
Member
From: Slovakia
Registered: 2012-05-04
Posts: 77

Re: DNS problem - lookup latency

Here it is

enjoy@arch ~ $ ping www.google.com
PING www.google.com (173.194.70.104) 56(84) bytes of data.
64 bytes from fa-in-f104.1e100.net (173.194.70.104): icmp_seq=4 ttl=43 time=18.2 ms
64 bytes from fa-in-f104.1e100.net (173.194.70.104): icmp_seq=5 ttl=43 time=18.9 ms
64 bytes from fa-in-f104.1e100.net (173.194.70.104): icmp_seq=39 ttl=43 time=18.8 ms
64 bytes from fa-in-f104.1e100.net (173.194.70.104): icmp_seq=40 ttl=43 time=19.2 ms
64 bytes from fa-in-f104.1e100.net (173.194.70.104): icmp_seq=42 ttl=43 time=18.9 ms
64 bytes from fa-in-f104.1e100.net (173.194.70.104): icmp_seq=43 ttl=43 time=18.5 ms
64 bytes from fa-in-f104.1e100.net (173.194.70.104): icmp_seq=78 ttl=43 time=18.4 ms
64 bytes from fa-in-f104.1e100.net (173.194.70.104): icmp_seq=79 ttl=43 time=18.8 ms
64 bytes from fa-in-f104.1e100.net (173.194.70.104): icmp_seq=81 ttl=43 time=19.3 ms
64 bytes from fa-in-f104.1e100.net (173.194.70.104): icmp_seq=82 ttl=43 time=18.5 ms
64 bytes from fa-in-f104.1e100.net (173.194.70.104): icmp_seq=83 ttl=43 time=18.3 ms
64 bytes from fa-in-f104.1e100.net (173.194.70.104): icmp_seq=124 ttl=43 time=18.4 ms
64 bytes from fa-in-f104.1e100.net (173.194.70.104): icmp_seq=125 ttl=43 time=18.4 ms
64 bytes from fa-in-f104.1e100.net (173.194.70.104): icmp_seq=126 ttl=43 time=18.4 ms
64 bytes from fa-in-f104.1e100.net (173.194.70.104): icmp_seq=127 ttl=43 time=19.0 ms
64 bytes from fa-in-f104.1e100.net (173.194.70.104): icmp_seq=128 ttl=43 time=18.8 ms
64 bytes from fa-in-f104.1e100.net (173.194.70.104): icmp_seq=129 ttl=43 time=19.2 ms
64 bytes from fa-in-f104.1e100.net (173.194.70.104): icmp_seq=130 ttl=43 time=18.6 ms
64 bytes from fa-in-f104.1e100.net (173.194.70.104): icmp_seq=131 ttl=43 time=18.5 ms
^C
--- www.google.com ping statistics ---
132 packets transmitted, 19 received, 85% packet loss, time 131066ms
rtt min/avg/max/mdev = 18.255/18.745/19.306/0.351 ms
enjoy@arch ~ $ sudo journalctl --since=today | grep eth0
[sudo] password for enjoy: 
May 03 00:38:42 arch NetworkManager[889]: <info> (eth0): device state change: unavailable -> unmanaged (reason 'sleeping') [20 10 37]
May 03 00:38:42 arch NetworkManager[889]: <info> (eth0): cleaning up...
May 03 00:38:42 arch NetworkManager[889]: <info> (eth0): taking down device.
May 03 10:42:31 arch NetworkManager[889]: <info> (eth0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
May 03 10:42:31 arch NetworkManager[889]: <info> (eth0): bringing up device.
May 03 10:42:31 arch NetworkManager[889]: <info> (eth0): preparing device.
May 03 10:42:31 arch NetworkManager[889]: <info> (eth0): deactivating device (reason 'managed') [2]
May 03 10:42:31 arch kernel: r8169 0000:04:00.0 eth0: link down
May 03 11:05:50 arch dhcpcd[1071]: eth0: carrier acquired
May 03 11:05:50 arch NetworkManager[889]: <info> (eth0): carrier now ON (device state 20)
May 03 11:05:50 arch NetworkManager[889]: <info> (eth0): device state change: unavailable -> disconnected (reason 'carrier-changed') [20 30 40]
May 03 11:05:50 arch kernel: r8169 0000:04:00.0 eth0: link up
May 03 11:05:50 arch NetworkManager[889]: <info> Activation (eth0) starting connection 'LAN'
May 03 11:05:50 arch NetworkManager[889]: <info> (eth0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
May 03 11:05:50 arch NetworkManager[889]: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) scheduled...
May 03 11:05:50 arch NetworkManager[889]: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) started...
May 03 11:05:50 arch NetworkManager[889]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) scheduled...
May 03 11:05:50 arch NetworkManager[889]: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) complete.
May 03 11:05:50 arch NetworkManager[889]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) starting...
May 03 11:05:50 arch NetworkManager[889]: <info> (eth0): device state change: prepare -> config (reason 'none') [40 50 0]
May 03 11:05:50 arch NetworkManager[889]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) successful.
May 03 11:05:50 arch NetworkManager[889]: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) scheduled.
May 03 11:05:50 arch NetworkManager[889]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) complete.
May 03 11:05:50 arch NetworkManager[889]: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) started...
May 03 11:05:50 arch NetworkManager[889]: <info> (eth0): device state change: config -> ip-config (reason 'none') [50 70 0]
May 03 11:05:50 arch NetworkManager[889]: <info> Activation (eth0) Beginning DHCPv4 transaction (timeout in 45 seconds)
May 03 11:05:50 arch NetworkManager[889]: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) complete.
May 03 11:05:50 arch NetworkManager[889]: <info> (eth0): DHCPv4 state changed nbi -> preinit
May 03 11:05:50 arch dhclient[18178]: Listening on LPF/eth0/10:1f:74:e9:76:5b
May 03 11:05:50 arch dhclient[18178]: Sending on   LPF/eth0/10:1f:74:e9:76:5b
May 03 11:05:50 arch dhclient[18178]: DHCPREQUEST on eth0 to 255.255.255.255 port 67
May 03 11:05:50 arch dhcpcd[1071]: eth0: rebinding lease of 192.168.1.4
May 03 11:05:55 arch dhclient[18178]: DHCPREQUEST on eth0 to 255.255.255.255 port 67
May 03 11:05:55 arch dhcpcd[1071]: eth0: broadcasting for a lease
May 03 11:05:55 arch dhcpcd[1071]: eth0: offered 192.168.1.4 from 192.168.1.1
May 03 11:05:55 arch dhcpcd[1071]: eth0: acknowledged 192.168.1.4 from 192.168.1.1
May 03 11:05:55 arch dhcpcd[1071]: eth0: checking for 192.168.1.4
May 03 11:06:00 arch dhclient[18178]: DHCPREQUEST on eth0 to 255.255.255.255 port 67
May 03 11:06:00 arch NetworkManager[889]: <info> (eth0): DHCPv4 state changed preinit -> reboot
May 03 11:06:00 arch NetworkManager[889]: <info> Activation (eth0) Stage 5 of 5 (IPv4 Configure Commit) scheduled...
May 03 11:06:00 arch NetworkManager[889]: <info> Activation (eth0) Stage 5 of 5 (IPv4 Commit) started...
May 03 11:06:01 arch dhcpcd[1071]: eth0: leased 192.168.1.4 for infinity
May 03 11:06:01 arch NetworkManager[889]: <info> (eth0): device state change: ip-config -> secondaries (reason 'none') [70 90 0]
May 03 11:06:01 arch NetworkManager[889]: <info> Activation (eth0) Stage 5 of 5 (IPv4 Commit) complete.
May 03 11:06:01 arch NetworkManager[889]: <info> (eth0): device state change: secondaries -> activated (reason 'none') [90 100 0]
May 03 11:06:01 arch NetworkManager[889]: <info> Policy set 'LAN' (eth0) as default for IPv4 routing and DNS.
May 03 11:06:01 arch NetworkManager[889]: <info> Activation (eth0) successful, device activated.

Offline

#37 2013-05-07 00:20:52

ub1quit33
Member
Registered: 2013-04-30
Posts: 58

Re: DNS problem - lookup latency

Hmm.... After taking another look at your ping results, I'm not confident that eth0 is actually the culprit. That seems to be backed up by the output from journalctl. Try testing your eth0 connection through a different access point and see if you get the same packet loss.

Offline

#38 2013-05-07 06:01:34

5ulo
Member
From: Slovakia
Registered: 2012-05-04
Posts: 77

Re: DNS problem - lookup latency

yep.. I tried it wherever I was with my notebook sad still the same result

Last edited by 5ulo (2013-05-07 06:01:56)

Offline

#39 2013-05-07 15:29:54

ub1quit33
Member
Registered: 2013-04-30
Posts: 58

Re: DNS problem - lookup latency

In that case, it might be time to start thinking about the physical interface being the culprit... The only other thing I could think to try would be testing with a different manager, such as wicd or netctl to see if the same results occur. If you get the same results across connection managers, then given all the information we've looked at, then in my estimation you are most likely facing a hardware problem.

Offline

#40 2013-05-07 16:16:18

5ulo
Member
From: Slovakia
Registered: 2012-05-04
Posts: 77

Re: DNS problem - lookup latency

I did not have time yet to test another network manager.. I'll try at first some live distro (eg. Ubuntu).. maybe it's hardware problem.. we'll see..
edit: Ubuntu 13.04 Live USB > internet via eth = speed of light.. going to try another network manager
edit2: wicd > speed of light too (aaargh..I don't like wicd).. so there must be something with the classic built-in gnome network-manager.
edit3: disabled and removed wicd, started and enabled NetworkManager, dhcpcd... after reboot eth0 works like a charm.. we'll see how long.

Last edited by 5ulo (2013-05-07 17:12:51)

Offline

Board footer

Powered by FluxBB