--MAH+hnPXVZWQ5cD/
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hi,

On Wed, Feb 11, 2004 at 03:57:38AM -0500, Matt Doughty wrote:

> The only thing I have found is that netbsd is being used on both sides, a=
nd
> NetBSD is returning an ipv6 address also which most sites don't at this
> point.

That's, of course, pure speculation... you have to test this.

The quickest check would be to contact http://www4.netbsd.org/, which is=20
the set of IPv4 addresses of www.netbsd.org only. (or check with netstat
or tcpdump, what kind of connection is attempted).

If this does not work, either:

As you can get small pages, I suspect something else - like, the ICMP
transmission from www.NetBSD.org (or intermediate hosts) back to you,
or maybe the ICMP transmission from you to www.netbsd.org, or being
broken, so that path MTU discovery does not work.

Workaround is to set the MTU if the Ethernet interface of your *BSD boxes
to 1452 or 1412, or tell your "router" (is it a NAT box in reality?) to
manipulate the TCP MSS values so that no packet will be created with bigger
size.

Regards,
	-is

--MAH+hnPXVZWQ5cD/
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: 2.6.i

iQEVAgUBQCn4FjCn4om+4LhpAQEjCggAoUVDDbeASKJJHw9cgUlw2oeIA1ME+jzX
c6w1NhxUimPqzIZ0M8R0bMYV3dTj47+029bOYgjLoRVazWiQG7OL8WJ9HfZ5+YSY
xyW2ouzeobul7hFPT8d2o0G4n4OqdDMkgRsLmjA9vdgAIwsRpH8aLP8GzpG9rpEK
Tuk04JC3+MtRWhmI7GNoNoQolPewQ3014oeRgONQLQf19+2znjtRx72EsJS41yA7
ioRWG80MCaiQMRBydJ3dghx9UfzblgY0Gt8cJLKLFCdIQ95O3hBYOnwHlJJvT2wo
+ZwE5m5c8jdWgstMcS8mbIy3cXgug/0OdbeoTzZc5tIYc32s/R+Hgg==
=fiGY
-----END PGP SIGNATURE-----

--MAH+hnPXVZWQ5cD/--