Skip to Content.
Sympa Menu

ndt-users - Re: NDT 3.3.12 - MSS weirdness

Subject: ndt-users list created

List archive

Re: NDT 3.3.12 - MSS weirdness


Chronological Thread 
  • From: Simon Leinen <>
  • To: Jeremian <>
  • Cc: Richard Carlson <>,
  • Subject: Re: NDT 3.3.12 - MSS weirdness
  • Date: Wed, 30 Aug 2006 17:40:24 +0200

Jeremian writes:
> I forgot that the patch in the mentioned mail wasn't complete. Here
> comes the missing part:

> /-----------------------------------------------------------------\
> @@ -703,7 +703,7 @@

> cp = agent->info.local.connection_head;
> while (cp) {
> - if (memcmp(&cp->spec_v6, spec_v6, sizeof (spec_v6)) != 0)
> + if (memcmp(&cp->spec_v6, spec_v6, sizeof (spec_v6)) == 0)
> break;
> cp = cp->info.local.next;
> }
> \-----------------------------------------------------------------/

Thanks. With that patch, the server logs this for an IPv6 transfer:

Sending 1408 Byte packets over the network
libweb100: warning: accessing depricated variable AckPktsIn
libweb100: warning: accessing depricated variable AckPktsOut

Looks better. But the client still says:

:
leinen@soekris[leinen];
./web100clt -n ndt.switch.ch
Testing network path for configuration and performance problems --
Using IPv6 address
[...]
Information: Network Middlebox is modifying MSS variable (changed to 1420)

...which I find confusing, because there is no middlebox. 1420 bytes
is simply the MSS that the client naturally advertises, because its
default route points to a tunnel interface with a 1480 byte IPv6 MTU.
--
Simon.



Archive powered by MHonArc 2.6.16.

Top of Page