Richard,
what version of the OS are you running ?
Also, could you do a 'netstat -p tcp' and send me the output.
jayanth
Richard A. Steenbergen ([EMAIL PROTECTED]) wrote:
> Memory statistics by type Type Kern
> Type InUse MemUse HighUse Limi
check the arp cache. You might want to do a arp -ad and try again.
jayanth
Luigi Rizzo ([EMAIL PROTECTED]) wrote:
> There is an annoying bug in FreeBSD networking/routing which has been
> around at least since 3.4.
>
> Symptoms are -- if you change the address to an interface,
.
jayanth
Paul Herman ([EMAIL PROTECTED]) wrote:
> Hi Jonathan,
>
> On Wed, 24 Jan 2001, Jonathan Lemon wrote:
>
> > >10:49:54.279497 16.1035 > 10.40438: . ack 19433 win 17520 (DF)
> > >10:49:54.371025 16.1035 > 10.40438: . ack 21481 win 17520 (DF)
> &
tcp_timer_delack, tp);
} else {
jayanth
Bruce Evans ([EMAIL PROTECTED]) wrote:
> On Wed, 24 Jan 2001, Jordan Hubbard wrote:
>
> > > Something just doesn't sit well me. This shouldn't happen in a
> > > 100Mbit LAN. This seems like a plain v
Y_ACK(tp) && (tp->t_flags & TF_NEEDSYN))
>
> At this point the DELAY_ACK macro returns false because there is a
> callout_pending(). Hence the TF_ACKNOW will be set.
> ^^^^^
>
>
588 why not anything between
589 and 1460. This assumption is based on the fact that the congestion
window is large enough for us to send data.
I dont think TF_NODELAY needs to be set by the application here.
jayanth
[EMAIL PROTECTED] ([EMAIL PROTECTED]) wrote:
> > >
> >
Yoshi,
I have attached a patch. Let me know if this fixes the problem.
jayanth
[EMAIL PROTECTED] ([EMAIL PROTECTED]) wrote:
>
> > This issue is a combination of mbuf cluster size and the
> > TF_MORETOCOME flag.
>
> > if (len) {
> >
.
jayanth
[EMAIL PROTECTED] ([EMAIL PROTECTED]) wrote:
>
> > This issue is a combination of mbuf cluster size and the
> > TF_MORETOCOME flag.
>
> > if (len) {
> > if (len == tp->t_maxseg)
> > goto
forces the local address of the socket to be INADDR_ANY.
Can we change this behaviour to retain the originally bound IP address ?
thanks,
jayanth
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-net" in the body of the message
Hmm, this is what has broken fast retransmit.
I should probably replace
if (tp->t_dupacks < tcprexmtthresh)
tp->t_dupacks = 0;
with
if (tcp_do_newreno && (tp->t_dupacks < tcprexmtthresh))
tp->t_du
Garrett,
Can you run these tests again with rfc1323 off ?
jayanth
Garrett Wollman ([EMAIL PROTECTED]) wrote:
> <
>said:
>
> [Quoting Bruce Mah:]
>
> >> happens. In *most* cases, the receiver somehow gets the missing data
> >> because you can later see it
t flag of the listening socket is used as a timer and an indicator
that a syncache entry has been removed. A dropped entry due to listen q full
should be treated the same way as zone allocation failure, bucket or cache
overflow, by updating ts_recent.
This will not reject the ACK assuming that t
ou.)
We have a sysctl that takes the four tuple as an argument, which can
be got from netstat -an output. It is used only for deleting a
connection not modifying it.
for e.g
sysctl net.inet.tcp.deleteconn="a.b.c.d:80:x.y.z.w:3".
netstat -Aan gives us the tcp control block address or the inpcb address
Can you dump the output of netstat -s -p tcp ?
Checking for listen queue overflows and syncache bucket overflows.
jayanth
Nguyen-Tuong Long Le ([EMAIL PROTECTED]) wrote:
> On Mon, 3 Jun 2002, Mike Silbersack wrote:
>
> > A few questions:
> >
> > 1. Is this 4.5-rel
t seems incorrect to have the newfd's flags and socket
state be out of sync.
Copying the state of the socket during the accept might lead to a slightly
different behaviour, but will solve this particular problem.
thanks,
jayanth
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "un
15 matches
Mail list logo