From: William Allen Simpson <william.allen.simpson@gmail.com>
To: cerowrt developers <cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] administrative questions
Date: Thu, 31 Jan 2013 11:28:18 -0500 [thread overview]
Message-ID: <510A9BA2.1080500@gmail.com> (raw)
In-Reply-To: <CAD6NSj5jMt0Wuw_rv_9EYmLbpQT40XT88OJEfwtqks4ecCZa8w@mail.gmail.com>
On 1/30/13 10:03 PM, Ketan Kulkarni wrote:
> On Wed, Jan 30, 2013 at 10:19 PM, William Allen Simpson
> <william.allen.simpson@gmail.com> wrote:
>> On 1/29/13 11:24 PM, Ketan Kulkarni wrote:
>>> You can submit the patches to this list, ccing Dave, or you can attach
>>> it to the reported bugs for better future tracking.
>>> All standard linux formatting applies here as well.
>>>
>> OK. I have various TCP, TCPCT (RFC 6013) and RFC1323bis patches from
>> several years ago. I'm slowly updating my patches from 2.6.33 and .37
>> to 3.7.4, but pretty much nothing is patching cleanly -- so it's going
>> to be a long hard slog.
>>
> Yes there was a discussion about TCPCT recently on this list.
> https://lists.bufferbloat.net/pipermail/cerowrt-devel/2013-January/000887.html
Aha, just the kinda thing that I was looking for....
> ...
> Though I personally haven't looked at the security aspect of TFO, it
> would be good to have wider views on the same. At the same time around
> Dave pointed me to TCPCT RFC.
>
I've actually got a preliminary "TFO Considered Harmful" written, but
was waiting for their RFC to be published.
Gettys had invited me here (from TCPM WG) some time ago, and I actually
bought a pair of WNDR3800 last February specifically to run CeroWRT.
But then the release seemed very unstable at the time, and I stuck with
the Netgear code and gave one to a brother.
I am now running sugarland. I'll start submitting proposed patches
(tested on a spare linux box, not risking my access to the net) via
the Issues. I'm patching against .../stable/linux-stable.git, but it
compiles as 2.8.0-rc3+ -- is that what CeroWRT is/will be using?
I was looking for a .git repository and compile instructions, but
didn't find anything under Documents or Files.
next prev parent reply other threads:[~2013-01-31 16:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-29 18:42 William Allen Simpson
2013-01-30 4:24 ` Ketan Kulkarni
2013-01-30 16:49 ` William Allen Simpson
2013-01-31 3:03 ` Ketan Kulkarni
2013-01-31 16:28 ` William Allen Simpson [this message]
2013-01-31 17:43 ` William Allen Simpson
2013-02-01 15:51 ` Ketan Kulkarni
2013-02-04 6:06 ` Dave Taht
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
List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=510A9BA2.1080500@gmail.com \
--to=william.allen.simpson@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
/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