[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4E0D87B6.8090108@krellan.com>
Date: Fri, 01 Jul 2011 01:39:18 -0700
From: Josh Lehan <linux@...llan.com>
To: Neil Horman <nhorman@...driver.com>
CC: Josh Lehan <linux@...llan.com>, janardhan.iyengar@...dm.edu,
Janardhan Iyengar <jana.iyengar@...il.com>, rick.jones2@...com,
Yuchung Cheng <ycheng@...gle.com>,
netdev <netdev@...r.kernel.org>, Bryan Ford <bryan.ford@...e.edu>
Subject: Re: Skipping past TCP lost packet in userspace
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
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists