From: Jonathan Morton <chromatix99@gmail.com>
To: David Lang <david@lang.hm>
Cc: "Dave Täht" <dave@taht.net>,
cake@lists.bufferbloat.net, cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cake] conntrack and ipv6
Date: Sun, 3 Jul 2016 10:44:06 +0300 [thread overview]
Message-ID: <A68C2D91-5D07-4242-BA86-44867F1FD685@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1607022314230.18304@nftneq.ynat.uz>
> On 3 Jul, 2016, at 09:16, David Lang <david@lang.hm> wrote:
>
>> It is generally my hope that ipv6 nat will not be widely deployed.
>>
>> Firewalls will be stateful instead, and thus there would be no need to
>> access the conntrack information for ipv6 in cake.
>
> well, conntrack is the way that the firewall handles it's state. Conntrack also has features to let you sync it's state from one system to it's backup so that failover maintains the state.
Yes, but the point is that in a stateful firewall (as opposed to NAT) no changes to IP addresses occur while traversing the router. Cake can therefore see the correct addresses without probing conntrack data.
There's still a huge number of people on IPv4 NAT though.
- Jonathan Morton
next prev parent reply other threads:[~2016-07-03 7:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-02 11:09 [Cake] flow dissector idea/enhancement - help Kevin Darbyshire-Bryant
2016-06-02 12:29 ` Jonathan Morton
2016-06-30 9:33 ` Kevin Darbyshire-Bryant
2016-06-30 10:27 ` Jonathan Morton
2016-06-30 19:23 ` Kevin Darbyshire-Bryant
2016-07-01 8:11 ` Kevin Darbyshire-Bryant
2016-07-01 15:38 ` Kevin Darbyshire-Bryant
2016-07-02 12:47 ` [Cake] conntrack and ipv6 Dave Täht
2016-07-02 13:00 ` moeller0
2016-07-03 6:16 ` David Lang
2016-07-03 7:44 ` Jonathan Morton [this message]
2016-07-03 21:12 ` [Cake] [Cerowrt-devel] " moeller0
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/cake.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=A68C2D91-5D07-4242-BA86-44867F1FD685@gmail.com \
--to=chromatix99@gmail.com \
--cc=cake@lists.bufferbloat.net \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave@taht.net \
--cc=david@lang.hm \
/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