netdev - Re[2]: [PATCH V3 0/8] ipvs: IPv6 fragment handling for IPVS

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-next>] [day] [month] [year] [list]

Message-ID: <ee5vnhe.0891bc4ff9e38f64c4c5c0da6c50af1c@obelix.schillstrom.com>
Date:	Thu, 13 Sep 2012 08:55:08 +0200 (CEST)
From:	"Hans Schillstrom" <hans@...illstrom.com>
To:	"Julian Anastasov" <ja@....bg>
Cc:	"Jesper Dangaard Brouer" <brouer@...hat.com>,
	"Hans Schillstrom" <hans.schillstrom@...csson.com>,
	netdev@...r.kernel.org, "Patrick McHardy" <kaber@...sh.net>,
	"Pablo Neira Ayuso" <pablo@...filter.org>,
	lvs-devel@...r.kernel.org, "Thomas Graf" <tgraf@...g.ch>,
	"Wensong Zhang" <wensong@...ux-vs.org>,
	netfilter-devel@...r.kernel.org,
	"Simon Horman" <horms@...ge.net.au>
Subject: Re[2]:  [PATCH V3 0/8] ipvs: IPv6 fragment handling for 
	IPVS

Hello
>
>Hello,
>
>On Tue, 11 Sep 2012, Jesper Dangaard Brouer wrote:
>
>> The following patchset implement IPv6 fragment handling for IPVS.
>> 
[snip]

>
>	I also see that we should not send ICMP
>errors (FRAG NEEDED/TOO BIG) in response to large
>ICMP error packets but it is not related to your changes,
>it needs separate change to all transmitters.

Just a curious question, have you seen such big ICMP packets in real life ?
(if you have normal MTU:s) 
 
Regards 
Hans

--
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