----- Original Message -----
From: "CHOI Junho" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Monday, January 19, 2004 9:27 AM
Subject: Re: FreeBSD -> Windows HTTP TCP performance


>
> After more investigation, I realized the problem is on the router
> side. I think the problem is solved... Thanks.
>
> From: Mike Silbersack <[EMAIL PROTECTED]>
> Subject: Re: FreeBSD -> Windows HTTP TCP performance
> Date: Sun, 18 Jan 2004 22:12:34 -0600 (CST)
>
> >
> > On Thu, 15 Jan 2004, CHOI Junho wrote:
> >
> > > For those who interested, I made packet dump file:
> > >
> > >   http://www.kr.freebsd.org/~cjh/misc/freebsd-net/
> > >
> > > Best thing is do tcpdump at client machine but I have no admin
> > > permission, so failed.
> > >
> > > --
> > > CHOI Junho <http://www.kr.FreeBSD.org/~cjh>     KFUG <cjh at
kr.FreeBSD.org>
> >
> > I can read these fine, Andre must be going through some web proxy that
> > corrupts them. :)
> >
> > All of the computers in the dumps are on a LAN, right?  There seems to
be
> > quite a bit of packet loss going on, from what I can see.  This is most
> > certainly the cause of low throughput; we'd need tcpdumps from both ends
> > to really determine if there's some suboptimal tcp interaction between
w2k
> > and freebsd.  (From a single side of the connection, we can't even be
sure
> > if retransmissions are getting through, etc.)
> >
> > Mike "Silby" Silbersack
>
> --
> CHOI Junho <http://www.kr.FreeBSD.org/~cjh>     KFUG <cjh at
kr.FreeBSD.org>
> FreeBSD Project <cjh at FreeBSD.org>        Web Data Bank <cjh at
wdb.co.kr>
> Key fingerprint = 1369 7374 A45F F41A F3C0  07E3 4A01 C020 E602 60F5
> _______________________________________________
> [EMAIL PROTECTED] mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-net
> To unsubscribe, send any mail to "[EMAIL PROTECTED]"
>

_______________________________________________
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Reply via email to