Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] ipsets in openwrt issues
Date: Wed, 15 Jan 2014 15:06:33 -0500	[thread overview]
Message-ID: <CAA93jw690dG9stSre089A=6243ZqtJgSmunBvqBF0PYj_zt47w@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw5cZmpULJi=sykaiQ_7TJvKxLijmqWxLAMq9EbUCm1Jzg@mail.gmail.com>

On Wed, Jan 15, 2014 at 2:46 PM, Dave Taht <dave.taht@gmail.com> wrote:
> I thought ipset had sprouted full ipv6 support a while back
>
> which would make for simpler rules like this
>
> ipset create egress-ipv4 hash:net
>
> ipset add egress-ipv4 127.0.0.0/8
> ipset add egress-ipv4 192.168.0.0/16
> ipset add egress-ipv4 10.0.0.0/8
> ipset add egress-ipv4 172.16.0.0/12
> ipset add egress-ipv4 169.254.0.0/16
>
> where you could do something like add the external
> network on a double natted situation easily, on
> bringing up the external interface.
>
> ipset add egress-ipv4 10.0.1.0/24 nomatch
>
> but no ipv6 in my build although the doc claims
> it exists.
>
> ipset create family inet6 egress-ipv6
> ipset add egress-ipv6 fd::/10
>
> reading source....

problem between eyes and keyboard...

ipset create egress-ipv6 hash:net family inet6
ipset add egress-ipv6 fc::/10 # 8? 12? 11? what
... don't know what exact ipv6 addresses to block escaping out

>
>
> --
> Dave Täht
>
> Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html



-- 
Dave Täht

Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html

      reply	other threads:[~2014-01-15 20:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-15 19:46 Dave Taht
2014-01-15 20:06 ` Dave Taht [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='CAA93jw690dG9stSre089A=6243ZqtJgSmunBvqBF0PYj_zt47w@mail.gmail.com' \
    --to=dave.taht@gmail.com \
    --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