[Cerowrt-devel] administrative questions

[Cerowrt-devel] administrative questions

[William Allen Simpson]

This link (and all the other Archives links):

   https://lists.bufferbloat.net/pipermail/cerowrt-devel/2013-January.txt.gz

gives an error message:

Forbidden

You don't have permission to access /pipermail/ on this server.
Apache/2.2.16 (Ubuntu) Server at lists.bufferbloat.net Port 443

This happens whether I am either logged in or not logged in to my account.

===

How do we get permission to add "Issues" and do tracking?

===

How do we submit patches?  Preferred format?

Re: [Cerowrt-devel] administrative questions

[Ketan Kulkarni]

Hi William,
To add issues and do tracking, you need to register. Once registered,
I can provide you the required access.
If you have registered already, please let me know your login id so I
can grant access. I couldn't find you in the user's list.

Downloading the archives is a problem for everyone which I think
Dave(?) needs to address.

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.

Thanks,
Ketan

On Wed, Jan 30, 2013 at 12:12 AM, William Allen Simpson
<william.allen.simpson@gmail.com> wrote:
> This link (and all the other Archives links):
>
>   https://lists.bufferbloat.net/pipermail/cerowrt-devel/2013-January.txt.gz
>
> gives an error message:
>
> Forbidden
>
> You don't have permission to access /pipermail/ on this server.
> Apache/2.2.16 (Ubuntu) Server at lists.bufferbloat.net Port 443
>
> This happens whether I am either logged in or not logged in to my account.
>
> ===
>
> How do we get permission to add "Issues" and do tracking?
>
> ===
>
> How do we submit patches?  Preferred format?
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel

Re: [Cerowrt-devel] administrative questions

[William Allen Simpson]

On 1/29/13 11:24 PM, Ketan Kulkarni wrote:
> To add issues and do tracking, you need to register. Once registered,
> I can provide you the required access.
> If you have registered already, please let me know your login id so I
> can grant access. I couldn't find you in the user's list.
>
Thought the mail login would be sufficient, but apparently not.  Made
DayDreamer today.  Was able to get https running, although it's not
default for login!  (probably should fix that.)


> Downloading the archives is a problem for everyone which I think
> Dave(?) needs to address.
>
OK, I still use POP3 and Thunderbird, so I can grep and organize.
None of that "cloud" stuff for me! :-)


> 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.

Re: [Cerowrt-devel] administrative questions

[Ketan Kulkarni]

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:
>>
>> To add issues and do tracking, you need to register. Once registered,
>> I can provide you the required access.
>> If you have registered already, please let me know your login id so I
>> can grant access. I couldn't find you in the user's list.
>>
> Thought the mail login would be sufficient, but apparently not.  Made
> DayDreamer today.  Was able to get https running, although it's not
> default for login!  (probably should fix that.)
>
Thanks William. Please try re-logging in and you should get the required access.
>
>
>> Downloading the archives is a problem for everyone which I think
>> Dave(?) needs to address.
>>
> OK, I still use POP3 and Thunderbird, so I can grep and organize.
> None of that "cloud" stuff for me! :-)
>
>
>
>> 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
I also note the latest cero 3.7.2+ has the TCP Fast Open support. We
also have hacked few tools (httping and polipo proxy notably) to
support TCP Fast Open. The gains over wifi by TFO are pretty good.
Preliminary results here -
http://www.bufferbloat.net/attachments/158/multiple_packet_sizes.ods

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.

Thanks,
Ketan

Re: [Cerowrt-devel] administrative questions

[William Allen Simpson]

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.

Re: [Cerowrt-devel] administrative questions

[William Allen Simpson]

On 1/30/13 10:03 PM, Ketan Kulkarni wrote:
> Thanks William. Please try re-logging in and you should get the required access.

OK, I've submitted a small patch series fixing a 0-day and a crashing bug.
Is this the correct process?  The lines don't display very well, but the
emails sent look OK.

Next time, I'll try {{{ }}} bracing to signal no text processing.  That
works on some other trackers.

Re: [Cerowrt-devel] administrative questions

[Ketan Kulkarni]

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

Thanks William
Its generally Dave who decides and applies the patches.
Building cerowrt has been a pain for us (except Dave) for a while.
On Jan 31, 2013 11:13 PM, "William Allen Simpson" <
william.allen.simpson@gmail.com> wrote:

> On 1/30/13 10:03 PM, Ketan Kulkarni wrote:
>
>> Thanks William. Please try re-logging in and you should get the required
>> access.
>>
>
> OK, I've submitted a small patch series fixing a 0-day and a crashing bug.
> Is this the correct process?  The lines don't display very well, but the
> emails sent look OK.
>
> Next time, I'll try {{{ }}} bracing to signal no text processing.  That
> works on some other trackers.
>
>

[-- Attachment #2: Type: text/html, Size: 1069 bytes --]

Re: [Cerowrt-devel] administrative questions

[Dave Taht]

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

re: your bugs https://www.bufferbloat.net/issues/424 through 426.

Thank you! Had I noticed I'd have tried to fold these into 3.7.5-2.

in the case of emailing the bug tracker a new bug, it is better to attach
the patch rather than put it inline.

In the case of emailing humans, inline on this list is fine and will get
you more eyeballs.

Did these patches apply to 3.7.x?

On Fri, Feb 1, 2013 at 7:51 AM, Ketan Kulkarni <ketkulka@gmail.com> wrote:

> Thanks William
> Its generally Dave who decides and applies the patches.
> Building cerowrt has been a pain for us (except Dave) for a while.
>

No, building cero is a PITA for me too!

I did build a builder vm recently in the hope I could make it easier for
people. Haven't had the bandwidth to upload 5GB... cut it down to 2GB...
it's a zillion times slower than a native build...

Not particularly well documented is that current development of cerowrt is
in the cerowrt-next, cerofiles-next, and ceropackages-3.3 repos on github.

I HAVE been pushing and tagging the more good releases in the hope that
someone would try to update the build_cero.sh script to match the current
reality. The website and onboard doc are in a dire need of a facelift...




> On Jan 31, 2013 11:13 PM, "William Allen Simpson" <
> william.allen.simpson@gmail.com> wrote:
>
>> On 1/30/13 10:03 PM, Ketan Kulkarni wrote:
>>
>>> Thanks William. Please try re-logging in and you should get the required
>>> access.
>>>
>>
>> OK, I've submitted a small patch series fixing a 0-day and a crashing bug.
>> Is this the correct process?  The lines don't display very well, but the
>> emails sent look OK.
>>
>> Next time, I'll try {{{ }}} bracing to signal no text processing.  That
>> works on some other trackers.
>>
>>


-- 
Dave Täht

Fixing bufferbloat with cerowrt:
http://www.teklibre.com/cerowrt/subscribe.html

[-- Attachment #2: Type: text/html, Size: 2905 bytes --]