From: Matt Taggart <matt@lackof.org>
To: Dave Taht <dave@taht.net>
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] bcp38 and the caida "spoofer" tool
Date: Mon, 17 Apr 2017 16:40:58 -0700 [thread overview]
Message-ID: <20170417234058.A01E5265@taggart.lackof.org> (raw)
In-Reply-To: <87tw5nt2rd.fsf@nemesis.taht.net>
Dave Taht writes:
> I am curious as to how many here are using the lede/openwrt bcp38 package?
I always install it everywhere since I consider it part of being a good
netizen, even if I think the odds of it getting used are low. So far it's
always just worked, with one exception where I was doing something weird
with rfc1918 ranges, and then I just had to use the luci interface to
adjust.
I've had similar ideas for ways to use openwrt/lede to help protect against
IoT devices participating in botnets. Ideally each time you added an IoT
device to your network, you'd have to go in to luci and approve the device
and what types of things it was allowed to do. Possibly separate ESSIDs for
them? Maybe dedicate one wired port to be sort of an IoT DMZ?
--
Matt Taggart
matt@lackof.org
next prev parent reply other threads:[~2017-04-17 23:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-17 16:31 Dave Taht
2017-04-17 23:40 ` Matt Taggart [this message]
2017-04-28 2:56 ` Aaron Wood
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=20170417234058.A01E5265@taggart.lackof.org \
--to=matt@lackof.org \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave@taht.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