RE: iperf server UDP response in IPv6 is fragemented
I've seen this too. I don't think the proper response
is to "respond with the size the client uses" (it's udp,
what response?) but instead lower the default when IPv6 is
being used. (Perhaps there also might be a warning
when packets will be fragmented.)
Actually, if the receiving side has a buffer that is smaller
than the sending side, making the sender match does make
sense (again, with a warning).
--Matt
--On Wednesday, November 27, 2002 12:05 PM +0200 Yaniv Kaul
<ykaul --at-- checkpoint.com> wrote:
> Apparently, you can use the '-l' size on the server too, which seems to
> solve the problem.
> How about setting it to automatically respond with the size the client
> uses, unless otherwise specified? It seems the default is to reply with a
> 1470 bytes of UDP data.
>
> -----Original Message-----
> From: owner-iperf-users --at-- dast.nlanr.net
> [mailto:owner-iperf-users --at-- dast.nlanr.net]On Behalf Of Yaniv Kaul
> Sent: Wednesday, November 27, 2002 11:55 AM
> To: Iperf-Users --at-- Dast. Nlanr. Net
> Subject: iperf server UDP response in IPv6 is fragemented
>
>
> I'm having the following problem:
> The response from the iperf server (Linux, 2.4.19 +USAGI patches) in UDP,
> with IPv6, is fragmented, since it is 1478 bytes in size. The same, but in
> IPv4, is not fragmented (I assume it's due to the v6 header size).
>
> Is there anything that can be done in order to reduce the server->client
> response size, so it won't get fragmented?
>
>
>
--
Mitch Kutzko | mitch --at-- dast.nlanr.net | mitch --at-- ncsa.uiuc.edu | 217-333-1199
http://hobbes.ncsa.uiuc.edu/