Text 782, 149 rader
Skriven 2006-07-26 18:18:32 av Randall Parker (1:379/45)
    Kommentar till text 768 av Geo (1:379/45)
Ärende: Re: My slow Linux Thunderbird on Barkto investigations
==============================================================
From: Randall Parker <future_take-out-this-stuff_pundit@_same-name-as-on-left-s
ide_dot-here_com>

Geo wrote:
> "Mike N." <mike@u-spam-u-die.net> wrote in message
> news:d3nec25h86m8rj5a6q6uaupe5k168qkm10@4ax.com...
>
>>    Still no joy ... we may need a wireshark (or the MS Network Monitor)
> run
>> on your end to identify what's going on.
>
> that's going to be difficult since the server is now on a switched gigE
> network, I'd have to stick a hub in front of the machine so I could sniff
> with my laptop.
>
> Why is this only happening to Randall? Typically when I see something like
> this the problem is with the dsl modem/router not having the correct MTU set
> for the ISP it's connected to. We use 1492 when that happens and usually
> that fixes the problem.

I have a few different problems:

1) My Linux Thunderbird is slow on your news server but fast on other news
servers. My Windows Thunderbird going thru the same DSL modem is fast on your
server.

2) I can't traceroute very well. Taking the Firewall/VPN box out of the link
does not help any. So that isn't it.

3) On Windows I can't ping or traceroute at all. I put that down to either
Trend Micro or MS's firewall.

>
> I think Randall should look in his dsl router and see what MTU is set to.
> That might explain why he can't traceroute as well.
>
> Randall if you are reading try this, try pinging something near you on the
> internet with a ping command
> p
> ping 216.144.8.1 -l 1024

Geo,

I can ping you from Linux. The argument on Linux is -s. See below. I went all
the way up to -s 1500. Worked okay.

[randall@localhost ~]$ ping 4.2.2.1 PING 4.2.2.1 (4.2.2.1) 56(84) bytes of
data. 64 bytes from 4.2.2.1: icmp_seq=1 ttl=245 time=50.6 ms 64 bytes from
4.2.2.1: icmp_seq=2 ttl=245 time=47.1 ms 64 bytes from 4.2.2.1: icmp_seq=3
ttl=245 time=62.1 ms 64 bytes from 4.2.2.1: icmp_seq=4 ttl=245 time=51.7 ms 64
bytes from 4.2.2.1: icmp_seq=5 ttl=245 time=51.6 ms 64 bytes from 4.2.2.1:
icmp_seq=6 ttl=245 time=45.8 ms 64 bytes from 4.2.2.1: icmp_seq=7 ttl=245
time=46.3 ms

-+- 4.2.2.1 ping statistics ---
7 packets transmitted, 7 received, 0% packet loss, time 6002ms rtt
min/avg/max/mdev = 45.874/50.800/62.197/5.198 ms [randall@localhost ~]$ ping
216.144.8.1 PING 216.144.8.1 (216.144.8.1) 56(84) bytes of data. 64 bytes from
216.144.8.1: icmp_seq=1 ttl=247 time=103 ms 64 bytes from 216.144.8.1:
icmp_seq=2 ttl=247 time=102 ms

-+- 216.144.8.1 ping statistics ---
3 packets transmitted, 2 received, 33% packet loss, time 2333ms rtt
min/avg/max/mdev = 102.134/103.028/103.922/0.894 ms [randall@localhost ~]$ ping
216.144.8.1 -l 1024 ping: cannot set preload to value > 3 [randall@localhost
~]$ ping 216.144.8.1 -s 1024 PING 216.144.8.1 (216.144.8.1) 1024(1052) bytes of
data. 1032 bytes from 216.144.8.1: icmp_seq=1 ttl=247 time=188 ms 1032 bytes
from 216.144.8.1: icmp_seq=2 ttl=247 time=122 ms 1032 bytes from 216.144.8.1:
icmp_seq=3 ttl=247 time=122 ms 1032 bytes from 216.144.8.1: icmp_seq=4 ttl=247
time=122 ms 1032 bytes from 216.144.8.1: icmp_seq=5 ttl=247 time=121 ms 1032
bytes from 216.144.8.1: icmp_seq=6 ttl=247 time=122 ms 1032 bytes from
216.144.8.1: icmp_seq=7 ttl=247 time=121 ms 1032 bytes from 216.144.8.1:
icmp_seq=8 ttl=247 time=122 ms

-+- 216.144.8.1 ping statistics ---
8 packets transmitted, 8 received, 0% packet loss, time 6999ms rtt
min/avg/max/mdev = 121.747/130.468/188.806/22.052 ms [randall@localhost ~]$
ping 216.144.8.1 -s 1324 PING 216.144.8.1 (216.144.8.1) 1324(1352) bytes of
data. 1332 bytes from 216.144.8.1: icmp_seq=1 ttl=247 time=122 ms 1332 bytes
from 216.144.8.1: icmp_seq=2 ttl=247 time=122 ms 1332 bytes from 216.144.8.1:
icmp_seq=3 ttl=247 time=123 ms 1332 bytes from 216.144.8.1: icmp_seq=4 ttl=247
time=122 ms

-+- 216.144.8.1 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3002ms rtt
min/avg/max/mdev = 122.183/122.760/123.349/0.434 ms [randall@localhost ~]$ ping
216.144.8.1 -s 1424 PING 216.144.8.1 (216.144.8.1) 1424(1452) bytes of data.
1432 bytes from 216.144.8.1: icmp_seq=1 ttl=247 time=136 ms 1432 bytes from
216.144.8.1: icmp_seq=2 ttl=247 time=136 ms 1432 bytes from 216.144.8.1:
icmp_seq=3 ttl=247 time=136 ms 1432 bytes from 216.144.8.1: icmp_seq=4 ttl=247
time=136 ms 1432 bytes from 216.144.8.1: icmp_seq=5 ttl=247 time=136 ms

-+- 216.144.8.1 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 3999ms rtt
min/avg/max/mdev = 136.072/136.626/136.866/0.284 ms [randall@localhost ~]$ ping
216.144.8.1 -s 1474 PING 216.144.8.1 (216.144.8.1) 1474(1502) bytes of data.
1482 bytes from 216.144.8.1: icmp_seq=1 ttl=247 time=128 ms 1482 bytes from
216.144.8.1: icmp_seq=2 ttl=247 time=139 ms 1482 bytes from 216.144.8.1:
icmp_seq=3 ttl=247 time=372 ms 1482 bytes from 216.144.8.1: icmp_seq=4 ttl=247
time=255 ms 1482 bytes from 216.144.8.1: icmp_seq=5 ttl=247 time=138 ms

-+- 216.144.8.1 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4073ms rtt
min/avg/max/mdev = 128.684/207.051/372.833/95.145 ms [randall@localhost ~]$
ping 216.144.8.1 -s 1484 PING 216.144.8.1 (216.144.8.1) 1484(1512) bytes of
data. 1492 bytes from 216.144.8.1: icmp_seq=1 ttl=247 time=140 ms 1492 bytes
from 216.144.8.1: icmp_seq=2 ttl=247 time=140 ms 1492 bytes from 216.144.8.1:
icmp_seq=3 ttl=247 time=156 ms 1492 bytes from 216.144.8.1: icmp_seq=4 ttl=247
time=138 ms 1492 bytes from 216.144.8.1: icmp_seq=5 ttl=247 time=138 ms

-+- 216.144.8.1 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4034ms rtt
min/avg/max/mdev = 138.922/143.084/156.657/6.829 ms [randall@localhost ~]$ ping
216.144.8.1 -s 1494 PING 216.144.8.1 (216.144.8.1) 1494(1522) bytes of data.
1502 bytes from 216.144.8.1: icmp_seq=1 ttl=247 time=141 ms 1502 bytes from
216.144.8.1: icmp_seq=2 ttl=247 time=142 ms 1502 bytes from 216.144.8.1:
icmp_seq=3 ttl=247 time=142 ms 1502 bytes from 216.144.8.1: icmp_seq=4 ttl=247
time=142 ms

-+- 216.144.8.1 ping statistics ---
5 packets transmitted, 4 received, 20% packet loss, time 3999ms rtt
min/avg/max/mdev = 141.117/141.895/142.236/0.646 ms [randall@localhost ~]$ ping
216.144.8.1 -s 1500 PING 216.144.8.1 (216.144.8.1) 1500(1528) bytes of data.
1508 bytes from 216.144.8.1: icmp_seq=1 ttl=247 time=135 ms 1508 bytes from
216.144.8.1: icmp_seq=2 ttl=247 time=152 ms 1508 bytes from 216.144.8.1:
icmp_seq=3 ttl=247 time=151 ms 1508 bytes from 216.144.8.1: icmp_seq=4 ttl=247
time=152 ms

-+- 216.144.8.1 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3000ms rtt
min/avg/max/mdev = 135.569/148.008/152.257/7.182 ms [randall@localhost ~]$




>
> see that last number, try 512, 1024, 2048 and find which works then cut the
> difference between that and the next bigger one in half until you find the
> exact maximum size you can ping with. My bet is it will be somewhere between
> 1400 and 1500
>
> Geo.
>
> Geo.
>
>

--- BBBS/NT v4.01 Flag-5
 * Origin: Barktopia BBS Site http://HarborWebs.com:8081 (1:379/45)