From: Dave Taht <dave.taht@gmail.com>
To: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] dhcp-pd and source specific routing on debian
Date: Thu, 18 Jun 2015 18:35:35 -0700 [thread overview]
Message-ID: <CAA93jw7tAk+nD2_R10eDd1s9p1BtrRjUYY=KJRx2vMHkuecN4g@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw7wiT4R0g=c0=VO0ZQs=0g0UmTvgSPuKnqQQ8f3uE=PZA@mail.gmail.com>
I retract that. The default scripts flush the existing addresses every
30 seconds. That would be fine if I wasn't also getting a long
duration address from RA that also gets flushed. Feeding this into dns
every 30 seconds is not fun either...
The route stuff is fixible using a proto and a replace rather than
"add"... a replace does an add if not found, and otherwise updates the
lifetime.
(ideas borrowed from the hnetd code)
prev parent reply other threads:[~2015-06-19 1:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-18 22:41 Dave Taht
2015-06-19 1:35 ` Dave Taht [this message]
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='CAA93jw7tAk+nD2_R10eDd1s9p1BtrRjUYY=KJRx2vMHkuecN4g@mail.gmail.com' \
--to=dave.taht@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