linux-stable.git/Documentation/networking/ip-sysctl.txt, branch v3.8

ip-sysctl: fix spelling errors

2013-01-04T23:12:34+00:00

Signed-off-by: Stephen Hemminger 
Signed-off-by: David S. Miller

ipv6: document ndisc_notify in networking/ip-sysctl.txt

2013-01-04T21:35:38+00:00

I slipped in a new sysctl without proper documentation. I would like to
make up for this now.

Signed-off-by: Hannes Frederic Sowa 
Signed-off-by: David S. Miller

doc: Tighten-up and clarify description of tcp_fin_timeout

2012-12-10T22:14:28+00:00

The description for tcp_fin_timeout should be tigher and more clear.

In addition to being tighter, we should make the spelling of the
state name consistent with what utilities report, remove the now
dated reference to 2.2 and put the default in the consistent place.

Signed-off-by: Rick Jones 
Signed-off-by: David S. Miller

net: doc : use more suitable word 'unexpected' to replace 'secluded'

2012-12-07T19:31:07+00:00

 'secluded' is used to describe places, not suitable here.

Suggested-by: Ben Hutchings 
Signed-off-by: Shan Wei 
Signed-off-by: David S. Miller

net: doc: add default value for neighbour parameters

2012-12-05T21:01:28+00:00

Signed-off-by: Shan Wei 
Signed-off-by: David S. Miller

doc: make the description of how tcp_ecn works more explicit and clear

2012-11-29T18:14:58+00:00

Make the description of how tcp_ecn works a bit more explicit and clear.

Signed-off-by: Rick Jones 
Signed-off-by: David S. Miller

sctp: Make hmac algorithm selection for cookie generation dynamic

2012-10-26T06:22:18+00:00

Currently sctp allows for the optional use of md5 of sha1 hmac algorithms to
generate cookie values when establishing new connections via two build time
config options.  Theres no real reason to make this a static selection.  We can
add a sysctl that allows for the dynamic selection of these algorithms at run
time, with the default value determined by the corresponding crypto library
availability.
This comes in handy when, for example running a system in FIPS mode, where use
of md5 is disallowed, but SHA1 is permitted.

Note: This new sysctl has no corresponding socket option to select the cookie
hmac algorithm.  I chose not to implement that intentionally, as RFC 6458
contains no option for this value, and I opted not to pollute the socket option
namespace.

Change notes:
v2)
	* Updated subject to have the proper sctp prefix as per Dave M.
	* Replaced deafult selection options with new options that allow
	  developers to explicitly select available hmac algs at build time
	  as per suggestion by Vlad Y.

Signed-off-by: Neil Horman 
CC: Vlad Yasevich 
CC: "David S. Miller" 
CC: netdev@vger.kernel.org
Acked-by: Vlad Yasevich 
Signed-off-by: David S. Miller

tcp: TCP Fast Open Server - header & support functions

2012-09-01T00:02:18+00:00

This patch adds all the necessary data structure and support
functions to implement TFO server side. It also documents a number
of flags for the sysctl_tcp_fastopen knob, and adds a few Linux
extension MIBs.

In addition, it includes the following:

1. a new TCP_FASTOPEN socket option an application must call to
supply a max backlog allowed in order to enable TFO on its listener.

2. A number of key data structures:
"fastopen_rsk" in tcp_sock - for a big socket to access its
request_sock for retransmission and ack processing purpose. It is
non-NULL iff 3WHS not completed.

"fastopenq" in request_sock_queue - points to a per Fast Open
listener data structure "fastopen_queue" to keep track of qlen (# of
outstanding Fast Open requests) and max_qlen, among other things.

"listener" in tcp_request_sock - to point to the original listener
for book-keeping purpose, i.e., to maintain qlen against max_qlen
as part of defense against IP spoofing attack.

3. various data structure and functions, many in tcp_fastopen.c, to
support server side Fast Open cookie operations, including
/proc/sys/net/ipv4/tcp_fastopen_key to allow manual rekeying.

Signed-off-by: H.K. Jerry Chu 
Cc: Yuchung Cheng 
Cc: Neal Cardwell 
Cc: Eric Dumazet 
Cc: Tom Herbert 
Signed-off-by: David S. Miller

tcp: Increase timeout for SYN segments

2012-08-31T19:42:10+00:00

Commit 9ad7c049 ("tcp: RFC2988bis + taking RTT sample from 3WHS for
the passive open side") changed the initRTO from 3secs to 1sec in
accordance to RFC6298 (former RFC2988bis). This reduced the time till
the last SYN retransmission packet gets sent from 93secs to 31secs.

RFC1122 is stating that the retransmission should be done for at least 3
minutes, but this seems to be quite high.

  "However, the values of R1 and R2 may be different for SYN
  and data segments.  In particular, R2 for a SYN segment MUST
  be set large enough to provide retransmission of the segment
  for at least 3 minutes.  The application can close the
  connection (i.e., give up on the open attempt) sooner, of
  course."

This patch increases the value of TCP_SYN_RETRIES to the value of 6,
providing a retransmission window of 63secs.

The comments for SYN and SYNACK retries have also been updated to
describe the current settings. The same goes for the documentation file
"Documentation/networking/ip-sysctl.txt".

Signed-off-by: Alexander Bergmann 
Acked-by: Eric Dumazet 
Signed-off-by: David S. Miller

ipv4: remove rt_cache_rebuild_count

2012-07-30T21:53:22+00:00

After IP route cache removal, rt_cache_rebuild_count is no longer
used.

Signed-off-by: Eric Dumazet 
Signed-off-by: David S. Miller