Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Robert Bradley <robert.bradley1@gmail.com>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] cerowrt-3.10.36-4 released
Date: Thu, 10 Apr 2014 16:18:40 +0100	[thread overview]
Message-ID: <5346B650.5040200@gmail.com> (raw)
In-Reply-To: <87sipll0fh.fsf@toke.dk>

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

On 10/04/2014 15:32, Toke Høiland-Jørgensen wrote:
> Robert Bradley <robert.bradley1@gmail.com> writes:
>
>> - I had to add my cable modem configuration address to the BCP38
>> exception list (192.168.100.1).  This gets used for nothing except
>> configuration and checking the modem logs so this is understandable.  I
>> also end up adding a static route anyway since if Internet breaks, I
>> need a route to the modem...
> If you add a 'scope link' route on the wan interface, the BCP38 code
> *should* pick this up automatically and add an exception. Would be cool
> if you could test this :)

Just tested this now and it works fine. :)

>> - dnsmasq's default of dnssec-check-unsigned broke my DNS, since my
>> ISP servers do not support DNSSEC. In that case, everything winds up
>> as failing.
> That's an interesting failure mode. FWIW you can point it at
> 8.8.8.8/8.8.4.4 instead if you want dnssec verification :)

I was tempted to leave it as-is, but tested it now with a custom
/tmp/resolv.conf.manual file and it also works well with added DNSSEC
checks.

-- 
Robert Bradley



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

  reply	other threads:[~2014-04-10 15:19 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-10  6:45 Dave Taht
2014-04-10  6:46 ` Dave Taht
2014-04-10 17:33   ` Dave Taht
2014-04-11 18:25   ` Jim Gettys
2014-04-10 13:48 ` Valdis.Kletnieks
2014-04-10 14:06   ` Robert Bradley
2014-04-10 14:32     ` Toke Høiland-Jørgensen
2014-04-10 15:18       ` Robert Bradley [this message]
2014-04-10 15:21         ` Toke Høiland-Jørgensen
2014-04-10 17:29         ` Dave Taht
2014-04-10 17:57           ` Toke Høiland-Jørgensen
2014-04-10 19:06           ` Sebastian Moeller
2014-04-11 12:34           ` Robert Bradley
2014-04-10 16:40     ` Valdis.Kletnieks
2014-04-10 16:48       ` Toke Høiland-Jørgensen
2014-04-10 16:51         ` Valdis.Kletnieks
2014-04-10 16:54           ` Toke Høiland-Jørgensen
2014-04-10 18:02       ` Sebastian Moeller
2014-04-13  0:22         ` Jim Reisert AD1C
2014-04-13  0:30           ` Sebastian Moeller
2014-04-13  0:44             ` Jim Reisert AD1C
2014-04-10 16:46 ` Jim Gettys
2014-04-10 17:31   ` Dave Taht
2014-04-10 17:35     ` Jim Gettys
2014-04-11  9:50       ` David Personette
2014-04-11 10:43         ` Aaron Wood
2014-04-12 11:45         ` Neil Shepperd
2014-04-12 19:04           ` Dave Taht
     [not found] ` <CANp2as81TR_kCR8a_sZs045tXFGADL1W4CFtNEJiJrjutmL7cg@mail.gmail.com>
2014-04-11 16:31   ` 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=5346B650.5040200@gmail.com \
    --to=robert.bradley1@gmail.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=toke@toke.dk \
    /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