Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Marc Petit-Huguenin <marc@petit-huguenin.org>
To: Dave Taht <dave.taht@gmail.com>
Cc: "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] [Dnsmasq-discuss]  DNSSEC and www.ietf.org
Date: Sat, 11 Apr 2015 09:03:15 -0600	[thread overview]
Message-ID: <552937B3.10008@petit-huguenin.org> (raw)
In-Reply-To: <CAA93jw40JmFXUcDLAeFEioUi+5zuO=UBiBucQmN3a_i-5bbE5A@mail.gmail.com>

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

On 03/30/2015 12:42 PM, Dave Taht wrote:
> for cerowrt-3.10? Really wasn't planning on it. Didn't even know there
> was a problem til today...

So I suppose that means that Cerowrt is now unmaintained and that I should switch to something else, because my job requires near constant access to www.ietf.org and I will not disable DNSSEC.

So, what would you recommend for my WNDR3800?

Thanks.

> 
> for my current openwrt builds - you betcha. thursday-ish.
> 
> On Mon, Mar 30, 2015 at 11:17 AM, Marc Petit-Huguenin
> <marc@petit-huguenin.org> wrote:
>> On 03/30/2015 11:49 AM, Simon Kelley wrote:
>>> Dnsmasq bug, should be fixed in 2.73rc3 pls shout if not.
>>>
>>> (the problem is that the clouldflare.bet zone includes the domains
>>> /003.cloudflare.net (that's ctrl-c at the start) and that was
>>> confusing dnsmasq.)
>>
>> Thanks.
>>
>> Dave, any chance to get a build of 2.73rc3?
>>
>>>
>>> Simon.
>>>
>>>
>>>
>>> On 30/03/15 16:58, Dave Taht wrote:
>>>> I have trouble accessing ietf.org, also, with older versions of
>>>> dnsmasq + dnssec, presently.
>>>
>>>> On Mon, Mar 30, 2015 at 8:52 AM, Marc Petit-Huguenin
>>>> <marc@petit-huguenin.org> wrote:
>>>>> Am I the only one who cannot access www.ietf.org since Cloudflare
>>>>> enabled DNSSEC? (with dnsmasq-full 2.73-3)
>>>>>
>>>>> Thanks.
>>>>>

-- 
Marc Petit-Huguenin
Email: marc@petit-huguenin.org
Blog: http://blog.marc.petit-huguenin.org
Profile: http://www.linkedin.com/in/petithug


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2015-04-11 15:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-30 15:52 [Cerowrt-devel] " Marc Petit-Huguenin
2015-03-30 15:58 ` Dave Taht
2015-03-30 16:19   ` David Personette
2015-03-30 17:49   ` [Cerowrt-devel] [Dnsmasq-discuss] " Simon Kelley
2015-03-30 18:17     ` Marc Petit-Huguenin
2015-03-30 18:42       ` Dave Taht
2015-04-11 15:03         ` Marc Petit-Huguenin [this message]
2015-04-11 16:32           ` Kevin Darbyshire-Bryant
2015-04-11 16:49             ` Dave Taht
2015-04-11 19:13               ` Kevin Darbyshire-Bryant
2015-04-13 14:02             ` Marc Petit-Huguenin
2015-04-11 16:38           ` Dave Taht

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=552937B3.10008@petit-huguenin.org \
    --to=marc@petit-huguenin.org \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=dave.taht@gmail.com \
    /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