Re: Slow browsing with cable modem
From: Stephen Zilliox (szilliox_at_charter.net)
Date: 04/26/04
- Previous message: John Gabriele: "Re: hopefully simple ppp dns or routing problem on Slack 9.1"
- In reply to: Joachim Mæland: "Re: Slow browsing with cable modem"
- Next in thread: P Gentry: "Re: Slow browsing with cable modem"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Sun, 25 Apr 2004 17:33:21 -0700
> Do you have any clues regarding the first 3 IP-addresses in this
> traceroute, (your LAN?)?
I have no home network. I have a single computer with an ethernet card
hooked directly into a cable modem. I do not know what these addresses
represent.
>
> In another posting, you mentioned the DHCP-server address: 192.168.4.27.
> Is this pingable? How about traceroute? Any clues regarding this
> IP-address?
root@stevescomputer stephen]# ping -c 3 192.168.4.27
PING 192.168.4.27 (192.168.4.27) 56(84) bytes of data.
--- 192.168.4.27 ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 1998ms
[root@stevescomputer stephen]# traceroute -n 192.168.4.27
traceroute to 192.168.4.27 (192.168.4.27), 30 hops max, 38 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 * * *
Can you please make the same traceroute, without the n-option...?
root@stevescomputer stephen]# traceroute 192.168.4.27
traceroute to 192.168.4.27 (192.168.4.27), 30 hops max, 38 byte packets
1 * * *
2 * * *
3 * * *
4 * * *
5 * * *
... The same traceroute from Windoze
> would be appreciated...
C:\WINDOWS>tracert 192.168.4.27
Tracing route to nr1.wa.charter.com [192.168.4.27]
over a maximum of 30 hops:
1 * * * Request timed out.
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Trace complete.
C:\WINDOWS>
C:\WINDOWS>pathping -n 192.168.4.27
Tracing route to 192.168.4.27 over a maximum of 30 hops
0 66.189.180.71
1 * * 10.210.32.1 reports: Destination net unreachable.
Computing statistics for 25 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 66.189.180.71
100/ 100 =100% |
1 --- 100/ 100 =100% 0/ 100 = 0% 0.0.0.0
Trace complete.
C:\WINDOWS>
C:\WINDOWS>
C:\WINDOWS>pathping 192.168.4.27
Tracing route to nr1.wa.charter.com [192.168.4.27]
over a maximum of 30 hops:
0 stevescomputer [66.189.180.71]
1 * 10.210.32.1 reports: Destination net unreachable.
Computing statistics for 25 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 stevescomputer [66.189.180.71]
100/ 100 =100% |
1 --- 100/ 100 =100% 0/ 100 = 0% stevescomputer [0.0.0.0]
Trace complete.
> Can you please make a traceroute to each of the 4 first IP-addresses
> listed in your traceroute?
[root@stevescomputer stephen]# traceroute -n 10.210.32.1
traceroute to 10.210.32.1 (10.210.32.1), 30 hops max, 38 byte packets
1 * * 10.210.32.1 8.336 ms !X
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * 10.210.32.1 14.010 ms !X *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
root@stevescomputer stephen]# traceroute -n 172.29.32.161
traceroute to 172.29.32.161 (172.29.32.161), 30 hops max, 38 byte packets
1 * * *
2 * * *
3 * * *
4 * * *
5 * * *
[root@stevescomputer stephen]# traceroute -n 172.29.32.2
traceroute to 172.29.32.2 (172.29.32.2), 30 hops max, 38 byte packets
1 * * *
2 * * *
3 * * *
4 * * *
5 * * *
[root@stevescomputer stephen]# traceroute -n 12.127.79.149
traceroute to 12.127.79.149 (12.127.79.149), 30 hops max, 38 byte packets
1 10.210.32.1 8.271 ms 9.984 ms 8.164 ms
2 172.29.32.161 8.322 ms 22.202 ms 23.461 ms
3 172.29.32.2 27.349 ms 11.656 ms 12.118 ms
4 12.127.79.149 20.238 ms * 19.928 ms
> Can you please make a traceroute to 1 or each of the nameserves listed
> in resolv.conf..?
root@stevescomputer stephen]# traceroute -n 66.189.219.29
traceroute to 66.189.219.29 (66.189.219.29), 30 hops max, 38 byte packets
1 10.210.32.1 31.010 ms 8.861 ms 9.962 ms
2 172.29.32.161 25.551 ms 11.832 ms 12.510 ms
3 172.29.32.3 10.248 ms 8.818 ms 25.552 ms
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 * * *
>
> The output from MTR, http://www.bitwizard.nl/mtr/ can give additional
> information:
Downloaded the rpm. Would not install.
Steve Z.
- Previous message: John Gabriele: "Re: hopefully simple ppp dns or routing problem on Slack 9.1"
- In reply to: Joachim Mæland: "Re: Slow browsing with cable modem"
- Next in thread: P Gentry: "Re: Slow browsing with cable modem"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
