From: GitHub <noreply@github.com>
To: cerowrt-commits@lists.bufferbloat.net
Subject: [dtaht/ceropackages-3.3] 6ea2ac: babeld: update to head for some bugfixes
Date: Fri, 12 Apr 2013 10:35:42 -0700 [thread overview]
Message-ID: <516845ee6b8c7_248d5ef13c6652f@hookshot-fe5-pe1-prd.aws.github.net.mail> (raw)
[-- Attachment #1: Type: text/plain, Size: 1441 bytes --]
Branch: refs/heads/master
Home: https://github.com/dtaht/ceropackages-3.3
Commit: 6ea2acade4e92e235bc3b7ec73f1ed82e15a393e
https://github.com/dtaht/ceropackages-3.3/commit/6ea2acade4e92e235bc3b7ec73f1ed82e15a393e
Author: Dave Taht <dave.taht@bufferbloat.net>
Date: 2013-04-12 (Fri, 12 Apr 2013)
Changed paths:
M net/babeld/Makefile
Log Message:
-----------
babeld: update to head for some bugfixes
Commit: b6f412ca9c2c8eb5d710f59619c37fd2f0541fdd
https://github.com/dtaht/ceropackages-3.3/commit/b6f412ca9c2c8eb5d710f59619c37fd2f0541fdd
Author: Dave Taht <dave.taht@bufferbloat.net>
Date: 2013-04-12 (Fri, 12 Apr 2013)
Changed paths:
M net/uftp/Makefile
Log Message:
-----------
uftp4: update to head
The protocol.txt file lists the updated packet formats and the
details of how Elliptic Curve crypto is integrated. The -k and -K
options on both sides have changed a bit to support Elliptic Curve.
I also added a -r option to specify an initial, min, and max GRTT,
and a -s option to set the robustness factor, which is how many
times the server will resend a particular message before giving up.
Those two should add some level of control that was lost with the
removal of the old timing parameters.
(I am uncertain if elliptic curve is available in openwrt's
crypto implementation)
Compare: https://github.com/dtaht/ceropackages-3.3/compare/a97591c50288...b6f412ca9c2c
reply other threads:[~2013-04-12 17:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=516845ee6b8c7_248d5ef13c6652f@hookshot-fe5-pe1-prd.aws.github.net.mail \
--to=noreply@github.com \
--cc=cerowrt-commits@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