From: Josh Lehan <linux@krellan•com>
To: Neil Horman <nhorman@tuxdriver•com>
Cc: Josh Lehan <linux@krellan•com>,
janardhan.iyengar@fandm•edu,
Janardhan Iyengar <jana.iyengar@gmail•com>,
rick.jones2@hp•com, Yuchung Cheng <ycheng@google•com>,
netdev <netdev@vger•kernel.org>, Bryan Ford <bryan.ford@yale•edu>
Subject: Re: Skipping past TCP lost packet in userspace
Date: Fri, 01 Jul 2011 01:39:18 -0700 [thread overview]
Message-ID: <4E0D87B6.8090108@krellan.com> (raw)
In-Reply-To: <20110630143614.GA4392@shamino.rdu.redhat.com>
On 06/30/2011 07:36 AM, Neil Horman wrote:
> I'll leave the rest of this alone, since its pretty obvious that no one is going
> to break TCP for you, but just so that you're aware, The only reason you have to
That's the fundamental disconnect we've been trying to communicate: TCP
*won't break*. None of the rules of TCP are broken, from the wire's
point of view. The OS merely gets a richer API, from the application's
point of view, to optimize the TCP protocol implementation to serve a
wider variety of needs.
> use the 2-Wire gateway that AT&T provides is because there are no commercially
> available routers that support the uplink interface (which I expect will change
That would be good to give the customer a choice of access devices with
which to get on the network, and let the market device what is best,
instead of AT&T dictating what's allowed. I'm getting deja vu of a
famous legal case from 27 years ago.
> eventually). In the time being, if you want to use a different router, place
> the RG in bridge mode by selecting a host as your DMZ device. That will assign
> the wan address to that connected device via DHCP and allow you to pass whatever
> traffic you want through it. I use it to pass SCTP and IPv6 traffice all the
> time, works great.
Wow, that's news to me, that it allows this.
http://www.ka9q.net/Uverse/
Have the limitations in these documents been addressed? If so, kudos to
AT&T.
Josh Lehan
next prev parent reply other threads:[~2011-07-01 8:39 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-31 1:19 Skipping past TCP lost packet in userspace Josh Lehan
2011-05-31 3:30 ` Marcus D. Leech
2011-05-31 4:12 ` Josh Lehan
2011-05-31 4:05 ` Mikael Abrahamsson
2011-05-31 11:12 ` Neil Horman
2011-05-31 17:23 ` Yuchung Cheng
2011-06-01 8:10 ` Josh Lehan
2011-06-01 16:57 ` Bill Sommerfeld
2011-06-01 17:35 ` Rick Jones
2011-06-24 14:58 ` Janardhan Iyengar
2011-06-30 8:38 ` Josh Lehan
2011-06-30 14:36 ` Neil Horman
2011-07-01 8:39 ` Josh Lehan [this message]
2011-07-01 13:37 ` Neil Horman
2011-06-01 19:36 ` juice
2011-06-03 11:51 ` Ilpo Järvinen
2011-06-06 6:30 ` Josh Lehan
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=4E0D87B6.8090108@krellan.com \
--to=linux@krellan$(echo .)com \
--cc=bryan.ford@yale$(echo .)edu \
--cc=jana.iyengar@gmail$(echo .)com \
--cc=janardhan.iyengar@fandm$(echo .)edu \
--cc=netdev@vger$(echo .)kernel.org \
--cc=nhorman@tuxdriver$(echo .)com \
--cc=rick.jones2@hp$(echo .)com \
--cc=ycheng@google$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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