From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: Dave Taht <dave.taht@gmail.com>
Cc: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] BCP38 implementation
Date: Thu, 20 Mar 2014 19:14:29 +0100 [thread overview]
Message-ID: <ebc72f39-f1d5-4656-82d8-5ff36e183e5d@email.android.com> (raw)
In-Reply-To: <CAA93jw5=TppxOGegDZj+xn1uWmY=k-GW0MDxrCFmkWoKv4X_aA@mail.gmail.com>
On 20 March 2014 18:38:17 CET, Dave Taht <dave.taht@gmail.com> wrote:
> I have tested this, made one small modification, and it will be in
> cerowrt-3.10.32-12 and on by default. Nice work!
Thanks! :)
> One possible problem with pushing this up to openwrt is that arguably
> it needs to apply this to the "wan" abstraction in the firewall rules
> rather than a specific interface, and hook into that chain instead.
> (on the other hand, using an actual interface is also good)
Well, having the configuration option be for a firewall zone rather than an interface shouldn't be that difficult. More of a policy question of how to handle upstream detection etc for potentially multiple interfaces. But then I suppose having the option of adding the filter to multiple interfaces might be useful too...
Either way, I can look into it at some later date if it becomes an issue. :)
> The ipset facility has great potential for other uses, for example:
Yeah, it seems to be pretty cool. How is it related to nftables?
-Toke
next prev parent reply other threads:[~2014-03-20 18:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-19 20:59 Toke Høiland-Jørgensen
2014-03-19 21:44 ` Dave Taht
2014-03-19 22:31 ` Toke Høiland-Jørgensen
2014-03-20 9:29 ` Toke Høiland-Jørgensen
2014-03-20 13:07 ` Toke Høiland-Jørgensen
2014-03-20 17:38 ` Dave Taht
2014-03-20 18:14 ` Toke Høiland-Jørgensen [this message]
2014-03-22 20:04 ` Norman Yarvin
[not found] ` <532AB801.6050702@openwrt.org>
2014-03-20 10:28 ` Toke Høiland-Jørgensen
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=ebc72f39-f1d5-4656-82d8-5ff36e183e5d@email.android.com \
--to=toke@toke.dk \
--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