Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: cerowrt-devel@lists.bufferbloat.net
Subject: [Cerowrt-devel] cerowrt-3.3.0-1 not worth using unless you want to help fix bug 113
Date: Mon, 19 Mar 2012 00:39:54 -0700	[thread overview]
Message-ID: <CAA93jw5vW8JVwTnx-ywjv5UbRWYVUdS1ZcrEDnp6EmOki5PepQ@mail.gmail.com> (raw)

I have had everybody hit bug 113 in the last month.

and as we are coming up on the 1 year anniversary of this bug, with no
resolution, I decided to try and fix it again,
by adding in the dnssec-tools patch to ntp.

Now, with that patch... ntp is doing it's own validation... and failing that,

and although it is supposed to try again with validation disabled, it
isn't, so we NEVER get time.

Mar 19 02:38:09 OpenWrt daemon.err ntpd[4205]: select() error:
Resource temporarily unavailable
Mar 19 02:38:10 OpenWrt daemon.err ntpd[4205]: select() error:
Resource temporarily unavailable
Mar 19 02:38:10 OpenWrt daemon.info ntpd[4205]: DNS response for
2.openwrt.pool.ntp.org failed validation

three steps backward, totally unusable dnssec, name service, and ntp.

We need to tear apart the patch this is keyed to, build it on a normal
x86 box, make it work, and try again.

I like the idea of dnssec, but boy, I hate this bug. Can I get a
volunteer not as scarred as I on this front
to pull down the ntp patch, and make it not fail?

https://github.com/dtaht/ceropackages/tree/master/net/ntpd

-- 
Dave Täht
SKYPE: davetaht
US Tel: 1-239-829-5608
http://www.bufferbloat.net

                 reply	other threads:[~2012-03-19  7:39 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

  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=CAA93jw5vW8JVwTnx-ywjv5UbRWYVUdS1ZcrEDnp6EmOki5PepQ@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