netdev - Re: [PATCH] Fix bug of update IPv4 PMTU when received ICMP Fragmentation Needed message

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20070604041406.GA28263@gondor.apana.org.au>
Date:	Mon, 4 Jun 2007 14:14:06 +1000
From:	Herbert Xu <herbert@...dor.apana.org.au>
To:	Wei Yongjun <yjwei@...fujitsu.com>
Cc:	netdev@...r.kernel.org
Subject: Re: [PATCH] Fix bug of update IPv4 PMTU when received ICMP Fragmentation Needed message

On Mon, Jun 04, 2007 at 12:03:57PM +0800, Wei Yongjun wrote:
>
> So I want to know how the route announce a MTU larger then 576, such as 
> 1280? RFC says ICMP error message return as much as we can without 
> exceeding 576 bytes.

I think there is a misunderstanding here.  The RFC is talking about
how much of the payload may be included in the ICMP packet.  It is
not talking about the length field in the original IP header.  That
must be left untouched.

> And ipv4 router alaways return as a packet size 576 because of this.
> If MTU is greater then 576, HOST will used "mtu = guess_mtu(old_mtu)" to 
> get a MTU. Method of send ICMP Fragmentation Needed message is 
> difference from receive,

Which router is doing that?

Cheers,
-- 
Visit Openswan at http://www.openswan.org/
Email: Herbert Xu ~{PmV>HI~} <herbert@...dor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html