From: GitHub <noreply@github.com>
To: cerowrt-commits@bufferbloat.net
Subject: [dtaht/cerofiles-3.3] 933153: radvd
Date: Tue, 10 Apr 2012 07:52:08 -0700 [thread overview]
Message-ID: <4f844918880df_371d3f979dced2f8165435@sh1.rs.github.com.mail> (raw)
[-- Attachment #1: Type: text/plain, Size: 2406 bytes --]
Branch: refs/heads/master
Home: https://github.com/dtaht/cerofiles-3.3
Commit: 9331530f58aab80ad73ff77c1d2cc40f283b4f23
https://github.com/dtaht/cerofiles-3.3/commit/9331530f58aab80ad73ff77c1d2cc40f283b4f23
Author: Dave Taht <dave.taht@bufferbloat.net>
Date: 2012-04-09 (Mon, 09 Apr 2012)
Changed paths:
M files/etc/config/firewall
M files/etc/config/radvd
M files/etc/opkg.conf
M files/etc/xinetd.conf
M packages.list
Log Message:
-----------
radvd
Commit: 71c640239c63afd70f5c0bcc2c7df97a8e08f250
https://github.com/dtaht/cerofiles-3.3/commit/71c640239c63afd70f5c0bcc2c7df97a8e08f250
Author: Dave Taht <dave.taht@bufferbloat.net>
Date: 2012-04-10 (Tue, 10 Apr 2012)
Changed paths:
M config-wndr3700v2
M packages.list
Log Message:
-----------
Re-added rrdtool and sftp-server to the build
rrdtool has broken several times, and the last time it did I
accidentally nuked sftp-server.
Commit: ce0b1fffb4dfd6d49dca9db03471a11d2f30a6fc
https://github.com/dtaht/cerofiles-3.3/commit/ce0b1fffb4dfd6d49dca9db03471a11d2f30a6fc
Author: Dave Taht <dave.taht@bufferbloat.net>
Date: 2012-04-10 (Tue, 10 Apr 2012)
Changed paths:
M files/etc/config/radvd
Log Message:
-----------
Added DNSSL support back into radvd
I have a kernel patch to do this in the kernel for clients, lets see
if we can make it work for servers and test both.
I'd really like it if we could make radvd work better in a meshed
environment.
Commit: ad1722cc12af56d8c4656cc942619c968a451aef
https://github.com/dtaht/cerofiles-3.3/commit/ad1722cc12af56d8c4656cc942619c968a451aef
Author: Dave Taht <dave.taht@bufferbloat.net>
Date: 2012-04-10 (Tue, 10 Apr 2012)
Changed paths:
M files/etc/babeld.conf
Log Message:
-----------
Make babel routing work over ipv6, but not ipv4, when nat is present
There is no easy way to detect if nat is present on an interface.
However it's possible to configure babel to at least route
ipv6 over that interface and announce ipv6 routes over it,
so you can take advantage of failover, etc.
This leads to 'interesting' paths for ipv6 vs ipv4 stuff, where
the routes can differ substantially.
Anyway, this code is mostly useful in the lab and in mesh network
scenarios, and is commented out by default.
Compare: https://github.com/dtaht/cerofiles-3.3/compare/a74b4df...ad1722c
reply other threads:[~2012-04-10 14:52 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=4f844918880df_371d3f979dced2f8165435@sh1.rs.github.com.mail \
--to=noreply@github.com \
--cc=cerowrt-commits@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