From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: Fred Stratton <fredstratton@imap.cc>
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] Request for the inclusion of 2 additional packages- curl and libcurl
Date: Sun, 29 Jun 2014 22:11:59 +0200 [thread overview]
Message-ID: <878uoffpbk.fsf@toke.dk> (raw)
In-Reply-To: <53B06423.3090800@imap.cc> (Fred Stratton's message of "Sun, 29 Jun 2014 20:08:19 +0100")
[-- Attachment #1: Type: text/plain, Size: 430 bytes --]
Fred Stratton <fredstratton@imap.cc> writes:
> works to update the endpoint from ceroWRT, either in a cron job, or in
> a script in rc.local, or both. I have yet to craft anything more
> sophisticated.
It's possible to add the ipv4 endpoint update mechanism as a provider to
the dyndns update mechanism. Had a patch lying around that did that
which I may or may not have misplaced. Will see if I can find it somewhere...
-Toke
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 472 bytes --]
prev parent reply other threads:[~2014-06-29 20:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-29 19:08 Fred Stratton
2014-06-29 20:11 ` Toke Høiland-Jørgensen [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=878uoffpbk.fsf@toke.dk \
--to=toke@toke.dk \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=fredstratton@imap.cc \
/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