netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Ford <david+challenge-response@blue-labs.org>
To: Tim Berti <tim@tsearch.com>
Cc: netdev@oss.sgi.com, linux-net@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fix tcp_default_win_scale.
Date: Tue, 06 Jul 2004 16:54:25 -0400	[thread overview]
Message-ID: <40EB1181.40406@blue-labs.org> (raw)
In-Reply-To: <828E111C7AEF60468FAA5FBC696DD80F67DF37@64-3-142-15.dia.xo.com>

[-- Attachment #1: Type: text/plain, Size: 1783 bytes --]

By recruiting someone with enough of a technology clue to scroll to the 
bottom of the message and read: "To unsubscribe from ...."

:P

David
p.s. and I wonder why I have so little faith in marketing and HR.

Tim Berti wrote:

>How do i get off this list?
>
>Tim Berti 
>Senior Recruiter 
>TECHNOLOGY SEARCH INTERNATIONAL 
>1737 North First Street, Suite 600 
>San Jose, CA. 95112 
>http://www.tsearch.com 
>Email: tim@tsearch.com 
>Phone: 408-437-9500 Ext. 303 
>
>
>
>-----Original Message-----
>From: Stephen Hemminger [mailto:shemminger@osdl.org]
>Sent: Tuesday, July 06, 2004 1:37 PM
>To: David S. Miller
>Cc: jamie@shareable.org; netdev@oss.sgi.com; linux-net@vger.kernel.org;
>linux-kernel@vger.kernel.org
>Subject: Re: [PATCH] fix tcp_default_win_scale.
>
>
>On Tue, 6 Jul 2004 13:28:22 -0700
>"David S. Miller" <davem@redhat.com> wrote:
>
>  
>
>>On Tue, 6 Jul 2004 13:05:49 -0700
>>Stephen Hemminger <shemminger@osdl.org> wrote:
>>
>>    
>>
>>>On Tue, 6 Jul 2004 20:40:34 +0100
>>>Jamie Lokier <jamie@shareable.org> wrote:
>>>
>>>      
>>>
>>>>Are you saying there are broken firewalls which strip TCP options in
>>>>one direction only?
>>>>        
>>>>
>>>It appears so.
>>>      
>>>
>>Ok, this is a possibility.  And why it breaks is that if the ACK
>>for the SYN+ACK comes back, the SYN+ACK sender can only assume
>>that the window scale was accepted.
>>
>>Stephen, do you have a trace showing exactly this?
>>    
>>
>
>No, I don't have a br0ken firewall here.  I can get out fine.
>When I setup with same kernel as packages.gentoo.org, it works fine as well.
>-
>To unsubscribe from this list: send the line "unsubscribe linux-net" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at  http://vger.kernel.org/majordomo-info.html
>
>  
>

[-- Attachment #2: david+challenge-response.vcf --]
[-- Type: text/x-vcard, Size: 183 bytes --]

begin:vcard
fn:David Ford
n:Ford;David
email;internet:david@blue-labs.org
title:Industrial Geek
tel;home:Ask please
tel;cell:(203) 650-3611
x-mozilla-html:TRUE
version:2.1
end:vcard


  reply	other threads:[~2004-07-06 20:54 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-06 20:35 [PATCH] fix tcp_default_win_scale Tim Berti
2004-07-06 20:54 ` David Ford [this message]
     [not found] <32886.63.170.215.71.1088564087.squirrel@www.osdl.org>
     [not found] ` <20040629222751.392f0a82.davem@redhat.com>
     [not found]   ` <20040630152750.2d01ca51@dell_ss3.pdx.osdl.net>
     [not found]     ` <20040630153049.3ca25b76.davem@redhat.com>
2004-07-01 20:37       ` [PATCH] TCP acts like it is always out of memory Stephen Hemminger
2004-07-01 21:04         ` David S. Miller
2004-07-02  1:32           ` Arnaldo Carvalho de Melo
2004-07-06  9:35             ` analysis of TCP window size issues still around - several reports / SACK involved? bert hubert
2004-07-06 18:47               ` [PATCH] fix tcp_default_win_scale Stephen Hemminger
2004-07-06 19:40                 ` Jamie Lokier
2004-07-06 20:05                   ` Stephen Hemminger
2004-07-06 20:28                     ` David S. Miller
2004-07-06 20:36                       ` Stephen Hemminger
2004-07-06 20:35                         ` David S. Miller
2004-07-06 21:55                           ` John Heffner
2004-07-06 22:50                             ` David S. Miller
2004-07-07  1:32                               ` John Heffner
2004-07-06 20:12                   ` David S. Miller
2004-07-06 22:44                     ` bert hubert
2004-07-06 22:49                       ` David S. Miller
2004-07-07 18:06                         ` Stephen Hemminger
2004-07-07 19:31                           ` Jamie Lokier
2004-07-07 19:38                             ` bert hubert
2004-07-07 19:41                           ` John Heffner
2004-07-09 23:14                           ` David S. Miller
2004-07-06 20:00                 ` Nivedita Singhvi
2004-07-06 20:16                   ` David S. Miller
2004-07-06 20:26                     ` David Ford
     [not found]                 ` <20040706185856.GN18841@lug-owl.de>
2004-07-06 20:17                   ` David S. Miller
2004-07-06 20:31                     ` Stephen Hemminger
2004-07-06 20:33                       ` David S. Miller
2004-07-06 20:24                 ` David S. Miller
2004-07-06 23:16                   ` Andi Kleen
2004-07-07  7:50                     ` Chris Wedgwood
2004-07-06 23:19                 ` Redeeman
2004-07-07 19:47                 ` John Heffner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=40EB1181.40406@blue-labs.org \
    --to=david+challenge-response@blue-labs.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-net@vger.kernel.org \
    --cc=netdev@oss.sgi.com \
    --cc=tim@tsearch.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).