From: Chuck Anderson <cra@WPI.EDU>
To: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] cerowrt-3.10.32-1 dev build NOT released due to 5ghz wifi issues
Date: Sun, 23 Feb 2014 19:43:21 -0500 [thread overview]
Message-ID: <20140224004320.GA4253@angus.ind.WPI.EDU> (raw)
In-Reply-To: <CAA93jw7i=o0T1V=equ0EZ=+DE0XwR2XvyG7dHR9j8xuqx=aRQA@mail.gmail.com>
On Sun, Feb 23, 2014 at 07:05:25PM -0500, Dave Taht wrote:
> - no bcp38 still (help?)
Can you explain exactly what you are trying to do with the bcp38 stuff
and what makes it so complicated? I would think you just need to drop
all packets with source addresses that are not contained in locally
configured subnets?
prev parent reply other threads:[~2014-02-24 0:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-24 0:05 Dave Taht
2014-02-24 0:43 ` Chuck Anderson [this message]
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=20140224004320.GA4253@angus.ind.WPI.EDU \
--to=cra@wpi.edu \
--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