Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Fred Stratton <fredstratton@imap.cc>
To: cerowrt-devel@lists.bufferbloat.net
Subject: [Cerowrt-devel] Fwd: Re: Request for the inclusion of 2 additional packages- curl and libcurl
Date: Sun, 29 Jun 2014 20:13:50 +0100	[thread overview]
Message-ID: <53B0656E.5070309@imap.cc> (raw)
In-Reply-To: <53B0652B.2080502@xyz.am>

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




-------- Original Message --------
Subject: 	Re: Request for the inclusion of 2 additional packages- curl 
and libcurl
Date: 	Sun, 29 Jun 2014 20:12:43 +0100
From: 	Fred Stratton <fredstratton@xyz.am>
To: 	cerowrt-devel@lists.bufferbloat.net



Slight reformatting

This also requires the use of version 17-1 version of 6in4, rather than
16-1 as included


On 29/06/14 20:08, Fred Stratton wrote:
> Keeping a Hurricane Electric tunnel up through a change of ipv4
> address has always been problematic with ceroWRT.
>
> After experimentation with openWRT Barrier Breaker, which itself does
> not perform adequately in this regard, I found that
>
>  /usr/bin/curl -s
> 'http://ipv4.tunnelbroker.net/ipv4_end.php?ip=AUTO&pass=(md5sum-of-password,or-plaintext-updatekey)&user_id=(user-id)&tid=(tunnel-id)'
> > /dev/null 2>&1
>
> 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.
>
> wget as included produces errors, even if correct values are included
> for all tunnel variables.
>
> curl, and the required libcurl, work.
>
> The error HE returns is:
>
>> -ERROR: Missing parameter(s).
>> Usage:
>> http://ipv4.tunnelbroker.net/ipv4_end.php?ip=IPV4ADDR&pass=PASSKEY&user_id=USERID&tid=TUNNELID
>>  -or-:
>> https://USERNAME:PASSWORD@ipv4.tunnelbroker.net/ipv4_end.php?tid=TUNNELID
>> (auto-detect IP)
>> https://USERNAME:PASSWORD@ipv4.tunnelbroker.net/ipv4_end.php?tid=TUNNELID&ip=IPV4ADDR
>>
>>
>> IPV4ADDR: Your IPv4 endpoint.  Set to AUTO to determine your IP based
>> on the IP you requested this page from.  Previously passed as ipv4b.
>> PASSKEY : Your tunnel update key, or MD5 hash of your
>> tunnelbroker.net password if a tunnel specific key is not set. You
>> may be able to 'echo -n YOURPASSWORD | md5sum' to produce the MD5
>> hash of your password.
>> USERID  : The UserID shown on the main page of tunnelbroker.net when
>> you log in.
>> TUNNELID: The ID of the tunnel you're updating the endpoint on. This
>> can be found on the tunnel information page.  Previously referred to
>> as the Global Tunnel ID / tunnel_id.
>>
>> The following parameters are only usable when accessing this script
>> over https.
>> USERNAME: Your tunnelbroker.net username.
>> PASSWORD: Your tunnel update key, or tunnelbroker.net password if a
>> tunnel specific key is not set.
>>
>> The legacy parameter names will continue to work for the forseable
>> future.  Naming of them changed to be more in line with industry
>> convention and their roles.
>




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

           reply	other threads:[~2014-06-29 19:13 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <53B0652B.2080502@xyz.am>]

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=53B0656E.5070309@imap.cc \
    --to=fredstratton@imap.cc \
    --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