[EMAIL PROTECTED] wrote:
> Ran through the docs, but what is a 'correct MTU', and how to check  
> current one?

something less than or equal to 1500, on some adsl circuits to 1450 or
1454 as it wil mean with the encapsulation overhead it is still less
than 1500.

> btw traceroute looks like this:
> traceroute to 87.97.100.8.pool.invitel.hu (87.97.100.8), 30 hops max,  
> 40 byte packets
>   1  gw.deninet.hu (212.92.23.1)  42.490 ms  0.287 ms  48.193 ms
>   2  bix.invitel.hu (193.188.137.44)  6.329 ms  5.606 ms  4.965 ms
>   3  213-163-21-13.pool.invitel.hu (213.163.21.13)  0.372 ms  0.385 ms  
>   0.576 ms
>   4  * * *
>   5  * * *
>   6  * * *
>   7  * * *
>   8  * * *
>   9  * * *
> 10  * * *
> 11  * * *
> 12  * * *
> 13  * * *
> 
> Isn't it weird?

Not overly:

$ traceroute 87.97.100.8
traceroute to 87.97.100.8 (87.97.100.8), 64 hops max, 40 byte packets
 1  bis-stmary-gw1 (192.168.2.249)  0.848 ms  0.658 ms  0.694 ms
 2  192.168.253.33 (192.168.253.33)  0.850 ms  0.956 ms  0.706 ms
 3  217.169.32.157 (217.169.32.157)  0.889 ms  0.962 ms  0.859 ms
 4  217.169.37.153 (217.169.37.153)  1.147 ms  1.121 ms  1.151 ms
 5  213.152.245.98 (213.152.245.98)  1.148 ms  1.176 ms  1.290 ms
 6  LON-SB1.LON.GB.NET.DTAG.de (217.79.160.39)  10.067 ms  9.494 ms  10.067 ms
 7  m-sb2.m.de.net.dtag.de (62.154.5.241)  63.590 ms  40.125 ms  39.884 ms
 8  * 217.6.51.154 (217.6.51.154)  35.931 ms  37.016 ms
 9  ten2.1-vh-p0.vivendi-th.net (213.163.52.2)  37.101 ms  35.494 ms  35.398 ms
10  * * *
11  * * *
12  * * *
13  * * *

It appears 213.163.0.0/16 (vivendi?) filter at their borders icmp - this
is not unusual. 

Regards

D.

-- 
## List details at http://www.exim.org/mailman/listinfo/exim-users 
## Exim details at http://www.exim.org/
## Please use the Wiki with this list - http://www.exim.org/eximwiki/

Reply via email to