e what's up with the originating
> checksum. Many Thanks!
Thanks. I submitted this problem to the bug tracker of the tcpdump
project at http://sourceforge.net/projects/tcpdump/ .
The request ID is 1298259.
Regards,
Noritoshi Demizu
___
freebsd-ne
y conclusion is that src/contrib/tcpdump/print-tcp.c has a bug.
And the patch below will fix it.
Regards,
Noritoshi Demizu
--- print-tcp.c-ORG Thu Apr 21 15:36:05 2005
+++ print-tcp.c Wed Sep 21 18:43:51 2005
@@ -799,7 +799,7 @@
MD5_Update(&ctx, tcpmd5secret, strlen(tcpmd5secret));
ou try this patch?
I think this patch can also be applied to tcpdump 3.9.3.
> I think there is a bug in syncache_respond().
I'm trying to fix this problem. But,,, I found you don't use SACK in
your trace :-). Anyway, I will try to fix the bug in syncache_respond().
Regards,
Nori
know how to test the
signature option well.
I will try to make a patch tomorrow.
Regards,
Noritoshi Demizu
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
> Are there other situations when timestamp gets disabled?
In case of active open and net.inet.tcp.rfc1323 is set to non-zero,
one possibility is TCP_NOOPT is turned on by setsockopt().
But I do not know which applications use TCP_NOOPT.
Regards,
Noritoshi Demizu
> From: jha miku &
ttp://www.demizu.org/~noritosi/memo/2005/0706/
http://www.demizu.org/~noritosi/memo/2005/0711/
Sorry, all senders in those examples are DragonFlyBSD.
Regards,
Noritoshi Demizu
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/
segments into networks.
So, if it underestimates bandwidth-delay product, throughtput may be
reduced.
Regards,
Noritoshi Demizu
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
_flags is overwritten
> by SCF_SIGNATURE. By this line, SCF_TIMESTAMP and SCF_WINSCALE
> are turned off. I think the operator "=" should be "|=".
>
> 987: - sc->sc_flags = SCF_SIGNATURE;
> 987: + sc->sc_flags |= SCF_SIGNA
mes awfully huge and a burst of data can be sent.
To fix this problem, I'd like to suggest the patch below.
Thanks.
Regards,
Noritoshi Demizu
Index: tcp_input.c
===
RCS file: /home/cvsup/FreeBSD/ncvs/src/sys/netinet/tcp_inpu
TOF_SIGNATURE))?
BTW, I think the line 977 has the same problem with #1 above.
Though it does not cause any practical problem at this moment,
it would be safe to fix it.
977: - sc->sc_flags = SCF_NOOPT;
977: + sc->sc_flags |= SCF_NOOPT;
Thank you.
Regards,
Noritoshi Dem
are reordered.
3. FreeBSD stable seems not to retransmit data higher than
snd_recover even if the data can be infered as lost.
Any comments are welcome.
Thank you.
Regards,
Noritoshi Demizu
___
freebsd-net@freebsd.org mailing list
http
http://www.dd.iij4u.or.jp/~demizu/memo/2005-0316/
Any comments are welcome.
Thank you.
Regards,
Noritoshi Demizu
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "[
> The Apple machine may be rate limiting their transmissions.
> The Apple is sending only 2 packets per round trip time.
I think (acknowledgment number + advertized window) of ACKs sent by
the FreeBSD machine limits how much data the Mac can inject into the
network.
Regards,
Noritoshi
ates would be
decreased and the chance the receiver sends consecutive three dup ACKs
would be increaced.
These may improve the TCP performance in this particular case.
Regards,
Noritoshi Demizu
ps. In tcpdump.osx-fbsd, I saw six retransmission timeouts.
Retransmission timeout values are from 1 se
s not use TCP timestamps option by default.
By the way, currently, both window scale option and timestamps option
are controled by one sysctl variable: net.inet.tcp.rfc1323.
Wouldn't it be nice if each option had its own sysctl variable?
Regards,
Norito
nsen's problem, too.
Regards,
Noritoshi Demizu
Index: tcp_input.c
===
RCS file: /home/ncvs/src/sys/netinet/tcp_input.c,v
retrieving revision 1.252
diff -u -r1.252 tcp_input.c
--- tcp_input.c 17 Aug 2004 22:05:54 - 1.252
+++ tcp
> I believe the select operation on bpf is not functioning as supposed to.
> I'm calling select with 100ms timeout. The bpf interface is listening to
> an interface with constant packet rate, so it's certain that multiple
> packets have been received during the select call. However the fd for
dor Information's "MPLS Software" section
http://www.mplsrc.com/vendor.shtml
Implementation list (old info..)
http://www.watersprings.org/links/mlr/#impl
Best Regards,
Noritoshi Demizu
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-net" in the body of the message
18 matches
Mail list logo