In article <
8ae0k850t2q01194l...@4ax.com>,
Peter <
occassional...@nospam.co.uk> wrote:
>The current news on this is that something on the AAISP ADSL is not
>responding to MTU size negotiation requests (ICMP packets).
>
>Pings work on it OK but the MTU negotiation is a different type of
>ICMP packet, which I have not found anybody able to test.
>
>Vodafone, apparently, do not support 1500 byte packets. They request
>smaller ones, so the connection will break if that ICMP packet is not
>effective.
>
>I cannot find anything in the Draytek 2955 config which might control
>this, and the www server in question is on a 2nd subnet so the router
>should not come into it anyway as the 2nd subnet bypasses it. So it's
>down to the server firewall rules, and we can't see anything relevant
>there either.
>
>On the "Voda working" site (on ZEN) the www server is behind NAT (with
>port 80 etc open, obviously) and the MTU negotiation is done with the
>router, not with the server, apparently, and the router does that
>correctly. That's why we think it is the server firewall which is
>doing this...
If you have a Unix based client to try from, there is a jolly useful
utility for this sort of thing called tracepath which is a sort of
traceroute with PMTU discovery included. For each hop it prints
the maximum MTU supported and should show you where the problem is.
Wish we'd had it when I used to have to diagnose similar for clients
- mostly it was their router wrongly configured to block all ICMPs
("because ICMPs are insecure" they would say) but occasionally we would
find somewhere in their ISP that was breaking path length discovery.
Nick
--
"The Internet, a sort of ersatz counterfeit of real life"
-- Janet Street-Porter, BBC2, 19th March 1996