2018-05-31 15:17 GMT-04:00 Carlos E. R. <robin.listas@telefonica.net>:
On 2018-05-31 20:51, Charles Robert wrote:
2018-05-31 6:25 GMT-04:00 Carlos E. R. <robin.listas@telefonica.net>:
On 2018-05-30 23:08, Charles Robert wrote:
Hello,
Here a traceroute on same computer for tumbleweed, leap and ubuntu:
Tumbleweed
traceroute to opensuse.org (130.57.66.19), 30 hops max, 60 byte packets 1 * * * 2 192.168.0.1 (192.168.0.1) 3.890 ms 6.022 ms 6.285 ms 3 * * * 4 10.170.183.61 (10.170.183.61) 16.574 ms 16.888 ms 16.886 ms 5 216.113.124.54 (216.113.124.54) 40.368 ms 216.113.123.174 (216.113.123.174) 37.985 ms 216.113.124.54 (216.113.124.54) 38.872 ms
Bowen:/home/charles # traceroute opensuse.org traceroute to opensuse.org (130.57.66.19), 30 hops max, 60 byte packets 1 * * * 2 * * *
And this machine is...?
Same machine.
Bowen:/home/charles # traceroute opensuse.org traceroute to opensuse.org (130.57.66.19), 30 hops max, 60 byte packets 1 * * * 2 * * * 3 * * *
And this machine is...?
Same machine.
17 intra.attachmategroup.com (130.57.66.19) 85.850 ms 85.685 ms 85.741 ms
Bowen:/home/charles # traceroute opensuse.org traceroute to opensuse.org (130.57.66.19), 30 hops max, 60 byte packets 1 * * * 2 192.168.0.1 (192.168.0.1) 10.117 ms 10.112 ms 10.646 ms 3 * * * 4 10.170.183.61 (10.170.183.61) 25.130 ms 24.126 ms 25.288 ms 5 216.113.123.174 (216.113.123.174) 48.312 ms 48.551 ms 49.083 ms
You have to explain how each test is different from the others. Different machine, different network, something changed, what?
Same machine, same network. Did back to back with just 1-2 seconds between each.
Ok, so you were testing the same machine with no changes, yet the results are different?
I don't then understand this:
1 * * * 2 192.168.0.1 (192.168.0.1) 10.117 ms 10.112 ms 10.646 ms 3 * * * 4 10.170.183.61 (10.170.183.61) 25.130 ms 24.126 ms 25.288 ms 5 216.113.123.174 (216.113.123.174) 48.312 ms 48.551 ms 49.083 ms
1 * * * 2 * * * 3 * * *
At least, you should get a response from your own router.
But what Ken said was «use traceroute to get the IP for the next hop after your wifi card, i.e., that of the access point/hotspot. This will give you more reliable test results than pinging all the way to google.»
Well, you have to ping 192.168.100.1 and 192.168.0.1, perhaps 10.170.183.61.
ping 192.168.100.1 PING 192.168.100.1 (192.168.100.1) 56(84) bytes of data. 64 bytes from 192.168.100.1: icmp_seq=1 ttl=64 time=0.060 ms 64 bytes from 192.168.100.1: icmp_seq=2 ttl=64 time=0.046 ms 64 bytes from 192.168.100.1: icmp_seq=3 ttl=64 time=0.047 ms 64 bytes from 192.168.100.1: icmp_seq=4 ttl=64 time=0.052 ms 64 bytes from 192.168.100.1: icmp_seq=5 ttl=64 time=0.048 ms 64 bytes from 192.168.100.1: icmp_seq=6 ttl=64 time=0.047 ms ^C --- 192.168.100.1 ping statistics --- 6 packets transmitted, 6 received, 0% packet loss, time 5084ms rtt min/avg/max/mdev = 0.046/0.050/0.060/0.004 ms
ping 192.168.0.1 PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data. 64 bytes from 192.168.0.1: icmp_seq=1 ttl=63 time=27.3 ms ^C --- 192.168.0.1 ping statistics --- 23 packets transmitted, 1 received, 95% packet loss, time 22485ms rtt min/avg/max/mdev = 27.352/27.352/27.352/0.000 ms
I would ping for a long time, like 15 minutes, and collect the stats. There are other ping variants best suited for this, I would have to read the man pages to see which and what options.
ping 10.170.183.61 PING 10.170.183.61 (10.170.183.61) 56(84) bytes of data. ^C --- 10.170.183.61 ping statistics --- 44 packets transmitted, 0 received, 100% packet loss, time 44024ms
It is possible that this host does not respond to ping, you would have to try perhaps tcp on some port. Try this one:
nping -c 10 --tcp -p 80 SomeMachine.
you may have to install nping.
-c is the number of pings, one per second roughly.
nping -c 900 --tcp 192.168.0.1 10.170.183.61 -p 80,433
I try it:
Telcontar:~ # nping -c 10 --tcp 192.168.0.1 10.170.183.61 -p 80,433
Starting Nping 0.6.47 ( http://nmap.org/nping ) at 2018-05-31 21:12 CEST SENT (0.0565s) TCP 192.168.1.14:5881 > 192.168.0.1:80 S ttl=64 id=44903 iplen=40 seq=795849567 win=1480 SENT (1.0566s) TCP 192.168.1.14:5881 > 10.170.183.61:80 S ttl=64 id=44903 iplen=40 seq=795849567 win=1480 SENT (2.0578s) TCP 192.168.1.14:5881 > 192.168.0.1:433 S ttl=64 id=44903 iplen=40 seq=795849567 win=1480 SENT (3.0589s) TCP 192.168.1.14:5881 > 10.170.183.61:433 S ttl=64 id=44903 iplen=40 seq=795849567 win=1480 SENT (4.0591s) TCP 192.168.1.14:5881 > 192.168.0.1:80 S ttl=64 id=44903 iplen=40 seq=795849567 win=1480 RCVD (4.2351s) ICMP [10.195.97.231 > 192.168.1.14 Host 10.170.183.61 unreachable (type=3/code=1) ] IP [ttl=64 id=61496 iplen=72 ] RCVD (4.2351s) ICMP [10.195.97.231 > 192.168.1.14 Host 10.170.183.61 unreachable (type=3/code=1) ] IP [ttl=64 id=61497 iplen=72 ] SENT (5.0593s) TCP 192.168.1.14:5881 > 10.170.183.61:80 S ttl=64 id=44903 iplen=40 seq=795849567 win=1480 SENT (6.0604s) TCP 192.168.1.14:5881 > 192.168.0.1:433 S ttl=64 id=44903 iplen=40 seq=795849567 win=1480
...
Statistics for host 192.168.0.1: | Probes Sent: 20 | Rcvd: 0 | Lost: 20 (100.00%) |_ Max rtt: N/A | Min rtt: N/A | Avg rtt: N/A Statistics for host 10.170.183.61: | Probes Sent: 20 | Rcvd: 18 | Lost: 2 (10.00%) |_ Max rtt: 1176.185ms | Min rtt: 1149.732ms | Avg rtt: 1162.072ms Raw packets sent: 40 (1.600KB) | Rcvd: 18 (1.296KB) | Lost: 22 (55.00%) Nping done: 2 IP addresses pinged in 40.12 seconds Telcontar:~ #
Funny. I do have some 10.*** network nearby. The standard ping fails completely on that host (which is not the same 10.170.183.61 as you see).
Statistics for host 192.168.0.1: | Probes Sent: 1800 | Rcvd: 309 | Lost: 1491 (82.83%) |_ Max rtt: 3739.069ms | Min rtt: 2.792ms | Avg rtt: 591.496ms Statistics for host 10.170.183.61: | Probes Sent: 1800 | Rcvd: 0 | Lost: 1800 (100.00%) |_ Max rtt: N/A | Min rtt: N/A | Avg rtt: N/A Raw packets sent: 3600 (144.000KB) | Rcvd: 309 (13.016KB) | Lost: 3291 (91.42%) Nping done: 2 IP addresses pinged in 3604.45 seconds
-- Cheers / Saludos,
Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org