History log of /netbsd-src/sys/netinet/tcp_input.c (Results 201 – 225 of 441)
Revision Date Author Comments
# bc93583f 25-May-2006 bouyer <bouyer@NetBSD.org>

If we're going to byteswap fields in the TCP header, make sure the mbuf
area is writable first.


# 4fd8acf0 15-Apr-2006 christos <christos@NetBSD.org>

Coverity CID 1152: Add KASSERT before deref.


# ae6865ba 18-Feb-2006 rpaulo <rpaulo@NetBSD.org>

PR 13952: Noritoshi Demizu: correct the TCP window information update check.


# 85427980 02-Feb-2006 riz <riz@NetBSD.org>

If TCP_SIGNATURE is defined, include netinet6/scope6_var.h for the
prototype of in6_clearscope(). Kernels with options TCP_SIGNATURE now
compile again after the IPv6 scoped address changes.


# c24781af 15-Nov-2005 dsl <dsl@NetBSD.org>

Pass the current process structure to in_pcbconnect() so that it can
pass it to in_pcbbind() so that can allocate a low numbered port
if setsockopt() has been used to set IP_PORTRANGE to IP_PORTRANGE

Pass the current process structure to in_pcbconnect() so that it can
pass it to in_pcbbind() so that can allocate a low numbered port
if setsockopt() has been used to set IP_PORTRANGE to IP_PORTRANGE_LOW.
While there, fail in_pcbconnect() if the in_pcbbind() fails - rather
than sending the request out from a port of zero.
This has been largely broken since the socket option was added in 1998.

show more ...


# 62269022 12-Aug-2005 christos <christos@NetBSD.org>

If called from syn_cache_add, we need to initialize t_state before calling
tcp_dooptions. Pointed out by yamt.


# a72fe4e4 12-Aug-2005 hubertf <hubertf@NetBSD.org>

Clarify comment that "the protocol specification dated September, 1981"
is really RFC 793.


# 5910d08b 11-Aug-2005 christos <christos@NetBSD.org>

Don't process TCP options in SYN packets after the connection has
been established. (FreeBSD-SA-05:15.tcp)


# f02551ec 10-Aug-2005 yamt <yamt@NetBSD.org>

move {tcp,udp}_do_loopback_cksum back to tcp/udp
so that they can be referenced by ipv6.


# 8220c378 10-Aug-2005 yamt <yamt@NetBSD.org>

device independent part of ipv6 rx checksum offloading.


# 89940190 19-Jul-2005 christos <christos@NetBSD.org>

Implement PMTU checks from:

http://www.gont.com.ar/drafts/icmp-attacks-against-tcp.html

1. Don't act on ICMP-need-frag immediately if adhoc checks on the
advertised MTU fail. The MTU update

Implement PMTU checks from:

http://www.gont.com.ar/drafts/icmp-attacks-against-tcp.html

1. Don't act on ICMP-need-frag immediately if adhoc checks on the
advertised MTU fail. The MTU update is delayed until a TCP retransmit
happens.
2. Ignore ICMP Source Quench messages meant for TCP connections.

From OpenBSD.

show more ...


# a85b0c68 30-Jun-2005 christos <christos@NetBSD.org>

Normalize our PAWS code with Free and Open, as mentioned in tech-security.


# 0e70c535 06-Jun-2005 yamt <yamt@NetBSD.org>

tcp_input: don't overload opti.ts_ecr.


# ea2d4204 29-May-2005 christos <christos@NetBSD.org>

- add const
- remove bogus casts
- avoid nested variables


# cddc3070 26-Apr-2005 manu <manu@NetBSD.org>

Fix build problem after recent NAT-T changes


# 4b935040 03-Apr-2005 yamt <yamt@NetBSD.org>

tcp_input: update a comment to match with the code.


# 8b0967ff 29-Mar-2005 yamt <yamt@NetBSD.org>

protect tcpipqent with splvm.


# df05ca70 16-Mar-2005 yamt <yamt@NetBSD.org>

simplify data receiver side sack processing.
- introduce t_segqlen, the number of segments in segq/timeq.
the name is from freebsd.
- rather than maintaining a copy of sack blocks (rcv_sack_block[]

simplify data receiver side sack processing.
- introduce t_segqlen, the number of segments in segq/timeq.
the name is from freebsd.
- rather than maintaining a copy of sack blocks (rcv_sack_block[]),
build it directly from the segment list when needed.

show more ...


# c9f058f6 02-Mar-2005 mycroft <mycroft@NetBSD.org>

Copyright maintenance.


# 4ae1f36d 28-Feb-2005 jonathan <jonathan@NetBSD.org>

Commit TCP SACK patches from Kentaro A. Karahone's patch at:
http://www.sigusr1.org/~kurahone/tcp-sack-netbsd-02152005.diff.gz

Fixes in that patch for pre-existing TCP pcb initializations were al

Commit TCP SACK patches from Kentaro A. Karahone's patch at:
http://www.sigusr1.org/~kurahone/tcp-sack-netbsd-02152005.diff.gz

Fixes in that patch for pre-existing TCP pcb initializations were already
committed to NetBSD-current, so are not included in this commit.

The SACK patch has been observed to correctly negotiate and respond,
to SACKs in wide-area traffic.

There are two indepenently-observed, as-yet-unresolved anomalies:
First, seeing unexplained delays between in fast retransmission
(potentially explainable by an 0.2sec RTT between adjacent
ethernet/wifi NICs); and second, peculiar and unepxlained TCP
retransmits observed over an ath0 card.

After discussion with several interested developers, I'm committing
this now, as-is, for more eyes to use and look over. Current hypothesis
is that the anomalies above may in fact be due to link/level (hardware,
driver, HAL, firmware) abberations in the test setup, affecting both
Kentaro's wired-Ethernet NIC and in my two (different) WiFi NICs.

show more ...


# f07677dd 26-Feb-2005 perry <perry@NetBSD.org>

nuke trailing whitespace


# 870f2067 03-Feb-2005 perry <perry@NetBSD.org>

ANSIfy function declarations


# 34944823 02-Feb-2005 perry <perry@NetBSD.org>

de-__P -- will ANSIfy .c files later.


# 47759e63 28-Jan-2005 mycroft <mycroft@NetBSD.org>

Several changes based on comparison with NS:

1) dupseg_fix_=true from NS: do not count a segment with completely duplicate
data as a duplicate ack. This can occur due to duplicate packets in the
ne

Several changes based on comparison with NS:

1) dupseg_fix_=true from NS: do not count a segment with completely duplicate
data as a duplicate ack. This can occur due to duplicate packets in the
network, or due to fast retransmit from the other side.

2) dupack_reset_=false from NS: do not reset the duplicate ack counter or exit
fast recovery if we happen to get data or a window update along with a
duplicate ack.

3) In the "very old ack" case that itojun added, send an ACK before dropping
the segment, to try to update the other side's send sequence number.

4) Check the ssthresh crossover point with >= rather than >. Otherwise we
start to do "exponential" growth immediately following recovery, where we
should be doing "linear". This is what NS does.

show more ...


# 746d109a 27-Jan-2005 mycroft <mycroft@NetBSD.org>

There is no reason to adjust ts_recent_age for ts_timebase; it's strictly an
internal variable.


12345678910>>...18